shwetank

@shwetank source repo

54 skills
0 followers
22 hours ago last updated

▌
Start · shwetank
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.

0
installs
▌
Doctor · shwetank
Doctor

0
installs
▌
Weekly · shwetank
Weekly

0
installs
▌
Capture · shwetank
Capture

0
installs
▌
Wins Due · shwetank
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 memory is selective and "anything notable?" alone surfaces nothing. Accepts "honestly, nothing this week" gracefully — the skill is for honest capture, not forced positivity.

0
installs
▌
Wins Log · shwetank
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-curate` into a promo packet, interview stories, perf-review self-eval, salary case, or year-in-review.

0
installs
▌
Demo Prep · shwetank
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.

0
installs
▌
Premortem · shwetank
Use for pre-mortem analysis of decisions, projects, or initiatives — solo and lightweight, 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. Applies a three-category framework (Critical, Perceived, Undiscussed risks) and, for team sessions, a facilitation flow that ends in an action plan with owners — not a brainstorm that ends in anxiety.

0
installs
▌
Glue Audit · shwetank
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, promotion-value assessment, and fairness analysis. Especially useful before promotion cycles, workload rebalancing, or role-transition decisions.

0
installs
▌
Commitments · shwetank
Commitments

0
installs
▌
Wins Curate · shwetank
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 artifact. Never invents wins — only curates from what's logged. Composes with `stakeholder-synthesize` and `self-reflect` for perf-review prep.

0
installs
▌
Career Retro · shwetank
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 retro to self/retros/ so the next one can measure change. Distinct from wins-curate (which builds one audience-facing artifact like a promo packet) and self-reflect (a single in-the-moment entry). The meta-synthesis whose output compounds over years.

0
installs
▌
Decision Log · shwetank
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.

0
installs
▌
Hiring Craft · shwetank
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.

0
installs
▌
Impact Audit · shwetank
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.

0
installs
▌
Self Reflect · shwetank
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 dated entry back. Mirrors `stakeholder-reflect` but aimed at the user themselves.

0
installs
▌
Strategy Doc · shwetank
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-spec-writer`, `prioritization-frameworks`, `metrics-design`, `product-pulse`, and `pulse-synthesize`. Inspired by Every.to's `/ce:strategy` pattern but composes more deeply with the rest of the bundle and supports multiple products/areas.

0
installs
▌
Team Charter · shwetank
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-reflections/team-charters/<team-slug>.md. Especially useful for new product teams, new management layers, or after major org changes.

0
installs
▌
User Profile · shwetank
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 like". Inspired by the `SOUL.md` pattern from agents like Hermes — explain yourself once, get tailored output forever.

0
installs
▌
Coaching Mode · shwetank
Coaching Mode

0
installs
▌
Leadership Os · shwetank
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.

0
installs
▌
Product Pulse · shwetank
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-MM-DD.md` so the folder accumulates into product memory over time. Designed for daily/weekly Desktop scheduled tasks (not cloud routines — those cannot read or write local files). Privacy-first — defaults to aggregated/redacted data; surfaces provenance.

0
installs
▌
Read The Room · shwetank
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 or just nodding". Retrospective interpretation, not real-time — you bring the situation, the skill helps you see what you might have missed.

0
installs
▌
Team Check In · shwetank
Team Check-In

0
installs
▌
Metrics Design · shwetank
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 the model into a worse product.

0
installs
▌
Patterns Watch · shwetank
Patterns Watch

0
installs
▌
Team Close Gap · shwetank
Team Close the Gap

0
installs
▌
Team Diagnosis · shwetank
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 inputs the user provides (recent retros, attrition events, eng survey scores), and produces a multi-dimensional diagnosis with patterns, risks, and concrete actions.

0
installs
▌
Team Lifecycle · shwetank
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 Tuckman's model applied to work teams with practical guidance for each phase. Complements team-charter, team-check-in, and stakeholder-manage.

0
installs
▌
Team Workspace · shwetank
Use to set up or work with a SHARED, git-backed team workspace for artifacts a team co-owns — team charters, strategy docs, decision records — kept strictly separate from your private reflections, which never leave your machine. Trigger phrases include "share our team charter with the team", "set up a shared bettersense workspace", "put our strategy doc in the team repo", "how do teams use bettersense together". Establishes `$BETTERSENSE_TEAM_HOME` (a separate git repo), enforces a hard wall that personal files (reflections, wins, retros, commitments) are NEVER shared, and drafts the branch/commit/PR — but never pushes or opens a PR for you. The multiplayer layer with the privacy wall built in.

0
installs
▌
One On One Prep · shwetank
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. If the other person is a registered stakeholder, reads their reflection file first so the agenda carries what the user already knows — open loops, recent observations, questions worth asking.

0
installs
▌
Promo Case Glue · shwetank
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 mode of `report-promo-case`. Produces a promotion-ready narrative that translates glue tasks into ladder-appropriate evidence, with artifact collection guidance and manager talking points.

0
installs
▌
Stakeholder Due · shwetank
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 weekly Desktop scheduled task (not cloud routines — those cannot access local files).

0
installs
▌
Workload Equity · shwetank
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. Manager-facing skill with sensitivity to privacy and psychological safety.

0
installs
▌
AI Pm Frameworks · 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.

0
installs
▌
Pulse Synthesize · shwetank
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 to specific dated pulse reports. Citation-disciplined; never claims a trend without evidence; distinguishes signal from noise. The Every.to gap, closed.

0
installs
▌
Exec Readout Prep · shwetank
Exec Readout Prep

0
installs
▌
Report Promo Case · shwetank
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-reflect entries on the report (and any growth plan from `report-career-architect`), produces a panel-ready packet with cited evidence per dimension, surfaces calibration concerns, and flags gaps before submission.

0
installs
▌
Engineering Health · shwetank
Engineering Health

0
installs
▌
Stakeholder Manage · shwetank
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 lifecycle without touching the reflection content. Composes with `stakeholder-register` (which handles add).

0
installs
▌
Feedback Frameworks · shwetank
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.

0
installs
▌
Manage Glue Workers · shwetank
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 guidance on credit amplification, workload rebalancing, promotion advocacy, and skill development that preserves technical growth.

0
installs
▌
Stakeholder Reflect · shwetank bundle
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 back.

0
installs
▌
Psychological Safety · shwetank
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 diagnostic (like team-diagnosis) but prescriptive — tells the leader exactly what to do this week.

0
installs
▌
Stakeholder Register · shwetank
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.

0
installs
▌
Team Style Inventory · shwetank
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 attention to "how you talk to each other." Produces a shared understanding of the team's style profile, surface mismatches, and norms adjustments. Precedes or complements team-charter and team-check-in.

0
installs
▌
Tech Strategy Writer · shwetank
Tech Strategy Writer

0
installs
▌
Performance Management · shwetank
Performance Management

0
installs
▌
Stakeholder Synthesize · shwetank
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 dated entries — never claims a pattern without evidence.

0
installs
▌
Visibility Sponsorship · shwetank
Visibility & Sponsorship

0
installs
▌
Model Migration Planner · shwetank
Model Migration Planner

0
installs
▌
Report Career Architect · shwetank
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 observations from `stakeholder-reflect` into a structured arc with concrete experiences, owners, and check-in cadence.

0
installs
▌
Prioritization Frameworks · shwetank
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.

0
installs
▌
Influence Without Authority · shwetank
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 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` (which delivers truth) and `coaching-mode` (which develops people). This is about *moving outcomes through people you don't manage*. Opinionated about legitimate vs. manipulative tactics.

0
installs

54 published skills