Claude Skills by shwetank

Use when scoping AI features, deciding build-vs-buy-vs-rule, designing eval harnesses, choosing models for cost/latency trade-offs, or planning guardrails for LLM-based products. Trigger when the user is doing AI product management work — feasibility, architecture, or reliability decisions for probabilistic systems.

Use when the user wants to coach someone — a report, peer, or mentee — through a problem rather than solve 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]". Flips the assistant into ask-not-tell mode: stays in question-mode for at least 5 turns, refuses to prescribe early, applies the GROW frame (Goal / Reality / Opt...

Use when the user makes or revisits a meaningful product, technical, or organizational decision and wants it captured in a durable, ADR-style format. Trigger when they say "we decided to…", "let's go with X over Y", "I need to write up the call we made on…", or when reviewing a past decision they can't fully reconstruct. Especially valuable for AI-product decisions (model choice, eval threshold, fallback design) that are easy to forget the rationale for three months later.

Use 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.

Use 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.

Use when the user wants to systematically identify, categorize, and quantify "glue work" (non-core technical activities like onboarding, documentation, unblocking, cross-team alignment, process improvement) 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". Produces a structured inventory with time estimates, pro...

Use 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". Treats hiring as a craft with measurable signals and calibrated decisions, not a vibe-driven exercise.

Use when the user needs to move a person, team, or decision *without having direct authority* over them — driving an architecture change across teams, getting buy-in from a skeptical principal engineer, persuading an exec sponsor, mobilizing a coalition for a contentious initiative, or pushing back on a leader's decision without bruising the relationship. 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 hav...

Use 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.

Use when managing engineers who naturally gravitate toward glue work (onboarding, documentation, unblocking, process improvement) and need protection from burnout, visibility for their impact, 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". Provides manager-specific...

Use when the user is designing the metric tree for a feature (especially an AI feature) — picking a north star, leading and lagging indicators, quality metrics, and counter-metrics. Trigger phrases include "what should we measure for…", "how do we know if this is working?", "I need to define success for…", or any spec where the success metrics section is fuzzy. Distinct from `the-eval-designer`, which measures model quality; this skill measures business success and guards against optimizing t...

Use when the user is preparing for a 1:1 — as a manager preparing to meet with a report, as an IC preparing to meet with their manager, or as a peer preparing for a regular 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 an agenda matched to the relationship and the moment, not a generic template.

Use to surface unsolicited patterns the user hasn't explicitly asked about — across stakeholder reflections, wins log, self-reflect entries, and (eventually) pulse reports. 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". Designed to be invoked on demand or fired on a weekly Desktop scheduled task (not cloud routines — those cannot access local files). Distinct from `stakehol...

Use when the user is dealing with underperformance, considering a PIP, navigating a brilliant-jerk pattern, documenting concerns, or preparing for 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". The hardest skill in management — most managers avoid it for too long, then escalate badly. This skill helps the user move th...

Use for individual or lightweight pre-mortem analysis of decisions, projects, or initiatives. Trigger when the user says "what could go wrong", "risk assessment", "pre-mortem this", or when evaluating risks for a plan. Applies a three-category framework for systematic risk identification.

Use 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) for the situation and forces the underlying assumptions out into the open.

Use to produce a single-page dated pulse report on product health — usage metrics, system performance, AI-feature signals (hallucination, refusal, eval drift), counter-metrics, and follow-up investigation. Trigger phrases include "run a pulse on [area]", "give me a product health snapshot", "weekly product pulse", "what does the data say this week". Reads strategy.md to know what to watch and which counter-metrics matter. Saves to `~/bettersense-work-reflections/pulses/<area-slug>/pulse-YYYY-...

Use when an engineer who does significant glue work (onboarding, documentation, unblocking, cross-team alignment, process improvement) needs to build a promotion packet that frames that work 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". Works alongside or as a specialized mo...

Use when a team lacks psychological safety — members don't speak up, withhold concerns, or fear making mistakes. Trigger phrases 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". Provides concrete, actionable practices to build psychological safety, drawing from Amy Edmondson's research and Moussa's emphasis on trust-building conversations. Not just diagno...

Use to derive insight across accumulated product-pulse reports — trends, anomalies, inflection points, regime shifts. 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 `~/bettersense-work-reflections/pulses/<area-slug>/` over a time window and produces a synthesis with citations...

Use to interpret the *subtext* of a conversation, meeting, design review, Slack thread, exec readout, or 1:1 — what was said vs. what was unsaid, who held back, where consensus is performative, what the disagreement is actually about beneath stated positions. 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 o...

Use when designing or revisiting a 12–18 month growth plan for one of the user's direct reports. 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` (per-meeting agenda) and from `coaching-mode` (the conversational layer). This is the *planning* layer — turning ...

