Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From hstack
Use when coaching technical leaders on conflict, burnout, cofounders, CTO transitions, or growth.
How this skill is triggered — by the user, by Claude, or both
Slash command
/hstack:executive-coachingThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use for coaching technical leaders through conflict, growth, burnout, cofounder dynamics, and CTO transition planning.
Use for coaching technical leaders through conflict, growth, burnout, cofounder dynamics, and CTO transition planning.
Coach when the person has context and can solve the problem. Advise when urgent, when they lack context, or when you have a specific answer. Ask: "Do you want advice, or space to think it through?"
Listen for content, emotion, and context. Use GROW questions: goal, reality, options, way forward. Keep ownership with the coachee and end with a concrete next step.
Use NVC for conflict: observation, feeling, need, request. Stay factual, avoid blame, and ask how the person may be contributing to the pattern.
Look for chronic depletion, not just workload. Track energizing and draining work, name strengths, and redesign toward more high-energy work.
Load CTO, stakeholder, goal, cofounder, or assessment references only when the user asks for that specific depth.
npx claudepluginhub leehanchung/hstack --plugin hstackGuides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
Guides reception of code review feedback: verify before implementing, avoid performative agreement, push back with technical reasoning when needed.
Forks private projects, strips secrets/internal references, verifies cleanliness, and packages them with CLAUDE.md, README, and setup.sh for safe public release.