All authors
Claude Skills by shrwnsan
github.com/shrwnsan58 skills1 installs106 views
- CaptureUse to log something from the current conversation into the user's haku memory — a decision just made, a win that surfaced, a stakeholder observation, a self-insight. Triggers: "log this", "capture this", "save that decision", "remember this", or a substantive conversation just concluded. Distinct from decision-log / wins-log / stakeholder-reflect / self-reflect invoked directly: drafts FROM the conversation, files after approval.Votes: 0GitHub stars: 7
- Decision LogUse when the user makes or revisits a meaningful product, technical, or organizational decision and wants it captured ADR-style. Triggers: "we decided to…", "let's go with X over Y", "write up the call we made on…", or reconstructing a past decision. Especially AI-product decisions — model choice, eval threshold, fallback design — whose rationale is easy to lose.Votes: 0GitHub stars: 7
- DoctorUse to health-check the user's haku memory directory — validate file layout, catch problems before they cost data. Triggers: "run haku doctor", "check my reflection files", "is my data okay", "back up my reflections", "I'm moving to a new machine". Validates ~/haku-work-reflections/ (or $HAKU_WORK_REFLECTIONS_HOME): registry integrity, orphaned files, layout drift, backup status, legacy bettersense-path migration. Read-only; proposes fixes, applies with approval.Votes: 0GitHub stars: 7
- StartUse when the user is new to haku and doesn't know where to begin, or wants a tour of what's available. Triggers: "where do I start", "how do I use this", "what can you do", "what should I run first", "I just installed this", "what is haku". Entry point for new users; branches into first-time setup or direct routing.Votes: 0GitHub stars: 7
- Strategy DocUse to create or update a product/area strategy document — target problem, approach, personas, 3-5 SMART metrics, 2-4 strategic tracks, explicit not-working-on section. Triggers: "draft a strategy doc for [area]", "I need a strategy.md for the platform team", "interview me about my strategy". Lives at ~/haku-work-reflections/strategy/<area-slug>.md; anchor read by the-spec-writer, prioritization-frameworks, metrics-design, product-pulse, pulse-synthesize.Votes: 0GitHub stars: 7
- User ProfileUse to create or update the user's anchor profile — one private file (~/haku-work-reflections/profile.md) capturing who they are and the context other skills need. Read automatically by other skills when present, so the user doesn't re-explain themselves every session. Triggers: "set up my profile", "update my profile", "I changed roles, refresh my profile". Explain yourself once, get tailored output forever.Votes: 0GitHub stars: 7
- WeeklyUse for the user's weekly review ritual — one ~15-minute guided session wrapping the haku maintenance loop. Triggers: "run my weekly review", "Friday review", "weekly check-in", "/haku:weekly", "catch up on the week". Composes wins-due, stakeholder-due, stakeholder-reflect, patterns-watch into four time-boxed segments: wins capture, stakeholder reflection, patterns, pulse glance. Prefer this for the ritual; individual skills for one piece.Votes: 0GitHub stars: 7
- Wins LogUse when the user wants to capture a "win at work" — something shipped, judgment exercised, someone mentored, a fire put out. Triggers: "I just shipped X", "log this win", "add to my brag doc", "I had a good week". Captures structured entries (situation, action, impact, evidence) to ~/haku-work-reflections/wins.md for later remix by wins-curate into promo packets, interview stories, perf self-evals.Votes: 0GitHub stars: 7