Use when building a promotion case for a direct report — internal promo packet, panel write-up, or the one-pager that goes to a calibration committee. 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". The mirror image of `wins-curate` — that one is for the user's own brag doc; this is for advocating *upward* for a report. Reads accumulated stakeholder-refle...

Use when the user wants to reflect on themselves as a leader — behavior under pressure, communication, time and energy, leadership style, fulfillment, advocating for themselves, calendar review. Trigger phrases include "let me reflect on myself", "self-check", "I want to think about how I've been leading lately", "self-reflection". Loads `~/bettersense-work-reflections/self/reflections.md`, picks 1–3 self-reflection questions appropriate to the moment, guides the reflection, and writes the da...

Use when the user wants to know which stakeholder reflections are overdue. Trigger phrases include "what's due", "who haven't I thought about lately", "what's on my plate this week for stakeholder reflection", "stakeholder check-in", or any Monday-morning planning moment. Scans `~/bettersense-work-reflections/`, computes which question × stakeholder pairs are overdue based on `suggested_freq` and last entry date, and outputs a prioritized list. Designed to be invoked on demand or fired on a w...

Use when the user wants to *change* something about an already-registered stakeholder — list them, edit role/background, re-categorize after a reorg, rename, archive (because they left), or delete. Trigger phrases 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". Mirrors stakeholder data lif...

Use when the user wants to reflect on a registered stakeholder — a manager, peer, direct report, or team — and capture the insight to a durable file. Trigger phrases 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]". Loads the stakeholder file, picks 1–3 questions appropriate to the moment based on cadence and what hasn't been touched recently, guides the reflection, and writes the dated entry b...

Use when the user wants to register a new stakeholder for ongoing reflection — a manager, peer, direct report, or team. Trigger phrases 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 `~/bettersense-work-reflections/<category>/<slug>.md` that the `stakeholder-reflect`, `stakeholder-due`, and `stakeholder-synthesize` skills will use.

Use when the user wants to derive insight across accumulated stakeholder reflections — patterns, trends, contradictions, blind spots. Trigger phrases include "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". Reads one or many stakeholder files and produces synthesis with citations to specific dat...

Use when the user is new to bettersense and doesn't know where to begin, or when they want a tour of what's available. Trigger phrases include "where do I start", "how do I use this", "what can you do", "what should I run first", "I just installed this", "help me get started", "what is bettersense", "how does this work", "I don't know what to do". Entry point for all new users.

Use to create or update a product/area strategy document — target problem, approach, personas, key metrics (3-5 SMART), 2-4 multi-month strategic tracks, and an explicit "not working on" section. Trigger phrases include "draft a strategy doc for [product/area]", "I need a strategy.md for the platform team", "interview me about my strategy", "update my strategy doc", "what's in my strategy doc". Lives at `~/bettersense-work-reflections/strategy/<area-slug>.md` and is read as an anchor by `the-...

Use when forming a new team, resetting an existing team after a reorg, or when a team's goals/roles/norms are unclear and causing friction. Trigger phrases 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 the three foundations from Mario Moussa's 3X3 framework (Goals, Roles, Norms) and produces a living charter document stored at ~/bettersense-work-refle...

Use when a team needs to regularly revisit their Goals/Roles/Norms foundation to surface drift and realign. Trigger phrases include "team check-in", "are we still aligned", "team retro on our operating model", "review our team charter", "3X3 check-in". Facilitates a structured conversation (30–90 min) that answers: Are we still committed to our stated goals/roles/norms? If not, what's the gap and how do we close it? The second step of Moussa's 3X3 framework. Works from an existing team charte...

Use when a team has identified a gap between stated goals/roles/norms and actual behavior, and needs concrete, small-step action plans to close it. Trigger phrases 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". The third step of Moussa's 3X3 framework: closes the gap between what the team says it wants to do and what it actually does, through targeted s...

Use when the user wants a structured read on the *health* of their team — beyond individual morale to delivery cadence, attrition risk, dependency tax, on-call burden, peer relationships, and cross-cutting patterns. Trigger phrases include "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 the user's stakeholder-reflect entries on direct reports + team file + any ...

Use when a team is going through a transition — forming (new team), storming (conflict emergence), norming (establishing ways of working), performing (high function), or adjourning (team disbandment/transition). Also for resets after reorgs, new member integration, or when a team is stuck in a dysfunctional phase. Trigger phrases include "our team is changing", "new team member joining", "team reorg transition", "how do we reset our team", "team dissolving", "adjourning a team". Based on Tuck...

Use when a team wants to understand and discuss their collective working style preferences — communication, decision-making, conflict, meeting effectiveness, and information sharing — to reduce friction and increase intentionality. Trigger phrases include "team work style assessment", "how does our team prefer to work together", "team style inventory", "understand our team dynamics", "communication preferences survey". Based on the insight from Moussa that team performance depends on paying a...

Use to create or update the user's anchor profile — a single private file (`~/bettersense-work-reflections/profile.md`) that captures who the user is, what they do, what context other skills need to know about them. Read automatically by other skills in the bundle when present, so the user doesn't re-explain themselves every session. Trigger phrases include "set up my profile", "create my user profile", "update my profile", "I changed roles, refresh my profile", "what does my profile look lik...

Use to turn the wins log into an audience-specific artifact — promo packet, behavioral interview stories (STAR), perf-review self-eval, salary negotiation case, or a personal 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 `~/bettersense-work-reflections/wins.md`, picks and remixes entries for the chosen audience, and produces a usable a...

Use when the user wants a low-pressure nudge on whether anything from the recent week is worth logging to their wins file. 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". Designed to be invoked on demand or fired on a weekly Desktop scheduled task (not cloud routines — those cannot access local files). Probes by category (delivery / judgment / mentorship / recovery / range) because memor...

Use when the user wants to capture a "win at work" — something they shipped, judgment they exercised, someone they mentored, a fire they put out, a hard decision they got right. Trigger phrases include "I just shipped X", "log this win", "add to my brag doc", "I want to remember what I did this week", "I had a good week and want to capture it". Captures structured entries (situation, action, impact, evidence) to `~/bettersense-work-reflections/wins.md` so they can be remixed later by `wins-cu...

