{
 "spec": "skill-federation/0.1",
 "built": "2026-07-21",
 "libraries": 1,
 "skills": 750,
 "members": [
  {
   "repo": "mohitagw15856/pm-claude-skills",
   "name": "pm-claude-skills",
   "homepage": "https://github.com/mohitagw15856/pm-claude-skills",
   "license": "MIT",
   "badge": "https://img.shields.io/endpoint?url=https%3A%2F%2Fpm-skills-mcp.pm-claude-skills.workers.dev%2Fbadge%3Frepo%3Dmohitagw15856%2Fpm-claude-skills",
   "count": 750,
   "skills": [
    {
     "name": "360-feedback-template",
     "description": "Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended qu"
    },
    {
     "name": "401k-plan-decoder",
     "description": "Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee"
    },
    {
     "name": "ab-test-planner",
     "description": "Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sampl"
    },
    {
     "name": "ab-test-readout",
     "description": "Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produce"
    },
    {
     "name": "accessibility-audit",
     "description": "Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessme"
    },
    {
     "name": "account-plan",
     "description": "Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan."
    },
    {
     "name": "acquirer-red-team",
     "description": "Simulate the acquirer's diligence team hunting for reasons to cut your price — their internal red-flags memo with a price-chip estimate per finding. Use when asked to red-team my company before a sale, how will an acquirer attack our valuation, pre-diligence audit, or what will DD find. Produces the"
    },
    {
     "name": "action-runner",
     "description": "Turn a skill's recommendations into real, executed actions — open the tickets, file the issues, post the updates — safely: dry-run preview, risk-classified, approval-gated, then recorded back to the brain. Use when asked to act on a plan, file tickets from a checklist, create issues from a PRD, exec"
    },
    {
     "name": "ad-copy",
     "description": "Write platform-native paid ad copy with multiple angles to test. Use when asked to write ad copy, Google/Facebook/LinkedIn/Instagram ads, PPC headlines, or paid social creative copy. Produces ready-to-ship variants per platform (headlines, primary text, descriptions, CTAs) across distinct angles, si"
    },
    {
     "name": "aeo-optimizer",
     "description": "Optimize an article for Answer Engine Optimization (AEO) so AI engines like ChatGPT, Perplexity, and Claude can extract, quote, and cite it. Use when asked to AEO-optimize, make content AI-readable, improve AI citation chances, or adapt an article for answer engines. Produces an AEO-optimised rewrit"
    },
    {
     "name": "agenda-or-cancel",
     "description": "Enforce the simplest meeting rule that works — no agenda, no meeting — with the three-line agenda format (purpose, decisions sought, pre-reads), the 24-hour rule, and the graceful cancel scripts. Use when asked write an agenda for this meeting, should this meeting happen, our meetings have no agenda"
    },
    {
     "name": "agent-design-review",
     "description": "Review an LLM agent design and find where it will be unreliable, expensive, or unsafe. Use when asked to review an agent architecture, critique a multi-step/tool-using agent, debug an agent that loops or goes off-task, or harden an agent before launch. Produces a structured review — task fit, contro"
    },
    {
     "name": "agent-era-pricing",
     "description": "Redesign seat-based pricing for the agent era — when one human runs ten agents, per-seat models collapse. Use when agents are eroding seat counts, when asked to migrate to usage- or outcome-based pricing, to price an agent/API tier, or to defend revenue as customers automate their own usage. Produce"
    },
    {
     "name": "agent-incident-postmortem",
     "description": "Run a blameless postmortem for an incident caused by an AI agent or LLM feature — hallucinated facts shipped to users, runaway tool use, prompt injection, cost blowouts, or wrong actions taken autonomously. Use when asked to write up an AI incident, analyse why an agent did something wrong, or produ"
    },
    {
     "name": "agent-observability-spec",
     "description": "Specify the tracing, metrics, and alerting for an AI agent or LLM feature in production. Use when asked what to log for an LLM app, design agent tracing or spans, define quality and cost monitors, or answer 'how do we know if the agent is misbehaving?'. Produces an observability spec with a trace sc"
    },
    {
     "name": "agent-readiness-audit",
     "description": "Audit whether AI agents can actually use your product — docs, APIs, onboarding, errors, and discoverability, evaluated from a non-human user's perspective. Use when asked if a product is agent-ready, to audit a site or API for AI usability, to prepare for agentic traffic, or when agents keep failing"
    },
    {
     "name": "agent-spec",
     "description": "Specify an autonomous or tool-using AI agent before building it. Use when asked to design an AI agent, define an agent's tools and guardrails, scope what an agent is allowed to do, or write an agent spec/PRD. Produces an agent spec — goal & scope, tools with permissions, the control loop, guardrails"
    },
    {
     "name": "ai-code-review",
     "description": "Review AI-authored code for its characteristic failure modes — plausible-but-wrong logic, hallucinated APIs, over-engineering, dead scaffolding, and silent security shortcuts. Use when reviewing an AI-generated or heavily AI-assisted PR, when AI-written code keeps shipping subtle bugs, or when setti"
    },
    {
     "name": "ai-content-audit",
     "description": "Audit a content library, docs site, or blog for AI-generated filler that's eroding trust and search performance — and triage what to fix, rewrite, or delete. Use when asked to find slop in a content library, audit AI-written content quality, explain why content engagement or rankings dropped after s"
    },
    {
     "name": "ai-ethics-review",
     "description": "Conduct a structured ethical review of an AI or ML feature, model, or product. Use when preparing to deploy an AI system, assessing algorithmic risk, auditing a model for bias, or producing a responsible AI impact assessment. Produces a structured ethics review covering fairness, transparency, priva"
    },
    {
     "name": "ai-eval-plan",
     "description": "Design an evaluation plan for an LLM or AI feature before shipping it. Use when asked how to evaluate a prompt/model/agent, set up an eval harness, define quality metrics for an AI feature, or build a regression gate. Produces an eval plan — task definition, datasets, metrics & rubrics, baselines, a"
    },
    {
     "name": "ai-feature-prd",
     "description": "Write a PRD for an AI-powered feature, covering the things normal PRDs miss. Use when asked to spec an AI/LLM feature, write a PRD for a feature that uses a model, or plan an AI capability (assistant, summarizer, generator, classifier). Produces an AI feature PRD — problem & UX of uncertainty, model"
    },
    {
     "name": "ai-product-canvas",
     "description": "Structure AI and ML product decisions with the rigour of any product decision. Use when building AI-powered features, evaluating LLM integrations, designing AI products, or assessing AI readiness. Produces a complete AI product canvas covering problem definition, model approach, data requirements, e"
    },
    {
     "name": "ai-roi-audit",
     "description": "Audit whether the organisation's AI spend actually paid — measured against baselines, not vendor math or vibes. Use when a CFO asks what the AI tools returned, when renewing AI contracts, when consolidating overlapping AI subscriptions, or to build the measurement plan before the next spend. Produce"
    },
    {
     "name": "ai-usage-policy",
     "description": "Write an AI usage policy people can actually follow — approved tools, data rules, disclosure duties, and review obligations, in one page instead of legal fog. Use when asked for a company AI policy, acceptable-use rules for ChatGPT/Claude/Copilot at work, guidance on what data may go into AI tools, "
    },
    {
     "name": "ai-assisted-performance-review",
     "description": "Evaluate performance fairly when output is AI-assisted — what still measures the human, what now measures the tooling, and how to run the review conversation. Use when reviewing someone whose work is heavily AI-assisted, when output volume stopped meaning anything, when calibrating a team with uneve"
    },
    {
     "name": "air-quality",
     "description": "Check live air quality anywhere with zero API keys — Open-Meteo's air-quality API via curl, decoded from raw PM2.5 and AQI numbers into what they mean for going outside. Use when asked what's the air quality, is it safe to run outside, AQI in my city, or pollution levels right now. Produces the curr"
    },
    {
     "name": "all-hands-deck",
     "description": "Build an all-hands that lands with everyone from intern to VP — the mixed-altitude structure (the story for all, the numbers for some), the wins-with-names section done right, the hard-news slide handled straight, and the Q&A design that gets real questions. Use when asked build the all-hands deck, "
    },
    {
     "name": "altitude-shifter",
     "description": "Re-pitch one piece of content for four audiences — the board, the engineers, a customer, a new hire — with a delta table showing what changed between altitudes and why. Use when asked to rewrite this for execs, explain this to the team, make this customer-facing, or say this four ways. Produces the "
    },
    {
     "name": "ambiguity-resolver",
     "description": "Structure vague opportunities and unclear briefs into actionable one-page problem statements. Use when asked to clarify a vague brief, frame an undefined problem, make sense of an unclear opportunity, or when the user says 'we need to figure out what to do about X' or 'I've been asked to look into Y"
    },
    {
     "name": "analyst-relations-brief",
     "description": "Prepare for an industry analyst briefing (Gartner, Forrester, IDC and similar). Use when asked to prep an analyst briefing, write an AR briefing document, build talking points for an analyst call, or prepare a Magic Quadrant / Wave submission narrative. Produces a briefing kit — objective, company/p"
    },
    {
     "name": "announcement-card",
     "description": "Write a short, punchy announcement designed to be shared as an image or social card. Use when asked to announce a launch, milestone, feature, hire, funding, or win — something to post on LinkedIn/X/Slack. Produces a tight, visually-structured announcement (headline, one-liner, 2-3 proof points, CTA)"
    },
    {
     "name": "api-docs-writer",
     "description": "Write clear, developer-facing API documentation. Use when asked to document an API endpoint, write API reference docs, create a developer guide, or turn a raw spec/Postman collection into documentation. Produces endpoint documentation with descriptions, parameters, request/response examples, and err"
    },
    {
     "name": "api-test-plan",
     "description": "Plan tests for an API endpoint or service — functional, negative, and contract. Use when asked to test an API, write API test cases, plan REST/GraphQL endpoint testing, or validate an API contract. Produces an API test plan — per-endpoint cases (status codes, schema, auth, validation, errors), bound"
    },
    {
     "name": "api-versioning-strategy",
     "description": "Write an API versioning strategy document for a service or API platform. Use when asked to define versioning policy, plan API deprecation, classify breaking changes, or document version lifecycle. Produces a complete versioning strategy with breaking-change classification table, deprecation timeline"
    },
    {
     "name": "apology-letter",
     "description": "Write a sincere, effective apology to a customer, group, or the public. Use when asked to write an apology, say sorry to a customer or community, make amends after a mistake, or respond to a complaint with an apology. Produces a genuine apology — acknowledgement, taking responsibility, empathy for t"
    },
    {
     "name": "architecture-decision-record",
     "description": "Create an Architecture Decision Record (ADR) for any technical decision. Use when asked to document a technical decision, write an ADR, record an architecture choice, or capture why a technology or approach was selected. Produces a structured ADR with context, decision, consequences, and tradeoffs."
    },
    {
     "name": "architecture-diagram",
     "description": "Diagram a system or technical architecture — services, data stores, and how they connect. Use when asked to draw an architecture, show how components fit together, map a system/data flow, or visualize services and dependencies. Produces a ready-to-render Mermaid diagram with grouped subgraphs (rende"
    },
    {
     "name": "archive-strategy",
     "description": "Design the archive layer that keeps current workspaces lean without losing history — what moves, when, to where, findable-by-search, with the project-close ritual that makes archiving automatic instead of aspirational. Use when asked set up an archiving system, our workspace is drowning in old proje"
    },
    {
     "name": "assumption-bounty",
     "description": "Extract every hidden assumption from a plan or document and put a price on each one — what it costs if wrong, what it costs to test. Use before committing to anything whose author says 'obviously' or whose spreadsheet has hardcoded cells: the bounty hunt makes the invisible load-bearing beliefs expl"
    },
    {
     "name": "assumption-mapper",
     "description": "Extract and risk-rate hidden assumptions in a product brief or PRD. Use when asked to review a product brief for assumptions, audit a PRD for risks, find hidden assumptions, validate product plans, or run an assumption analysis. Produces a prioritised assumption map with confidence and impact scores"
    },
    {
     "name": "async-decision-memo",
     "description": "Run a decision asynchronously — the memo, the silent-read window, the comment protocol, and the deadline that makes it land without a meeting. Use when asked to decide something async, replace a decision meeting with a document, run an Amazon-style written decision process, or when a decision keeps "
    },
    {
     "name": "async-instead",
     "description": "Convert a meeting into async work that actually decides — the doc-plus-deadline format that replaces the room, the comment-window rules, the decision-closure step that async usually fumbles, and the honest test for what still needs synchronous. Use when asked can this meeting be async, replace our s"
    },
    {
     "name": "async-standup-compiler",
     "description": "Compile the team's REAL updates into one async standup — pull what people posted in Slack (and moved in Notion/Linear), not a template for running standups. Use when asked to compile today's standup, pull the team's updates into one post, what did the team ship, or run async standup in Cowork. Reads"
    },
    {
     "name": "async-update-format",
     "description": "Write status updates people actually read — the traffic-light-plus-narrative format (state first, story second), the blockers-are-asks rule, and the skimmable structure that respects a reader with thirty seconds. Use when asked write my weekly update, format our team's status posts, nobody reads my "
    },
    {
     "name": "auto-repair-estimate-decoder",
     "description": "Decode an auto repair estimate — what each line actually is, which items are urgent vs upsell, and the questions that separate a fair shop from a fishing expedition. Use when someone asks 'is this repair quote fair', 'decode my mechanic's estimate', 'do I really need all this', or 'is the shop rippi"
    },
    {
     "name": "autopilot-charter",
     "description": "Decide which of your recurring rituals to put on autopilot — and which to keep manual. Use when asked what to automate, how to set up recurring AI runs, which reports or briefings could run on a schedule, or to design an automation charter for a team. Produces a ritual inventory with automate/assist"
    },
    {
     "name": "beneficiary-audit",
     "description": "Audit the beneficiary designations that quietly override wills — the account-by-account sweep, the life-event triggers that make them stale, and the coordination check against actual intentions. Use when asked check my beneficiaries, does my 401k go to my ex, do beneficiary forms beat a will, or wha"
    },
    {
     "name": "benefits-decoder",
     "description": "Decode an employment benefits package into what it's actually worth and where the fine print bites. Use when someone asks 'is this offer good', 'decode my benefits package', 'what does my equity actually mean', or 'what should I ask HR before signing'. Produces a benefit-by-benefit decode with real "
    },
    {
     "name": "bid-tender-review",
     "description": "Analyse a construction bid or tender package for scope gaps, risk-shifting exclusions, unit-rate red flags, and front-loading in the schedule of values. Use when asked to review a bid, level bids, check a tender for gaps, compare sub quotes, or vet a schedule of values before award. Produces a struc"
    },
    {
     "name": "blast-radius-drill",
     "description": "Run the worst-case drill before an agent goes autonomous — the 'if this agent were fully hijacked right now, what's the damage' walk-through, the containment controls (caps, kill-switch, reversibility, isolation), and the recovery plan. Use when asked what's the worst my agent could do, run a blast-"
    },
    {
     "name": "board-deck-narrative",
     "description": "Build the storyline and slide structure for a board presentation. Use when asked to create a board deck, board presentation narrative, board meeting slides, or quarterly board update. Produces a complete slide-by-slide structure with narrative beats, talking points, and slide content guidance."
    },
    {
     "name": "board-minutes",
     "description": "Write formal board meeting minutes from an agenda, notes, transcript, or discussion summary. Use when asked to draft board minutes, governance minutes, meeting minutes for a board, or a formal record of decisions and actions. Produces structured board minutes with attendees, agenda items, resolution"
    },
    {
     "name": "board-pre-read",
     "description": "Write a board pre-read that's sent before the meeting so the meeting is about decisions, not status. Use when asked to prepare a board pre-read, a board update/package, or pre-meeting materials for a board. Produces a board pre-read — a TL;DR, the metrics dashboard vs. plan, what's working / what's "
    },
    {
     "name": "bom-cost-review",
     "description": "Review a bill of materials for cost, risk, and supply exposure — cost rollup, top-10 cost drivers, single-source and EOL risk, MOQ vs forecast mismatch, cost-down candidates, and tariff/logistics sensitivity. Use when asked to review a BOM, find cost-down opportunities, check component sourcing risk"
    },
    {
     "name": "bookkeeping-categorization",
     "description": "Set up a chart of accounts and rules for categorizing transactions. Use when asked how to categorize expenses/transactions, set up a chart of accounts, organize bookkeeping, or sort bank transactions into the right buckets. Produces a practical chart of accounts for the business, categorization rule"
    },
    {
     "name": "boolean-search-builder",
     "description": "Build boolean and X-ray search strings to source candidates. Use when asked to build a boolean search, source candidates on LinkedIn/Google, write an X-ray search, or find people with specific skills. Produces ready-to-paste boolean strings (with synonyms, must-haves, and exclusions), X-ray variants"
    },
    {
     "name": "brag-doc",
     "description": "Keep a running brag document of your accomplishments so reviews and promo cases write themselves. Use when asked to start or update a brag doc, log a win, track accomplishments, or prep evidence for a review/promotion. Produces a structured, dated accomplishment log — impact-first entries with metri"
    },
    {
     "name": "brainstorming",
     "description": "Run a real brainstorm — divergent generation without judgment, then convergent selection with explicit criteria — instead of listing ten obvious ideas and calling it creativity. Use when asked to brainstorm, generate ideas or options, explore a solution space, or name something. Produces a genuinely"
    },
    {
     "name": "brand-guidelines",
     "description": "Extract a brand's visual and verbal identity into an applicable guideline kit — tokens, voice rules, and do/don't pairs — then apply it consistently to any artifact. Use when asked to apply brand guidelines to a document/deck/page, to extract a brand kit from existing materials or a website, to keep"
    },
    {
     "name": "brand-impersonation-response",
     "description": "Respond to a brand or executive impersonation incident — deepfaked executives, cloned support lines, fake apps, spoofed domains, or AI-generated scam content wearing your name. Use when a deepfake of a leader is circulating, customers report a fake version of your product or support channel, or to p"
    },
    {
     "name": "brief-builder",
     "description": "Interview the user with sharp, one-at-a-time questions to turn a vague request into a tight, complete brief any other skill can run on. Use when a request is fuzzy, under-specified, or 'help me think this through', or before running a skill that needs inputs the user hasn't given. Produces a structu"
    },
    {
     "name": "brief-from-pile",
     "description": "Turn a folder of accumulated documents into one decision-ready brief — the skim-map pass over the pile, the extraction against the brief's actual questions, the conflict reconciliation when documents disagree, and the provenance trail back to sources. Use when asked read all this and tell me what ma"
    },
    {
     "name": "briefing-note",
     "description": "Write a one-page briefing note that gets a busy principal up to speed fast. Use when asked to brief a minister/executive/official, prepare a briefing note or read-ahead, or summarize an issue for a decision or meeting. Produces a tight, single-page note: purpose, background, key facts/considerations"
    },
    {
     "name": "browser-agent-preflight",
     "description": "Run the pre-flight checklist before an agent drives a browser — the untrusted-web-content threat (every page is attacker-controllable), the credential and session-cookie exposure, the action-confirmation gates for purchases and posts, and the sandboxing that limits the damage. Use when asked let my "
    },
    {
     "name": "budget-builder",
     "description": "Build a realistic personal monthly budget from someone's income and expenses. Use when asked to make a budget, plan monthly spending, allocate income, or get finances under control. Produces a categorized budget (a 50/30/20-style allocation tuned to their reality), a surplus/shortfall number, and co"
    },
    {
     "name": "budget-tracker-design",
     "description": "Design a budget-vs-actuals tracker that stays alive past February — the category grain that matches real statements, the variance view that answers 'are we okay', the update ritual small enough to survive, and the honest handling of irregular expenses. Use when asked build me a budget spreadsheet, t"
    },
    {
     "name": "budget-variance-analysis",
     "description": "Produce a structured budget variance analysis from actual vs budget figures. Use when asked to analyse budget variances, explain underspend or overspend, write a variance commentary, or investigate why actuals differ from plan. Produces a categorised variance table with root cause analysis and manag"
    },
    {
     "name": "bug-diagnosis",
     "description": "Diagnose a bug systematically instead of guessing — reproduce, isolate, form hypotheses, and test them to root cause. Use when debugging, chasing a defect, an intermittent failure, or 'why is this happening?'. Produces a structured diagnosis: a reliable repro, the narrowed-down location, ranked hypo"
    },
    {
     "name": "bug-report",
     "description": "Write a clear, reproducible bug report that gets fixed fast. Use when asked to write a bug report, file a defect, report an issue, or turn 'it's broken' into an actionable ticket. Produces a structured report — a precise title, steps to reproduce, expected vs. actual, environment, severity/priority,"
    },
    {
     "name": "calendar-defrag",
     "description": "Defragment a work calendar through a tool-using agent — find the meeting debt, propose the consolidation, and (approval-gated) execute the moves. Use when asked to defrag my calendar, get me focus time, audit my meetings, or fix my week. Produces the calendar audit (cost per meeting, fragmentation m"
    },
    {
     "name": "candidate-scorecard",
     "description": "Turn interview notes into a structured candidate scorecard and hire recommendation. Use when asked to write an interview scorecard, a candidate evaluation, an interview debrief, or to summarize feedback into a hire/no-hire call. Produces a per-competency assessment with evidence and ratings, an over"
    },
    {
     "name": "cap-table-explainer",
     "description": "Explain a cap table, dilution, SAFEs, option pools, and round mechanics in plain English with the actual math. Use when asked to explain dilution, model a SAFE or priced round, size an option pool, understand a term sheet's economics, or figure out who owns what after a raise. Produces a worked owne"
    },
    {
     "name": "capacity-planning",
     "description": "Produce a capacity planning document for a service covering traffic forecasts, resource requirements, and scaling strategy. Use when asked to plan infrastructure capacity, forecast resource needs, model traffic growth, define scaling strategy, or produce a capacity review for a service. Produces a s"
    },
    {
     "name": "capital-allocation",
     "description": "Allocate a finite budget or headcount across competing initiatives by return and strategic fit. Use when asked to allocate budget, decide where to invest, build a funding/portfolio plan, or make trade-offs across initiatives under a cap. Produces a capital-allocation plan — initiatives scored by exp"
    },
    {
     "name": "car-lease-decoder",
     "description": "Decode a car lease offer — the money factor converted to APR, the cap-cost math, mileage and disposition traps, and what to negotiate. Use when asked to decode my car lease, is this lease deal good, what's a money factor, or review this lease before I sign. Produces the real-numbers decode (money fa"
    },
    {
     "name": "car-tco",
     "description": "Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly payment. Use when asked should I lease or buy a car, is it cheaper to keep my old car, what does this car"
    },
    {
     "name": "carbon-accounting-check",
     "description": "Sanity-check a greenhouse gas inventory before it goes into a report or gets audited. Use when asked to review a carbon footprint, check a GHG inventory, validate scope 1/2/3 numbers, explain a year-over-year emissions change, or prepare emissions data for assurance. Produces a boundary review, data"
    },
    {
     "name": "career-ladder-map",
     "description": "Map where you are against the next level and build a concrete plan to close the gap. Use when asked to map a career ladder, find the gap to the next level, build a development/growth plan, or figure out what to work on to get promoted. Produces a level-gap map — current vs. target competencies side "
    },
    {
     "name": "caregiver-coordination",
     "description": "Organize care for an aging or ill family member across multiple helpers — the shared care map, a fair rotation with backup rules, the information binder, and family-meeting agendas that prevent the one-sibling-does-everything spiral. Use when asked help me coordinate care for my mom, my siblings and"
    },
    {
     "name": "case-for-support",
     "description": "Write a fundraising case for support that makes donors want to give. Use when asked to write a case for support, a fundraising case statement, a major-gift or campaign case, or the core argument for a donation appeal. Produces a persuasive case — the need, your solution and why you, the impact a gif"
    },
    {
     "name": "case-study-writeup",
     "description": "Write a client case study that sells future work — challenge, approach, results. Use when asked to write a case study, a client success story, a project write-up, or a portfolio case for consulting/agency work. Produces a results-led case study — the client & challenge, your approach, quantified out"
    },
    {
     "name": "cash-flow-forecast",
     "description": "Build a short-term (13-week) cash flow forecast to see if you can cover what's due. Use when asked to build a cash flow forecast, a 13-week cash flow, a cash projection, or to plan around a cash crunch. Produces a week-by-week forecast structure — opening cash, expected inflows, scheduled outflows, "
    },
    {
     "name": "category-page-brief",
     "description": "Plan an e-commerce category / collection page that ranks and merchandises well. Use when asked to design a category page, a PLP (product listing page), a collection page, or to improve category SEO and merchandising. Produces a brief — search intent & keywords, intro copy, merchandising/sort logic, "
    },
    {
     "name": "change-management-plan",
     "description": "Create a structured change management plan for any organisational change. Use when asked to write a change management plan, manage a change initiative, plan a system rollout, or lead an organisational transformation. Produces a plan covering stakeholder analysis, impact assessment, communication str"
    },
    {
     "name": "change-order-writer",
     "description": "Draft a defensible construction change order with entitlement basis, scope delta, itemised pricing, and schedule impact. Use when asked to write a change order, price extra work, draft a CO or COR/PCO, respond to a directive for changed work, or paper a field change. Produces a complete change order"
    },
    {
     "name": "changelog-for-humans",
     "description": "Write changelogs and release notes readers actually benefit from — changes translated to so-whats, grouped by reader impact (breaking first, gifts second, plumbing last), with the upgrade path stated and the marketing kept honest. Use when asked write the release notes, turn this commit list into a "
    },
    {
     "name": "changelog-from-commits",
     "description": "Write a human changelog from the REAL commit history — read the actual commit range via the GitHub connector, not a template. Use when asked to write the changelog for this release, what changed since the last tag, draft release notes from my commits, or summarise this range for users in Cowork. Rea"
    },
    {
     "name": "changelog-generator",
     "description": "Convert a git log, commit list, or release notes into a polished, user-facing changelog. Use when writing release notes, generating a CHANGELOG.md entry, or documenting what changed in a version. Produces a structured changelog section with version header, categorised changes, and migration notes. F"
    },
    {
     "name": "changelog-writer",
     "description": "Turn a list of changes, commits, or PRs into clean release notes / a changelog entry. Use when asked to write release notes, a changelog, or a version announcement from raw changes. Produces a Keep-a-Changelog-style entry grouped by type (Added/Changed/Fixed/etc.), written for users — surfacing brea"
    },
    {
     "name": "channel-hygiene",
     "description": "Fix a team's chat sprawl — the channel map with one purpose per channel, the naming scheme that makes purpose findable, the archive pass for the dead and duplicated, and the posting norms (threads, @-discipline, urgency signals) that keep signal findable. Use when asked clean up our Slack/Teams, we "
    },
    {
     "name": "chart",
     "description": "Turn numbers into a chart — bar, line, area, pie, or doughnut. Use when asked to chart or graph data, visualize metrics/trends/breakdowns, or show numbers as a picture instead of a table. Produces a ready-to-render chart spec (renders live in the playground and exports as PNG) plus a one-line read o"
    },
    {
     "name": "chart-choice",
     "description": "Pick the chart the data and the point actually need — the question-to-chart mapping (comparison, trend, composition, distribution, relationship), the honesty rules (axes, baselines, dual-axis traps), and the one-chart-one-point discipline. Use when asked what chart should I use, make this data visua"
    },
    {
     "name": "chart-data-extractor",
     "description": "Extract pixel-level data from an image of a chart or graph and produce a structured data table. Use when asked to extract data from a chart image, transcribe numbers from a graph, digitise a chart, or turn a screenshot of data into a table. Produces a structured table with extracted values, confiden"
    },
    {
     "name": "churn-analysis",
     "description": "Produce a structured churn analysis that separates avoidable from unavoidable churn. Use when investigating why customers are leaving, identifying at-risk segments, calculating net revenue retention, or building a retention intervention plan. Produces a churn report with rate calculations, categoris"
    },
    {
     "name": "cicd-playbook",
     "description": "Write a CI/CD pipeline playbook for a service or team. Use when asked to document a CI/CD pipeline, write a deployment process, define release gates, document build and test stages, or create a deployment guide. Produces a structured playbook covering pipeline stages, environment definitions, deploy"
    },
    {
     "name": "citation-hygiene",
     "description": "Keep citations honest in business documents — every load-bearing claim sourced, links that actually contain the claim, the as-of dates that keep numbers honest, and the internal-vs-external sourcing rules for decks and memos. Use when asked check the sourcing in this deck, add citations to this doc,"
    },
    {
     "name": "claim-denial-decoder",
     "description": "Decode an insurance claim denial letter — what the cited reason actually means, whether it's commonly overturnable, and the appeal letter that answers it point by point. Use when someone asks 'my insurance claim was denied what do I do', 'decode this denial letter', 'can I appeal this denial', or 'w"
    },
    {
     "name": "claims-triage",
     "description": "Triage an incoming insurance claim: check the coverage trigger against policy wording, band severity and complexity, screen for fraud indicators, set a first-pass reserve range, and route with an SLA. Use when asked to triage a claim, review a first notice of loss (FNOL), assess a new claim, decide "
    },
    {
     "name": "claude-superpowers",
     "description": "Activate a 4-stage coding discipline framework that forces Claude to plan before coding, isolate changes on a branch, write tests first, and self-review output twice before presenting it. Use when starting a complex coding task, when past Claude sessions produced broken first drafts, or when you wan"
    },
    {
     "name": "clause-explainer",
     "description": "Explain a contract clause in plain English — what it means, who it favours, the realistic risk, and what to negotiate. Use when asked what a clause means, to decode legal language, explain a term in a contract, or assess whether a provision is standard or aggressive. Produces a plain-language transl"
    },
    {
     "name": "client-discovery",
     "description": "Run a consulting client discovery session — uncover the real problem, scope, and decision process. Use when asked to prepare for a client discovery call, qualify a consulting lead, scope an engagement, or run a kickoff. Produces a discovery plan — the questions that surface the real problem (not the"
    },
    {
     "name": "climate-risk-assessment",
     "description": "Assess physical and transition climate risk for a site, product, or portfolio with scenario-based structure. Use when asked to run a climate risk assessment, evaluate physical or transition risk, prepare TCFD/ESRS-style climate risk analysis, or assess how climate scenarios affect an asset or busine"
    },
    {
     "name": "clinical-case-summary",
     "description": "Write a structured clinical case summary or case presentation. Use when asked to write a clinical case summary, case presentation, patient case report, or clinical handover. Produces a structured summary using SBAR or SOAP format. For educational and documentation purposes only — not a substitute fo"
    },
    {
     "name": "clinical-trial-protocol",
     "description": "Draft a clinical trial protocol synopsis with the elements regulators and IRBs expect. Use when asked to write a clinical trial protocol, a study protocol synopsis, a trial design, or to structure endpoints/eligibility/statistics for an interventional study. Produces a structured protocol synopsis —"
    },
    {
     "name": "closing-disclosure-decoder",
     "description": "Decode a mortgage Closing Disclosure line by line — which fees are real, which are shoppable or junk, and what changed since the Loan Estimate. Use when asked to decode my closing disclosure, review my closing costs, why did my costs go up, or which fees can I negotiate. Produces a section-by-sectio"
    },
    {
     "name": "co-marketing",
     "description": "Plan a co-marketing partnership — two brands reaching each other's audiences for mutual gain. Use when asked to plan a partnership, joint campaign, co-branded content/webinar, integration launch, or partner outreach. Produces the partner fit rationale, a fair value exchange, the joint campaign plan,"
    },
    {
     "name": "code-explainer",
     "description": "Explain what a piece of code does in plain English, at the depth the reader needs. Use when asked to explain code, walk through a function, understand an unfamiliar snippet, or onboard to a file. Produces a one-line summary, a step-by-step walkthrough, the non-obvious parts called out, and any bugs "
    },
    {
     "name": "code-review-checklist",
     "description": "Generate a tailored code review checklist for any pull request based on the language, type of change, and risk level. Use when asked to review code, check a PR, review a pull request, or generate a code review checklist. Produces a focused checklist with language-specific checks, risk-level-appropri"
    },
    {
     "name": "code-review-guide",
     "description": "Review a pull request or diff like a thoughtful senior engineer — prioritized, kind, and focused on what matters. Use when reviewing code, giving PR feedback, or asked to 'review this change'. Produces a structured review: a correctness/design pass, comments ranked by severity (blocking → nit), what"
    },
    {
     "name": "code-simplification",
     "description": "Simplify code that works — remove speculative abstraction, dead flexibility, and needless indirection while keeping behaviour identical and verified. Use after a feature lands ('now simplify it'), when AI-generated code arrives over-engineered, when a file has grown hard to follow, or as the cleanup"
    },
    {
     "name": "cohort-analysis",
     "description": "Structure a cohort analysis for retention, LTV, or behavioural patterns. Use when asked to run a cohort analysis, analyse retention by cohort, segment users by behaviour over time, or calculate lifetime value by acquisition period. Produces a complete cohort analysis framework with methodology, coho"
    },
    {
     "name": "cohort-curve-model",
     "description": "Fit a retention curve to observed cohort data and project LTV — computed, not estimated. Use when someone has real cohort retention numbers (month 0, 1, 2…) and asks what lifetime value, lifetime periods, or long-run retention they imply, or whether retention is flattening or leaking. Produces a fit"
    },
    {
     "name": "cold-email",
     "description": "Write a cold sales/B2B outreach email that earns a reply. Use when asked to write a cold email, a sales outreach email, a prospecting email, or a cold email sequence to a business prospect. Produces a short, personalised email — subject, a relevant opener, one clear value-led ask, and a low-friction"
    },
    {
     "name": "collaboration-contract",
     "description": "Start a cross-team project with the collaboration contract that prevents the classic collisions — who decides what, how work flows between teams, the communication channels and cadence, and what done means — agreed before the first collision instead of during it. Use when asked kick off this cross-t"
    },
    {
     "name": "collections-email",
     "description": "Write a polite-but-firm payment-reminder / collections email sequence for overdue invoices. Use when asked to write a collections email, a payment reminder, a dunning sequence, or to chase an overdue invoice. Produces a staged sequence — gentle pre-due nudge through escalating overdue reminders to a"
    },
    {
     "name": "college-app-parent-guide",
     "description": "Support a teenager through college applications without taking them over — the parent's actual jobs (logistics, finances, emotional ballast), the ownership lines that keep the application theirs, and the scripts for the hard moments. Use when asked how do I help my kid with college apps, how involve"
    },
    {
     "name": "college-cost",
     "description": "Compute what a degree will actually cost — sticker minus real aid, inflated per year, split into cash and loans, with the loan's decade-long monthly tail made visible before enrollment instead of after. Use when asked what will college really cost, compare these two offers' real prices, how much loa"
    },
    {
     "name": "community-management-playbook",
     "description": "Build a community management playbook for a brand's social media channels. Use when asked to create guidelines for managing comments, DMs, and community interactions, define a moderation policy, or build response frameworks for social media community managers. Produces a complete playbook with respo"
    },
    {
     "name": "company-brief",
     "description": "Build a candidate's research brief on a company before an application or interview. Use when asked to research a company for a job, prep a company brief before an interview, or understand a prospective employer fast. Produces a one-page brief — what they do & how they make money, recent news & traje"
    },
    {
     "name": "company-event-ops",
     "description": "Run a company event — the launch party, the customer day, the team celebration — as the operation it is: the goal that shapes every choice, the budget with its forgotten lines, the vendor and venue coordination, the run-of-show with owners, and the day-of roles that keep hosts hosting. Use when aske"
    },
    {
     "name": "comparative-market-analysis",
     "description": "Build a comparative market analysis (CMA) to price a property. Use when asked to do a CMA, a comparative market analysis, price a home, or estimate a property's value from comparables. Produces a structured CMA — the subject property, selected comparables with adjustments, an estimated value range, "
    },
    {
     "name": "competitive-analysis",
     "description": "Analyze competitors and create competitive landscape documentation with feature matrices, positioning maps, and strategic recommendations. Use when asked to analyze competitors, create competitive analysis, compare features with competitors, build a competitive landscape, track competitive positioni"
    },
    {
     "name": "competitive-intelligence-monitor",
     "description": "Monitor competitor signals and surface strategic implications for your roadmap. Use when asked to monitor competitors, track the competitive landscape, produce a competitive briefing, or understand what has changed in the market this week or month. Produces a structured intelligence brief with high/"
    },
    {
     "name": "competitive-scan-lite",
     "description": "Run a fast, honest competitive scan — the dimension table built from public evidence (sites, docs, pricing pages, changelogs, reviews), the claims-vs-observed discipline, and the so-what synthesis that ends in moves, not a landscape mural. Use when asked what are competitors doing, quick scan of the"
    },
    {
     "name": "competitor-signal-tracker",
     "description": "Analyse competitor moves and translate them into strategic implications for your product roadmap. Use when a competitor announces a new feature, pricing change, partnership, or strategic shift, or when producing a periodic competitive intelligence report. Produces a categorised signal analysis with "
    },
    {
     "name": "competitor-teardown",
     "description": "Produce a structured competitive analysis for any product or market. Use when asked for a competitor analysis, competitive teardown, market comparison, SWOT, or positioning map. Generates a structured teardown with positioning map, feature comparison, messaging gaps, and strategic recommendations. F"
    },
    {
     "name": "complaint-letter",
     "description": "Write a firm, effective complaint letter that gets a resolution. Use when asked to write a complaint letter, complain to a company about a product/service, escalate poor service, or demand a refund/replacement. Produces a structured complaint — the facts, the impact, the specific resolution you want"
    },
    {
     "name": "compliance-checklist",
     "description": "Generate a prioritised compliance checklist for GDPR, SOC 2, ISO 27001, FCA, HIPAA, or other frameworks with a gap analysis. Use when asked for a compliance checklist, gap analysis, readiness assessment, or audit preparation for any regulatory framework. Produces a structured checklist with prioriti"
    },
    {
     "name": "conference-talk-proposal",
     "description": "Write a conference talk proposal / CFP submission for a tech or developer conference. Use when asked to submit to a CFP, propose a talk, or write a session abstract. Produces a compelling title, abstract, audience takeaways, an outline, and the speaker pitch — tuned to what selection committees actu"
    },
    {
     "name": "consulting-proposal",
     "description": "Write a consulting proposal that wins the engagement — outcomes over hours. Use when asked to write a consulting proposal, a project proposal, a pitch for a client engagement, or to respond to an RFP. Produces a proposal — the client's problem in their words, your approach & deliverables, outcomes/v"
    },
    {
     "name": "content-calendar",
     "description": "Generate a structured content calendar for any brand, product, or creator. Use when asked for a content plan, editorial calendar, social media schedule, or weekly/monthly content strategy. Produces a calendar with topics, formats, channels, and copy hooks."
    },
    {
     "name": "content-repurposer",
     "description": "Turn one piece of content into a full multi-platform pack — X/Twitter thread, LinkedIn post, newsletter section, Instagram carousel, and a short-form video script — each rewritten natively for its platform, not copy-pasted. Use when asked to repurpose content, atomize a blog post or video, turn one "
    },
    {
     "name": "content-style-guide",
     "description": "Create a content style guide / voice & tone guide so everyone writes consistently. Use when asked to write a content style guide, a voice and tone guide, editorial guidelines, or UX-writing standards. Produces a usable guide — voice principles with do/don't examples, tone-by-context, mechanics (gram"
    },
    {
     "name": "context-budget",
     "description": "Plan a session's context window like the budget it is — what loads up front, what gets linked instead, what stays fetch-on-demand, and how to keep the stable prefix cache-friendly so repeated turns cost cents instead of dollars. Use when asked my agent keeps blowing its context, plan what to load in"
    },
    {
     "name": "context-crusher",
     "description": "Compress tool outputs, logs, and JSON before they enter the context window — structural compression via a deterministic stdlib script (schema + samples + stats instead of 300 raw rows), no API, no summarization loss. Use when asked shrink this tool output, my context is full of JSON, compress these "
    },
    {
     "name": "context-engineering-review",
     "description": "Review what an LLM feature or agent actually puts in its context window — and find what's bloating, missing, or fighting itself. Use when asked to review a system prompt and context assembly, cut token usage without losing quality, debug an agent that ignores instructions, or audit how retrieval res"
    },
    {
     "name": "context-mode",
     "description": "Keep Claude Code sessions productive across resets with output filtering, session logging, and auto-resume. Use when starting a long or complex coding session, when previous sessions lost context mid-task, or when you need Claude to resume exactly where it left off after a reset. Produces a session."
    },
    {
     "name": "context-switch-budget",
     "description": "Treat context switches as the budget line they are — the switch census (how fragmented the week really is), the batching moves that consolidate scattered same-kind work, the calendar defrag that turns Swiss cheese into slabs, and the switch-cost line for saying no. Use when asked my day is fragmente"
    },
    {
     "name": "contract-renewal-tracker",
     "description": "Never get auto-renewed into another year again — the contract inventory with the dates that matter (notice deadlines, not renewal dates), the calendar system with decision-time buffers, and the renewal-decision ritual that renegotiates instead of rubber-stamping. Use when asked track our contracts a"
    },
    {
     "name": "contract-review",
     "description": "Review and summarise any contract or legal agreement. Use when asked to review a contract, check an agreement, flag legal risks, or summarise key clauses. Produces a structured review with key terms, flagged clauses, risk rating, and plain English summary. Not a substitute for qualified legal advice"
    },
    {
     "name": "contributor-guide",
     "description": "Write a CONTRIBUTING guide that helps people contribute to an open-source project without friction. Use when asked to write a CONTRIBUTING.md, set up contribution guidelines, or make a repo welcoming to contributors. Produces a clear guide: how to set up, the contribution workflow, standards, PR exp"
    },
    {
     "name": "conversion-rate-optimization",
     "description": "Audit a landing page or funnel step and produce a prioritised CRO test plan. Use when asked to improve conversion rate, audit a landing/signup/checkout page, reduce funnel drop-off, or plan A/B tests for a page. Produces a CRO plan — a heuristic conversion audit, the diagnosed friction, prioritised "
    },
    {
     "name": "counteroffer-decoder",
     "description": "Decode a counteroffer after you resign — what the raise, promotion promise, or title bump really signals, the statistics-informed risks of staying, and a clear-eyed decision framework. Use when asked my company countered my resignation, should I accept a counteroffer, they offered me more to stay, o"
    },
    {
     "name": "cover-letter",
     "description": "Write a specific, non-generic cover letter that connects your evidence to the role. Use when asked to write a cover letter, an application letter, or a note to accompany a resume. Produces a tight 3–4 paragraph letter — a real hook, two evidence paragraphs mapping your proof to the job's needs, and "
    },
    {
     "name": "coverage-gap-analysis",
     "description": "Map an organisation's risks against its insurance policy portfolio to find what's uncovered, underinsured, or double-covered. Use when asked to run a coverage gap analysis, review an insurance programme against a risk register, check what risks aren't insured, or audit a policy portfolio. Produces a"
    },
    {
     "name": "creator-brand-kit",
     "description": "Define a creator's brand foundation — niche, audience, positioning, content pillars, voice/tone, and bio — so every post is consistent and on-brand. Use when asked to define a creator brand, find a niche, set content pillars, write a voice guide, craft a bio, or build a brand kit for a personal bran"
    },
    {
     "name": "creator-media-kit",
     "description": "Build a creator's sponsorship media kit and brand-deal outreach — the one-pager brands ask for, plus a pitch email and a rate card. Use when asked to make a media kit, pitch a brand, land a sponsorship, write a brand-deal email, or set creator rates. Produces a structured media kit (audience, stats,"
    },
    {
     "name": "credit-memo",
     "description": "Write a credit memo for a lending decision: borrower story, facility structure, repayment sources, financial-ratio spread with covenant headroom, risk factors with mitigants, risk-rating rationale, and a recommendation. Use when asked to write a credit memo, credit application, credit paper, loan wr"
    },
    {
     "name": "crypto-prices",
     "description": "Fetch live cryptocurrency prices with zero API keys — CoinGecko's public endpoints primary, Coinbase spot fallback, via plain curl. Use when asked what's bitcoin at, ETH price in euros, how's the crypto market today, or price of some altcoin. Produces the current price with 24h context, the source a"
    },
    {
     "name": "csat-nps-analysis",
     "description": "Analyse CSAT / NPS / CES survey results and turn the score into actions. Use when asked to analyse NPS, CSAT, or CES data, compute an NPS score, interpret survey verbatims, or build a voice-of-customer readout. Produces a readout — the computed score, the trend & benchmark, themed analysis of the co"
    },
    {
     "name": "currency-rates",
     "description": "Convert currencies and fetch live exchange rates with zero API keys — Frankfurter (ECB rates) primary, open.er-api.com fallback, via plain curl. Use when asked convert 500 dollars to euros, what's the USD-INR rate, how much is this in my currency, or historical exchange rate for a date. Produces the"
    },
    {
     "name": "customer-advisory-board",
     "description": "Plan and run a customer advisory board (CAB). Use when asked to design a customer advisory board, plan a CAB meeting agenda, choose CAB members, or write CAB invitations and follow-ups. Produces a CAB program plan — objectives, member selection criteria, a meeting agenda, discussion guides, roles, l"
    },
    {
     "name": "cs-escalation-brief",
     "description": "Write a structured escalation brief for an at-risk customer account. Use when an account has escalated, when a customer is threatening churn, when a P1 customer issue needs executive attention, or when preparing an internal save play. Produces a crisp escalation brief with account context, timeline,"
    },
    {
     "name": "cs-health-scorecard",
     "description": "Build a customer health scorecard for a specific account. Use when asked to score account health, assess renewal risk, build a health dashboard, or evaluate an account's likelihood to renew or expand. Produces a structured health scorecard with a RAG status, dimension scores, key risks, and recommen"
    },
    {
     "name": "customer-journey-map",
     "description": "Build a customer journey map for a product, service, or experience. Use when asked to map a customer journey, create a user journey, document touchpoints and pain points, or design an experience map. Produces a complete journey map with stages, touchpoints, emotions, pain points, and prioritised opp"
    },
    {
     "name": "customer-outage-notice",
     "description": "Write clear customer-facing outage and service-disruption notifications. Use when asked to write an outage notice, a status-page update, a service-disruption email, a maintenance notice, or an incident update sequence. Produces status-page updates for each phase (investigating → identified → monitor"
    },
    {
     "name": "customer-success-plan",
     "description": "Build a joint customer success plan for a specific account. Use when asked to create a success plan, joint success plan, mutual action plan, or customer onboarding plan. Produces a structured success plan with business goals, milestones, success metrics, ownership, and a 90-180 day roadmap."
    },
    {
     "name": "dashboard-brief",
     "description": "Convert a business question into a complete dashboard specification. Use when asked to design a dashboard, create a dashboard spec or brief, plan a BI report, or define what charts and metrics a dashboard should include. Produces a structured spec with metrics, dimensions, chart types, filters, and "
    },
    {
     "name": "data-analysis-standard",
     "description": "Structure a product data analysis, metric deep-dive, funnel analysis, or cohort study. Use when asked to analyse product metrics, investigate a drop in conversion, explain a data change to stakeholders, or find the root cause of a metric movement. Produces a structured analysis with question, root c"
    },
    {
     "name": "data-breach-response",
     "description": "Respond to your data being breached — triage by what actually leaked, the freeze/rotate/monitor ladder in the right order, and the calibrated watchfulness that follows, without panic or paralysis. Use when someone asks my data was in a breach what do I do, I got a breach notification letter, my SSN/"
    },
    {
     "name": "data-cleaning-pass",
     "description": "Clean a messy dataset methodically — the profiling pass that finds what's actually wrong (dupes, format drift, phantom spaces, mixed types), the fix order that doesn't corrupt while correcting, and the log that makes the cleaning defensible. Use when asked clean this export, why is my pivot double-c"
    },
    {
     "name": "data-contract",
     "description": "Define a data contract between a producer and consumers of a dataset/event/API. Use when asked to write a data contract, define a schema agreement, set data SLAs, or stop a producer from silently breaking downstream consumers. Produces a contract — schema with types & constraints, semantics, quality"
    },
    {
     "name": "data-pipeline-spec",
     "description": "Design an ETL/ELT data pipeline specification. Use when asked to design a data pipeline, spec an ETL or ELT process, document a data ingestion workflow, or plan a data integration. Produces a complete pipeline spec with sources, transforms, destinations, SLAs, error handling, and data quality rules."
    },
    {
     "name": "data-quality-audit",
     "description": "Audit a dataset for the quality problems that silently break analysis — missingness, duplicates, outliers, type and range errors, consistency, and freshness — and produce a prioritised fix list. Use when asked to assess data quality, audit a dataset, check data before analysis, or explain why number"
    },
    {
     "name": "data-quality-checks",
     "description": "Design the data quality checks for a table or pipeline across the standard dimensions. Use when asked to add data quality tests, define DQ checks, catch bad data before it hits dashboards, or set up monitoring for a dataset. Produces a checks plan across completeness, validity, uniqueness, freshness"
    },
    {
     "name": "data-retention-policy",
     "description": "Build a data retention and deletion schedule grounded in legal basis. Use when asked to create a data retention policy, set retention periods, plan data deletion/minimisation, or answer 'how long can we keep this data?'. Produces a retention schedule — data categories with their retention period, le"
    },
    {
     "name": "data-slide-design",
     "description": "Design slides where the data makes the argument — the takeaway-titled chart, the one-chart-per-slide rule, the annotation layer that guides the eye to the point, and the honesty pass on projected data. Use when asked make this data slide land, my chart slide confuses people, how do I present these n"
    },
    {
     "name": "database-migration-plan",
     "description": "Write a safe, zero-downtime database migration plan for a schema change. Use when asked to plan a database migration, design a zero-downtime schema change, document an expand/contract migration, produce a rollback procedure for a database change, or coordinate a database schema update with a deploym"
    },
    {
     "name": "database-schema-design",
     "description": "Document or design a database schema with entity relationships, table definitions, constraints, indexes, and access patterns. Use when asked to design a database, document an existing schema, model entities and relationships, define table structures, plan an index strategy, or produce a data model f"
    },
    {
     "name": "dataset-datasheet",
     "description": "Document a dataset so others know what it is, how it was made, and when not to use it. Use when asked to write a datasheet for a dataset, document training/eval data, or assess whether a dataset is fit for a use. Produces a datasheet — motivation, composition, collection process, preprocessing, reco"
    },
    {
     "name": "daycare-vs-stay-home",
     "description": "Run the real math on a parent leaving work versus paying for childcare — the second income net of daycare, marginal taxes, and work costs, AND the career-trajectory cost of years out, over horizons instead of one brutal year. Use when asked does it make sense for me to keep working, daycare costs my"
    },
    {
     "name": "dbt-model-spec",
     "description": "Spec a dbt model — its grain, sources, transformations, tests, and materialization. Use when asked to design a dbt model, plan a data transformation, write a staging/intermediate/mart model spec, or define dbt tests for a table. Produces a model spec — purpose & grain, lineage (sources → refs), the "
    },
    {
     "name": "debt-payoff",
     "description": "Build a debt payoff plan — avalanche vs snowball simulated month by month on your actual debts, the real payoff dates, and the psychology-vs-arithmetic tradeoff priced in dollars. Use when asked how do I pay off my debts, avalanche or snowball, make me a debt payoff plan, or when will I be debt-free"
    },
    {
     "name": "debt-payoff-plan",
     "description": "Build a debt-payoff plan across multiple debts using the avalanche or snowball method. Use when asked to pay off debt, tackle credit cards/loans, or choose between avalanche and snowball. Produces an ordered payoff schedule, the total interest and time for each method, and a clear recommendation. Ed"
    },
    {
     "name": "debugging-log-analyser",
     "description": "Parse error logs, stack traces, and crash reports into a structured root cause diagnosis. Use when an application is throwing exceptions, crashing, or producing unexpected errors and you need to understand why and what to fix. Produces a structured diagnosis with error classification, stack trace wa"
    },
    {
     "name": "decision-autopsy",
     "description": "Judge a past decision by its PROCESS, not its outcome — because good decisions lose and bad decisions win, and teams that can't tell the difference learn the wrong lessons. Use when reviewing a big call after the fact (a bet that failed, a pass that haunts, a hire, a pivot) and the room is about to "
    },
    {
     "name": "decision-forensics",
     "description": "Reconstruct the decision actually made in a messy Slack, email, or meeting thread into a proper decision record — commitments named, silent assumptions surfaced, non-decisions called out. Use when asked what did we actually decide, turn this thread into a decision record, who committed to what, or r"
    },
    {
     "name": "decision-journal",
     "description": "Record decisions the way good judgment compounds — the reasoning, the alternatives, the probabilities, and what would change your mind, written down BEFORE the outcome arrives, then reviewed against reality. Use when asked help me think through this decision, start a decision journal, review my past"
    },
    {
     "name": "decision-log-setup",
     "description": "Set up the team decision log that ends relitigation — the one-line-per-decision format (what, why, who, when, reopening rule), the capture moments wired into existing rituals, and the lookup habit that makes it pay. Use when asked set up a decision log, we keep re-deciding the same things, where do "
    },
    {
     "name": "decision-meeting-format",
     "description": "Run meetings that actually decide — the pre-read-then-decide format, the options-on-the-table rule, the decider named before debate starts, and the recorded-or-it-didn't-happen close. Use when asked run this decision meeting, we discuss forever and never decide, structure the meeting where we pick t"
    },
    {
     "name": "decision-memo",
     "description": "Write a crisp decision memo that drives a clear decision, not a discussion. Use when asked to write a decision memo, a recommendation memo, a one/six-pager for a decision, or to get leadership to decide something. Produces a decision memo — the decision & recommendation up front, the context, option"
    },
    {
     "name": "deck-autopsy",
     "description": "Autopsy a slide deck from photos or screenshots of its slides — the narrative arc, the numbers, and what each slide is hiding. Use when given slide images (a competitor's pitch, a conference talk, your own deck before a big meeting) and asked what the deck argues, whether it holds up, or how to coun"
    },
    {
     "name": "deck-from-doc",
     "description": "Turn the user's REAL doc into a slide deck — open the source, structure the narrative, and build the actual .pptx — not slide-writing tips. Use when asked to make a deck from this doc, turn my brief into slides, build the presentation from my Drive doc, or deckify this in Cowork. Reads the document "
    },
    {
     "name": "deck-narrative-arc",
     "description": "Give a deck a spine the room can follow — the situation-complication-resolution arc, the tension that makes the recommendation feel necessary, the transitions that carry the thread between slides, and the arc-check that catches sag. Use when asked make this deck flow, my presentation feels like disc"
    },
    {
     "name": "deck-outline-first",
     "description": "Outline a deck as headline sentences before opening the slide tool — each slide a claim that reads as an argument top to bottom, the audience-and-ask header, and the skim test that catches broken decks while they're still bullet points. Use when asked start this presentation, structure my deck, why "
    },
    {
     "name": "deck-review-rubric",
     "description": "Review a deck against a rubric instead of taste — the five dimensions (argument, evidence, density, arc, honesty), the severity-sorted feedback that separates broken from suboptimal, and the review conversation that improves the deck without rewriting it in the reviewer's voice. Use when asked revie"
    },
    {
     "name": "deep-work-blocking",
     "description": "Protect focus time that actually survives the week — the block placement matched to real energy hours, the defense rules (what moves a block, what never), the entry ritual that beats the blank-stare start, and the honest sizing that stops 8-hour fantasy blocks. Use when asked block focus time that k"
    },
    {
     "name": "delay-claim-letter",
     "description": "Draft a construction delay notice or delay claim letter with contract clause citation, cause classification, and critical-path impact narrative. Use when asked to write a delay notice, put the owner or GC on notice of delay, draft a time extension request, respond to weather or owner-caused delay, o"
    },
    {
     "name": "delegation-brief",
     "description": "Delegate so the work comes back right the first time — the brief that transfers outcome, context, and constraints (not just the task), the autonomy level stated explicitly, and the check-in design that catches drift without hovering. Use when asked hand this off properly, my delegations come back wr"
    },
    {
     "name": "delta-briefing",
     "description": "Make a recurring brief report what changed since the last edition instead of restating everything. Use when a weekly or monthly report keeps repeating itself, when setting up a scheduled monitor or digest, or when asked to make a recurring update delta-aware. Produces a changes-first brief plus the "
    },
    {
     "name": "demand-forecast-review",
     "description": "Interrogate a demand forecast before the business commits supply and inventory to it. Use when asked to review a demand plan, challenge a forecast, check forecast accuracy, decompose baseline vs uplift, or find hockey sticks in the numbers. Produces a forecast credibility review with baseline/uplift"
    },
    {
     "name": "demand-letter",
     "description": "Draft a firm, professional demand letter that states the facts, the legal/contractual basis, the specific demand, and a deadline. Use when asked to write a demand letter, send a formal demand for payment, draft a cease-and-desist, or formally request resolution before legal action. Produces a struct"
    },
    {
     "name": "demo-script",
     "description": "Script a product demo that lands — the audience's-workflow storyline (their day, not your feature list), the golden path rehearsed with fallbacks, the wow moment placed early, and the demo-death contingencies (the backup video, the reset state, the narration bridge). Use when asked script our produc"
    },
    {
     "name": "dependency-audit",
     "description": "Audits project dependencies for security vulnerabilities, license compliance issues, outdated packages, and transitive dependency risk. Use when asked to audit dependencies, review package security, check license compliance, assess dependency health, or produce a vulnerability report. Produces a vul"
    },
    {
     "name": "dependency-conflict-resolver",
     "description": "Resolve a dependency or version conflict (npm, pip, yarn, pnpm, Maven, Go modules) step by step. Use when an install fails with peer-dependency or version-conflict errors, packages won't co-exist, or a lockfile is fighting you. Produces the conflict explained, the resolution options ranked by safety"
    },
    {
     "name": "design-critique",
     "description": "Give structured, constructive feedback on any design using UX frameworks. Use when asked to critique a design, review a UI, give feedback on a Figma file or wireframe, assess a user flow, or evaluate a design against UX principles. Produces actionable critique applying Jobs-to-be-Done, Gestalt princ"
    },
    {
     "name": "design-handoff-brief",
     "description": "Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emo"
    },
    {
     "name": "design-system-audit",
     "description": "Audit a design system for consistency, coverage, and quality. Use when asked to audit a design system, review a component library, assess design token coverage, or evaluate the health of a shared design system. Produces a structured audit with a health score, component coverage gaps, token inconsist"
    },
    {
     "name": "desk-research-sprint",
     "description": "Run a timeboxed desk-research sprint that ends with an answer instead of forty tabs — the question decomposition, the source plan by question type, the capture discipline that prevents re-reading, and the stop rule that beats completionism. Use when asked research this market/tool/topic by Friday, I"
    },
    {
     "name": "desktop-zero",
     "description": "Clear the desktop that's become a hundred-icon guilt mosaic — the fast triage that empties it today, the honest read of what the desktop was being used for (it's a to-do list wearing icons), and the replacement systems that keep it clear. Use when asked clean up my desktop, my desktop has 200 files "
    },
    {
     "name": "developer-onboarding-doc",
     "description": "Write a developer onboarding document for a service, codebase, or team. Use when asked to write a developer guide, service README, onboarding doc for a new engineer, codebase orientation, or getting-started guide for a technical team. Produces a structured doc covering service overview, architecture"
    },
    {
     "name": "devils-twin",
     "description": "The strongest possible case AGAINST what you just wrote — argued to win, not to check a box. Use when a document is about to ship and everyone around it already agrees: the twin writes the opposition's best memo (not a critique of yours), so you meet the real counter-argument before your audience do"
    },
    {
     "name": "dictionary-lookup",
     "description": "Look up word definitions, pronunciation, etymology and synonyms with zero API keys — the Free Dictionary API via curl, with honest handling of words it doesn't know. Use when asked define a word, how do you pronounce this, what's the origin of a word, or synonyms for something. Produces the definiti"
    },
    {
     "name": "difficult-conversation",
     "description": "Prepare for and script a hard conversation — conflict, bad news, a boundary, an apology. Use when asked to prepare for a difficult conversation, address a conflict, deliver bad news, confront a colleague, or have a hard talk with a manager/report/peer. Produces a prep brief — the real goal, the othe"
    },
    {
     "name": "digital-legacy-planner",
     "description": "Plan what happens to your digital life — the account inventory, the access plan that doesn't violate terms or law, platform legacy settings, and the memorialize/delete/preserve decisions, written down while it's easy. Use when asked what happens to my accounts when I die, set up a digital legacy pla"
    },
    {
     "name": "disability-insurance-decoder",
     "description": "Decode a disability insurance policy or employer LTD plan — own-occupation vs any-occupation, the benefit math after offsets and taxes, and the definitions that decide whether it pays. Use when someone asks 'is my disability insurance any good', 'decode my LTD policy', 'what does own-occupation mean"
    },
    {
     "name": "disaster-recovery-plan",
     "description": "Write a disaster recovery plan for a service or system — covering RPO/RTO targets, failure scenario runbooks, backup and restore procedures, DR testing cadence, and communication templates. Use when asked to write a DR plan, document failover procedures, create recovery runbooks, define RTO/RPO targ"
    },
    {
     "name": "discharge-summary",
     "description": "Turn a hospital stay into a complete, well-structured discharge summary. Use when asked to write a discharge summary, a hospital discharge note, or to document a patient's admission-to-discharge course for handoff. Produces a standard discharge summary — admission reason, hospital course, diagnoses,"
    },
    {
     "name": "discovery-call-prep",
     "description": "Prepare a structured discovery call plan for any prospect. Use when asked to prepare for a sales call, discovery call, prospect meeting, or first call with a potential customer. Produces a call brief with research, hypotheses, questions, and success criteria."
    },
    {
     "name": "discovery-eyes",
     "description": "Read your team's messages the way opposing counsel would in litigation discovery — prevention training that makes communication hygiene visceral. Use when asked how would our Slack look in discovery, train my team on communication hygiene, review this thread like a plaintiff's lawyer, or what should"
    },
    {
     "name": "discovery-interview-guide",
     "description": "Create a structured user discovery interview guide with screener questions, a discussion guide, and a synthesis framework. Use when planning user interviews, customer discovery sessions, Jobs-to-be-Done research, or problem validation. Produces a complete guide covering warm-up, problem exploration,"
    },
    {
     "name": "dispute-letter",
     "description": "Write a letter to dispute an incorrect charge, bill, or record. Use when asked to dispute a credit-card charge, contest a bill or invoice, challenge a credit-report error, or formally dispute a fee. Produces a clear dispute letter — what's being disputed, why it's wrong, the evidence, and the correc"
    },
    {
     "name": "dns-lookup",
     "description": "Query DNS records and domain registration data with zero API keys — DNS-over-HTTPS via dns.google and domain registration via RDAP, through plain curl. Use when asked what does this domain resolve to, check the MX or TXT records, who registered this domain, when does it expire, or has DNS propagated"
    },
    {
     "name": "doc-restructure-live",
     "description": "Restructure the user's REAL Google Doc — open it, tighten and reorganise it, and return a clean version — not advice on how to edit it. Use when asked to clean up this doc, restructure my draft in Drive, make this readable, or tighten the doc for review in Cowork. Reads the document via the Google D"
    },
    {
     "name": "doc-versioning-discipline",
     "description": "Keep living documents trustworthy over time — the status header (draft/active/superseded) that tells readers what they're holding, the change-log-for-decisions inside the doc, the supersession chain that kills zombie versions, and the review-date heartbeat. Use when asked which version of this doc i"
    },
    {
     "name": "docs-quickstart",
     "description": "Write a 'get started in 5 minutes' quickstart for a tool, library, or API. Use when asked to write a quickstart, getting-started guide, or onboarding docs for developers. Produces a copy-paste-friendly quickstart that takes a developer from zero to a first working result fast, with install, a minima"
    },
    {
     "name": "doctor-visit-prep",
     "description": "Prepare for a doctor's appointment so the 12 minutes actually get used — the symptom timeline in the format clinicians think in, the prioritized question list, and the advocacy scripts for being heard. Use when asked help me prepare for my doctor appointment, what should I tell my doctor, organize m"
    },
    {
     "name": "document-retention-map",
     "description": "Decide what documents to keep, for how long, and where — the personal/small-biz retention map by category (tax, legal, medical, warranties, employment), jurisdiction-flagged periods, and the destruction discipline for what's past its date. Use when asked how long do I keep tax documents, can I shred"
    },
    {
     "name": "donor-update",
     "description": "Write a warm donor update or stewardship message that makes a supporter feel their gift mattered. Use when asked to write a donor update, a thank-you/stewardship email, a supporter newsletter, or a gift acknowledgement. Produces a donor-centred update — sincere thanks, the specific impact of their s"
    },
    {
     "name": "double-opt-in-intro",
     "description": "Make introductions that respect both sides — the double-opt-in flow (ask each party privately before connecting them), the forwardable blurb that makes saying yes easy, and the connecting email that sets both up to succeed. Use when asked introduce me to someone, can you connect us, write an intro e"
    },
    {
     "name": "downloads-triage",
     "description": "Empty the Downloads folder that's become a junk drawer — the four-bucket pass (file, delete, action, quarantine), the age-based bulk rules that make 2,000 items tractable, and the tiny habit that keeps it empty. Use when asked clean up my downloads folder, 2000 files in downloads help, what's safe t"
    },
    {
     "name": "earthquake-watch",
     "description": "Check recent earthquakes worldwide with zero API keys — USGS real-time GeoJSON feeds via curl, filtered by magnitude, region, and time window. Use when asked was there an earthquake just now, recent quakes near a place, any big earthquakes today, or monitor seismic activity somewhere. Produces the m"
    },
    {
     "name": "elder-scam-briefing",
     "description": "Protect aging parents from the scams that target them — the conversation that doesn't condescend, the family code word, the top patterns aimed at seniors, and the guardrails that help without taking over. Use when asked how do I talk to my parents about scams, my mom almost sent money to someone, se"
    },
    {
     "name": "email-agent-preflight",
     "description": "Run the pre-flight checklist before an agent touches an inbox — the read-vs-send permission line, the injection-in-email-body threat, the send-guard rules, and the blast-radius limits that keep a compromised agent from mailing the company. Use when asked let my agent read/send email safely, set up g"
    },
    {
     "name": "email-campaign",
     "description": "Write and sequence multi-email nurture or launch campaigns. Use when asked for an email sequence, drip campaign, onboarding emails, product launch emails, or nurture flow. Produces subject lines, preview text, full email body, and send-timing recommendations for each email in the sequence."
    },
    {
     "name": "email-sequence",
     "description": "Write a multi-email nurture/onboarding/launch sequence with a goal per email. Use when asked to write an email sequence, a welcome/onboarding series, a nurture drip, a launch sequence, or a re-engagement series. Produces the sequence map (trigger, timing, goal per email) plus the full copy for each "
    },
    {
     "name": "email-to-tasks",
     "description": "Convert an email (or a whole thread) into real tasks — the actual asks extracted from the prose, each with owner, deadline, and the done-test, so nothing lives in the inbox as its own reminder. Use when asked what am I actually being asked to do here, turn this thread into a task list, extract the a"
    },
    {
     "name": "email-triage",
     "description": "Triage a Gmail inbox down to only what needs you. Use when asked to triage email, clear an inbox, find what needs a reply, or summarise recent mail. Produces a prioritised list of items needing action — replies, decisions, follow-ups — for a configurable window (default last 8 hours), filtering out "
    },
    {
     "name": "email-triage-system",
     "description": "Turn an overflowing inbox into a four-verb system — archive, reply-now, task, or park — with the two-minute rule enforced and a daily cadence that survives busy weeks. Use when asked help me get to inbox zero, my email is out of control, build me an email triage system, or process this backlog. Prod"
    },
    {
     "name": "emergency-fund",
     "description": "Size an emergency fund from essential spend and real risk factors — not a one-size 'six months' — with the funding timeline and where the money should sit. Use when asked how big should my emergency fund be, do I have enough saved, emergency fund or invest, or how many months of expenses do I need. "
    },
    {
     "name": "employee-engagement-survey",
     "description": "Design an employee engagement survey and analyse results. Use when asked to create an employee survey, engagement questionnaire, pulse survey, or eNPS survey. Also use when asked to analyse survey results. Produces a complete survey with questions, rating scales, and an analysis framework."
    },
    {
     "name": "empty-state-writer",
     "description": "Write empty-state content that turns a blank screen into a next step. Use when asked to write an empty state, a zero-data / first-run state, a no-results state, or onboarding placeholder content. Produces empty-state copy — a clear headline, a helpful line, and a primary action — for each type (firs"
    },
    {
     "name": "energy-scheduling",
     "description": "Schedule work by energy, not just time — the week of self-observation that maps your real peaks and troughs, the work-to-energy matching (hard creative work on peaks, admin on slopes, meetings on shoulders), and the calendar rebuild that honors the map. Use when asked when should I do my hardest wor"
    },
    {
     "name": "engagement-retro",
     "description": "Run a close-out retrospective on a client engagement — capture lessons, results, and the renewal/referral path. Use when asked to wrap up a client project, run an engagement retro, write a project close-out, or plan the follow-on. Produces a close-out — outcomes vs. goals, what worked / what didn't,"
    },
    {
     "name": "engineering-hiring-rubric",
     "description": "Build an engineering hiring rubric and technical interview scorecard for evaluating software engineers at a specific level. Use when asked to create an interview rubric, design a hiring process, build a technical scorecard, or standardize engineer evaluation. Produces a full interview scorecard, beh"
    },
    {
     "name": "engineering-weekly-report",
     "description": "Write a weekly engineering status report for a team, service, or initiative. Use when asked to write a team update, weekly engineering report, sprint status email, or standing team communication to stakeholders. Produces a concise, scannable weekly report covering shipping progress, metrics, decisio"
    },
    {
     "name": "entity-relationship-diagram",
     "description": "Turn a data model into an entity-relationship (ER) diagram. Use when asked to design a schema, model data, show how tables/entities relate, or diagram a database. Produces a ready-to-render Mermaid ER diagram (renders live, exportable as PNG/SVG) plus key attributes, cardinality, and design notes."
    },
    {
     "name": "error-decoder",
     "description": "Decode an error message or stack trace into a plain-English cause, the exact fix, and how to prevent it. Use when asked to explain an error, debug a stack trace, figure out why code is throwing, or make sense of a cryptic exception. Produces a structured diagnosis: what the error means, the most lik"
    },
    {
     "name": "error-message-writer",
     "description": "Write clear, helpful error messages that tell users what happened and how to fix it. Use when asked to write an error message, validation text, a failure/empty-error state, or to rewrite a cryptic system error. Produces human, blame-free error copy — what went wrong, why (if useful), and the next st"
    },
    {
     "name": "escalation-email",
     "description": "Escalate an issue up the chain without burning the person you're escalating past — the facts-first structure, the tried-already section that earns the escalation, and the specific ask that makes action easy. Use when asked I need to escalate this, write an email to my boss's boss, this vendor issue "
    },
    {
     "name": "escalation-tree",
     "description": "Design a support/incident escalation tree — who handles what, when it escalates, and to whom. Use when asked to design an escalation path, an escalation matrix, support tiers, an on-call escalation policy, or to fix 'tickets bounce around / nothing gets escalated in time'. Produces an escalation tre"
    },
    {
     "name": "esg-disclosure-draft",
     "description": "Draft an honest, audit-ready ESG disclosure section in a CSRD/ESRS-flavored structure, adaptable to other frameworks. Use when asked to write a sustainability report section, draft an ESRS or CSRD disclosure, prepare an ESG section for an annual report, or turn raw sustainability data into disclosur"
    },
    {
     "name": "estate-settlement-organizer",
     "description": "Organize an executor's work — the settlement ladder from will-to-probate-to-distribution, the asset/debt inventory, the creditor and beneficiary communications, and the records that keep an executor protected. Use when asked I'm the executor what do I do, organize settling an estate, what's the prob"
    },
    {
     "name": "eulogy-writer",
     "description": "Help someone write a eulogy — the hardest writing most people ever do, at the worst possible time. Use when someone must speak at a funeral or memorial and doesn't know where to start, or has fragments and no shape. Produces a 3-5 minute eulogy built from their memories in their voice, plus a delive"
    },
    {
     "name": "ev-vs-gas",
     "description": "Compare an EV against a comparable gas car on total cost — upfront gap after incentives, energy vs fuel per year, maintenance delta, and the crossover year when the EV pulls ahead (or doesn't). Use when asked is an EV worth it, EV vs gas total cost, when does an EV pay for itself, or should my next "
    },
    {
     "name": "eval-rubric-designer",
     "description": "Design a scoring rubric and LLM-as-judge prompt to evaluate the quality of an AI feature's output. Use when asked to create an eval rubric, define quality dimensions, build an LLM judge, or decide how to measure whether AI output is good. Produces a rubric with weighted dimensions and concrete 1–5 a"
    },
    {
     "name": "evidence-grading",
     "description": "Grade the evidence behind a claim before betting on it — the hierarchy for business evidence (experiments > usage data > surveys > interviews > anecdotes > opinion), the fit-for-decision test, and the mixed-evidence verdicts that real questions produce. Use when asked how strong is our evidence for "
    },
    {
     "name": "evidence-lock",
     "description": "Write or rewrite a document in evidence-locked mode: no unsourced sentences — every substantive claim carries a footnote citing the exact passage in the user's provided sources, and anything unsupportable is explicitly marked. Use when asked to make a document fully sourced, add citations from my do"
    },
    {
     "name": "evt-dvt-pvt-gate-review",
     "description": "Run an NPI phase-gate review for EVT, DVT, or PVT — exit criteria per phase, open-issue triage, yield readout, waiver discipline, and a go/no-go call. Use when asked to run a gate review, decide EVT exit or DVT entry, review build results, assess whether to proceed to the next build, or triage open "
    },
    {
     "name": "exam-prep-planner",
     "description": "Build a realistic exam-prep schedule with spaced repetition and retrieval practice — the plan that survives contact with an actual week. Use when asked to plan my exam prep, make a study schedule, I have N weeks until finals, or how do I study for multiple exams. Produces a day-by-day plan across al"
    },
    {
     "name": "excel-model",
     "description": "Build a real, formula-driven Excel (.xlsx) model — not a static table. Use when asked to build an Excel model, a financial model, a budget/forecast spreadsheet, or any .xlsx with live formulas a user can edit. Produces an actual .xlsx file via a generated openpyxl script: an inputs/assumptions sheet"
    },
    {
     "name": "exec-vs-working-deck",
     "description": "Stop presenting the working deck to executives — the two-deck split (answer-first exec cut vs. exploration-rich working deck), the compression rules from 40 slides to 8, and the appendix strategy that keeps the depth one click away. Use when asked turn this analysis into an exec version, my leadersh"
    },
    {
     "name": "executing-plans",
     "description": "Execute a written plan with discipline — verify each step before advancing, surface deviations instead of improvising around them, and keep a visible execution log. Use when working through a plan (yours or another agent's), resuming multi-session work, or when execution keeps drifting from what was"
    },
    {
     "name": "executive-presence",
     "description": "Sharpen how you show up in high-stakes rooms — communicate with gravitas, concision, and confidence. Use when asked to improve executive presence, prepare to present to leadership, sound more senior, command a room, or get coaching before a big meeting. Produces specific guidance — how to open, stru"
    },
    {
     "name": "executive-summary",
     "description": "Write an executive summary for any document, report, or proposal. Use when asked to write an executive summary, management summary, briefing paper, or one-pager for senior stakeholders. Produces a structured summary that busy executives can read in under 3 minutes and act on."
    },
    {
     "name": "executive-update",
     "description": "Transform detailed product updates into concise executive briefings. Use when asked to write an executive update, leadership update, product update for the exec team, or a C-suite product briefing. Produces a structured 250-word briefing with headline, key metrics, progress, risks, decisions needed,"
    },
    {
     "name": "exit-interview-strategy",
     "description": "Walk into an exit interview knowing what it's for, what to say, and what to keep — honest-but-strategic answers that protect references and leave the door open. Use when asked what do I say in my exit interview, should I be honest in my exit interview, prep me for my exit interview, or is the exit i"
    },
    {
     "name": "exit-waterfall",
     "description": "Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses. Use when asked to model an exit waterfall, what do I get if we sell for X, explain liquidation preferences on my cap table, or compare payouts across exit "
    },
    {
     "name": "expense-audit",
     "description": "Audit spending to find leaks — recurring subscriptions, creep, and cuttable costs — ranked by impact. Use when asked to cut expenses, review subscriptions, find where money is going, or free up cash. Produces a categorized spend breakdown, a ranked list of cuts with dollar amounts, and the annualize"
    },
    {
     "name": "expense-discipline",
     "description": "Submit expenses that sail through approval — the capture-at-spend habit, the policy-fluency that prevents rejections (thresholds, receipt rules, the pre-approval traps), the report assembled in minutes, and the approver-side rules for reviewing fairly and fast. Use when asked my expense reports are "
    },
    {
     "name": "expense-filer",
     "description": "Turn a pile of receipts into a filed expense report through a tool-using agent — extraction, policy checks, and categorization done for you; submission gated on your approval. Use when asked to file my expenses, process these receipts, build my expense report, or expense this trip. Produces the item"
    },
    {
     "name": "expense-policy",
     "description": "Write a clear company expense & reimbursement policy. Use when asked to write an expense policy, a reimbursement policy, a travel & expense (T&E) policy, or spending guidelines. Produces a practical policy — what's covered, limits by category, the approval and submission process, timelines, and what"
    },
    {
     "name": "expense-sheet-design",
     "description": "Design an expense-tracking sheet that survives real receipts — the capture-at-spend habit, the category set that matches reimbursement or tax rules, the receipt-link discipline, and the month-end close that takes minutes because the work happened at spend-time. Use when asked track my business expen"
    },
    {
     "name": "experiment-designer",
     "description": "Design statistically rigorous A/B tests and interpret experiment results. Use when asked to design an experiment, run an A/B test, calculate sample size, interpret test results, or assess whether an experiment was successful. Produces a complete experiment design with hypothesis, sample size, run ti"
    },
    {
     "name": "experiment-readout",
     "description": "Analyse a finished A/B test and write an honest results readout with real statistics. Use when asked to read out an A/B test, analyse experiment results, check if a result is statistically significant, or decide ship/no-ship from test data. Produces a readout — the computed lift, p-value & confidenc"
    },
    {
     "name": "expert-interview-prep",
     "description": "Get the most from an hour with an expert — the do-your-homework floor (never ask what's googleable), the question arc from calibration to the frontier, the follow-up discipline that goes deep instead of wide, and the capture that survives the call. Use when asked prep me for the expert call, what sh"
    },
    {
     "name": "exploratory-test-charter",
     "description": "Write session-based exploratory testing charters to find what scripted tests miss. Use when asked to plan exploratory testing, write a test charter, design a testing session, or do risk-based exploration of a feature. Produces focused charters — a mission, areas/risks to explore, tactics and oracles"
    },
    {
     "name": "factory-acceptance-test",
     "description": "Write a factory acceptance test (FAT) plan or report — test coverage matrix against spec, AQL sampling plan, pass/fail criteria, golden-sample handling, deviation log, and sign-off structure. Use when asked to write a FAT plan, define outgoing quality inspection, set AQL levels, prepare for a factor"
    },
    {
     "name": "faq-builder",
     "description": "Build an FAQ from the questions people actually ask — mined from tickets, chats, and repeated explanations, answered once and well, organized by the asker's words, and maintained by a capture loop instead of annual archaeology. Use when asked create an FAQ for this product/process/team, I answer the"
    },
    {
     "name": "feature-flag-guide",
     "description": "Write a feature flag management guide and lifecycle playbook for a service or team — covering flag taxonomy, creation checklist, rollout strategy, monitoring requirements, cleanup policy, and governance. Use when asked to document feature flag practices, create a flag rollout plan, write a feature f"
    },
    {
     "name": "feature-prioritisation",
     "description": "Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items. Use when asked to prioritise features, rank a backlog, decide what to build next, or evaluate tradeoffs between competing ideas. Produces a scored, ranked feature list with framework-sp"
    },
    {
     "name": "feature-sunset-plan",
     "description": "Plan the retirement of a product feature — the kill decision made honest, user migration, data handling, comms sequencing, and the code actually deleted. Use when deprecating or sunsetting a feature, killing an underused capability, retiring an AI feature that didn't land, or when a 'deprecated' fea"
    },
    {
     "name": "figma-annotation-guide",
     "description": "Generate structured developer handoff annotations for a Figma screen or component. Use when asked to write Figma annotations, create dev handoff notes, document a Figma design for developers, or write specs for a screen. Produces a complete annotation set covering interactions, states, spacing, acce"
    },
    {
     "name": "figma-component-audit",
     "description": "Audit a Figma component library for consistency, coverage gaps, and naming issues. Use when asked to audit components, review a design system, check component consistency, identify missing components, or assess Figma library health. Produces a structured audit report with issues prioritised by impac"
    },
    {
     "name": "figma-design-brief",
     "description": "Write a structured design brief for a Figma design task from a product requirement or feature request. Use when asked to write a design brief, create a design spec for Figma, turn a PRD into design requirements, or brief a designer on what to build in Figma. Produces a brief with goals, scope, user "
    },
    {
     "name": "figma-design-critique-pm",
     "description": "Runs a PM-perspective design critique focused on product outcomes and user goals, not aesthetics. Use when asked for a PM design critique, a product review of a Figma design, or feedback from a product perspective without needing to be a designer. Produces structured outcome-based feedback tied to u"
    },
    {
     "name": "figma-design-qa",
     "description": "Runs a pre-handoff QA checklist on a Figma design before it goes to engineering. Use when asked to QA a Figma design, do a pre-handoff check, or validate a Figma file is ready to build. Produces a structured QA report covering file hygiene, component usage, accessibility, and handoff readiness with "
    },
    {
     "name": "figma-design-review",
     "description": "Runs a structured PM design review against product requirements. Use when asked to review a Figma design, check a design against requirements, or assess whether a design meets the product spec. Produces a requirements coverage check, UX concerns, open questions, and an explicit approval status — app"
    },
    {
     "name": "figma-prototype-plan",
     "description": "Plan prototype interactions and flows for user testing in Figma. Use when asked to plan a Figma prototype, set up prototype interactions, define what to prototype for a user test, or prepare a Figma prototype for usability testing. Produces a prototype scope, interaction specification, test task scr"
    },
    {
     "name": "figma-spacing-system",
     "description": "Design a spacing and layout token system for a Figma design system. Use when asked to create a spacing system, define layout tokens, set up a grid system, build a spacing scale, or establish layout foundations for a Figma file. Produces a complete spacing scale, grid definition, component spacing co"
    },
    {
     "name": "figma-user-flow-planner",
     "description": "Plan user flows and screen states for a Figma design before any designing starts. Use when asked to plan a user flow, map out screens for a feature, define screen states, plan a Figma file structure, or work out what needs to be designed before opening Figma. Produces a complete flow map with all sc"
    },
    {
     "name": "figma-variant-matrix",
     "description": "Define component variants and states systematically for Figma. Use when asked to plan component variants, define states for a component, set up a Figma variant matrix, or work out what properties a component needs before building it. Produces a complete variant matrix with all properties, values, an"
    },
    {
     "name": "file-access-preflight",
     "description": "Run the pre-flight checklist before an agent gets filesystem access — the scope boundary (which directories, read vs write), the secrets-exposure sweep, the destructive-operation gates, and the path-traversal and untrusted-file defenses. Use when asked let my agent access my files safely, is it safe"
    },
    {
     "name": "filename-convention",
     "description": "Set a filename convention that sorts, searches, and survives — date-first ISO format, the descriptor grammar, version suffixes that end the FINAL-final2 era, and the rollout that gets a team actually using it. Use when asked set up file naming rules, our filenames are chaos, what should we call our "
    },
    {
     "name": "financial-aid-appeal",
     "description": "Write a financial-aid appeal or scholarship request letter that aid offices act on — factual, documented, and specific about the ask. Use when asked to appeal my financial aid, write a scholarship letter, ask for more aid after circumstances changed, or respond to an aid decision. Produces the appea"
    },
    {
     "name": "financial-due-diligence",
     "description": "Generate a financial due diligence checklist and analysis framework for any investment, acquisition, or partnership. Use when asked for a due diligence checklist, M&A financial review, investment analysis framework, or vendor financial assessment. Produces a document request list, key analytical que"
    },
    {
     "name": "financial-model-narrative",
     "description": "Turn financial model outputs into a clear written narrative. Use when asked to write a financial narrative, explain a financial model, summarise a P&L, or translate spreadsheet numbers into a board-ready story. Produces an executive narrative with key insights, drivers, and forward-looking commentar"
    },
    {
     "name": "financial-statement-explainer",
     "description": "Explain a financial statement (P&L, balance sheet, or cash flow) in plain English. Use when asked to explain a P&L / income statement, a balance sheet, a cash flow statement, or to make financials understandable to a non-finance reader. Produces a plain-language walkthrough — what each section means"
    },
    {
     "name": "fine-appeal-letter",
     "description": "Appeal a parking ticket, penalty charge, or administrative fine with the grounds that actually get appeals granted — not indignation. Use when someone got a ticket/fine/penalty notice and either has a legitimate case or wants an honest read on whether they do. Produces a short formal appeal letter b"
    },
    {
     "name": "fire-number",
     "description": "Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer. Use when asked what's my FIRE number, when can I retire early, how much do I need to be financially independent, or "
    },
    {
     "name": "first-client-contract",
     "description": "Put your first client agreement in writing — the eight clauses a simple service contract must have, in plain language a non-lawyer can use, with the blanks filled from your actual deal. Use when asked write my first client contract, what should a freelance agreement include, my client wants to start"
    },
    {
     "name": "flight-tracker",
     "description": "Track live aircraft positions with zero API keys — adsb.lol's open ADS-B network primary, OpenSky fallback, via curl: by callsign, registration, or area. Use when asked where is this flight right now, what planes are overhead, track a tail number, or is that flight in the air. Produces the live posi"
    },
    {
     "name": "flowchart",
     "description": "Turn a process, workflow, or decision logic into a clean flowchart. Use when asked to diagram a process, map a workflow, visualize steps/branches, or show 'how this works' as a chart. Produces a ready-to-render Mermaid flowchart (renders live in the playground, exportable as PNG/SVG) plus a short le"
    },
    {
     "name": "foia-request",
     "description": "Draft a public-records request (FOIA / FOI / state open-records) that's specific enough to get records and hard to deny. Use when asked to write a FOIA request, records request, or freedom-of-information request to a government body. Produces a properly-scoped request: the records sought, date range"
    },
    {
     "name": "folder-structure-designer",
     "description": "Design a folder structure people actually file into — shallow, purpose-first, with a home for everything and an inbox for the undecided, sized to the team that must maintain it. Use when asked organize our shared drive, design a folder structure for the project, where should things live, or our file"
    },
    {
     "name": "follow-up-chaser",
     "description": "Chase unanswered emails without being annoying — the escalating-gently sequence with timing rules, the re-ask that makes replying easy, and the close-the-loop discipline that ends zombie threads. Use when asked they haven't replied what do I send, write a follow-up that isn't pushy, how long do I wa"
    },
    {
     "name": "follow-up-sequence",
     "description": "Write the follow-up messages that keep a candidate on the radar without being annoying. Use when asked to write a post-interview thank-you, a follow-up after no reply, a nudge on a stalled application, or a check-in sequence during a job search. Produces a timed sequence — what to send, when, and th"
    },
    {
     "name": "followup-sweep",
     "description": "Sweep the user's REAL mail and calendar for dropped balls — threads awaiting their reply, promises they made, and replies they're owed — then draft the nudges. Use when asked what am I forgetting, what have I not replied to, who owes me a reply, or chase my open threads in Cowork. Reads sent/receive"
    },
    {
     "name": "form-filler-operator",
     "description": "Fill long web forms and applications through a computer-use agent — from a fact sheet you approve, field by field, with a full transcript and nothing submitted without your word. Use when asked to fill this application for me, complete this government/vendor/insurance form, or do this registration. "
    },
    {
     "name": "formula-detangler",
     "description": "Untangle the spreadsheet formula nobody dares touch — decompose the seven-function nest into named readable steps, explain what it actually does (vs. what it's believed to do), and rebuild it maintainably with helper columns and modern functions. Use when asked what does this formula do, this IFERRO"
    },
    {
     "name": "founder-market-fit",
     "description": "Articulate founder-market fit — the why-you and why-now story investors and accelerators (YC-style) probe hardest. Use when asked to write the founder story, answer 'why are you the right team', draft YC / accelerator application answers, or explain founder-market fit. Produces a sharp narrative con"
    },
    {
     "name": "freelance-rate",
     "description": "Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000. Use when asked what should I charge as a freelancer, how do I set my consulting rate, why is my freelanc"
    },
    {
     "name": "frontend-design",
     "description": "Produce frontend UI that actually looks designed — a working spacing/type system, deliberate color use, real states, and restraint — instead of the generic AI-generated interface. Use when asked to build or restyle a UI, landing page, dashboard, or component, when output 'works but looks like a prot"
    },
    {
     "name": "fundraising-faq",
     "description": "Pressure-test a fundraise by anticipating the hard investor questions and arming the founder with crisp answers. Use when asked to prep for investor Q&A, anticipate due-diligence questions, handle pushback on a raise, or build a fundraising FAQ. Produces the toughest questions an investor will ask —"
    },
    {
     "name": "gantt-roadmap",
     "description": "Turn a plan or set of milestones into a timeline / Gantt chart. Use when asked to build a roadmap, schedule phases, show a project timeline, or visualize what happens when. Produces a ready-to-render Mermaid Gantt chart (renders live, exportable as PNG/SVG) — and, because it has real dates, the resu"
    },
    {
     "name": "gdpr-compliance",
     "description": "Assess GDPR compliance and build the core records (ROPA, lawful basis, DSAR, DPIA triggers). Use when asked to get GDPR-compliant, build a Record of Processing Activities, decide a lawful basis, handle data-subject requests, or check whether a DPIA is needed. Produces a GDPR assessment — a ROPA, law"
    },
    {
     "name": "git-troubleshooter",
     "description": "Diagnose a tangled git situation and give the exact, safe commands to fix it. Use when asked to undo a commit, recover lost work, fix a bad merge or rebase, resolve a detached HEAD, unstage files, or get out of a git mess. Produces the diagnosis, the precise commands to run in order, what each does,"
    },
    {
     "name": "github-repo-vitals",
     "description": "Read a GitHub repository's vital signs with keyless curl — commit recency, release cadence, issue/PR responsiveness, and bus factor — interpreted into an is-this-project-alive verdict. Use when asked is this repo maintained, check this project before we build on it, how active is this library's deve"
    },
    {
     "name": "giving-feedback",
     "description": "Turn a vague concern into specific, kind, actionable feedback. Use when asked to give feedback, write a feedback note, prepare to tell someone something hard about their work, or coach a report/peer. Produces ready-to-deliver feedback structured on situation–behaviour–impact, separating observation "
    },
    {
     "name": "glossary-builder",
     "description": "Build a translation/terminology glossary so a product's key terms render consistently everywhere. Use when asked to create a glossary, a termbase, a do-not-translate list, or to keep terminology consistent across translators/locales. Produces a glossary — each source term with its approved translati"
    },
    {
     "name": "go-to-market",
     "description": "Create go-to-market assets for any product or feature. Use when asked for a GTM plan, positioning statement, product launch plan, messaging pillars, use cases, or feature/benefit list. Produces a full GTM pack: positioning statement, messaging pillars, feature-to-benefit mapping, and role-specific u"
    },
    {
     "name": "go-to-market-planner",
     "description": "Build a go-to-market plan for any product launch, feature release, or new market entry. Use when planning a product launch, writing a GTM strategy, defining launch tiers, or coordinating cross-functional launch activities. Produces a tiered GTM plan with messaging, cross-functional activity tracker,"
    },
    {
     "name": "grant-proposal",
     "description": "Write a structured grant proposal or funding application for any grant type. Use when asked to write a grant proposal, funding application, research grant, charitable grant, or innovation fund application. Produces a complete proposal with project summary, rationale, methodology, impact, and budget "
    },
    {
     "name": "greenwashing-self-audit",
     "description": "Audit your own marketing and report claims for greenwashing risk before a regulator, journalist, or competitor does. Use when asked to review sustainability claims, check marketing copy for greenwash, audit environmental claims on a website or report, or pressure-test green messaging. Produces a cla"
    },
    {
     "name": "growth-experiment-backlog",
     "description": "Build and prioritise a growth experiment backlog. Use when asked to plan growth experiments, prioritise growth ideas, set up a test backlog, or run a growth process/sprint. Produces a prioritised backlog — each experiment as a hypothesis with the metric it moves, an ICE/PXL score, the minimum test d"
    },
    {
     "name": "handbook-page",
     "description": "Write the handbook page that ends the repeated explanation — the answer-shaped structure (task-first, context second), the ownership and freshness header, and the write-once-point-forever discipline that turns tribal knowledge into infrastructure. Use when asked document how we do X, write the wiki "
    },
    {
     "name": "hardware-prd",
     "description": "Write a PRD for a physical hardware product — target cost (BOM and landed), industrial design constraints, regulatory certifications, reliability targets, serviceability, packaging, and forecast assumptions. Use when asked to write a hardware PRD, spec a new device, define requirements for a physica"
    },
    {
     "name": "headline-options",
     "description": "Generate and pressure-test headline options across proven formulas. Use when asked for headlines, a title, a subject line, a hook, or to improve a weak headline for a page, post, email, or ad. Produces 10–15 headline options grouped by formula (benefit, how-to, number, question, curiosity, social pr"
    },
    {
     "name": "help-center-article",
     "description": "Write a help-center / knowledge-base article that actually resolves the issue and deflects tickets. Use when asked to write a help doc, KB article, FAQ entry, how-to, or support documentation. Produces a findable, skimmable article — task-based title, the answer up front, numbered steps, screenshots"
    },
    {
     "name": "hipaa-safeguards",
     "description": "Map HIPAA Security Rule safeguards and run a risk analysis for systems handling PHI. Use when asked to become HIPAA-compliant, assess HIPAA safeguards, prepare for handling PHI/ePHI, or scope a BAA. Produces a HIPAA assessment — the administrative/physical/technical safeguards with required-vs-addre"
    },
    {
     "name": "hiring-rubric",
     "description": "Generate a structured interview scorecard and interview guide for any role. Use when asked to create a hiring rubric, interview scorecard, structured interview guide, or assessment criteria for a job. Produces a scorecard with competencies, behavioural questions, and scoring guidance."
    },
    {
     "name": "hn-digest",
     "description": "Pull the current Hacker News front page, top comments, or a topic search with zero API keys — the official Firebase API and Algolia search via curl, digested instead of dumped. Use when asked what's on Hacker News, summarize HN today, what's the discussion on this story, or has HN covered some topic"
    },
    {
     "name": "hoa-decoder",
     "description": "Decode HOA covenants (CC&Rs) and the fee structure before you buy into them. Use when someone asks 'what do these HOA rules actually mean', 'decode these CC&Rs', 'is this HOA going to be a problem', or 'what should I check before buying in an HOA'. Produces a restriction decode ranked by lifestyle i"
    },
    {
     "name": "home-contractor-quote-decoder",
     "description": "Decode a home renovation or repair quote — allowances that aren't prices, exclusions that become change orders, payment schedules that shift risk, and what a comparable-bids check should cover. Use when someone asks 'is this contractor quote fair', 'decode this renovation bid', 'what should be in a "
    },
    {
     "name": "hook-writer",
     "description": "Generate scroll-stopping hooks — the first line of a post, thread, video, or email that decides whether anyone keeps reading. Use when asked to write a hook, an opener, a first line, a thread starter, a video cold-open, or to make something more clickable. Produces multiple distinct hook options acr"
    },
    {
     "name": "house-style-enforcer",
     "description": "Apply a team's writing style consistently — extract the house style from exemplar documents into a checkable rule card, run the conformance pass on new drafts, and fix violations without flattening the author's voice. Use when asked make this match our style, why do our docs all sound different, bui"
    },
    {
     "name": "human-in-the-loop-design",
     "description": "Design the human approval surface for an agent system — which actions gate, how approvals batch without becoming rubber stamps, and what the audit trail must hold. Use when asked to add human oversight to an agent, design approval workflows for AI actions, decide what an agent may do autonomously, o"
    },
    {
     "name": "i18n-readiness-review",
     "description": "Review a product/codebase for internationalization readiness before you localize. Use when asked if a product is ready to localize, to review i18n readiness, find hard-coded strings/locale bugs, or prep for going multilingual. Produces a readiness audit — externalized strings, locale-aware formattin"
    },
    {
     "name": "iep-504-meeting-kit",
     "description": "Walk into an IEP or 504 meeting prepared and effective — the process decoded in plain language, the parent-input statement that gets read, the questions that make goals measurable, and advocacy that stays collaborative. Use when asked prepare me for my child's IEP meeting, what's the difference betw"
    },
    {
     "name": "iep-goal-support",
     "description": "Draft SMART IEP goals, accommodations, and present-levels statements that are measurable and compliant in spirit. Use when asked to write an IEP goal, draft special-education goals, list accommodations, or write a present-levels (PLAAFP) statement. Produces measurable annual goals with baselines, cr"
    },
    {
     "name": "impact-report",
     "description": "Write a compelling nonprofit impact or annual report that shows donors what their money achieved. Use when asked to write an impact report, an annual report, a grant outcomes report, or to report results to funders/donors. Produces a structured report — mission and year in brief, outcomes with real "
    },
    {
     "name": "inbox-triage-live",
     "description": "Triage the user's REAL inbox through the Gmail connector — not a framework they run by hand. Use when asked to clear my inbox, get me to inbox zero on the actual account, triage my unread, or process my email backlog in Cowork. Reads unread via the Gmail connector, sorts every message into archive /"
    },
    {
     "name": "inbox-unsubscribe-purge",
     "description": "Cut inbox volume at the source — the unsubscribe purge that classifies recurring senders into kill/digest/keep, executes safely (real unsubscribes vs. spam-report vs. never-click), and installs the filters that catch the rest. Use when asked my inbox is all newsletters, mass unsubscribe safely, cut "
    },
    {
     "name": "inbox-zero-operator",
     "description": "Drive an email inbox to zero through a computer-use or tool-using agent — triage every message into act/delegate/defer/archive with drafts prepared, never a send. Use when asked to get my inbox to zero, triage my email hands-on, process my inbox for me, or run inbox zero. Produces the triage ledger,"
    },
    {
     "name": "incident-postmortem",
     "description": "Write a structured incident postmortem or post-incident review. Use when asked to write a postmortem, incident report, P1/P2 review, outage report, or RCA (root cause analysis). Produces a blameless postmortem with timeline, root cause, contributing factors, impact summary, and action items."
    },
    {
     "name": "incident-public-statement",
     "description": "Write a single clear, honest public statement about an incident. Use when asked to draft a public statement, a press statement, or an official response to a security breach, outage, data incident, recall, or public controversy. Produces a ready-to-publish statement — acknowledgement, what happened, "
    },
    {
     "name": "incremental-implementation",
     "description": "Build in small, individually-verified increments that each leave the system working — instead of big-bang changes that fail mysteriously at the end. Use when implementing multi-part features, refactoring anything load-bearing, making large mechanical changes, or when past work produced huge diffs th"
    },
    {
     "name": "influencer-brief",
     "description": "Create a structured brief for an influencer or creator partnership campaign. Use when asked to brief an influencer, plan a creator collaboration, set up a paid partnership, or define deliverables for a sponsored content campaign. Produces a complete campaign brief with objectives, deliverables, crea"
    },
    {
     "name": "infra-as-code-review",
     "description": "Write an infrastructure-as-code review checklist and conduct a structured review of Terraform, CloudFormation, Pulumi, or Ansible code. Use when asked to review IaC code, audit infrastructure configurations, check cloud security posture, or produce a reusable IaC review checklist. Produces a structu"
    },
    {
     "name": "injection-spotter",
     "description": "Spot prompt-injection in untrusted content before an agent acts on it — the anatomy of injected instructions across the channels attackers use (email, web, files, tool outputs, documents), the tell-list, and the safe-handling response. Use when asked is this content trying to hijack my agent, check "
    },
    {
     "name": "inspection-report-decoder",
     "description": "Decode a home inspection report into what's cosmetic, what's expensive, and what kills deals — with repair-cost ranges and the negotiation list. Use when asked to decode my inspection report, is this inspection bad, what should I ask the seller to fix, or should I walk after inspection. Produces a f"
    },
    {
     "name": "instagram-post-downloader",
     "description": "Download and save Instagram posts as high-resolution files. Use when asked to download, save, or archive an Instagram post, reel thumbnail, or carousel. Produces saved high-res images in a named folder, with carousel slides stitched into a single PDF; supports batch downloading of multiple URLs at o"
    },
    {
     "name": "insurance-claim",
     "description": "Write a clear insurance claim letter or appeal that supports a payout. Use when asked to write an insurance claim, file a claim letter, document a loss for insurance, or appeal a denied claim. Produces a structured claim — policy and incident details, the documented loss, the amount claimed, and the"
    },
    {
     "name": "insurance-policy-decoder",
     "description": "Decode a home, renters, or auto insurance policy into what's actually covered, what's excluded, and what the payout math really looks like before you need it. Use when someone asks 'what does my insurance actually cover', 'decode my policy', 'is this deductible normal', or 'actual cash value vs repl"
    },
    {
     "name": "interview-me",
     "description": "Elicit the real requirements by interviewing the requester BEFORE building or writing anything — one question at a time, until the brief is buildable. Use when a request is vague ('make me a dashboard', 'write something for the board'), when past deliverables missed the mark, or when the user says '"
    },
    {
     "name": "interview-prep",
     "description": "Prepare for a specific interview at a specific company, not just 'an interview'. Use when asked to prep for an interview, prepare answers for a role, practice for a specific company's interview, or get ready for a behavioural/case/PM round. Produces a tailored prep pack — likely questions for this r"
    },
    {
     "name": "interview-question-bank",
     "description": "Build a structured, role-specific interview question bank with what good answers look like. Use when asked to create interview questions, an interview guide, a structured interview kit, or competency-based questions for a role. Produces questions mapped to the competencies that matter — behavioral ("
    },
    {
     "name": "interview-synthesis",
     "description": "Turn a pile of interview notes into findings that survive scrutiny — the code-then-theme pass, the counting discipline (how many actually said it), the quote selection that illustrates instead of cherry-picks, and the confidence lines a small sample earns. Use when asked synthesize these user/custom"
    },
    {
     "name": "inventory-policy",
     "description": "Set inventory policy for an item class: segmentation, safety stock, and replenishment method. Use when asked to set safety stock levels, segment items by ABC/XYZ, choose reorder points vs min-max, define stocking policy, or review excess and obsolete inventory. Produces a segmentation grid, per-segm"
    },
    {
     "name": "investing-policy-statement",
     "description": "Draft a personal investing policy statement (IPS) — the rules someone sets for their own investing. Use when asked to define an investment strategy, set a target asset allocation, or write rules to avoid panic-driven decisions. Produces a structured IPS: goals, risk tolerance, target allocation, con"
    },
    {
     "name": "investor-cold-email",
     "description": "Write a cold or warm-intro email to an investor that actually gets a reply — short, specific, traction-forward, with a clear ask. Use when asked to email an investor, write a fundraising outreach, request a warm intro, or craft a forwardable blurb. Produces a tight cold email, a forwardable intro bl"
    },
    {
     "name": "investor-pitch-deck",
     "description": "Build the narrative and slide structure for an investor pitch deck. Use when asked to create a pitch deck, investor presentation, fundraising deck, or startup pitch. Produces a slide-by-slide structure with narrative beats, key messages, and what each slide must prove to an investor."
    },
    {
     "name": "investor-update",
     "description": "Write a structured monthly or quarterly investor update. Use when asked to write an investor update, investor newsletter, board update, or startup progress report for investors. Produces a clear, credible update with highlights, metrics, challenges, and asks — in the format investors actually want t"
    },
    {
     "name": "invoice-generator",
     "description": "Create a professional, complete invoice for a client or customer. Use when asked to write an invoice, create a bill, draft a freelance/contractor invoice, or set up an invoice template. Produces a clear invoice — your and the client's details, a unique number, line items with quantities/rates, subto"
    },
    {
     "name": "ip-lookup",
     "description": "Look up IP addresses and your own public IP with zero API keys — geolocation, ISP/ASN, and hosting flags via ip-api.com and ipify through curl. Use when asked what's my public IP, where is this IP from, whose network is this address, or is this IP a VPN/datacenter. Produces the lookup with ISP, ASN,"
    },
    {
     "name": "iso-27001-isms",
     "description": "Scope an ISO 27001 ISMS and build the Statement of Applicability across Annex A controls. Use when asked to implement ISO 27001, scope an ISMS, build a Statement of Applicability (SoA), or prepare for ISO 27001 certification. Produces an ISMS plan — scope & context, risk-treatment approach, an Annex"
    },
    {
     "name": "iss-tracker",
     "description": "Track the International Space Station live with keyless curl — where it is right now, what it's over, and when to look up, with the orbital math translated into human terms. Use when asked where is the ISS right now, is the space station overhead, when can I see the ISS tonight, or track the station"
    },
    {
     "name": "issue-triage-live",
     "description": "Triage the user's REAL issue tracker — read open issues via the GitHub/Linear connector, label / prioritise / dedupe / flag them, and apply the safe changes — not advice on triage. Use when asked to triage my issues, clean up the backlog, label and prioritise open issues, or sort my GitHub issues in"
    },
    {
     "name": "jd-decoder",
     "description": "Decode a job description to find what they actually want beneath the buzzwords. Use when asked to analyse a job description, decode a JD, assess fit for a role, or figure out what a posting really means before applying. Produces a decode — the real must-haves vs. nice-to-haves, hidden priorities & c"
    },
    {
     "name": "job-application",
     "description": "Tailors a CV and cover letter to a specific job description. Use when asked to write a cover letter, tailor a CV or resume, optimise for ATS, match a job description, or prepare a job application. Produces an ATS-optimised tailored CV summary and a personalised cover letter aligned to the role's req"
    },
    {
     "name": "job-description-writer",
     "description": "Write a clear, inclusive, and structured job description for any role. Use when asked to write a job description, job posting, JD, or job advert. Produces a complete JD with role summary, responsibilities, requirements, and inclusive language review."
    },
    {
     "name": "job-story-mapper",
     "description": "Write Jobs-to-be-Done (JTBD) job stories and map customer jobs across functional, social, and emotional dimensions. Use when defining user needs, writing job stories, conducting JTBD research, or reframing features around customer outcomes. Produces a job story map with opportunity scoring, pain int"
    },
    {
     "name": "kb-audit",
     "description": "Audit a knowledge base / help center for coverage, accuracy, and findability. Use when asked to audit a help center, review KB health, find documentation gaps, reduce ticket volume with better docs, or prioritise what to write/fix. Produces an audit — a health scorecard, content gaps (driven by top "
    },
    {
     "name": "knowledge-gardening",
     "description": "Keep a team knowledge base alive — the gardener role and its weekly half-hour, the rot signals (stale pages, orphans, duplicates) and their fixes, the capture funnels that feed the garden, and the pruning that keeps search useful. Use when asked our wiki is a graveyard, who maintains the knowledge b"
    },
    {
     "name": "kpi-tracker-design",
     "description": "Design a KPI tracker that drives decisions instead of decorating them — the few-metrics discipline (5–9, each with an owner and a so-what), targets with honest baselines, the trend-first layout, and the review ritual where the tracker actually gets used. Use when asked set up KPI tracking for the te"
    },
    {
     "name": "kyc-escalation",
     "description": "Write an internal KYC/AML escalation memo: a factual time-stamped trigger description, customer-profile vs activity mismatch analysis, red-flag taxonomy mapping, outstanding information, and a recommendation with rationale. Use when asked to escalate a KYC alert, document an AML concern, write up un"
    },
    {
     "name": "landing-page-copy",
     "description": "Write full landing-page copy that converts — section by section. Use when asked to write a landing page, homepage copy, a product page, or copy for a marketing site. Produces complete copy for every section (hero, problem, solution, social proof, features-as-benefits, objections/FAQ, final CTA) with"
    },
    {
     "name": "last-30-days-research",
     "description": "Searches Reddit, X/Twitter, and the broader web for recent opinions, sentiment, and signal on any topic. Use when you need to know what real people are saying about a tool, product, trend, or event in the past 30 days — cutting through SEO content to surface genuine community reaction. Produces a st"
    },
    {
     "name": "last-two-weeks-handoff",
     "description": "Turn your notice period into a handoff that makes you missed for the right reasons — the transition doc nobody has to call you about, the knowledge-transfer sessions, and the graceful goodbye mechanics. Use when asked I just resigned how do I hand off my work, write my transition document, plan my l"
    },
    {
     "name": "late-invoice-escalation",
     "description": "Collect overdue invoices with a graduated escalation ladder — friendly nudge to firm notice to work-stop to final demand, each with send-ready wording and timing, plus the prevention terms that stop the next one. Use when asked my client hasn't paid me, write a payment reminder email, invoice is 60 "
    },
    {
     "name": "launch-post",
     "description": "Write a developer-audience launch post — Show HN, a Product Hunt blurb, a 'we shipped X' dev blog intro, or a launch tweet thread. Use when launching a tool, library, API, or open-source project to a technical audience. Produces a credible, hype-free post that leads with what it does and why it's di"
    },
    {
     "name": "launch-readiness",
     "description": "Assesses pre-launch readiness across every function and produces an explicit Go / Conditional Go / No-Go recommendation. Use when preparing for any product or feature launch, running a pre-launch review, or determining whether a release is safe to ship. Produces a function-by-function readiness stat"
    },
    {
     "name": "launch-tiering-framework",
     "description": "Tier a product launch (T1/T2/T3) and scope the right go-to-market effort. Use when asked to decide a launch tier, right-size launch activities, build a launch tiering framework, or plan channels and effort proportional to a launch's impact. Produces a tiering recommendation with the scoring rational"
    },
    {
     "name": "layoff-announcement",
     "description": "Write the layoff communications a leader has to get right once — the all-hands script, the affected/unaffected messages, and the external note, without corporate euphemism or legal risk. Use when asked to write a layoff announcement, communicate a RIF, tell the team about job cuts, or draft the diff"
    },
    {
     "name": "layoff-communication",
     "description": "Plan and write the communications for a layoff or restructure with clarity and dignity. Use when asked to communicate a layoff, write a RIF/redundancy announcement, prepare manager talking points for letting people go, or plan workforce-reduction comms. Produces a comms package — sequencing plan, th"
    },
    {
     "name": "layoff-financial-triage",
     "description": "The first-72-hours money plan after a layoff — runway computed, deadlines caught, bleeding stopped, in priority order. Use when asked I just got laid off what do I do about money, build my layoff budget, how long can I last, or what needs to happen this week. Produces the runway number, the deadline"
    },
    {
     "name": "lease-decoder",
     "description": "Decode a residential lease into plain English and rank the clauses that can hurt you. Use when someone asks 'what am I signing', 'decode my lease', 'is this rental agreement normal', or 'can my landlord really do this'. Produces a clause-by-clause decode table, ranked red flags, break-clause and dep"
    },
    {
     "name": "legal-brief",
     "description": "Draft a structured legal brief, case summary, or legal argument outline. Use when asked to write a legal brief, case note, legal memo, argument outline, or position paper. Produces a structured document using IRAC format (Issue, Rule, Application, Conclusion)."
    },
    {
     "name": "lending-risk-brief",
     "description": "Write a portfolio-level lending risk brief: concentration analysis by sector, geography and single name, vintage performance, migration matrix narrative, macro-sensitivity scenarios, top watch names, and actions. Use when asked to write a portfolio risk report, credit risk committee brief, loan book"
    },
    {
     "name": "lesson-plan",
     "description": "Build a complete, standards-aligned lesson plan with clear objectives, a timed activity sequence, differentiation, and assessment. Use when asked to write a lesson plan, plan a class or lesson, design a teaching session, or structure instruction for a topic. Produces a ready-to-teach plan with measu"
    },
    {
     "name": "lifecycle-crm-plan",
     "description": "Design lifecycle marketing / CRM journeys across the customer lifecycle. Use when asked to plan onboarding emails, lifecycle/CRM campaigns, drip sequences, re-engagement or winback flows, or a messaging calendar. Produces a lifecycle plan — stage map, the trigger/message/goal for each journey, chann"
    },
    {
     "name": "linkedin-profile",
     "description": "Optimise a LinkedIn profile to be found and to convert. Use when asked to write or improve a LinkedIn headline, About section, or profile, or to make a profile recruiter-friendly. Produces an optimised headline, a first-person About section with a hook and keywords, achievement-led experience bullet"
    },
    {
     "name": "literature-review",
     "description": "Structure and write a literature review for any research topic. Use when asked to write a literature review, systematic review summary, narrative review, or research background section. Produces a structured review with thematic organisation, critical analysis, and gap identification."
    },
    {
     "name": "literature-review-builder",
     "description": "Structure a literature review that argues, not lists — thematic synthesis from your sources with the debate mapped and the gap identified. Use when asked to write or structure a literature review, organize my sources, synthesize these papers, or find the gap for my thesis. Produces a themed review s"
    },
    {
     "name": "llm-cost-latency-budget",
     "description": "Model the cost and latency of an LLM feature before it ships and surprises the bill. Use when asked to estimate LLM API costs, set a latency/token budget, decide which model tier to use, or bring down the cost of an AI feature. Produces a cost & latency budget — token math per request, monthly cost "
    },
    {
     "name": "llm-guardrails-spec",
     "description": "Specify the safety and reliability guardrails for an LLM feature before it ships. Use when asked to define LLM guardrails, add safety controls to an AI feature, prevent prompt injection or jailbreaks, or harden a chatbot/agent against misuse. Produces a guardrails spec — threats, input/output contro"
    },
    {
     "name": "load-testing-plan",
     "description": "Write a load and performance testing plan for a service. Use when asked to create a performance test plan, write load testing documentation, define stress or soak test scenarios, or set performance regression gates for CI. Produces a complete test plan document with scenario definitions, k6/Locust s"
    },
    {
     "name": "loan-covenant-review",
     "description": "Run a quarterly loan covenant compliance review: covenant table with required vs actual vs headroom, trend and trajectory-to-breach analysis, waiver and amendment options with pricing implications, early-warning indicators, and a watch-list recommendation. Use when asked to review covenant complianc"
    },
    {
     "name": "loan-decoder",
     "description": "Decode a personal, auto, or mortgage loan offer into what it really costs and where the traps are. Use when someone asks 'is this loan a good deal', 'decode my loan offer', 'what am I signing', or 'what will this mortgage actually cost me'. Produces a total-cost-of-loan number, APR vs advertised-rat"
    },
    {
     "name": "local-dev-setup",
     "description": "Write a local development environment setup guide for a service or project — covering prerequisites, repository setup, environment variables, local service dependencies, database seeding, running the service, running tests, common gotchas, IDE recommendations, and first-contribution checklist. Use w"
    },
    {
     "name": "localization-brief",
     "description": "Plan the localization of a product/content for a new market — beyond translating the words. Use when asked to localize a product, plan market entry localization, prepare a localization brief, or figure out what to adapt for a new region. Produces a brief — target locales, what to translate vs. adapt"
    },
    {
     "name": "logistics-incident-report",
     "description": "Write up a supply chain disruption — port delay, carrier failure, customs hold, or in-transit damage — as a decision-ready incident report. Use when asked to document a shipment delay, write up a logistics failure, report a customs hold, quantify a supply disruption, or draft the customer notice for"
    },
    {
     "name": "manager-first-90-days",
     "description": "Plan a new manager's first 90 days — first-time or new-to-team — as listen/decide/move phases: the 1:1 listening tour with real questions, the early-judgment traps, the quick-wins filter, and the 30/60/90 artifacts. Use when asked I just became a manager what do I do, plan my first 90 days as a mana"
    },
    {
     "name": "managing-up",
     "description": "Work more effectively with your manager — communicate, align, escalate, and get what you need. Use when asked how to manage up, work better with a boss, get buy-in from your manager, escalate without overstepping, or prepare to raise something with leadership. Produces a managing-up plan — what your"
    },
    {
     "name": "marketing-funnel-plan",
     "description": "Plan a full-funnel marketing strategy from awareness to retention. Use when asked to build a marketing funnel, map the customer journey to tactics, plan demand generation, or diagnose where a funnel leaks. Produces a funnel plan — stage definitions, the metric and conversion target per stage, channe"
    },
    {
     "name": "marketing-psychology",
     "description": "Apply behavioral-psychology principles to a marketing asset or decision — ethically. Use when asked to make copy/a page/an offer more persuasive, apply psychological triggers, reduce friction, or understand why something does/doesn't convert. Produces the relevant principles (social proof, scarcity,"
    },
    {
     "name": "marketplace-listing-optimizer",
     "description": "Audit and optimize a marketplace listing (Amazon, Etsy, eBay, Walmart) to rank and convert. Use when asked to optimize an Amazon/Etsy listing, improve marketplace SEO, fix a product listing that isn't selling, or write keyword-rich titles and bullets. Produces a prioritised optimization — title, bul"
    },
    {
     "name": "mcp-server-spec",
     "description": "Design an MCP server for a product — the tool surface, auth model, and safety boundaries that make it genuinely usable by AI agents. Use when asked to spec an MCP server, expose a product to agents, design tools for Claude or other MCP clients, or review why an existing MCP server performs badly. Pr"
    },
    {
     "name": "media-pitch",
     "description": "Write a media pitch or press outreach email for any story or announcement. Use when asked to write a media pitch, journalist outreach email, press pitch, or story angle for PR. Produces a concise pitch with a compelling news angle, journalist-specific hook, and clear call to action."
    },
    {
     "name": "medical-bill-decoder",
     "description": "Decode an itemized medical bill or EOB into plain English and find the charges worth disputing. Use when someone asks 'why is my medical bill so high', 'decode my hospital bill', 'what is this EOB saying', or 'can I negotiate this bill'. Produces a line-by-line decode, duplicate and unbundling flags"
    },
    {
     "name": "medical-records-request",
     "description": "Request your medical records and actually get them — what to ask for, the request letter that can't be shuffled aside, the timelines and fee rules to cite (jurisdiction-flagged), and the escalation path for stonewalls. Use when asked how do I get my medical records, write a records request, my docto"
    },
    {
     "name": "meeting-cost-meter",
     "description": "Price meetings in money and focus — the attendee-hours × loaded-rate math, the recurring multiplier that turns a weekly 30-minutes into a real annual number, and the cost-vs-outcome read that decides what the price buys. Use when asked what does this meeting cost, price our meeting culture, is this "
    },
    {
     "name": "meeting-notes",
     "description": "Structure and format meeting notes following PM best practices. Use when asked to create meeting notes, format discussion notes, capture action items, or document decisions from any meeting type. Produces structured notes with decisions, action items (owner + deadline), open questions, and next step"
    },
    {
     "name": "meeting-prep-live",
     "description": "Prepare the user for a REAL upcoming meeting by pulling the actual Calendar event, its attendees, the linked Drive docs, and the last email/Slack thread — then producing a brief. Use when asked to prep me for my next meeting, get me ready for the 2pm, or what do I need for the sync with X in Cowork."
    },
    {
     "name": "meeting-prep-pack",
     "description": "Arrive at a meeting armed in fifteen minutes — the prep pack: what this meeting decides, your position with its reasons, the other attendees' likely stances, the questions to ask, and the outcome you're steering toward. Use when asked prep me for this meeting, what should I know before this call, I "
    },
    {
     "name": "meeting-room-etiquette",
     "description": "Set the shared-space norms that end the small daily frictions — meeting room booking discipline (the ghost-booking cure), hybrid-call room behavior, the shared kitchen/space contracts, and the enforcement that works without a hall monitor. Use when asked set office space norms, rooms are always book"
    },
    {
     "name": "messaging-framework",
     "description": "Build a messaging framework (message house) that the whole company can use consistently. Use when asked to create messaging, a value proposition, a message house, key messages, or to make marketing/sales/product say the same thing. Produces a messaging framework — audience & value proposition, the o"
    },
    {
     "name": "metric-gaslighting-detector",
     "description": "Find out how a dashboard, KPI report, or metrics slide is lying to you — before you repeat its story in a bigger room. Use when numbers feel too tidy, a narrative rests on one chart, or you inherited metrics you didn't define. Produces a deception audit: every metric graded for the eleven classic di"
    },
    {
     "name": "metric-semantic-layer",
     "description": "Define a metric in a semantic layer so it means one thing everywhere. Use when asked to define a metric, build a semantic layer / metrics layer entry, stop 'revenue means three things' problems, or write a metric definition for dbt MetricFlow / Cube / LookML. Produces a metric definition — exact for"
    },
    {
     "name": "metric-tree-builder",
     "description": "Decompose a north-star metric into a driver tree — the inputs and sub-inputs that actually move it — so a team knows which levers to pull. Use when asked to build a metric tree, break down a north-star metric, map metric drivers, or find the inputs behind an output metric. Produces a hierarchical tr"
    },
    {
     "name": "metrics-framework",
     "description": "Build a metrics framework for any product, team, or business. Use when asked for a metrics tree, KPI framework, North Star metric, AARRR funnel, HEART framework, or OKR metrics. Produces a structured metrics hierarchy from North Star down to leading indicators, with measurement guidance."
    },
    {
     "name": "microcopy-writer",
     "description": "Write the small UI text that guides users — buttons, labels, tooltips, CTAs, confirmations. Use when asked to write microcopy, button/CTA text, form labels, tooltips, helper text, or to make UI wording clearer. Produces specific, action-oriented microcopy with options and rationale, matched to the m"
    },
    {
     "name": "microservices-decomposition",
     "description": "Design a microservices decomposition for a monolith or new system, defining service boundaries, ownership, communication patterns, and migration plan. Use when asked to decompose a monolith, define service boundaries, design a microservices architecture, or plan a strangler-fig migration. Produces a"
    },
    {
     "name": "migration-day-runbook",
     "description": "Move a team's files to a new platform without losing work or a week — the pre-migration freeze, the verified copy, the permissions remap, the cutover announcement, and the old-system read-only afterlife. Use when asked we're moving from Dropbox to Drive, migrate our files to SharePoint, plan the fil"
    },
    {
     "name": "mind-map",
     "description": "Turn a topic, brainstorm, or document into a structured mind map. Use when asked to brainstorm around a theme, organize ideas, break a topic into branches, or summarize something as a mind map. Produces a ready-to-render Mermaid mindmap (renders live, exportable as PNG/SVG) plus a short note on the "
    },
    {
     "name": "model-card",
     "description": "Document a deployed ML/AI model so others can use it responsibly. Use when asked to write a model card, document a model's intended use and limitations, or prepare an AI model for review/launch. Produces a complete model card — intended use, training data, evaluation metrics across slices, limitatio"
    },
    {
     "name": "model-migration-plan",
     "description": "Plan the migration of an LLM feature from one model to another without breaking production. Use when a model is being deprecated, a newer model looks better or cheaper, or when asked how to upgrade models safely, run shadow traffic, or set rollback criteria for a model change. Produces a phased migr"
    },
    {
     "name": "model-selection-advisor",
     "description": "Choose the right LLM for a task by trading off quality, cost, latency, and constraints. Use when asked which model to use, whether to upgrade/downgrade a model, how to cut LLM costs without hurting quality, or to justify a model choice. Produces a recommendation with the decision criteria, a per-opt"
    },
    {
     "name": "monitoring-setup-guide",
     "description": "Write a monitoring setup guide for a service — defining what to measure, how to alert on it, and how to build the observability stack covering the four golden signals, business metrics, log strategy, distributed tracing, alerting rules, dashboard layout, and observability debt. Use when asked to set"
    },
    {
     "name": "morning-intelligence",
     "description": "Interviews you across 15 questions to capture your role, topics, sources, exclusions, and format preferences, then writes a master prompt you can paste into a scheduled task or Claude Code Routine. Use when you want to set up a personalised daily news brief, build a reusable morning news prompt, or "
    },
    {
     "name": "moving-company-estimate-decoder",
     "description": "Decode a moving company estimate — binding vs non-binding, the weight and cubic-feet games, valuation vs insurance, and the red flags that precede hostage-load stories. Use when someone asks 'is this moving quote legit', 'decode my moving estimate', 'binding vs non-binding estimate', or 'how do I av"
    },
    {
     "name": "multi-source-signal-synthesiser",
     "description": "Synthesises user signals from multiple research sources into a unified, weighted insight brief. Use when you have data from interviews, support tickets, NPS verbatims, app reviews, or sales calls and need to reconcile contradictions, surface the underlying need behind requests, or answer 'what are u"
    },
    {
     "name": "nda-analyser",
     "description": "Analyses a Non-Disclosure Agreement clause by clause and flags unusual terms, one-sided provisions, and negotiation points. Use when reviewing an NDA, mutual NDA, confidentiality agreement, or non-disclosure deed before signing or countering. Produces a plain English verdict, clause-by-clause risk a"
    },
    {
     "name": "net-worth-statement",
     "description": "Produce a personal net-worth statement — assets minus liabilities — and a way to track it. Use when asked to calculate net worth, summarize finances, or set up net-worth tracking. Produces a categorized assets/liabilities statement, the net-worth figure, liquidity and debt ratios, and a tracking cad"
    },
    {
     "name": "new-parent-logistics",
     "description": "Turn the pre-baby chaos into a staged logistics plan — leave paperwork, insurance deadlines, the hospital-bag/home-setup checklists, and the first-two-weeks operating plan with named owners. Use when asked help me prepare for a baby, what do I need to do before my due date, set up our parental leave"
    },
    {
     "name": "newsletter-digest-brief",
     "description": "Turn a pile of newsletters and subscriptions into one skimmable brief — the items that matter to YOUR interests extracted with sources, the noise dropped with a count, on a cadence that replaces daily trickle-reading. Use when asked digest my newsletters, summarize what my subscriptions said this we"
    },
    {
     "name": "newsletter-writer",
     "description": "Write a full creator newsletter issue — subject line, preview text, hook, body with a clear takeaway, and a CTA — in the writer's voice, for Substack, beehiiv, ConvertKit, or email. Use when asked to write a newsletter, an email issue, a Substack post, or to turn notes/a topic into a sendable newsle"
    },
    {
     "name": "notebooklm-connector",
     "description": "Automates NotebookLM from Claude Code using browser automation via the Claude Chrome extension — creating notebooks, adding sources, and triggering outputs without manual clicking. Use when you want to create a NotebookLM notebook, add URLs or documents as sources, or generate mindmaps, audio overvi"
    },
    {
     "name": "notes-humanizer",
     "description": "Strips AI writing patterns from text and rewrites it to sound genuinely human by removing statistical defaults and injecting the specific signals that human writers produce. Use when a draft reads as AI-generated, over-polished, or rhythmically uniform — including blog posts, emails, LinkedIn posts,"
    },
    {
     "name": "notion-db-hygiene",
     "description": "Clean the user's REAL Notion database — read it, find stale/incomplete/duplicate entries, and fix them via the connector — not advice on keeping Notion tidy. Use when asked to clean up my Notion database, my tracker is a mess, find the stale and duplicate entries, or tidy my projects DB in Cowork. R"
    },
    {
     "name": "offer-comparison",
     "description": "Compare two or more job offers as total-comp curves over four years — vesting cliffs, bonuses, 401(k) match, and the crossover year computed, not vibed. Use when asked to compare job offers, which offer pays more over time, model my equity vesting, or is the startup offer actually worth it. Produces"
    },
    {
     "name": "offer-letter",
     "description": "Draft a job offer — the written offer letter and a verbal-offer script. Use when asked to write an offer letter, a job offer, an employment offer, or to prepare to extend/verbal an offer to a candidate. Produces a clear, warm offer letter (role, comp, start, key terms, contingencies, acceptance) plu"
    },
    {
     "name": "office-hours-design",
     "description": "Replace ad-hoc interruptions with office hours that actually get used — the slot design (cadence, length, format), the routing rules that tell people what goes there vs. what shouldn't wait, and the empty-hours and overflow failure modes handled in advance. Use when asked set up office hours, I'm in"
    },
    {
     "name": "office-move-runbook",
     "description": "Run an office move or reconfiguration without losing a week of work — the dependency-ordered plan (internet lead times rule everything), the workstream owners, the comms that keep the team functional through the chaos, and the day-one-that-works checklist. Use when asked plan our office move, we're "
    },
    {
     "name": "offsite-planner",
     "description": "Plan a team offsite that earns its cost — the purpose split (connection vs. decisions vs. planning, weighted on purpose), the agenda that alternates work and air, the logistics runbook, and the follow-through that makes Monday different from before. Use when asked plan our team offsite, design two d"
    },
    {
     "name": "okr-builder",
     "description": "Create well-structured OKRs (Objectives and Key Results) for product teams, startups, and individuals. Use when asked to write OKRs, set quarterly goals, define key results, or review existing OKRs. Produces a complete OKR set with objectives, measurable key results, baselines, and a scoring guide."
    },
    {
     "name": "oncall-handoff",
     "description": "Write a structured end-of-shift on-call handoff so the incoming engineer inherits state, not surprises. Use when asked to write an on-call handoff, oncall handover, shift handoff, pager handoff, or end-of-week SRE summary. Produces a handoff note with open incidents, watchlist alerts, in-flight inve"
    },
    {
     "name": "oncall-runbook",
     "description": "Write an on-call runbook for a service — covering alert definitions, escalation paths, common incident responses, and on-call handoff procedures. Use when asked to write an on-call guide, create alert runbooks, document escalation procedures, or prepare an on-call handoff document. Produces a struct"
    },
    {
     "name": "onboarding-buddy-plan",
     "description": "Design the buddy system that makes new-hire onboarding human — the buddy's actual job (context and safety, not training), the 30-day touchpoint plan, the ask-me-anything contract, and the buddy selection that avoids the two classic miscasts. Use when asked set up an onboarding buddy program, I'm bud"
    },
    {
     "name": "onboarding-copy",
     "description": "Write in-product onboarding copy that gets users to value fast. Use when asked to write onboarding copy, a welcome flow, product tour/tooltips, setup steps, or activation messaging. Produces the copy for an onboarding flow — welcome, the guided steps/tooltips toward the first win, progress and empty"
    },
    {
     "name": "onboarding-plan",
     "description": "Create a structured 30/60/90-day onboarding plan for any new hire. Use when asked to write an onboarding plan, new hire plan, 30-60-90 day plan, or first 90 days roadmap. Produces a week-by-week plan with milestones, meetings, learning goals, and success criteria."
    },
    {
     "name": "one-on-one-prep",
     "description": "Prepare for a 1:1 so it drives outcomes instead of becoming a status update. Use when asked to prep for a one-on-one, build a 1:1 agenda, prepare to talk to your manager (or a report), or raise something hard in a 1:1. Produces a focused 1:1 agenda — your top topics with the outcome you want for eac"
    },
    {
     "name": "one-pager",
     "description": "Distil anything — a startup, product, project, or idea — into a single persuasive page. Use when asked to make a one-pager, a one-page summary, a leave-behind, a startup/product one-sheet, or a tl;dr brief. Produces a structured single page — headline + tagline, the problem, the solution, why-now/pr"
    },
    {
     "name": "open-house-plan",
     "description": "Plan and promote an open house that draws buyers and generates leads. Use when asked to plan an open house, market an open house, or create an open-house checklist. Produces a plan — timing and promotion across channels, prep and staging checklist, a day-of run sheet, lead capture, and follow-up — s"
    },
    {
     "name": "opposing-counsel",
     "description": "Read a contract the way the counterparty's lawyer will — hunting for leverage, not fairness. Use when someone says 'read this like opposing counsel', 'how would the other side attack this agreement', 'find the weaknesses before they do', or before sending or signing any contract. Produces the demand"
    },
    {
     "name": "org-chart",
     "description": "Turn a team or reporting structure into a clean org chart. Use when asked to draw an org chart, show reporting lines, visualize team structure, or map who reports to whom. Produces a ready-to-render Mermaid org chart (renders live, exportable as PNG/SVG) plus headcount notes and any structural obser"
    },
    {
     "name": "out-of-office-designer",
     "description": "Design an out-of-office that actually protects the time off — the auto-reply that routes instead of apologizes, the coverage map behind it, and the pre-departure handoff that prevents the beach laptop. Use when asked write my out of office message, going on vacation what do I set up, cover my work w"
    },
    {
     "name": "outcome-tracker",
     "description": "Record the testable predictions inside a decision, then score them against reality later — so frameworks earn trust from outcomes, not vibes. Use when committing to a prioritisation, forecast, or plan (to log what it predicts), when asked to review what actually happened, or to compute how well-cali"
    },
    {
     "name": "outline-before-prose",
     "description": "Outline documents before drafting them — the argument skeleton that gets alignment cheaply, the one-line-per-section discipline, and the review-the-outline step that saves rewriting the prose. Use when asked help me start this document, outline before I write, why do my docs get rewritten from scrat"
    },
    {
     "name": "outreach-message",
     "description": "Write cold outreach and networking messages that actually get replies. Use when asked to write a cold message to a recruiter/hiring manager, a LinkedIn connection note, a referral request, or a networking/coffee-chat ask during a job search. Produces short, specific, reply-worthy messages — tuned to"
    },
    {
     "name": "package-health",
     "description": "Check a package's health before you depend on it — npm and PyPI registry APIs via keyless curl: downloads, release recency, maintenance signals, and the dependency-decision read. Use when asked is this npm package maintained, check this PyPI library before we adopt it, compare these two packages, or"
    },
    {
     "name": "paid-acquisition-plan",
     "description": "Plan a paid acquisition / performance marketing program with unit economics that work. Use when asked to plan paid media, allocate an ad budget across channels, set CAC/LTV targets, or structure a creative-testing program. Produces a paid acquisition plan — economic guardrails (CAC/LTV/payback), cha"
    },
    {
     "name": "parent-communication",
     "description": "Draft clear, warm, professional messages to parents or guardians — progress notes, concerns, positive news, behaviour issues, or meeting requests. Use when asked to email a parent, write home about a student, raise a concern with a guardian, or share an update. Produces a ready-to-send message that "
    },
    {
     "name": "parent-teacher-conference-prep",
     "description": "Get real information out of a 15-minute parent-teacher conference — the questions that beat 'how's she doing', the data to bring from home, and the follow-up that makes the meeting matter. Use when asked prepare me for the parent teacher conference, what should I ask my kid's teacher, the conference"
    },
    {
     "name": "partnership-proposal",
     "description": "Write a B2B partnership proposal or business case. Use when asked to write a partnership proposal, draft a partnership brief, structure a co-marketing proposal, or create a business case for a strategic partnership. Produces a structured proposal with value proposition, partnership model, commercial"
    },
    {
     "name": "patient-communication",
     "description": "Write clear, plain-English patient communications for any healthcare context. Use when asked to write a patient letter, patient information leaflet, appointment letter, test-results letter, discharge summary for patients, or health education content. Produces an accessible patient communication at a"
    },
    {
     "name": "pay-stub-decoder",
     "description": "Decode a pay stub line by line — every deduction explained, the gross-to-net story, and the errors worth catching. Use when asked to explain my pay stub, why is my paycheck smaller than expected, what are all these deductions, or check my paycheck for mistakes. Produces a line-by-line decode, the gr"
    },
    {
     "name": "paywall-optimization",
     "description": "Design or optimize a paywall / upgrade screen to convert free users to paid without killing trust. Use when asked to improve a paywall, upgrade prompt, or free-to-paid conversion, or to decide what to gate. Produces the gating strategy (what's free vs. paid and why), the paywall placement and moment"
    },
    {
     "name": "pentest-report",
     "description": "Write a clear penetration-test report from findings of an authorized engagement. Use when documenting a pentest, security assessment, or authorized red-team engagement — turning findings into a report clients act on. Produces an executive summary, scope & methodology, findings with severity/evidence"
    },
    {
     "name": "performance-budget",
     "description": "Define and document performance budgets for a web service or application. Use when asked to set performance targets, define SLOs for latency or throughput, establish Core Web Vitals targets, create a performance baseline, or document performance regression policy. Produces a structured performance b"
    },
    {
     "name": "performance-review",
     "description": "Write structured, balanced performance reviews from bullet-point inputs. Use when asked to write a performance review, self-assessment, peer review, 360 feedback, or manager evaluation. Produces a complete, fair, professionally written review covering achievements, areas for growth, and development "
    },
    {
     "name": "personal-bio",
     "description": "Write a professional bio in the three lengths you actually need. Use when asked to write a bio, an 'about me', a speaker/author bio, or a short profile blurb. Produces three ready-to-use versions — a one-liner, a short (~50-word) bio, and a long (~150-word) bio — in a consistent third-person voice, "
    },
    {
     "name": "personal-board-of-directors",
     "description": "Five standing advisors — the Operator, the Skeptic, the CFO, the Coach, the Customer — debate your decision on paper and vote. Use when asked to help me decide, pressure-test this decision, what would smart advisors say, or convene my board. Produces five distinct advisor memos, a disagreement map, "
    },
    {
     "name": "personal-wip-limits",
     "description": "Cap your work-in-progress so things finish — the personal WIP limit (3 active outcomes, defended), the finish-before-start rule with its exceptions named, the parking lot for the overflow, and the throughput evidence that converts the skeptic. Use when asked I have twelve things half-done, why does "
    },
    {
     "name": "persuasion-brief",
     "description": "Build the case to win someone over to a decision, idea, or change. Use when asked to persuade someone, build a case for an idea, get buy-in, win over a skeptic, or prepare to pitch a proposal internally. Produces a persuasion brief — the audience's current view and what moves them, the core argument"
    },
    {
     "name": "photo-library-rescue",
     "description": "Rescue a photo library drowning in duplicates, screenshots, and 40,000 unsorted items — the triage order that shrinks first (screenshots, bursts, dupes), the album-vs-search philosophy that ends over-organizing, and the backup rule that comes before any deleting. Use when asked organize my photo lib"
    },
    {
     "name": "pip-responder",
     "description": "Respond to a performance improvement plan strategically — decode what the PIP really is, decide fight-vs-land-softly with clear eyes, build the evidence file, and run the parallel job search the situation demands. Use when asked I was just put on a PIP what do I do, help me respond to a performance "
    },
    {
     "name": "pitch-vs-teach",
     "description": "Know which talk you're giving — the pitch (drive one decision) vs. the teach (build understanding) — because mixing their structures fails both, and most bad presentations are one wearing the other's clothes. Use when asked is this a pitch or a training, my informative deck didn't land the ask, my p"
    },
    {
     "name": "pivot-analysis-planner",
     "description": "Plan pivot-table analysis that answers the actual question — the question-to-layout mapping (rows, values, filters chosen on purpose), the data-shape check that pivots require, and the drill-down path from summary to so-what. Use when asked analyze this data with a pivot, what's driving the total, b"
    },
    {
     "name": "plain-language-rewrite",
     "description": "Rewrite jargon-dense text into plain language without losing precision — the translation pass that keeps every fact and qualifier, the jargon triage (terms to replace, terms to keep-and-define), and the reading-level honesty for the actual audience. Use when asked make this readable, translate this "
    },
    {
     "name": "pm-weekly-review",
     "description": "Structure a PM's weekly review and planning session. Use when doing a weekly PM review, writing a weekly update, preparing for Monday planning, or reviewing sprint health. Produces a shareable weekly update covering metrics movement, shipping progress, blockers, insights, and next week's top 3 prior"
    },
    {
     "name": "policy-drafter",
     "description": "Draft an internal policy people can actually follow — the rule stated plainly with its reason, the bright lines separated from the judgment zones, the edge cases resolved by principle, and the enforcement reality stated honestly. Use when asked write our expense/remote-work/AI-use/security policy, t"
    },
    {
     "name": "policy-memo",
     "description": "Write a decision-ready policy memo that frames an issue and recommends an option. Use when asked to write a policy memo, options paper, decision memo for a principal/minister/executive, or brief a decision-maker on a policy choice. Produces a tight memo: the issue, background, options with trade-off"
    },
    {
     "name": "policy-renewal-review",
     "description": "Run a pre-renewal review of an insurance programme: scan coverage gaps against current operations, test limit adequacy against inflation and exposure growth, read the claims experience into pricing expectations, frame market alternatives, and arm the broker negotiation. Use when asked to prepare for"
    },
    {
     "name": "portfolio-page",
     "description": "Structure a portfolio or case-study page that shows your work, not just lists it. Use when asked to write a portfolio page, a project case study, a work showcase, or an 'is this person good?' proof page. Produces a portfolio structure — a positioning header, and per-project case studies (context → y"
    },
    {
     "name": "pptx-slide-auditor",
     "description": "Audit a PowerPoint presentation for layout issues, text overflow, visual hierarchy problems, and consistency gaps. Use when asked to review a slide deck, check a presentation before a meeting, audit slides for layout problems, or QA a deck before sharing. Produces a slide-by-slide report with issues"
    },
    {
     "name": "pr-crisis-response",
     "description": "Build a crisis communications plan to respond fast and credibly when something goes wrong. Use when asked to handle a PR crisis, draft a crisis comms plan, respond to a public backlash/scandal/incident, or prepare holding statements. Produces a crisis comms plan — situation assessment, stakeholder m"
    },
    {
     "name": "pr-description",
     "description": "Write a clear pull-request description that gets reviewed fast and merged with confidence. Use when opening a PR, summarizing a change for review, or asked to write a PR/merge-request description. Produces a structured PR: what changed and why, how it was tested, risk and rollout, and a focused revi"
    },
    {
     "name": "pr-description-live",
     "description": "Write a PR description grounded in the REAL diff — read the branch's actual changes via the GitHub connector, not a template the user fills in. Use when asked to write my PR description, describe this pull request, draft the PR body from my branch, or document these changes in Cowork. Reads the comm"
    },
    {
     "name": "pr-description-writer",
     "description": "Write a clear, structured pull request description from a git diff, branch summary, or commit list. Use when asked to write a PR description, draft a pull request, or document code changes. Produces a description with summary, motivation, changes made, testing steps, and reviewer guidance."
    },
    {
     "name": "prd-template",
     "description": "Create a Product Requirements Document following proven PM template structure. Use when asked to write a PRD, product spec, feature specification, or requirements document for a new feature or product. Produces a complete PRD with problem statement, user stories, functional requirements, technical c"
    },
    {
     "name": "premortem-assassin",
     "description": "Kill the plan on paper before reality does it for money. Use when a plan, launch, migration, or strategy is about to be committed to and nobody has tried hard to murder it yet — the assassin attacks through twelve named failure vectors and writes the post-mortem of the failure that hasn't happened. "
    },
    {
     "name": "prescription-cost-navigator",
     "description": "Work down the cost of a prescription systematically — the generic and therapeutic-alternative conversation, discount programs vs insurance math, pharmacy price variance, and manufacturer/assistance programs, in the order that saves the most first. Use when asked my prescription is too expensive, how"
    },
    {
     "name": "presenter-notes",
     "description": "Write presenter notes that actually help mid-talk — cue-grain phrases instead of scripts, the transitions and numbers that deserve verbatim capture, the timing marks that keep the talk on schedule, and the Q&A crib built in. Use when asked write my speaker notes, I either script everything or wing i"
    },
    {
     "name": "press-release",
     "description": "Write a professional press release for any announcement. Use when asked to write a press release, media announcement, news release, or press statement. Produces a structured press release with headline, dateline, body, boilerplate, and media contact — ready to send to journalists."
    },
    {
     "name": "pricing-calculator",
     "description": "Model pricing scenarios — tiers, margins, break-even, and the revenue impact of a price change. Use when asked to calculate pricing, model a price increase, find break-even volume, set tier prices to a margin target, or estimate the revenue effect of a pricing change. Produces a computed pricing mod"
    },
    {
     "name": "pricing-page-copy",
     "description": "Write pricing page copy that helps buyers self-select the right plan and convert. Use when asked to write or improve a pricing page, name and describe pricing tiers, write plan feature lists, pricing CTAs, or a pricing FAQ. Produces complete pricing page copy — a header, tier cards with names, price"
    },
    {
     "name": "pricing-sensitivity-model",
     "description": "Van Westendorp price sensitivity, computed from real survey answers — crossings found by interpolation, not read off a chart by eye. Use when someone has (or plans) the four-question pricing survey (too cheap / cheap / expensive / too expensive) and needs the optimal price point, the acceptable rang"
    },
    {
     "name": "pricing-strategy",
     "description": "Structure pricing strategy decisions, packaging options, and tier design for SaaS and digital products. Use when reviewing or setting pricing, designing pricing tiers, evaluating freemium vs paid, or preparing a pricing change. Produces a pricing strategy recommendation with model rationale, tier st"
    },
    {
     "name": "pricing-your-services",
     "description": "Design a freelance/consulting pricing structure — hourly vs day-rate vs project vs retainer chosen per engagement type, anchored packages, and the rules for saying the number out loud without flinching. Use when asked how should I price my freelance services, hourly or fixed price, build my pricing "
    },
    {
     "name": "prior-authorization-letter",
     "description": "Write a persuasive prior-authorization / medical-necessity letter to an insurer. Use when asked to write a prior authorization letter, a letter of medical necessity, or to appeal a denied treatment/medication/procedure. Produces a structured letter — patient and request, clinical justification tied "
    },
    {
     "name": "privacy-policy-drafter",
     "description": "Draft a clear, plain-language privacy policy tailored to what a product actually collects and does with data. Use when asked to write a privacy policy, draft a data-protection notice, or create a GDPR/CCPA-aware privacy statement. Produces a structured policy covering data collected, purposes, legal"
    },
    {
     "name": "process-documentation",
     "description": "Document any business process in a clear, structured format. Use when asked to document a process, write a process guide, create a workflow document, or map out how something works. Produces a complete process document with steps, roles, inputs, outputs, and edge cases."
    },
    {
     "name": "product-description",
     "description": "Write a product description / listing that sells and ranks. Use when asked to write a product description, e-commerce listing copy, a product page, or to rewrite a flat product blurb. Produces benefit-led listing copy — a hook, scannable feature→benefit bullets, specs, an SEO-aware title and keyword"
    },
    {
     "name": "product-health-analysis",
     "description": "Interpret product metrics against goals and surface actionable signals. Use when asked to analyse product health, review key metrics, investigate a performance issue, produce a health report, or assess product-market fit signals. Produces a structured health report with RAG status, trend analysis, r"
    },
    {
     "name": "product-launch-checklist",
     "description": "Generate a comprehensive pre-launch, launch day, and post-launch checklist for any product release. Use when preparing for a product launch, feature release, or major update. Produces a role-assigned, tiered checklist covering engineering readiness, marketing and comms, support, and post-launch moni"
    },
    {
     "name": "product-naming",
     "description": "Generate and evaluate names for a product, feature, or release. Use when asked to name a product/feature/company, brainstorm naming options, or choose between name candidates. Produces a shortlist of names across naming strategies, each with rationale, plus an evaluation against clear criteria (clar"
    },
    {
     "name": "product-positioning-doc",
     "description": "Write a product positioning document and messaging framework. Use when asked to define product positioning, write a positioning statement, build a messaging framework, or create a messaging hierarchy. Produces a complete positioning doc with category definition, target customer, differentiation, pro"
    },
    {
     "name": "professional-brain",
     "description": "Maintain a durable, local markdown memory ('brain') of your product context, decisions, hypotheses, and stakeholders that other skills read from and write back to. Use when asked to set up a brain, ingest notes/artifacts into memory, recall what's known about a topic, log a decision with provenance,"
    },
    {
     "name": "professional-translator",
     "description": "Translate text professionally — preserving tone, register, and meaning, not word-for-word. Use when asked to translate a document, email, or content between languages, or to improve a literal/machine translation. Produces a natural, register-appropriate translation plus translator's notes on choices"
    },
    {
     "name": "programmatic-seo",
     "description": "Plan a programmatic SEO strategy — generate many ranking pages from a data set and a template. Use when asked about pSEO, scaling content with templates/data, building [X] for [Y] pages, or capturing long-tail search at scale. Produces the head-term + modifier model, the page template and data schem"
    },
    {
     "name": "project-status-report",
     "description": "Write a structured project status report for any project. Use when asked to write a project update, status report, RAG report, project dashboard narrative, or weekly project communication. Produces a clear status report with RAG ratings, milestone progress, risks, and decisions needed."
    },
    {
     "name": "promotion-packet",
     "description": "Build a promotion case that proves you're already operating at the next level. Use when asked to write a promo packet/case, prepare for a promotion committee, or make the case for a level-up or title change. Produces a promotion packet — the level-up thesis, evidence mapped to each next-level compet"
    },
    {
     "name": "promotion-plan",
     "description": "Plan a sale or promotion that drives revenue without wrecking margin. Use when asked to plan a promotion, a discount/sale campaign, a BFCM/holiday promo, or a product launch offer. Produces a promo plan — objective, the offer mechanic, margin math, audience & channels, timing, messaging, and how you"
    },
    {
     "name": "prompt-optimizer",
     "description": "Diagnose and rewrite an underperforming LLM prompt so it produces reliable, well-structured output. Use when asked to improve a prompt, fix a prompt that gives inconsistent or wrong results, reduce hallucination/refusals, or make output follow a format. Produces a rewritten prompt with a diagnosis o"
    },
    {
     "name": "prompt-regression-suite",
     "description": "Design a regression test suite that catches an LLM feature getting worse when the prompt, model, or context changes. Use when asked to stop prompt changes breaking production, set up golden tests or CI gates for an LLM feature, or test a model/prompt upgrade before shipping it. Produces a golden cas"
    },
    {
     "name": "property-investment-analysis",
     "description": "Analyze a rental / investment property's returns — cash flow, cap rate, cash-on-cash, ROI. Use when asked to analyze a rental property, evaluate a real-estate investment, run the numbers on an investment property, or compute cap rate / cash-on-cash. Produces an investment analysis — income and expen"
    },
    {
     "name": "property-listing",
     "description": "Write a compelling, accurate real-estate listing description. Use when asked to write a property listing, an MLS/Zillow description, a real-estate listing, or to make a property description more appealing. Produces a listing — a hook headline, a flowing description that sells the lifestyle and key f"
    },
    {
     "name": "property-offer-letter",
     "description": "Write a buyer's offer cover letter to a seller to strengthen a real-estate bid. Use when asked to write a real-estate offer letter, a buyer's 'love letter' to a seller, an offer cover note, or to make a home offer stand out. Produces a warm, genuine letter — who the buyers are, why they love the hom"
    },
    {
     "name": "proposal-skeleton",
     "description": "Structure an internal proposal that gets a decision — the problem-cost-options-recommendation-ask spine, the objection pre-handling that shortens the meeting, and the reversibility framing that makes yes easier. Use when asked write a proposal for the new tool or process or hire, how do I pitch this"
    },
    {
     "name": "proposal-writer",
     "description": "Write a structured sales proposal or commercial proposal for any deal. Use when asked to write a proposal, sales proposal, commercial proposal, statement of work, or quote document. Produces a complete proposal with problem statement, solution, investment, and next steps."
    },
    {
     "name": "public-comment",
     "description": "Draft a persuasive public comment on a proposed rule, regulation, or plan. Use when asked to comment on a rulemaking, respond to a consultation, submit feedback on a proposed regulation, or write a comment to an agency. Produces a structured comment: your position, specific evidence-based arguments "
    },
    {
     "name": "public-holidays",
     "description": "Look up public holidays for any country and year with zero API keys — the Nager.Date API via curl, with long-weekend detection and cross-country planning. Use when asked what are the holidays in a country, is date X a holiday somewhere, find long weekends this year, or which days is the team in Japa"
    },
    {
     "name": "punch-list-builder",
     "description": "Turn walkthrough notes, photos, or voice-memo transcripts into a proper construction punch list with location, trade, and spec reference per item. Use when asked to build a punch list, clean up walkthrough notes, organise a deficiency list, prep for substantial completion, or track punch items to cl"
    },
    {
     "name": "purchase-justification",
     "description": "Write the purchase request that gets approved — the cost-of-not-buying framing, the ROI math at the approver's altitude, the alternatives-considered section that preempts the obvious pushback, and the right-sized ask for the approval tier. Use when asked justify this tool/hire/equipment purchase, wr"
    },
    {
     "name": "qa-release-signoff",
     "description": "Produce a QA release sign-off / go-no-go readiness report. Use when asked for a release sign-off, a go/no-go QA report, release readiness, or a test summary before shipping. Produces a sign-off — what was tested and the results, open defects by severity, coverage and residual risk, the go/no-go reco"
    },
    {
     "name": "qbr-deck",
     "description": "Build a Quarterly Business Review (QBR) deck structure and narrative for a customer account. Use when asked to prepare a QBR, business review meeting, executive review, or quarterly check-in with a customer. Produces a slide-by-slide QBR structure with talking points, metrics review, value narrative"
    },
    {
     "name": "quarterly-tax-rhythm",
     "description": "Build the tax habit self-employment requires — the setaside percentage from day one, the quarterly calendar, the records that make filing boring, and the no-withholding mindset shift nobody explains. Use when asked how do taxes work for my side income, how much should I set aside, what are estimated"
    },
    {
     "name": "quiz-generator",
     "description": "Generate a quiz or test on any topic with a balanced mix of question types and difficulty, plus a complete answer key with explanations. Use when asked to create a quiz, write a test, make practice questions, or build an assessment. Produces well-formed questions aligned to learning objectives, tagg"
    },
    {
     "name": "quote-card",
     "description": "Pull the single most shareable quote out of a testimonial, review, interview, or long text and format it as a clean quote card. Use when asked to make a pull-quote, testimonial graphic, or 'quote card' for social/marketing. Produces a tightly-edited quote with attribution and 2-3 alternates, structu"
    },
    {
     "name": "raci-matrix",
     "description": "Define a RACI matrix for a cross-functional project or process. Use when asked to build a RACI, create a responsibility matrix, clarify ownership across teams, or document decision rights. Produces a complete RACI matrix with role definitions, decision mapping, and a process for resolving conflicts."
    },
    {
     "name": "rag-architecture-review",
     "description": "Review an existing Retrieval-Augmented Generation system and find why it underperforms. Use when asked to review or audit a RAG pipeline, diagnose wrong/ungrounded answers from a 'chat with your docs' feature, or improve an already-built knowledge assistant. Produces a staged review — ingestion, chu"
    },
    {
     "name": "rag-design-doc",
     "description": "Design a Retrieval-Augmented Generation system end to end. Use when asked to design a RAG pipeline, a 'chat with your docs' feature, a knowledge assistant, or to debug why a RAG system gives wrong/ungrounded answers. Produces a RAG design doc — ingestion & chunking, embeddings & index, retrieval & r"
    },
    {
     "name": "raise-vs-jump",
     "description": "Model staying for annual raises vs job-hopping for bigger bumps — cumulative earnings trajectories, the crossover year, and the costs the salary math hides (vesting resets, promotion paths, search risk). Use when asked should I switch jobs for more money, is job hopping worth it, model my salary if "
    },
    {
     "name": "rate-card",
     "description": "Build a consulting/freelance rate card and pricing structure — and the floor rate to not go broke. Use when asked to set freelance/consulting rates, build a rate card, decide what to charge, package services, or move off hourly billing. Produces a rate card — your minimum viable rate (from real targ"
    },
    {
     "name": "readme-writer",
     "description": "Write a clear, well-structured README for a software project or open-source repo. Use when asked to write or improve a README, document a project, or make a repo approachable. Produces a complete README — one-line pitch, badges, quickstart, usage, install, contributing, license — that gets someone f"
    },
    {
     "name": "receipts-audit",
     "description": "Audit any document against its own sources — every factual claim extracted and graded as evidenced, partially evidenced, unsupported, or contradicted, with the exact source line that supports or fails it. Use when asked to fact-check a document against its sources, check whether a report's claims ar"
    },
    {
     "name": "recruiter-outreach",
     "description": "Write personalized candidate outreach that gets replies. Use when asked to write a recruiter InMail, a candidate outreach email, a sourcing message, or a follow-up sequence. Produces a short, personalized first message (hook tied to the candidate, the role's appeal, a low-friction ask) plus a 2–3 st"
    },
    {
     "name": "recurring-meeting-pruner",
     "description": "Prune your own recurring-meeting load — the personal calendar audit (your role in each, honestly), the four exit moves (leave, delegate, downgrade to notes, halve), and the graceful exit scripts that don't burn standing. Use when asked get me out of some of these meetings, my calendar is 80% recurri"
    },
    {
     "name": "red-team-review",
     "description": "Stress-test a plan, strategy, PRD, or launch by simulating hostile expert personas who attack it from every angle. Use when asked to red-team, stress-test, pre-mortem, pressure-test, play devil's advocate, or find the blind spots in a plan before committing. Produces a per-persona critique, a ranked"
    },
    {
     "name": "redundancy-consultation",
     "description": "Structure a redundancy consultation process and draft key communications (UK employment law focus). Use when asked to plan a redundancy process, write a redundancy letter, structure a consultation, or manage a reduction in force. Produces a structured consultation plan and draft letters; always reco"
    },
    {
     "name": "refactoring-plan",
     "description": "Plan a safe, incremental refactor of messy code without changing behavior. Use when code needs restructuring, is hard to change, has grown tangled, or you want to clean it up before adding a feature. Produces a sequenced plan of small behavior-preserving steps, the safety net (tests/characterization"
    },
    {
     "name": "reference-letter",
     "description": "Write a credible, specific letter of recommendation or reference. Use when asked to write a reference letter, a letter of recommendation, a character reference, or to recommend someone for a job, school, or tenancy. Produces a structured reference — your relationship, specific evidence of their stre"
    },
    {
     "name": "reference-request-kit",
     "description": "Secure strong references after a departure — who to ask, the ask messages, the briefing sheet that makes their reference specific, and the LinkedIn recommendation swap. Use when asked to help me get references, write a reference request, prep my referee, or ask my old manager for a recommendation. P"
    },
    {
     "name": "referral-program",
     "description": "Design a referral program that drives real word-of-mouth growth. Use when asked to build a referral or refer-a-friend program, create an incentive/reward structure, or turn happy users into a growth channel. Produces the incentive design (who gets what, when), the mechanics and trigger moment, fraud"
    },
    {
     "name": "referral-program-design",
     "description": "Design a referral or viral-loop program that actually drives growth. Use when asked to design a referral program, build a viral/invite loop, set referral incentives, or improve word-of-mouth growth. Produces a referral design — the loop mechanics, incentive structure (who gets what, when), the viral"
    },
    {
     "name": "refinance-breakeven",
     "description": "Compute the month a refinance actually starts saving money — payment delta, breakeven month, and total interest on both paths including the term-reset trap. Use when asked should I refinance, when does a refi break even, compare my loan to a refi offer, or is this refinance worth the closing costs. "
    },
    {
     "name": "regex-builder",
     "description": "Build a regular expression from a plain-English description, or explain an existing one. Use when asked to write a regex, match/validate/extract a pattern, or understand what a regex does. Produces the regex, a token-by-token breakdown, passing and failing test cases, and notes on flavor/edge cases."
    },
    {
     "name": "regression-test-plan",
     "description": "Design and prioritize a regression test suite so changes don't break what worked. Use when asked to plan regression testing, build a regression suite, decide what to re-test after a change, or trim a bloated regression pack. Produces a risk-based regression plan — what to re-test and why, prioritise"
    },
    {
     "name": "regulator-eyes",
     "description": "Read your marketing claims, landing page, or ad copy the way a consumer-protection investigator would (FTC/ASA framing) and draft the inquiry letter they could send. Use when asked to check my marketing claims, read this like a regulator, audit my landing page for claim risk, or is this ad compliant"
    },
    {
     "name": "regulatory-impact-analysis",
     "description": "Produce a regulatory impact analysis (RIA) weighing the costs, benefits, and alternatives of a proposed rule. Use when asked to assess a regulation's impact, do a cost-benefit analysis of a policy, justify a rulemaking, or compare regulatory options. Produces a structured RIA: the problem and ration"
    },
    {
     "name": "relocation-planner",
     "description": "Plan a move — across town or across a border — as a dependency-ordered project: the lease/housing chain, address-change cascade, utilities cutover, movers, and the go-bag for the gap days. Use when asked help me plan my move, relocation checklist, I'm moving in six weeks what do I do, or moving to a"
    },
    {
     "name": "renewal-playbook",
     "description": "Build a structured renewal playbook for a customer account. Use when asked to plan a renewal, structure a renewal negotiation, prepare for an expansion conversation, or build a renewal strategy for at-risk or healthy accounts. Produces a renewal brief with health assessment, negotiation strategy, ob"
    },
    {
     "name": "rent-increase-response",
     "description": "Respond to a rent increase strategically — check its validity first, price your alternatives honestly, then negotiate with the leverage tenants forget they have (turnover costs the landlord more than a compromise). Use when asked my rent is going up what can I do, negotiate my rent increase, is this"
    },
    {
     "name": "rent-vs-buy",
     "description": "Model rent-vs-buy honestly — year-by-year net position for both paths including the assumption everyone drops (the renter invests the difference), with a breakeven horizon instead of a verdict. Use when asked should I rent or buy, does buying beat renting in my city, when does buying break even, or "
    },
    {
     "name": "rental-application",
     "description": "Write a standout rental application / cover letter to a landlord or letting agent. Use when asked to write a rental application, a letter to a landlord, a renter cover letter, or to strengthen an application for a competitive rental. Produces a concise renter profile and cover letter — who you are, "
    },
    {
     "name": "repair-request-escalation",
     "description": "Get a landlord to actually fix things — the repair request that creates a record, the escalation ladder from reminder to habitability leverage, and the jurisdiction-flagged map of tenant remedies with their prerequisites. Use when asked my landlord won't fix anything, write a repair request, how lon"
    },
    {
     "name": "reply-in-their-tone",
     "description": "Draft email replies that match the sender's register — formality, length, directness, and emoji-tolerance read from their message, so the reply lands as native instead of off-key. Use when asked reply to this email, draft a response that doesn't sound stiff, match their tone, or answer this without "
    },
    {
     "name": "repo-map",
     "description": "Navigate a codebase by map instead of reading files wholesale — a deterministic stdlib script that emits the tree with line counts and top-level symbols, plus the read-the-map-first discipline that cuts exploration tokens by an order of magnitude. Use when asked explore this repo efficiently, stop r"
    },
    {
     "name": "research-protocol",
     "description": "Write a structured research protocol or study design document. Use when asked to write a research protocol, study protocol, research plan, methodology section, or research proposal. Produces a complete protocol with objectives, methodology, ethical considerations, and analysis plan."
    },
    {
     "name": "research-repo-setup",
     "description": "Set up a research repository the team actually reuses — the atomic-insight format (finding + evidence + source + date), the tagging that makes old research findable by new questions, and the check-the-repo-first norm that stops re-researching. Use when asked set up a research repository, we keep re-"
    },
    {
     "name": "resignation-letter",
     "description": "Write a resignation letter that closes a chapter without burning it — short, warm, legally clean, and silent on everything that doesn't belong in a permanent file. Use when asked write my resignation letter, how do I resign professionally, what do I say when I quit, or review my resignation email. P"
    },
    {
     "name": "resume",
     "description": "Write a sharp, achievement-led resume/CV that passes ATS and earns the interview. Use when asked to write or rewrite a resume or CV, turn experience into a resume, or tailor a resume to a job. Produces a clean, single-column, ATS-friendly resume — summary, experience as quantified accomplishment bul"
    },
    {
     "name": "retention-analysis",
     "description": "Structure a retention analysis, churn investigation, or engagement deep-dive for any product team. Use when asked to analyse user retention, investigate churn, measure DAU/MAU, or build a retention improvement plan. Produces a retention snapshot with root cause hypotheses, aha-moment correlation, an"
    },
    {
     "name": "retention-loop-design",
     "description": "Design retention and engagement loops that bring users back. Use when asked to improve retention, design an engagement/habit loop, fix a leaky retention curve, or build a re-engagement system. Produces a retention design — the retention curve diagnosis, the core habit loop (trigger→action→reward→inv"
    },
    {
     "name": "retro-analysis",
     "description": "Analyses sprint delivery data and produces a structured retrospective brief. Use when asked to run a retrospective, analyse sprint data, prepare a retro brief, or turn sprint metrics into discussion prompts. Produces a data-grounded retrospective brief with completion stats, pattern analysis, Start/"
    },
    {
     "name": "return-refund-policy",
     "description": "Write a clear, fair returns, refunds & exchanges policy for an online store. Use when asked to write a return policy, refund/exchange policy, or store returns page. Produces a customer-friendly policy — window, conditions, process, refund method/timing, exceptions, and shipping — in plain language t"
    },
    {
     "name": "review-comments-resolver",
     "description": "Resolve a document's forty review comments systematically — triage by type (accept, push back, conflict, out-of-scope), batch the mechanical fixes, draft the disagreement replies, and reconcile reviewers who contradict each other. Use when asked work through these review comments, two reviewers want"
    },
    {
     "name": "review-response",
     "description": "Write the right reply to a customer review — positive, negative, or mixed. Use when asked to respond to a review, reply to a bad/1-star review, handle online reviews, or write review-response templates. Produces tailored, on-brand responses that thank advocates, de-escalate and resolve complaints, a"
    },
    {
     "name": "rfc-writer",
     "description": "Write an engineering RFC (Request for Comments) for a technical decision, architectural change, or significant implementation approach. Use when asked to write an RFC, document a technical proposal, create a design doc, write an architecture decision for review, or produce a technical specification "
    },
    {
     "name": "rfp-response",
     "description": "Write a compliant, competitive response to an RFP/RFQ/ITT (government or enterprise procurement). Use when responding to a request for proposal, bidding on a tender, or answering a procurement questionnaire. Produces a compliance-matrix-driven response that answers every requirement, wins on evaluat"
    },
    {
     "name": "rfp-scoring-matrix",
     "description": "Build a weighted RFP evaluation matrix and defensible award recommendation. Use when asked to score RFP responses, compare vendor bids, build a supplier evaluation matrix, run a sourcing event scorecard, or decide which bidder to award. Produces a criteria tree with weights, scoring anchors, normali"
    },
    {
     "name": "rfp-writer",
     "description": "Write a clear Request for Proposal that gets comparable, high-quality vendor bids. Use when asked to write an RFP, a request for proposal/quote/tender, or to solicit and compare vendor proposals. Produces a complete RFP — background, scope of work, requirements, evaluation criteria with weights, sub"
    },
    {
     "name": "rice-impact-matrix",
     "description": "Scores features using both RICE and strategic alignment for nuanced prioritisation. Use when asked to prioritise features, build a priority matrix, combine quantitative scoring with strategic fit, or decide what to build next with multiple competing initiatives. Produces a scored priority matrix wit"
    },
    {
     "name": "rice-prioritisation",
     "description": "Scores and ranks product initiatives using the RICE framework. Use when asked to prioritise features, rank a backlog using RICE, score initiatives for quarterly planning, or apply an objective framework to a list of competing ideas. Produces a ranked RICE table with scores, quick wins and moonshot f"
    },
    {
     "name": "risk-register",
     "description": "Build and maintain a project or product risk register. Use when asked to create a risk register, identify project risks, build a risk matrix, or document risks and mitigations for a programme. Produces a complete risk register with likelihood/impact scoring, RAG status, ownership, and prioritised mi"
    },
    {
     "name": "rma-failure-analysis",
     "description": "Turn field returns into a structured failure-analysis report — RMA triage taxonomy (NTF vs real failures), Pareto by verified failure mode, 8D-style containment→root-cause→corrective-action structure, and cost-of-quality framing. Use when asked to analyse RMA data, investigate field returns, run fai"
    },
    {
     "name": "roadmap-narrative",
     "description": "Transform a prioritised initiative list into a compelling strategic roadmap narrative. Use when asked to write a roadmap narrative, explain the product roadmap to non-technical stakeholders, connect roadmap items to company goals, or produce an exec-shareable roadmap story. Produces a themed narrati"
    },
    {
     "name": "roadmap-presentation",
     "description": "Create structured roadmap presentations calibrated to any audience. Use when asked to build a product roadmap, present roadmap to leadership, create a roadmap slide, or communicate quarterly plans to execs, teams, or customers. Produces an audience-calibrated Now/Next/Later roadmap with strategic co"
    },
    {
     "name": "roi-estimator",
     "description": "Estimate the ROI, payback, and NPV of an investment, project, or purchase. Use when asked to calculate ROI, build a business case, justify a purchase/initiative, work out payback period, or compare options by return. Produces a computed ROI summary (net benefit, ROI %, payback, simple NPV) with the "
    },
    {
     "name": "role-redesign-for-ai",
     "description": "Redesign a job role that AI now does a large part of — deliberately, instead of quietly expecting the same headcount to absorb 140% output. Use when AI has changed what a role spends time on, when writing a revised role charter or job description post-AI, when a team asks 'what is my job now', or wh"
    },
    {
     "name": "rollback-plan",
     "description": "Write a concrete rollback plan for a risky change (deploy, migration, feature-flag flip, config rollout) so the reverse is one command away — not an improvised debate at 2am. Use when asked to write a rollback plan, back-out plan, revert plan, or 'what if we need to undo this'. Produces a rollback p"
    },
    {
     "name": "rss-digest",
     "description": "Fetch and digest any RSS or Atom feed with zero API keys — curl plus disciplined parsing into a ranked, deduplicated briefing instead of a link dump. Use when asked summarize this feed, what's new on this blog, digest these RSS feeds, or build me a morning briefing from these sources. Produces the d"
    },
    {
     "name": "rubric-builder",
     "description": "Create a clear grading rubric with criteria and performance-level descriptors that make scoring fair, fast, and consistent. Use when asked to build a rubric, create grading criteria, design an assessment scoring guide, or make grading more objective. Produces an analytic rubric table (criteria × per"
    },
    {
     "name": "runbook-writer",
     "description": "Write an operational runbook for a service, incident type, or deployment procedure. Use when asked to write a runbook, create an ops guide, document an operational procedure, or prepare an incident response playbook. Produces a runbook with overview, prerequisites, step-by-step procedures, rollback "
    },
    {
     "name": "runway-calculator",
     "description": "Calculate cash runway, burn, and the zero-cash date — and whether you're default alive or dead. Use when asked to work out runway, monthly burn, when the money runs out, or how much to raise/cut to reach a target. Produces a computed runway summary (net burn, months of runway, zero-cash date, defaul"
    },
    {
     "name": "runway-monte-carlo",
     "description": "Cash runway as a distribution, not a number — Monte Carlo simulated. Use when someone asks how long their cash lasts, when to start fundraising, or how burn/revenue volatility changes their runway; especially when the naive cash÷burn answer is driving a decision. Produces P10/P50/P90 runway, month-b"
    },
    {
     "name": "runway-planner",
     "description": "Turn burn and cash into a clear runway picture and a raise decision — months left, default-alive vs default-dead, and what to cut or change. Use when asked to calculate runway, model burn rate, decide when to raise, figure out if the company is default-alive, or plan a scenario with hiring/cuts. Pro"
    },
    {
     "name": "sop-meeting-prep",
     "description": "Prepare an S&OP cycle readout that surfaces the demand-supply gaps and forces the three decisions the meeting must make. Use when asked to prep an S&OP meeting, build the executive S&OP deck, summarize demand vs supply for the monthly cycle, or prepare a supply review readout. Produces a gap table, "
    },
    {
     "name": "saas-metrics",
     "description": "Compute the core SaaS metrics — MRR/ARR, growth, NRR/GRR, churn, quick ratio, magic number — from your numbers. Use when asked to calculate SaaS metrics, MRR/ARR, net revenue retention, the quick ratio, or to build a SaaS metrics snapshot for a board/investor update. Produces a computed metrics dash"
    },
    {
     "name": "salary-negotiation",
     "description": "Plan a compensation negotiation grounded in numbers and leverage, not nerves. Use when asked to negotiate salary, evaluate or counter a job offer, prepare for a comp conversation, or compare offers. Produces a negotiation plan — total-comp comparison across offers, your target/walk-away and BATNA, t"
    },
    {
     "name": "sales-battlecard",
     "description": "Create a competitive sales battlecard for any competitor. Use when asked to build a battlecard, competitive comparison, sales cheat sheet, or objection handling guide for a specific competitor. Produces a one-page battlecard with positioning, differentiators, objection responses, and landmines."
    },
    {
     "name": "sales-demo-script",
     "description": "Write a product demo script that tells a value story instead of a feature tour. Use when asked to write a sales demo script, structure a product demo, plan demo talk track and flow, or turn a feature list into a compelling demo. Produces a demo script — the setup and discovery hooks, a scene-by-scen"
    },
    {
     "name": "sales-enablement-kit",
     "description": "Build a sales enablement kit so reps can sell a product, feature, or launch confidently. Use when asked to create sales enablement materials, a rep-ready one-pager, talk tracks, objection handling, or a launch enablement package. Produces a complete kit — positioning summary, discovery questions, ta"
    },
    {
     "name": "sales-forecasting-model",
     "description": "Build a structured sales forecast framework for any business or team. Use when asked to build a sales forecast, create a revenue model, project pipeline, or build a bottom-up forecast. Produces a forecast methodology, pipeline model, scenario analysis, and assumption log."
    },
    {
     "name": "sales-page",
     "description": "Write a long-form sales page that takes a cold reader to a purchase. Use when asked to write a sales page, a long-form sales letter, a course/offer page, or direct-response copy that has to close on the page. Produces a full long-form structure — hook, problem agitation, the offer & mechanism, proof"
    },
    {
     "name": "savings-goal-plan",
     "description": "Turn a savings goal into a month-by-month funding plan. Use when asked to save for something (emergency fund, house deposit, trip, big purchase), or to figure out how much to set aside each month. Produces the required monthly contribution, a timeline, milestones, and trade-offs if the target date i"
    },
    {
     "name": "saying-no",
     "description": "Decline a request, push back on scope, or protect priorities without burning the relationship. Use when asked how to say no, turn down a request, push back on your boss/stakeholder, decline extra work, or protect the roadmap from a pet feature. Produces a graceful, firm response — the no, the honest"
    },
    {
     "name": "saying-no-kindly",
     "description": "Decline requests without damaging relationships or your standing — the fast-clear-warm formula, the alternative-attached no, the no-to-the-boss version (tradeoffs, not refusal), and the scripts for the asks that recur. Use when asked how do I say no to this, decline this project politely, I say yes "
    },
    {
     "name": "scam-message-decoder",
     "description": "Decode a suspicious message — text, email, call transcript, or DM — against the anatomy of known scam families, with a 🔴🟡🟢 read and the safe next move. Use when someone asks is this a scam, decode this suspicious text, my 'bank' just called me, this job offer seems off, or my parent got a weird m"
    },
    {
     "name": "schedule-monte-carlo",
     "description": "Project completion as a distribution, not a date — Monte Carlo over the task graph. Use when a plan's finish date came from summing 'likely' estimates (it's wrong, mathematically), when leadership needs a commit date, or when you need to know which tasks actually control the timeline. Produces P10/P"
    },
    {
     "name": "schedule-recipe",
     "description": "Turn 'run this every Friday at 4pm' into a working, copy-paste schedule on the user's actual runner. Use when asked to schedule a recurring AI task, set up a routine or cron job for a skill, automate a weekly report, or wire a skill into n8n or GitHub Actions. Produces the exact setup for the chosen"
    },
    {
     "name": "schema-markup",
     "description": "Generate structured-data (Schema.org / JSON-LD) markup to win rich results in search. Use when asked about schema markup, structured data, rich snippets, JSON-LD, or making a page eligible for stars/FAQ/breadcrumb results. Produces valid JSON-LD for the right schema type, the rich-result it targets,"
    },
    {
     "name": "scope-creep-response",
     "description": "Handle scope creep on client work without torching the relationship — classify the ask against the agreement, respond with the goodwill/change-order/renegotiate move that fits, and install the prevention language for next time. Use when asked my client keeps adding requests, is this scope creep, how"
    },
    {
     "name": "screenshot-teardown",
     "description": "Tear down a competitor's product from screenshots of its actual UI — onboarding, pricing page, core flows. Use when given screenshots of a rival's app or website and asked what they're doing, how their flow works, or what to learn/steal/avoid. Produces a UX-and-strategy teardown grounded in what is "
    },
    {
     "name": "second-opinion-request",
     "description": "Get a second medical opinion without torching the first relationship — when it's warranted, how to raise it with the current doctor, the records package the consulting doctor needs, and how to weigh two opinions that disagree. Use when asked should I get a second opinion, how do I ask for a second o"
    },
    {
     "name": "security-deposit-recovery",
     "description": "Get your security deposit back — the move-out documentation that wins disputes before they start, the itemized-deduction challenge, the demand-letter ladder, and the small-claims decision point. Use when asked how do I get my deposit back, my landlord is keeping my deposit, dispute these deposit ded"
    },
    {
     "name": "security-incident-response",
     "description": "Run or document a security incident response — contain, eradicate, recover, and learn. Use when responding to a breach/compromise/security incident, writing an IR plan or runbook, or producing a post-incident report. Produces a phase-by-phase response (triage, contain, eradicate, recover, post-incid"
    },
    {
     "name": "security-review",
     "description": "Review a design, PR, or feature for security issues before it ships. Use when asked to do a security review, security-review a change/PR, or check a feature for vulnerabilities. Produces a structured review across the common risk areas (authn/authz, input handling, secrets, data exposure, dependenci"
    },
    {
     "name": "security-threat-model",
     "description": "Write a STRIDE-based threat model for a service or feature. Use when asked to produce a threat model, document security risks, identify attack vectors, assess a service's security posture, or prepare for a security design review. Produces a structured threat model covering assets, trust boundaries, "
    },
    {
     "name": "self-review",
     "description": "Write a performance self-review that's specific, evidenced, and balanced. Use when asked to write a self-review, self-assessment, or self-evaluation for a performance cycle. Produces a complete self-review — accomplishments mapped to impact and competencies, growth areas owned honestly, and a forwar"
    },
    {
     "name": "seo-content-brief",
     "description": "Create a structured SEO content brief for any target keyword or topic. Use when asked to write an SEO brief, content brief, keyword brief, or content strategy document. Produces a complete brief with target keyword, search intent, outline, competitor insights, internal links, and on-page SEO guidanc"
    },
    {
     "name": "sequence-diagram",
     "description": "Diagram an interaction as a sequence of messages between participants over time. Use when asked to show an API flow, request/response, auth handshake, integration, or 'what calls what in what order'. Produces a ready-to-render Mermaid sequence diagram (renders live, exportable as PNG/SVG) plus notes"
    },
    {
     "name": "service-catalog-entry",
     "description": "Write a service catalog entry for a microservice or internal platform service — covering service identity, purpose, architecture context, SLAs, API contract summary, data classification, dependencies, operational runbooks, and known limitations. Use when asked to document a service for an internal d"
    },
    {
     "name": "session-handoff",
     "description": "Write a handoff summary so another agent or person (or a fresh session) can pick up the work with full context. Use when ending a work session, hitting a context limit, switching agents, or pausing a task mid-flight. Produces a structured handoff: what the goal is, what's done, the current state, wh"
    },
    {
     "name": "severance-agreement-decoder",
     "description": "Decode a severance agreement before you sign it — what you're giving up, what's negotiable, and the deadlines that decide your leverage. Use when asked to decode my severance, is this severance offer normal, review my separation agreement, or should I sign this release. Produces a clause-by-clause d"
    },
    {
     "name": "shared-drive-cleanup",
     "description": "Clean up a shared drive nobody owns — the ownership-first move, the top-down audit that finds the 80% (stale projects, duplicates, ex-employee folders), the archive-don't-delete discipline for shared property, and the norms that prevent regrowth. Use when asked our shared drive is a disaster, clean "
    },
    {
     "name": "short-form-script",
     "description": "Write a short-form video script for TikTok, Instagram Reels, or YouTube Shorts — built on the hook→retention→payoff structure that drives watch-time. Use when asked to script a Reel, TikTok, Short, or any 15–60s vertical video. Produces a timed script with a 0–3s hook, retention beats with on-screen"
    },
    {
     "name": "shutdown-ritual",
     "description": "End the workday on purpose — the ten-minute shutdown that closes open loops, stages tomorrow's start, and gives the brain permission to actually stop (the incomplete-task hum has an off switch, and it's written). Use when asked I can't stop thinking about work at night, build an end-of-day routine, "
    },
    {
     "name": "side-business-setup",
     "description": "Set up a side business in the right order — the do-first sequence (separate money, basic terms, simple records) vs. the feels-official-but-waits list (logos, LLCs-by-default, office chairs), with the structure question framed honestly and routed properly. Use when asked I'm starting a side business "
    },
    {
     "name": "site-check",
     "description": "Answer 'is this site down or is it just me' properly — curl status/timing diagnostics, DNS cross-check, and TLS certificate reads, assembled into a where-it's-broken diagnosis. Use when asked is this website down, why can't I reach this site, check if my site is up, or is the SSL certificate expired"
    },
    {
     "name": "site-safety-briefing",
     "description": "Produce a toolbox talk or pre-task safety briefing from the day's planned construction work. Use when asked to write a toolbox talk, prepare a pre-task plan or JHA/JSA briefing, brief a crew on today's hazards, or plan safety for a specific task like a crane pick, excavation, or hot work. Produces a"
    },
    {
     "name": "skill-fusion",
     "description": "Fuse two skills from this library into one hybrid brief for a task that sits between them — the meta-skill. Use when a task straddles two skills (a PRD that's also a pitch; a postmortem that must double as a board update) and running them separately would produce two documents where one is needed. P"
    },
    {
     "name": "skill-security-auditor",
     "description": "Audit a Claude/Agent SKILL.md (or any AI skill / system prompt) for safety before installing or merging it. Use when asked to review a skill for security, check a prompt for injection, vet a community skill, or assess whether an instruction file is safe to run. Produces a risk-rated report of findin"
    },
    {
     "name": "skill-vetting",
     "description": "Vet an agent skill before installing it — read the SKILL.md and any scripts for the red-flag patterns (credential access, obfuscation, exfiltration, prompt injection), audit its blast radius, and produce a risk-tiered verdict. Use when asked is this skill safe to install, vet this SKILL.md, review t"
    },
    {
     "name": "slide-deck",
     "description": "Build a real, editable PowerPoint (.pptx) deck from an outline or brief. Use when asked to make a slide deck, a PowerPoint, a pitch/board/sales deck as an actual file, or to turn a doc/notes into slides. Produces an actual .pptx via a generated python-pptx script — a title slide, one idea per conten"
    },
    {
     "name": "slide-density-rules",
     "description": "Fix slides that are documents in landscape mode — the one-point-per-slide rule, the projection-vs-reading fork that decides density, the text diet (headlines and evidence, prose to notes), and the glance test. Use when asked my slides are too busy, how much text per slide, fix this wall-of-bullets d"
    },
    {
     "name": "slo-error-budget",
     "description": "Define Service Level Objectives (SLOs) and an error budget policy for a service. Use when asked to write SLOs, define SLIs, calculate an error budget, set reliability targets, or create an error budget policy. Produces a complete SLO document with SLI definitions, target calculation, error budget po"
    },
    {
     "name": "soap-note",
     "description": "Structure a clinical encounter into a clean SOAP note. Use when asked to write a SOAP note, document a patient encounter, turn visit notes into clinical documentation, or structure subjective/objective/assessment/plan. Produces a well-organised SOAP note — Subjective, Objective, Assessment (with dif"
    },
    {
     "name": "soc2-readiness",
     "description": "Assess SOC 2 readiness across the Trust Services Criteria and produce a gap remediation plan. Use when asked to prepare for a SOC 2 audit, run a SOC 2 readiness/gap assessment, scope controls, or get audit-ready. Produces a readiness report — scope & criteria, a control-by-control status, a weighted"
    },
    {
     "name": "social-ad-campaign",
     "description": "Plan and write a paid social advertising campaign. Use when asked to build a paid social campaign, create Meta/LinkedIn/TikTok/X ad copy, define a social ad strategy, or plan an advertising funnel across social platforms. Produces a complete campaign plan with audience targeting, ad set structure, c"
    },
    {
     "name": "social-media-audit",
     "description": "Audit an existing social media presence across all active platforms. Use when asked to review social media performance, analyse a brand's social presence, benchmark against competitors, or identify what's working and what isn't. Produces a scored audit with platform-by-platform analysis, content per"
    },
    {
     "name": "social-media-strategy",
     "description": "Build a social media strategy for a brand, product, or creator. Use when asked to create a social media strategy, define a social content strategy, plan content pillars, set social KPIs, or build a posting framework. Produces a complete strategy with audience definition, platform selection, content "
    },
    {
     "name": "solar-breakeven",
     "description": "Model whether solar panels pay for themselves for your roof — net cost after incentives, bill offset with degradation, electricity inflation, the inverter replacement, and the breakeven year, plus the policy risk no calculator controls. Use when asked are solar panels worth it, when does solar break"
    },
    {
     "name": "sop-writer",
     "description": "Write a Standard Operating Procedure (SOP) for any operational task. Use when asked to write an SOP, standard operating procedure, work instruction, or operating manual. Produces a formal SOP with purpose, scope, procedure steps, quality checks, and version control."
    },
    {
     "name": "source-triangulation",
     "description": "Verify a claim before repeating it — the independent-sources test (three citations of one press release is one source), the provenance trace to the original, and the confidence grading that separates established from echoed. Use when asked is this claim actually true, verify this stat before the dec"
    },
    {
     "name": "sourcing-strategy",
     "description": "Build a talent sourcing strategy for a hard-to-fill role. Use when asked to create a sourcing strategy, a candidate sourcing plan, a channel plan for hiring, or to figure out where to find candidates for a role. Produces a strategy — the ideal-candidate profile and where they are, prioritised sourci"
    },
    {
     "name": "sports-scores",
     "description": "Get live scores, schedules, and standings for major leagues with zero API keys — ESPN's public JSON endpoints via curl, covering NFL, NBA, MLB, NHL, and world football. Use when asked what's the score, did my team win, today's games, or league standings right now. Produces the scores with game state"
    },
    {
     "name": "spreadsheet-audit",
     "description": "Audit a spreadsheet before trusting it — the error hunt (hardcoded overrides, broken ranges, silent unit mixes), the fragility map (what breaks when rows are added), and the load-bearing-formula review that catches the mistake before the meeting does. Use when asked check this spreadsheet before we "
    },
    {
     "name": "spreadsheet-audit-live",
     "description": "Audit the user's REAL spreadsheet by opening it in the Cowork sandbox — not by reading a description of it. Use when asked to check this sheet before we present it, audit the model in my Drive, why don't these numbers add up, or is this spreadsheet safe to build on. Pulls the file via the Google Dri"
    },
    {
     "name": "spreadsheet-handover",
     "description": "Hand over a spreadsheet so it survives its author leaving — the README tab that decodes the sheet's logic, the update runbook with sources and cadence, the fragility warnings, and the walkthrough that transfers the judgment. Use when asked document this spreadsheet before I leave, hand over the mode"
    },
    {
     "name": "spreadsheet-or-database",
     "description": "Decide honestly when a spreadsheet should become a database or app — the five outgrowth signals (concurrent editing, relational strain, permission needs, scale, process-in-comments), what staying costs vs what migrating costs, and the incremental escape paths. Use when asked should this be a databas"
    },
    {
     "name": "sprint-brief",
     "description": "Generate a structured sprint brief from sprint data and goals. Use when asked to write a sprint brief, create a sprint summary, document sprint goals and scope, or produce a team-facing sprint overview. Produces a scannable brief with sprint goal, rationale, grouped work, critical path, risks, and d"
    },
    {
     "name": "sprint-planning",
     "description": "Structure and facilitate sprint planning sessions. Use when asked to plan a sprint, organise backlog items, assign story points, create sprint goals, or prepare sprint planning agendas. Produces a sprint goal, velocity-calibrated backlog, capacity plan, risk flags, and a structured sprint planning m"
    },
    {
     "name": "sprint-velocity-analysis",
     "description": "Analyze sprint velocity data and produce an engineering team health report covering delivery trends, capacity utilization, and improvement recommendations. Use when asked to analyze sprint velocity, review team delivery health, identify delivery risks, or produce a retrospective data analysis. Produ"
    },
    {
     "name": "sql-optimizer",
     "description": "Diagnose a slow SQL query and produce a concrete optimization plan. Use when asked to optimize SQL, speed up a slow query, reduce a query's cost/scan, fix a timeout, or review a query plan. Produces an analysis — the likely bottleneck, what the plan is doing wrong (full scans, bad joins, spills), th"
    },
    {
     "name": "sql-query-explainer",
     "description": "Explains, optimises, writes, and documents SQL queries. Use when asked to explain a SQL query, optimise slow SQL, translate SQL to plain English for non-technical stakeholders, write a query from a natural language description, or produce query documentation. Produces plain-English explanations, ann"
    },
    {
     "name": "stakeholder-influence-mapper",
     "description": "Map stakeholders for a product decision and produce a tailored influence strategy with talking points. Use when asked to get alignment, build consensus, get buy-in from engineering or finance or legal, navigate organisational resistance, or plan stakeholder conversations for a major initiative. Prod"
    },
    {
     "name": "stakeholder-update",
     "description": "Create concise executive stakeholder updates using the BLUF (Bottom Line Up Front) framework. Use when asked to write a status update, progress report, project communication, or executive briefing for leadership or stakeholders. Produces a BLUF-led update with status, key metrics, risks, upcoming mi"
    },
    {
     "name": "standing-meeting-audit",
     "description": "Audit the recurring meetings a team has accreted — each standing slot tested against its original purpose, current attendance reality, and outcomes, with keep/shrink/merge/kill verdicts and the two-week cancellation experiment that settles arguments. Use when asked audit our recurring meetings, our "
    },
    {
     "name": "startup-idea-validator",
     "description": "Pressure-test a startup idea the way a sharp investor or co-founder would — problem, market, wedge, moat, why-now, and the fastest cheap way to test it. Use when asked to validate a startup idea, evaluate a business idea, stress-test a concept, or decide whether something is worth building. Produces"
    },
    {
     "name": "statement-coach",
     "description": "Coach a statement of purpose or personal essay to admission strength — structural diagnosis, specific feedback, and revision plans on YOUR draft; the words stay yours. Use when asked to review my personal statement, improve my SOP, give feedback on my application essay, or why is my essay generic. P"
    },
    {
     "name": "statement-of-work",
     "description": "Write a tight Statement of Work (SOW) that prevents scope creep and payment disputes. Use when asked to write a SOW, a scope of work, a project agreement, or to formalise what was agreed after a proposal. Produces an SOW — scope (and explicit exclusions), deliverables with acceptance criteria, timel"
    },
    {
     "name": "status-report-pipeline",
     "description": "Build the pipeline that turns team updates into the rollup report without the Friday scramble — the collection format that aggregates cleanly, the altitude translation (team detail → leadership signal), and the automation-lite assembly that takes minutes. Use when asked I compile status from five te"
    },
    {
     "name": "stock-snapshot",
     "description": "Fetch a stock quote snapshot with keyless curl — Yahoo Finance's public chart endpoint, read with the discipline unofficial market data demands: timestamped, delayed-flagged, and never advice. Use when asked what's this stock at, how did the market do today, get me a ticker's recent range, or pull b"
    },
    {
     "name": "strategic-narrative-generator",
     "description": "Generate the strategic story connecting a product roadmap to company goals in a form non-technical stakeholders can repeat. Use when asked to explain the roadmap, present strategy to leadership or the board, write the why behind the roadmap, create a narrative for all-hands, or make the roadmap tell"
    },
    {
     "name": "strategy-memo",
     "description": "Write a strategy memo that commits to a bet and says what you won't do. Use when asked to write a strategy memo, articulate a strategy, make the case for a strategic direction, or align the team on where to focus. Produces a strategy memo — the strategic question, the diagnosis, the bet/approach, wh"
    },
    {
     "name": "student-feedback",
     "description": "Write constructive, specific feedback on student work that motivates and tells the student exactly how to improve. Use when asked to give feedback on a student's work, write grading comments, respond to an essay or assignment, or coach a learner. Produces feedback that names concrete strengths, prio"
    },
    {
     "name": "student-loan-strategy",
     "description": "Decide what the extra money does about student loans — attack them, invest alongside them, or ride a forgiveness track — with the three paths simulated on your actual loans and the guaranteed-vs-assumed framing kept honest. Use when asked should I pay off my student loans faster, pay loans or invest"
    },
    {
     "name": "study-notes-synthesizer",
     "description": "Turn lecture notes, slides, and readings into one exam-ready study guide — synthesis, not summary. Use when asked to make a study guide, combine my notes, prep me for the exam, or organize this course material. Produces a structured guide: core concepts with plain-language explanations, connections "
    },
    {
     "name": "style-fingerprint",
     "description": "Study 3-5 documents the user actually shipped and distil a compact style card — so every skill writes in their voice, not the model's. Use when asked to learn my writing style, make outputs sound like me, build a voice profile, or when a user complains AI drafts don't sound like them. Produces a sty"
    },
    {
     "name": "subagent-orchestration",
     "description": "Decompose work across parallel subagents properly — task slicing that avoids collisions, briefs that stand alone, and result integration that catches contradictions. Use when work can genuinely parallelise (research fan-outs, multi-file changes, independent analyses), when deciding whether to delega"
    },
    {
     "name": "subcontractor-scorecard",
     "description": "Score a subcontractor's performance across schedule reliability, quality, safety, paperwork, and change-order behaviour with weighted anchors. Use when asked to evaluate a sub, build a subcontractor scorecard, decide whether to rebid or rehire a trade, review sub performance for prequalification, or"
    },
    {
     "name": "subscription-audit",
     "description": "Find and rank the recurring-payment leak — every subscription annualized, sorted by real yearly cost, with the keep/cancel/downgrade pass and the where-they-hide checklist. Use when asked audit my subscriptions, how much am I spending on subscriptions, help me cancel stuff, or what recurring charges"
    },
    {
     "name": "subscription-auditor",
     "description": "Find the subscriptions you forgot you pay for — a tool-using agent audits statements and inboxes, prices the waste annually, and preps (never executes) the cancellations. Use when asked to audit my subscriptions, find recurring charges, what am I paying for, or help me cancel unused services. Produc"
    },
    {
     "name": "substack-notes-scraper",
     "description": "Scrapes a Substack Notes page and exports engagement data to a formatted .xlsx file. Use when asked to download, analyse, or export Substack Notes performance data including likes, comments, and restacks. Produces a formatted spreadsheet with conditional formatting, summary stats, and per-note engag"
    },
    {
     "name": "subtitle-caption",
     "description": "Write or translate subtitles/captions that respect reading speed and timing rules. Use when asked to write subtitles, captions, SRT/VTT content, or to translate subtitles for a video. Produces properly-formatted, readable subtitles — line-length and reading-speed compliant, well-segmented, with tran"
    },
    {
     "name": "sun-and-moon",
     "description": "Get sunrise, sunset, golden hour, day length, and moon phase for any location with zero API keys — sunrise-sunset.org and Open-Meteo via curl, times converted to local. Use when asked when is sunset today, golden hour for a photo shoot, how long is the day, what's the moon phase tonight, or sun time"
    },
    {
     "name": "supplier-scorecard",
     "description": "Build a quarterly supplier performance scorecard with a weighted grade and a clear escalate/develop/exit call. Use when asked to review supplier performance, prepare a quarterly business review for a vendor, score a supplier on OTIF and quality, or decide whether to escalate or exit a supplier. Prod"
    },
    {
     "name": "support-macro",
     "description": "Write reusable support macros / canned responses that sound human, not robotic. Use when asked to write a support macro, a canned response, a saved reply, or a template for a common customer ticket. Produces a macro — an empathetic opener, the clear answer/steps, placeholders for personalisation, an"
    },
    {
     "name": "support-runbook",
     "description": "Write a support runbook for handling a recurring issue type consistently. Use when asked to write a support runbook, a troubleshooting playbook for agents, a handling guide for a common issue, or a tier-1 response procedure. Produces a runbook — issue identification, triage/severity, step-by-step di"
    },
    {
     "name": "support-staffing-model",
     "description": "How many support agents does the queue actually need — Erlang C, computed, not 'tickets per agent' folklore. Use when staffing a support/CS team, defending headcount, or checking whether an SLA is mathematically possible with the current roster. Produces agent counts across load scenarios (with shri"
    },
    {
     "name": "survey-design-basics",
     "description": "Design a survey that measures instead of leads — neutral question wording, answer scales that don't smuggle conclusions, the length that respects completion rates, and the analysis plan written before launch. Use when asked write our customer/employee survey, check these questions for bias, why are "
    },
    {
     "name": "sycophancy-challenger",
     "description": "Flip Claude’s default from validation to adversarial critique. Use when you are about to make a high-stakes decision, commit to a plan, or pitch something you have not stress-tested. Produces structured challenges, steelmanned counter-arguments, and the strongest case against your position — a genui"
    },
    {
     "name": "synthetic-user-research",
     "description": "Use AI personas for early-stage research signal — with hard guardrails on what synthetic methods can and cannot validate. Use when asked to run synthetic user testing, simulate user reactions with AI personas, pretest a survey or message before fielding it, or decide whether synthetic research is ap"
    },
    {
     "name": "system-design-interview",
     "description": "Structure a complete system design answer for interview questions or real architecture sessions. Use when asked to design a system, answer a system design interview question, or architect a solution at scale. Produces a structured answer covering requirements, capacity estimates, high-level design, "
    },
    {
     "name": "task-triage-matrix",
     "description": "Triage an overwhelming task list into what actually gets done — the urgent/important sort applied honestly (with the two corrections the classic matrix needs), the do/schedule/delegate/drop verbs, and the list hygiene that keeps triage from becoming a weekly archaeology dig. Use when asked my task l"
    },
    {
     "name": "tax-planning-checklist",
     "description": "Generate a structured tax planning checklist and review framework for any individual or business context. Use when asked to review tax planning, prepare for year-end tax, check tax efficiency, or identify tax-saving opportunities. Produces a checklist of considerations, common reliefs, and a review "
    },
    {
     "name": "tdd-workflow",
     "description": "Drive a feature with a disciplined test-driven development loop — red, green, refactor. Use when implementing a feature or fixing a bug and you want tests to lead, or when asked to 'do this with TDD' / write the test first. Produces a step-by-step red-green-refactor plan: the failing test to write f"
    },
    {
     "name": "teaching-lesson-plan",
     "description": "Design a structured lesson plan for any subject, audience, or format. Use when asked to write a lesson plan, course outline, teaching session, workshop curriculum, or training module. Produces a complete lesson plan with learning objectives, activities, timing, assessment, and differentiation guidan"
    },
    {
     "name": "team-budget-tracker",
     "description": "Track a team's budget so surprises die young — the commitment-based view (spent + committed + planned, not just invoiced), the category grain that matches how the team actually spends, the monthly close with its one-sentence read, and the forecast honesty for the year-end question. Use when asked tr"
    },
    {
     "name": "team-health-check",
     "description": "Runs a structured team health assessment across key dimensions. Use when asked to run a team health check, assess team morale, facilitate a retrospective on ways of working, or evaluate team dynamics. Produces a health assessment with RAG status per dimension, underlying signals, and prioritised imp"
    },
    {
     "name": "team-offsite-planner",
     "description": "Plan a team offsite from goals to full agenda. Use when asked to plan a team offsite, away day, team retreat, quarterly offsite, or team-building event. Produces a full agenda, session designs, facilitation notes, and logistics checklist."
    },
    {
     "name": "tech-radar",
     "description": "Build a technology radar for an engineering team, categorizing technologies into Adopt/Trial/Assess/Hold quadrants following the ThoughtWorks Tech Radar format. Use when asked to create a tech radar, evaluate the team's technology landscape, categorize tools and frameworks, or establish a technology"
    },
    {
     "name": "technical-debt-register",
     "description": "Document and prioritize a technical debt backlog with business impact, effort estimates, and resolution strategy. Use when asked to audit technical debt, create a debt register, prioritize tech debt for a quarter, document architectural shortcuts, or build a debt reduction roadmap. Produces a struct"
    },
    {
     "name": "technical-spec-template",
     "description": "Create structured technical specification documents that bridge product requirements and engineering implementation. Use when writing a tech spec, engineering spec, system design doc, or API specification. Produces a complete spec with problem statement, proposed solution, data model, API design, al"
    },
    {
     "name": "template-designer",
     "description": "Turn a document the team keeps rewriting into a template that actually helps — extract the recurring skeleton, mark what varies with real placeholder prompts, keep it lighter than the ceremony it replaces, and pilot it before decreeing it. Use when asked make a template from this doc, we write this "
    },
    {
     "name": "tenant-screening-guide",
     "description": "Design a fair, consistent tenant screening process for a rental. Use when asked how to screen tenants, set rental criteria, evaluate rental applicants, or build a tenant screening process. Produces a screening framework — written objective criteria, the application & checks, a consistent evaluation "
    },
    {
     "name": "test-case-writer",
     "description": "Turn a requirement or user story into clear, executable test cases. Use when asked to write test cases, test scenarios, a test suite for a feature, or to derive tests from acceptance criteria. Produces structured test cases — preconditions, steps, test data, expected results — across happy path, edg"
    },
    {
     "name": "test-strategy-doc",
     "description": "Write a test strategy document from a feature spec, PRD, or system description. Use when asked to create a test plan, write a test strategy, define QA approach, or plan testing for a feature or release. Produces a complete test strategy with scope, risk assessment, test types, coverage targets, and "
    },
    {
     "name": "the-car-dealership",
     "description": "Simulate the car-buying gauntlet before you walk in — the four-square worksheet, the payment-question trap, the trade-in shuffle, and the finance office's second sales floor, all run against your actual deal. Use when asked practice negotiating at a dealership, simulate the finance office, what tric"
    },
    {
     "name": "the-churning-customer",
     "description": "Simulate the exact customer who will quietly cancel in month 4 — their internal monologue through the lifecycle and the honest exit interview they never gave you. Use when asked why do customers really churn, simulate a churning customer, roleplay the customer who cancels, or what does silent churn "
    },
    {
     "name": "the-due-diligence-call",
     "description": "Simulate the due-diligence call where an acquirer's or investor's analyst takes your metrics apart — the questions behind the spreadsheet, the moment a number wobbles, and a debrief on which answers create risk. Use when asked simulate due diligence on my startup, stress-test my metrics before the r"
    },
    {
     "name": "the-insurance-adjuster",
     "description": "Simulate the adjuster's settlement call after your accident or loss — the recorded-statement asks, the quick-settlement anchor, the friendly minimization — run against your actual claim, with a debrief on every answer that shrank it. Use when asked the adjuster wants a recorded statement, practice t"
    },
    {
     "name": "the-journalist-call",
     "description": "Simulate a hostile-but-fair journalist interview about your company or announcement — the questions you fear, live follow-ups on every dodge, then the story they'd file. Use when asked to media-train me, simulate a press interview, prep me for a journalist call, or how will this announcement be cove"
    },
    {
     "name": "the-open-house",
     "description": "Simulate the open house and the listing agent's read of you — the questions that profile your budget and urgency, the staging that hides what inspection finds, and the offer-pressure choreography, run before you fall in love with anything. Use when asked what is the listing agent thinking, practice "
    },
    {
     "name": "the-price-pushback",
     "description": "Simulate the client who grinds on your price — the budget theater, the competitor quote, the scope squeeze — against your actual offer, with a debrief on where you caved and what holding would have sounded like. Use when asked simulate a client negotiating my rate, practice price pushback, they said"
    },
    {
     "name": "the-procurement-gauntlet",
     "description": "Simulate enterprise procurement and security review of your product before your first big deal meets it for real — the questionnaire, the gaps, the deal-slowing findings. Use when asked to prep for enterprise procurement, simulate a security review, why do enterprise deals stall, or get ready for ve"
    },
    {
     "name": "the-promotion-committee",
     "description": "Simulate the calibration meeting that discusses your promotion after your manager leaves the room — the debate, the packet's holes, the verdict. Use when asked will I get promoted, simulate the promo committee, stress-test my promotion packet, or why did my promo get rejected. Produces the committee"
    },
    {
     "name": "the-thesis-defense",
     "description": "Simulate your thesis defense before the real one — a committee of examiner archetypes probing YOUR actual thesis, the questions you hoped nobody would ask, and a debrief with preparation priorities. Use when asked simulate my thesis defense, grill me on my dissertation, what will my committee ask, o"
    },
    {
     "name": "the-visa-interview",
     "description": "Simulate a consular visa interview — the 90-second assessment, the questions behind the questions, and a debrief on which answers helped and hurt. Use when asked prep me for my visa interview, simulate the consular interview, why might my visa be denied, or practice my student visa questions. Produc"
    },
    {
     "name": "thesis-outline",
     "description": "Build a defensible thesis or dissertation outline — argument-first structure, chapter by chapter, with the through-line visible. Use when asked to outline my thesis, structure my dissertation, plan my capstone, or organize my research into chapters. Produces a full outline: the one-sentence thesis, "
    },
    {
     "name": "thread-to-decision",
     "description": "Land a sprawling chat thread on an actual decision — the summarize-and-fork move (positions restated, the question isolated), the decider-and-deadline injection, and the recorded close that ends the forty-message orbit. Use when asked this thread is going in circles, get a decision out of this discu"
    },
    {
     "name": "thread-to-decision-live",
     "description": "Turn a REAL Slack thread (or channel) into a logged decision — read it, extract what was decided, who owns what, and record it in Notion — not a template for writing decisions. Use when asked to capture the decision from this thread, log what we agreed, turn this Slack discussion into a decision rec"
    },
    {
     "name": "threat-model",
     "description": "Threat-model a system or feature to find where it could be attacked, before you build it. Use when asked to threat-model, do a security design review, identify attack surface, or apply STRIDE to a design. Produces a structured threat model: assets, trust boundaries and data flows, threats enumerated"
    },
    {
     "name": "thumbnail-creator",
     "description": "Generate article or newsletter thumbnail candidates using the Gemini API from inside Claude Code. Claude reads article copy, proposes composition concepts, writes image generation prompts incorporating brand specs, calls Gemini to generate the images, evaluates the results via computer vision, and r"
    },
    {
     "name": "timeshare-contract-decoder",
     "description": "Decode a timeshare contract before signing — the lifetime cost math, the perpetuity and fee-escalation clauses, the rescission window, and the honest resale reality. Use when asked to review this timeshare, decode my timeshare contract, can I get out of a timeshare, or is this vacation ownership wor"
    },
    {
     "name": "token-cost",
     "description": "Measure before optimizing — estimate token counts locally with stated heuristics, price them at your model's rates, and quantify before/after savings, because token optimization without measurement is vibes. Use when asked how many tokens is this, what does this context cost per call, is this optimi"
    },
    {
     "name": "token-diet",
     "description": "Cut LLM output tokens 40–70% by stripping grammatical scaffolding while preserving every fact — telegraphic output modes, when they pay (pipelines, long sessions) and when they don't (single shots, human-facing prose), with the mode lines to switch on demand. Use when asked make the model respond te"
    },
    {
     "name": "tool-permission-review",
     "description": "Review what an agent is actually allowed to do before you turn it loose — the tool-by-tool audit (each capability's blast radius), the least-privilege pass that removes what the task doesn't need, the dangerous-combination check, and the allow/ask/deny tiering. Use when asked review my agent's permi"
    },
    {
     "name": "tool-procurement-eval",
     "description": "Evaluate a new tool before it joins the stack — the problem-first framing (tools answer needs, not demos), the trial designed with success criteria upfront, the stack-fit check (integration, overlap, the tool-sprawl tax), and the security/data review sized to the stakes. Use when asked should we buy"
    },
    {
     "name": "tooling-risk-assessment",
     "description": "Assess an injection-mold or production tooling decision before cutting steel — soft vs hard tooling tradeoff, tool life vs forecast, cavitation math, T1 sample timeline, cost of design changes after tooling, and kill criteria. Use when asked whether to kick off tooling, choose soft vs hard tools, si"
    },
    {
     "name": "tornado-sensitivity",
     "description": "Which assumption actually moves the answer — one-at-a-time sensitivity, ranked into a tornado. Use when a model's output is being argued about (LTV, ROI, forecast) and the room is debating drivers that don't matter, or before spending diligence effort: swing every driver low→high and see which one o"
    },
    {
     "name": "tos-decoder",
     "description": "Decode a terms of service or privacy policy into what you're actually agreeing to, ranked by real-world impact. Use when someone asks 'what am I agreeing to', 'decode this privacy policy', 'is this ToS bad', or 'should I click accept'. Produces a ranked findings table with a 'should I care?' verdict"
    },
    {
     "name": "transcreation",
     "description": "Transcreate marketing/brand copy for another language and culture — recreate the impact, not the words. Use when asked to adapt a tagline, ad, slogan, campaign, or brand message for a new market, or when a translation is 'correct but flat'. Produces a transcreated version that lands emotionally in-c"
    },
    {
     "name": "travel-brief",
     "description": "Turn a business trip into a one-page brief that runs itself — the itinerary with buffers and failure modes, the meeting logistics pre-solved (addresses, contacts, backup numbers), the packing-and-prep list by trip type, and the expense capture set up before departure. Use when asked prep my business"
    },
    {
     "name": "unblock-protocol",
     "description": "Get unstuck on purpose — the stuck-type diagnosis (don't-know-how, can't-decide, waiting, avoiding, too-big), the matched unblock move for each, and the timebox that stops noble struggling before it eats the day. Use when asked I'm stuck on this and don't know why, I keep avoiding this task, how lon"
    },
    {
     "name": "underwriting-narrative",
     "description": "Write the underwriting file narrative for a risk: the risk story, exposure quantification, loss-history read, mitigating and aggravating factors, terms and subjectivities rationale, appetite fit, and a refer-or-bind recommendation. Use when asked to write up an underwriting file, document why we're "
    },
    {
     "name": "unit-economics",
     "description": "Model the unit economics of a business — CAC, LTV, payback, contribution margin — from real inputs. Use when asked to calculate unit economics, work out LTV:CAC, find the payback period, or check whether a business model is viable per customer. Produces a computed unit-economics summary (LTV, CAC, r"
    },
    {
     "name": "user-interview-synthesis",
     "description": "Synthesises user interview transcripts into structured research findings. Use when asked to analyse interview notes, synthesise qualitative research, identify themes from interviews, or turn raw interview data into actionable product insights. Produces a themed synthesis with supporting quotes per t"
    },
    {
     "name": "user-journey-map",
     "description": "Map a user's journey through a product or experience, phase by phase, with their actions and how they feel. Use when asked to map a user/customer journey, show the experience end-to-end, or find friction and drop-off points. Produces a ready-to-render Mermaid journey diagram (renders live, exportabl"
    },
    {
     "name": "user-research-synthesis",
     "description": "Analyze and synthesize user research findings into structured, actionable insights. Use when given user research data, interview transcripts, survey results, or user feedback that needs to be analyzed and summarised. Produces a themed synthesis with prevalence data, supporting quotes, pain points an"
    },
    {
     "name": "user-story-writer",
     "description": "Write well-structured user stories with acceptance criteria and edge cases. Use when asked to write user stories, create tickets from a feature brief, convert a PRD into stories, or write acceptance criteria. Produces ready-to-estimate stories in the standard format with clear acceptance criteria, e"
    },
    {
     "name": "ux-research-plan",
     "description": "Create a structured UX research plan for any product question or feature. Use when asked to write a research plan, design a user study, create a discussion guide, write screener questions, or plan usability testing. Produces a full research plan with objectives, methodology, screener, discussion gui"
    },
    {
     "name": "value-proposition",
     "description": "Craft a sharp value proposition that says who it's for, the outcome, and why you over the alternative. Use when asked to write a value prop, a value proposition, a one-liner, or to clarify 'what do we even say we do?'. Produces a primary value-prop statement, a plain-language one-liner, 3 benefit-le"
    },
    {
     "name": "vc-partner-meeting",
     "description": "Simulate the VC partner meeting that discusses your pitch after you leave the room — four partner archetypes debate, then write the internal verdict memo. Use when asked how will VCs discuss my pitch, simulate the partner meeting, stress-test my fundraise, or what happens after the pitch. Produces t"
    },
    {
     "name": "vendor-breakup-email",
     "description": "End a vendor, freelancer, or service relationship cleanly — the notice email that cites the contract, the transition asks that protect your data and continuity, and the door-open close that costs nothing. Use when asked write a cancellation email to our vendor, we're not renewing how do I tell them,"
    },
    {
     "name": "vendor-comparison-matrix",
     "description": "Compare vendors on a matrix that decides instead of decorates — the criteria weighted before the demos (so the shiny demo can't rewrite them), the evidence-based scoring with the marketing-vs-verified flags, the total-cost row that includes switching, and the reference-check questions that get hones"
    },
    {
     "name": "vendor-contract-checklist",
     "description": "Review a vendor/SaaS contract against a practical checklist before you sign. Use when asked to review a vendor contract, check a SaaS/MSA/subscription agreement, flag risky terms, or prepare negotiation points before signing. Produces a structured review — key terms extracted, a risk-flagged checkli"
    },
    {
     "name": "vendor-evaluation",
     "description": "Create a structured vendor evaluation framework for any procurement decision. Use when asked to evaluate vendors, compare suppliers, run an RFP scoring process, or assess a software or service provider. Produces a weighted scorecard, evaluation criteria, and recommendation framework."
    },
    {
     "name": "vendor-security-review",
     "description": "Run a third-party / vendor security review and assign a risk tier with required controls. Use when asked to assess a vendor's security, run a third-party risk assessment, complete a security questionnaire about a vendor, or decide what due diligence a new tool needs. Produces a vendor risk assessmen"
    },
    {
     "name": "verification-before-completion",
     "description": "Verify work actually meets its brief BEFORE declaring it done — a structured self-review pass that catches the gaps, unmet requirements, and untested claims that 'looks finished' hides. Use before handing over any deliverable (document, code, analysis, plan), when past work kept coming back with 'yo"
    },
    {
     "name": "version-chaos-untangler",
     "description": "Untangle a document that exists in six copies across email, drives, and desktops — establish the canonical version defensibly, merge the divergent edits, and install the single-source rule that prevents the rematch. Use when asked which version is the real one, merge these document copies, we've bee"
    },
    {
     "name": "vet-estimate-decoder",
     "description": "Decode a veterinary treatment estimate — what each line is for, which items are core vs precautionary, and how to have the options conversation nobody offers you. Use when someone asks 'is this vet estimate reasonable', 'decode my vet's treatment plan', 'do we need all these tests', or 'I can't affo"
    },
    {
     "name": "viral-content-framework",
     "description": "Build a framework for creating shareable, high-reach social media content. Use when asked to plan viral content, develop a shareable content strategy, create a hook writing system, or build a repeatable process for content that gets shared. Produces a platform-specific viral content framework with h"
    },
    {
     "name": "voice-agent-design",
     "description": "Design a voice AI agent for phone or in-app conversations — call flows, interruption handling, escalation to humans, and the metrics that catch a bad voice experience. Use when asked to design a voice agent, automate a phone line, spec an IVR replacement, or review why callers hate an existing voice"
    },
    {
     "name": "voice-of-customer-program",
     "description": "Stand up a Voice of Customer (VoC) program that turns feedback into action. Use when asked to build a VoC program, design a customer feedback loop, consolidate feedback sources, or set up a closed-loop feedback process. Produces a VoC program design — objectives, feedback sources and channels, a tax"
    },
    {
     "name": "vuln-triage",
     "description": "Triage a vulnerability or scanner finding — assess real severity, exploitability, and how urgently to fix. Use when asked to triage a CVE, prioritize scanner/pentest findings, assess a vuln's risk, or decide what to patch first. Produces a triage verdict: CVSS-informed severity adjusted for your con"
    },
    {
     "name": "weather-now",
     "description": "Get current weather and forecasts with zero API keys — wttr.in one-liners for humans, Open-Meteo JSON for data, with the exact curl commands and format codes. Use when asked what's the weather, will it rain today, forecast for a city, or get me weather data for a location. Produces the live conditio"
    },
    {
     "name": "wedding-budget",
     "description": "Build a wedding budget that survives to the wedding — allocation by real shares, the per-guest lever made explicit, the routinely-forgotten line items priced in from day one, and a contingency that isn't decorative. Use when asked make a wedding budget, how do people split X across a wedding, we hav"
    },
    {
     "name": "wedding-logistics-planner",
     "description": "Plan the wedding day as the operation it is — the minute-level run sheet, the vendor call sheet, the who-handles-problems roster, and the buffer discipline that keeps the couple out of logistics on the day. Use when asked make our wedding day timeline, day-of run sheet, who tells the vendors where t"
    },
    {
     "name": "wedding-speech",
     "description": "A best-man/maid-of-honour/parent wedding toast that actually lands — funny without roasting, moving without syrup, short enough that nobody checks their phone. Use when someone has to give a wedding speech and has either nothing or a dangerous first draft. Produces a 2-4 minute toast built on one go"
    },
    {
     "name": "wedding-vendor-contract-decoder",
     "description": "Decode a wedding vendor contract — venue, photographer, caterer, band — before signing: deposits and their refundability, cancellation and postponement terms, the substitute-performer and force-majeure clauses, and overtime math. Use when someone asks review this venue contract, is this photographer"
    },
    {
     "name": "weekly-review-ritual",
     "description": "Install the weekly review that keeps work from managing you — the 30-minute Friday ritual: close the week's loops, sweep the capture points, choose next week's big three before the calendar chooses for you, and the two questions that compound. Use when asked set up a weekly review, my weeks just hap"
    },
    {
     "name": "what-to-ask",
     "description": "Get the five questions that matter before you sign, buy, or agree to anything — the front door to the decoder family, routed by situation. Use when asked what should I ask before signing this, I'm about to buy X what do I check, what questions for the landlord/dealer/contractor/HR, or what am I forg"
    },
    {
     "name": "when-someone-dies",
     "description": "The first two weeks after a death, organized — what genuinely needs doing now, what only feels urgent, who to notify in what order, and the documents everything else will require. Use when asked someone just died what do I do, checklist after a death, help me handle my parent's affairs, or what need"
    },
    {
     "name": "which-skill",
     "description": "Route a fuzzy request to the right skill in this library. Use when the user is unsure which skill fits, asks 'which skill should I use for X', describes a task without naming a skill, or when a request could plausibly match several skills. Produces a best-fit recommendation with the inputs to gather"
    },
    {
     "name": "whiteboard-to-spec",
     "description": "Turn photos of a whiteboard, sticky-note wall, or napkin sketch into a structured spec the team can execute. Use when given whiteboard photos after a workshop, sketch images of a flow or architecture, or asked to 'write up what we drew'. Produces a structured write-up — decisions, flows, open questi"
    },
    {
     "name": "wiki-summary",
     "description": "Fetch Wikipedia's current summary of any topic with zero API keys — the REST summary endpoint via curl, for answers that need today's article rather than training-data memory. Use when asked what does Wikipedia say about X, get me the current summary of a topic, check a fact against Wikipedia, or ha"
    },
    {
     "name": "win-loss-analysis",
     "description": "Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win"
    },
    {
     "name": "docx-tracked-changes",
     "description": "Produce properly-formatted tracked changes for a Word document. Use when asked to redline a document, suggest edits to a contract or document, create tracked changes for review, or mark up a document with proposed revisions. Produces a complete redline with insertions, deletions, and margin comments"
    },
    {
     "name": "word-document",
     "description": "Build a real, formatted Word (.docx) document — headings, styles, tables, TOC-ready. Use when asked to produce a Word doc, a .docx, a formatted report/contract/proposal/letter as an actual file (not markdown). Produces an actual .docx via a generated python-docx script with proper heading styles, bo"
    },
    {
     "name": "working-agreements",
     "description": "Write a team's working agreements — the small set of explicit norms (communication, meetings, decisions, conflict) that replace the assumptions people were silently violating, built from the team's actual frictions and revisited on a cadence. Use when asked create team working agreements, set norms "
    },
    {
     "name": "workshop-designer",
     "description": "Design working sessions that produce artifacts, not vibes — the outcome-backwards agenda, the activity formats that beat open discussion (silent writing, dot voting, structured rounds), the energy arc, and the output-capture that survives the room. Use when asked design a workshop for X, plan our pl"
    },
    {
     "name": "workshop-facilitation-guide",
     "description": "Design and facilitate any workshop, working session, or collaborative meeting. Use when asked to plan a workshop, design a facilitated session, run a ideation session, or create a workshop agenda. Produces a complete facilitation guide with session design, activity instructions, timing, and material"
    },
    {
     "name": "world-clock",
     "description": "Get the current time anywhere and convert between time zones with zero API keys — timeapi.io via curl (worldtimeapi fallback), plus the DST-safe meeting-window math. Use when asked what time is it in a city, convert 3pm my time to Tokyo, find a meeting slot across time zones, or what's the UTC offse"
    },
    {
     "name": "writing-great-skills",
     "description": "Author a high-quality Agent Skill (SKILL.md) that an AI reliably triggers and executes well — strong frontmatter, a sharp description with trigger phrases, a clear output contract, quality checks, and anti-patterns. Use when asked to write a skill, create a SKILL.md, improve a skill, review a skill "
    },
    {
     "name": "writing-plans",
     "description": "Write an executable work plan BEFORE starting a complex task — decomposed steps with verification points, risks pre-named, and explicit stop conditions — so execution becomes checking boxes instead of improvising. Use when a task will take many steps, when asked to plan before doing, when previous a"
    },
    {
     "name": "youtube-script-writer",
     "description": "Write engaging, high-retention YouTube video scripts with visual and audio cues. Use when asked to write a YouTube script, design a video outline, draft a video hook, or structure a video narrative. Produces a polished script with multiple hook options, step-by-step video body, and clear visual/audi"
    }
   ],
   "ok": true
  }
 ]
}