All authors
Claude Skills by shrwnsan
github.com/shrwnsan58 skills1 installs106 views
- Crafting CommitsAutomatically invoked when user requests git commit message creation, commit drafting, or needs help with conventional commit formatting. Use for phrases like "help me commit", "draft a commit message", "create a proper commit", "write commit message for [changes]", "I need to commit these changes". Handles conventional commit standards.Votes: 0GitHub stars: 7
- Plans<!-- Version: 0.5.0 | Status: COMPLETE | Updated: 2026-04-09 -->Votes: 0GitHub stars: 7
- Branch HygieneClassify and clean up merged, stale, and orphaned git branches and worktrees. Detects squash-merges that git branch --merged cannot see, stale worktrees, and remote-gone branches. Use when user asks to clean up branches, prune worktrees, tidy the repo, or perform git housekeeping.Votes: 0GitHub stars: 7
- Handoff ContextDetects natural language handoff requests and generates structured context summaries for seamless thread continuation. Use when user says "handoff", "new thread", "continue in fresh thread", or similar phrases.Votes: 0GitHub stars: 7
- Systematic DebuggingSystematic debugging approach for errors, test failures, and unexpected behavior. Use when encountering bugs, test failures, errors, or when debugging is needed. Prevents common anti-patterns like random fixes, skipping root cause analysis, and thrashing.Votes: 0GitHub stars: 7
- Meta SearchRecovers web content when searches fail with 403, 429, 422 errors, blocked sites, or empty results. Runs a bundled multi-provider script (works without API keys), then falls back to manual strategies.Votes: 0GitHub stars: 7
- Demo PrepUse when the user is preparing for a demo — exec review, customer pitch, board update, investor meeting, sales call, or all-hands. Trigger phrases include "I'm demoing X tomorrow", "help me prep for the review", "what could go wrong in this demo?". Especially valuable for AI-feature demos, where probabilistic systems can fail in ways scripted demos can't predict.Votes: 0GitHub stars: 7
- Exec Readout PrepUse when the user needs a decision from executives and is preparing the meeting or memo that gets it — QBRs, roadmap reviews, headcount asks, investment pitches. Trigger phrases include "prep my exec readout", "I'm presenting to leadership", "I need sign-off from the VP", "help me get this decision approved". Distinct from demo-prep (performing a product) and the-status-crafter (recurring update rhythm).Votes: 0GitHub stars: 7
- Product PulseUse to produce a single-page dated pulse report on product health — usage metrics, AI-feature signals (hallucination, refusal, eval drift), counter-metrics, follow-ups. Trigger phrases include "run a pulse on [area]", "give me a product health snapshot", "weekly product pulse", "what does the data say this week". Saves to `~/haku-work-reflections/pulses/<area-slug>/pulse-YYYY-MM-DD.md`. Desktop scheduled tasks only — cloud routines cannot read local files.Votes: 0GitHub stars: 7
- Pulse SynthesizeUse to derive trends, anomalies, inflection points, and regime shifts across accumulated product-pulse reports. Trigger phrases include "what's been the pattern across pulses this quarter", "synthesize my product pulses for [area] over the last 8 weeks", "before my exec readout, what does the data say across the period", "is anything trending that I missed week to week". Reads `~/haku-work-reflections/pulses/<area-slug>/`.Votes: 0GitHub stars: 7
- Read The RoomUse for retrospective subtext reads on meetings, reviews, Slack threads, or 1:1s. Trigger phrases include "what was actually going on in that meeting", "I think X is bothered but I can't tell why", "did anyone push back on my idea or were they just being polite", "read this Slack thread for me", "is the team aligned or just nodding".Votes: 0GitHub stars: 7
- Engineering HealthUse when an EM wants to assess engineering systems and processes—not team morale (that's team-diagnosis): measurement, developer experience, onboarding friction, and platform investment. Trigger phrases include "is my team actually productive", "I want to understand developer experience on my team", "how do I measure engineering productivity", "I need to justify platform team investment", "our onboarding is too slow".Votes: 0GitHub stars: 7
- Glue AuditUse when the user wants to systematically identify, categorize, and quantify "glue work" on themselves or their team. Trigger phrases include "what glue work am I doing", "audit my glue work", "what non-promotable work is our team doing", "catalog our glue tasks", "how much time do we spend on glue", "map our glue work".Votes: 0GitHub stars: 7
- Impact AuditUse when a PM or team stress-tests whether work connects to business outcomes—"are we even pointed at the right thing?"—before strategy-doc or prioritization-frameworks. Trigger phrases include "are we doing the right work?", "I'm worried my team isn't driving real impact", "help me check if my team is aligned", "I'm worried about layoffs", or any doubt the work would survive scrutiny.Votes: 0GitHub stars: 7
- Leadership OsUse when the user is navigating people/leadership situations as a PM — managing up to executives, managing down to a team, cross-functional conflict, 1:1s, performance reviews, post-mortems, incident response, roadmap negotiation, or stakeholder communication. Trigger when the question is about *how to handle a person or situation*, not about code or product mechanics.Votes: 0GitHub stars: 7
- Manage Glue WorkersUse when managing engineers who gravitate toward glue work (onboarding, documentation, unblocking) and need burnout protection, visibility, and career development that doesn't force them off the IC track. Trigger phrases include "my report does too much glue", "how do I protect my glue person", "glue worker promotion", "coaching someone who's always helping others", "my engineer is drowning in non-promotable work".Votes: 0GitHub stars: 7
- Metrics DesignUse when the user is designing the metric tree for a feature (especially an AI feature)—north star, leading and lagging indicators, quality metrics, counter-metrics. Trigger phrases include "what should we measure for…", "how do we know if this is working?", "I need to define success for…". Distinct from `the-eval-designer`, which measures model quality; this measures business success.Votes: 0GitHub stars: 7
- Patterns WatchUse to surface unsolicited patterns across stakeholder reflections, wins log, and self-reflect entries. Trigger phrases include "what patterns am I missing", "anything notable across my files", "scan my reflections for things I should know", "weekly cross-cutting check". Distinct from `stakeholder-synthesize` (user-driven, one person/category)—this is unsolicited and cross-cutting; every claim cites dated entries.Votes: 0GitHub stars: 7
- PremortemUse for pre-mortem analysis of decisions, projects, or initiatives—solo or facilitated with a team before a launch or strategic commitment. Trigger when the user says "what could go wrong", "risk assessment", "pre-mortem this", "let's run a pre-mortem", or when evaluating risks for a plan. Three-category framework (Critical, Perceived, Undiscussed risks); team sessions end in an action plan with owners.Votes: 0GitHub stars: 7
- Prioritization FrameworksUse when the user is prioritizing a backlog, building a roadmap, cutting scope, or arguing about what to build next. Trigger phrases include "what should we build first?", "help me cut this list", "I need to defend my roadmap", "should we do X or Y?". Surfaces the right framework—RICE, ICE, WSJF, MoSCoW, Kano, Cost of Delay.Votes: 0GitHub stars: 7
- Tech Strategy WriterUse when a senior IC (staff/principal, architect, tech lead) writes a technical strategy or direction doc. Trigger phrases include "write a tech strategy for [domain]", "I need a technical direction doc", "our platform needs a north star doc", "help me write the tech vision for [area]". Distinct from strategy-doc (product/business peer) and the-rfc-reviewer (one proposal). Saves to strategy/tech-<area>.md.Votes: 0GitHub stars: 7
- Career RetroUse for a quarterly/annual career retrospective across the haku memory; cited growth deltas vs. last retro, written to self/retros/. Trigger phrases include "run my career retro", "where am I in my career", "annual self-assessment", "how have I grown this year", "it's review season, take stock of everything". Distinct from wins-curate (audience-facing artifacts) and self-reflect (single entries).Votes: 0GitHub stars: 7
- Coaching ModeUse when coaching a report, peer, or mentee through a problem rather than solving it for them. Trigger phrases include "coach me through how to talk to [report]", "I want to help [name] figure out X without telling them what to do", "let me practice a coaching conversation", "GROW conversation about [topic]". Ask-not-tell mode using the GROW frame.Votes: 0GitHub stars: 7
- CommitmentsUse to track promises in ~/haku-work-reflections/commitments.md and keep them from going stale. Trigger phrases include "what have I committed to", "add a commitment", "I promised X by Friday", "am I overcommitted", "help me say no to this", "I need to renegotiate a deadline". Renegotiate early; pressure-test new asks. Distinct from wins-log (what you did vs. what you owe).Votes: 0GitHub stars: 7
- Feedback FrameworksUse when the user is preparing to give feedback to a teammate, direct report, peer, or stakeholder — performance reviews, 1:1 prep, post-incident conversations, peer reviews, 360s, written async feedback, or any moment they're drafting "how do I tell them that…". Apply the COIN structure to compose the message and the SOLID checklist to pressure-test it before delivery.Votes: 0GitHub stars: 7
- Hiring CraftUse when designing interview loops, writing interview questions or rubrics, calibrating panel feedback, running hiring debriefs, or making a hire/no-hire call. Trigger phrases include "design an interview loop for [role]", "write interview questions for [signal]", "help me run the debrief", "should we hire X", "I need a rubric for the system design round".Votes: 0GitHub stars: 7
- Influence Without AuthorityUse when moving outcomes without authority. Trigger phrases include "how do I get [team] to do X without going to their manager", "I need to convince [person] to support this", "I have to push back on [exec] without burning the relationship", "build the coalition", "I'm a TPM/staff eng/IC and I need [team] to prioritize this". Distinct from feedback-frameworks and coaching-mode.Votes: 0GitHub stars: 7
- One On One PrepUse when preparing for a 1:1 — manager with a report, IC with their manager, or peer sync. Trigger phrases include "I have a 1:1 with X tomorrow", "help me prep for my 1:1", "what should I bring up in my next 1:1?". Builds a relationship-matched agenda; if the other person is a registered stakeholder, reads their reflection file first.Votes: 0GitHub stars: 7
- Performance ManagementUse when dealing with underperformance, considering a PIP, navigating a brilliant-jerk pattern, documenting concerns, or preparing a hard performance conversation. Trigger phrases include "I have a report who's underperforming", "should I PIP X", "I need to document this", "how do I have the hard conversation", "I'm worried about [report]'s trajectory". Guides the ladder: coaching, formal feedback, improvement plan, termination.Votes: 0GitHub stars: 7
- Promo Case GlueUse when a glue-heavy engineer needs a promo packet framing it as technical leadership. Trigger phrases include "promotion case for glue work", "I do a lot of glue work how do I get promoted", "frame my non-code work for promotion", "my manager says I need more technical accomplishments", "I'm a glue person how do I get senior". Mode of `report-promo-case`.Votes: 0GitHub stars: 7
- Report Career ArchitectUse when designing or revisiting a 12–18 month growth plan for a direct report. Trigger phrases include "build a growth plan for [report]", "what should [name]'s next year look like", "I want to architect [report]'s path to senior", "I'm prepping for promo cycle and [report] needs a plan", "let's think about [report]'s development". Distinct from one-on-one-prep and coaching-mode.Votes: 0GitHub stars: 7
- Report Promo CaseUse when building a promotion case for a direct report — internal promo packet, panel write-up, or calibration-committee one-pager. Trigger phrases include "build the promo case for [report]", "I'm submitting [name] for staff this cycle", "draft [report]'s promo packet", "help me make the case for [name]'s promotion". Mirror of wins-curate; reads stakeholder-reflect entries and growth plans; produces a cited, calibrated packet.Votes: 0GitHub stars: 7
- Self ReflectUse when the user wants to reflect on themselves as a leader — behavior under pressure, communication, time and energy, fulfillment, advocating for themselves. Trigger phrases include "let me reflect on myself", "self-check", "I want to think about how I've been leading lately", "self-reflection". Loads `~/haku-work-reflections/self/reflections.md`, picks 1–3 fitting questions, writes the dated entry back. Mirrors `stakeholder-reflect` for the user.Votes: 0GitHub stars: 7
- Visibility SponsorshipUse when work outpaces its visibility; build sponsor awareness before promo/calibration. Trigger phrases include "nobody knows what I do", "how do I get more visibility", "I need a sponsor", "my work speaks for itself but nobody's listening", "I was passed over because people don't know me", "how do I self-promote without being obnoxious". Distinct from wins-curate (formal packets).Votes: 0GitHub stars: 7
- Wins CurateUse to turn the wins log into an audience-specific artifact — promo packet, behavioral interview stories (STAR), perf-review self-eval, salary case, or year-in-review. Trigger phrases include "build my promo packet", "I have a behavioral interview Tuesday", "draft my self-eval for the perf review", "make a case for a raise", "year in review for me". Reads `~/haku-work-reflections/wins.md`; never invents wins.Votes: 0GitHub stars: 7
- Wins DueUse for a low-pressure nudge on whether anything from the recent week is worth logging. Weekly Desktop scheduled task friendly (never cloud routines); probes by category. Trigger phrases include "what should I log this week", "is anything missing from my wins doc", "did I do anything notable this week", "Friday wins check".Votes: 0GitHub stars: 7
- Stakeholder DueUse when the user wants to know which stakeholder reflections are overdue — "what's due", "who haven't I thought about lately", "what's on my plate this week for stakeholder reflection", "stakeholder check-in", Monday-morning planning. Scans `~/haku-work-reflections/`, computes overdue question × stakeholder pairs from `suggested_freq`, outputs a prioritized list. Weekly Desktop task OK; cloud routines can't read local files.Votes: 0GitHub stars: 7
- Stakeholder ManageUse when changing a registered stakeholder — list, edit role/background, re-categorize, rename, archive, or delete. Triggers include "list my stakeholders", "show all my reports", "Jill is my manager now", "move Jill to managing-up", "Draymond left the company", "archive [name]", "Jill changed her name to [...]", "update [name]'s role", "delete [name] — registered by mistake". Distinct from `stakeholder-register` (add).Votes: 0GitHub stars: 7
- Stakeholder ReflectUse when reflecting on a registered stakeholder — manager, peer, report, or team — capturing insight to a durable file. Triggers include "let me reflect on John", "I want to think through my 1:1 with Jill", "log my thoughts on the Client Delivery ABC team", "reflect on [name]". Picks 1–3 questions by cadence/recency, guides reflection, writes dated entries back.Votes: 0GitHub stars: 7
- Stakeholder RegisterUse when the user wants to register a new stakeholder for ongoing reflection — manager, peer, direct report, or team. Triggers include "add a new stakeholder", "register Jill in managing-across", "I just got a new manager", "I'm now leading the X team", "let me set up reflection for [name]". Creates a persistent file at `~/haku-work-reflections/<category>/<slug>.md` used by `stakeholder-reflect`, `stakeholder-due`, and `stakeholder-synthesize`.Votes: 0GitHub stars: 7
- Stakeholder SynthesizeUse when deriving insight across stakeholder reflections — patterns, trends, contradictions, blind spots. Triggers: "how is my managing-up overall", "summarize what I've learned about Jill this quarter", "before my performance review, what do I know about my reports", "what patterns do I see across my team leads", "give me a read on the Client Delivery ABC team". Claims cite dated entriesVotes: 0GitHub stars: 7
- Psychological SafetyUse when a team lacks psychological safety — members don't speak up, withhold concerns, or fear making mistakes. Triggers include "build psychological safety", "team is afraid to speak up", "create safe environment", "people are withholding their opinions", "no one challenges decisions", "fear-based culture". Prescriptive practices from Amy Edmondson's research — not just diagnostic like `team-diagnosis`, but what to do this week.Votes: 0GitHub stars: 7
- Team CharterUse when forming a new team, resetting after a reorg, or when a team's goals/roles/norms are unclear and causing friction. Triggers include "create a team charter", "align our team on goals roles norms", "reset the team operating model", "new team kickoff", "team alignment workshop". Facilitates explicit conversation on Moussa's 3X3 foundations (Goals, Roles, Norms); produces a living charter at ~/haku-work-reflections/team-charters/<team-slug>.md.Votes: 0GitHub stars: 7
- Team Check InUse when a team must revisit their Goals/Roles/Norms foundation to surface drift and realign. Triggers include "team check-in", "are we still aligned", "team retro on our operating model", "review our team charter", "3X3 check-in". Structured conversation (30–90 min): still committed to our goals/roles/norms — if not, what's the gap? Second step of Moussa's 3X3. Works from a charter or de novo.Votes: 0GitHub stars: 7
- Team Close GapUse when a team has identified a gap between stated goals/roles/norms and actual behavior and needs small-step action plans to close it. Triggers include "close the saying-doing gap", "how do we actually change our behavior", "action plan for team norm change", "small steps to improve team work", "bridge the intention-behavior gap". Third step of Moussa's 3X3; follows `team-check-in` or `team-charter`.Votes: 0GitHub stars: 7
- Team DiagnosisUse when the user wants a structured read on their team's *health*, beyond individual morale. Triggers: "how is my team doing", "I want a team health check", "diagnose my team", "before my skip-level update, what should I flag", "is something off with the team that I'm missing". Reads stakeholder-reflect entries + team file; outputs patterns, risks, actions.Votes: 0GitHub stars: 7
- Team LifecycleUse when a team is transitioning — forming, storming, norming, performing, adjourning — or resetting after a reorg, new member, or a stuck team. Triggers: "our team is changing", "new team member joining", "team reorg transition", "how do we reset our team", "team dissolving", "adjourning a team". Tuckman's model with practical per-phase guidance. Complements team-charter, team-check-in, stakeholder-manage.Votes: 0GitHub stars: 7
- Team Style InventoryUse when a team wants to understand their collective working style preferences — communication, decisions, conflict, meetings, information sharing. Triggers: "team work style assessment", "how does our team prefer to work together", "team style inventory", "understand our team dynamics", "communication preferences survey". From Moussa's "how you talk to each other" insight; produces a Team Style Profile and norm adjustments.Votes: 0GitHub stars: 7
- Team WorkspaceSet up or work with a git-backed team workspace for co-owned artifacts — charters, strategy docs, decision records — separate from private reflections. Triggers: "share our team charter with the team", "set up a shared haku workspace", "put our strategy doc in the team repo", "how do teams use haku together". Establishes `$HAKU_TEAM_HOME`; enforces the privacy wall; drafts PRs but never pushes.Votes: 0GitHub stars: 7
- Workload EquityUse when the user wants to analyze whether non-promotable (glue) work is fairly distributed across their team, with attention to demographic patterns. Triggers: "is our glue work fair", "who does the non-promotable work on our team", "audit workload distribution", "are women doing more glue work", "workload equity analysis", "non-promotable work allocation". Produces a diagnosis with bias signals and redistribution recommendationsVotes: 0GitHub stars: 7