Use when the user wants to analyze whether non-promotable (glue) work is fairly distributed across their team, with attention to demographic and seniority patterns. Trigger phrases include "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 fairness diagnosis with evidence, bias signals, and concrete redistribution recommendations. Mana...

Use to log something from the current conversation into the user's bettersense memory without re-typing it — a decision that just got made, a win that surfaced mid-discussion, an observation about a stakeholder, a self-insight. Trigger phrases include "log this", "capture this", "save that decision", "add that to my wins", "put that in my reflections", "remember this", or when a substantive conversation just concluded and its outcome would otherwise evaporate. Distinct from decision-log / win...

Use for a periodic (quarterly / annual) career retrospective across the ENTIRE bettersense memory — producing a longitudinal self-assessment with cited growth deltas since the last retro and the honest gaps to work on next. 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". Reads wins, all stakeholder reflections, self-reflections, pulses, and charters; writes a dated...

Use to track what the user has promised — to their manager, execs, partner teams — and to keep those promises from silently 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". Maintains a lightweight ledger at ~/bettersense-work-reflections/commitments.md: log promises when made, review what's due or slipping, renegotiate early with a script, and press...

Use to health-check the user's bettersense memory directory — validate the file layout, catch problems before they cost data, and set up backups. Trigger phrases include "run bettersense doctor", "check my reflection files", "is my bettersense data okay", "something seems off with my stakeholder files", "back up my reflections", "I'm moving to a new machine". Validates ~/bettersense-work-reflections/ (or $BETTERSENSE_WORK_REFLECTIONS_HOME): stakeholders.json integrity, orphaned or unregistere...

Use when an EM wants to assess how well their engineering systems and processes are working — not team morale or people dynamics (that's team-diagnosis), but the productivity layer: are the right things being measured, where is developer experience breaking down, is onboarding a signal of deeper friction, and how to make the case for platform investment. Trigger phrases include "is my team actually productive", "I want to understand developer experience on my team", "how do I measure engineer...

Use when the user needs a decision or backing from executives and is preparing the meeting or memo that gets it — QBRs, roadmap reviews, headcount asks, architecture investment pitches, "I'm presenting to the VP/C-suite next week". 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". Managing up at the decision moment: audience power map, the explicit ask, pre-wiring, and objection handling. Distin...

Use when a PM or team wants to stress-test whether their work is actually connected to something the business cares about. Runs before strategy-doc or prioritization-frameworks — it answers "are we even pointed at the right thing?" 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 moment of doubt about whether the team's work would survive scrutiny.

Use when a new model version ships (or a current one is deprecated) and the user must decide whether and how to migrate a LIVE AI feature — "Claude X just came out, should we move?", "our model is being deprecated in 90 days", "the new model is cheaper, can we switch?", "plan the migration to [model]". Runs the checklist: inventory what's pinned to the old model, re-run evals before believing anything, revisit decision-log entries tied to the old version, re-baseline cost and latency, stage t...