Tools & Automation

CLI tools, utilities, converters, workflow automation, and productivity helpers

skills in category: 47,645
pages available: 1,986

Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.

Open in full browser

Browse tools & automation skills

Showing 7,561–7,584 of 47,645 skills

Team LifecycleAUse 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.toolsrustgoVotes: 0GitHub stars: 7
Team DiagnosisAUse 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.toolsrustgoVotes: 0GitHub stars: 7
Team Close GapAUse 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`.toolsgoperformanceVotes: 0GitHub stars: 7
Team CharterAUse 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.toolsgoperformanceVotes: 0GitHub stars: 7
Stakeholder SynthesizeAUse 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 entriestoolsgoapiVotes: 0GitHub stars: 7
Stakeholder RegisterAUse 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`.toolsgogitVotes: 0GitHub stars: 7
Skills DirectorySkills Directory Pro Download any skill as a ZIP for Claude.ai, Claude Desktop, or .claude/skills.See Pro
Stakeholder ReflectAUse 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.toolsgoVotes: 0GitHub stars: 7
Stakeholder ManageAUse 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).toolsgoVotes: 0GitHub stars: 7
Stakeholder DueAUse 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.toolsgoVotes: 0GitHub stars: 7
Wins DueAUse 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".toolsgoVotes: 0GitHub stars: 7
Wins CurateAUse 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.toolsgoperformanceVotes: 0GitHub stars: 7
Visibility SponsorshipAUse 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).toolsgoVotes: 0GitHub stars: 7
Self ReflectAUse 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.toolsgoperformanceVotes: 0GitHub stars: 7
Report Promo CaseAUse 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.toolsrustVotes: 0GitHub stars: 7
Promo Case GlueAUse 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`.toolsgodocumentationVotes: 0GitHub stars: 7
Performance ManagementAUse 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.toolsgoperformanceVotes: 0GitHub stars: 7
CommitmentsAUse 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).toolsrustgoVotes: 0GitHub stars: 7
Coaching ModeAUse 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.toolsrustgoVotes: 0GitHub stars: 7
Tech Strategy WriterAUse 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.toolsrustgoVotes: 0GitHub stars: 7
Prioritization FrameworksAUse 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.toolsgoexpressVotes: 0GitHub stars: 7
PremortemAUse 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.toolsgoVotes: 0GitHub stars: 7
Patterns WatchAUse 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.toolsgoVotes: 0GitHub stars: 7
Metrics DesignAUse 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.toolsrustgoVotes: 0GitHub stars: 7
Impact AuditAUse 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.toolsgoexpressVotes: 0GitHub stars: 7