{
  "$comment": "RFC-0034. The catalogue index: pack display order and the outcome browse axis (RFC-0026). Pack metadata lives in packs/<pack>/pack.json; membership is the folders — a skill is in a pack because it sits at packs/<pack>/skills/<name>/.",
  "version": "1.0.0",
  "packs": ["core", "solution-architect", "product-manager", "dev-team", "sre-oncall", "stakeholder-comms", "design", "ai-engineering", "api-builder", "converters", "experience-design", "research", "trackers", "data-analytics", "grc", "infra-as-code", "frontend", "skill-engineering", "career", "civil-architect", "operations-manager", "event-planner", "interior-designer", "startup-legal"],
  "outcomes": {
    "decide-what-to-build": {
      "for": "Product managers · founders · strategists",
      "description": "Turn a direction into a committed, measurable plan: press releases, strategy frameworks, OKRs, business cases, requirements, PRDs, and the metrics that will say whether it worked.",
      "skills": [
        "prfaq",
        "strategy-analysis",
        "okr-cascade",
        "business-case",
        "capacity-cost-model",
        "requirements-interview",
        "prd-draft",
        "nfr-spec",
        "success-metrics",
        "user-story-splitter",
        "user-journey-map",
        "feedback-synthesis"
      ]
    },
    "design-the-system": {
      "for": "Architects · tech leads",
      "description": "Commit the shape before the code: decision records, design docs, diagrams, API and data contracts, migration and threat models, and the design of any agentic parts.",
      "skills": [
        "adr-generator",
        "design-doc",
        "architecture-diagrams",
        "reverse-architecture",
        "interactive-diagram",
        "figma-diagrams",
        "api-contract-draft",
        "data-contract",
        "threat-model",
        "agent-threat-model",
        "migration-plan",
        "agent-loop-design",
        "subagent-design",
        "agent-budget",
        "terraform-module",
        "mcp-pairing",
        "context-graph",
        "event-contract-draft"
      ]
    },
    "build-and-review-software": {
      "for": "Software teams · coding agents",
      "description": "The loop around the code itself: supervised implementation, adversarial review panels, test plans, triage, pull request descriptions, a ranked technical-debt register, accessibility and static-analysis passes, and the policy files agents read.",
      "skills": [
        "feature-implement-loop",
        "pre-merge-review",
        "devils-advocate",
        "council-review",
        "accessibility-audit",
        "sonar-onboard",
        "sonar-review",
        "test-plan-generator",
        "bug-triage",
        "pr-description-writer",
        "tech-debt-register",
        "agents-md-generator",
        "llm-eval-harness",
        "eval-harness-generator",
        "backlog-triage",
        "tracker-brief-sync",
        "dependency-upgrade-review",
        "codebase-tour",
        "refactor-plan",
        "behaviour-equivalence",
        "rendering-strategy",
        "web-performance-review",
        "bundle-size-review",
        "judge-audit"
      ]
    },
    "build-on-the-claude-api": {
      "for": "Teams building on the Anthropic API",
      "description": "Skills for teams building directly on the Anthropic API — prompt caching strategy, token budgeting, eval generation, and tool-use schema writing.",
      "skills": [
        "prompt-caching-advisor",
        "token-budget-estimator",
        "eval-harness-generator",
        "tool-use-schema-writer"
      ]
    },
    "run-and-recover-the-service": {
      "for": "SRE · on-call · platform teams",
      "description": "Operate what shipped: runbooks, observability design, release notes, incident communication, and the postmortem that closes the loop.",
      "skills": [
        "runbook-generator",
        "observability-plan",
        "release-notes",
        "incident-comms",
        "postmortem-generator",
        "launch-readiness",
        "cloud-cost-review",
        "delivery-metrics-report",
        "terraform-plan-review",
        "rollout-plan",
        "slo-spec"
      ]
    },
    "explain-it-to-decision-makers": {
      "for": "Anyone presenting to leadership",
      "description": "Get a non-technical audience to a decision: audience profiling, deck outlines and real decks, exec summaries, decision logs, and how-to guides.",
      "skills": [
        "audience-profile",
        "slide-outliner",
        "exec-summary",
        "decision-log",
        "guide-builder",
        "team-status-report"
      ]
    },
    "govern-ai-use": {
      "for": "AI enablement · engineering leaders · risk owners",
      "description": "Adopt AI deliberately and prove what it is doing: readiness assessment, use-case triage, rollout plans, acceptable-use policy, adoption staging, and usage reporting.",
      "skills": [
        "ai-readiness-assessment",
        "ai-use-case-triage",
        "ai-adoption-rollout",
        "ai-usage-policy",
        "agent-adoption-stage",
        "agent-config-review",
        "agent-incident-response"
      ]
    },
    "create-on-brand-collateral": {
      "for": "Marketers · designers · anyone making a deck",
      "description": "Make collateral that looks like it came from your team: capture the brand once, then build decks with your logo, colours and fonts.",
      "skills": [
        "brand-kit",
        "slide-outliner"
      ]
    },
    "get-a-draft-ready-to-ship": {
      "for": "Anyone shipping a document",
      "description": "The passes either side of a generator: collect a messy input into a structured brief, critique the argument, and strip the machine artifacts before it leaves the building.",
      "skills": [
        "brief-intake",
        "doc-critique",
        "output-hygiene",
        "file-to-markdown",
        "md-to-docx",
        "md-to-xlsx",
        "md-to-pptx",
        "md-to-confluence"
      ]
    },
    "design-the-experience": {
      "for": "Designers · content designers · UX writers",
      "description": "Shape what people see and read before it's built: information architecture, interface copy, content specs, component specs and service blueprints.",
      "skills": [
        "content-design",
        "design-system-spec",
        "information-architecture",
        "service-blueprint",
        "ux-writing",
        "locale-check"
      ]
    },
    "research-a-question": {
      "for": "Researchers · analysts · anyone with a question to answer",
      "description": "Take a question to a sourced answer: a research plan with a stopping rule, a cited synthesis of the sources, and competing explanations weighed against the evidence.",
      "skills": [
        "hypothesis-comparison",
        "research-plan",
        "source-synthesis"
      ]
    },
    "define-and-trust-the-numbers": {
      "for": "Data analysts · analytics engineers",
      "description": "Make the numbers a business runs on mean one thing: SQL reviewed for wrong answers, and dashboards specced before they're built, with every number on them defined.",
      "skills": [
        "dashboard-spec",
        "sql-review"
      ]
    },
    "manage-risk-and-compliance": {
      "for": "Compliance, privacy and risk leads",
      "description": "Prepare the material compliance asks for: a data protection impact assessment, a SOC 2 evidence map, a risk register with owners and review dates, and answers to a customer's security questionnaire with the evidence behind each.",
      "skills": [
        "dpia",
        "risk-register",
        "soc2-evidence-map",
        "security-questionnaire-response"
      ]
    },
    "build-agent-skills": {
      "for": "Anyone writing skills for an AI agent",
      "description": "Write and review Agent Skills for any tool: a portable SKILL.md with evals, and an audit of an existing skill before it ships.",
      "skills": [
        "skill-author",
        "skill-review"
      ]
    },
    "apply-for-a-job": {
      "for": "Anyone applying for a job, in any field",
      "description": "Choose which of an employer's roles to go for, then prepare one application that is tailored and true: an honest fit check against the posting, a resume reworked without adding a claim, a cover letter built only from what you supplied, and the application form's answers drafted from your resume.",
      "skills": [
        "role-shortlist",
        "job-fit-analysis",
        "resume-tailor",
        "cover-letter",
        "application-form-answers"
      ]
    },
    "design-a-building": {
      "for": "Architects · building designers · owners planning a build",
      "description": "Go from a room list and a footprint to a first floor plan: every room at its size, doors on real walls, every room reachable, drawn to scale and checked before anyone sees it.",
      "skills": [
        "floor-plan-layout"
      ]
    },
    "staff-the-shifts": {
      "for": "Operations managers · shop, hotel, leisure-centre and care-home managers",
      "description": "Turn who is available and what each shift needs into a rota with every shift covered by the right people, and nobody double-booked, over their hours or short of rest.",
      "skills": [
        "shift-roster"
      ]
    },
    "plan-an-event": {
      "for": "Event planners · wedding planners · conference organisers",
      "description": "Seat every guest with the people they should and shouldn't be near, and run the day with no room or person booked twice.",
      "skills": [
        "seating-plan",
        "run-of-show"
      ]
    },
    "furnish-a-room": {
      "for": "Interior designers · homeowners · office managers",
      "description": "Fit a room's furniture at real sizes with every door, bed side, chair and route clear, and each turning space where it's needed, drawn to scale and checked.",
      "skills": [
        "furniture-layout"
      ]
    },
    "handle-the-legal-basics": {
      "for": "Founders without a lawyer on retainer",
      "description": "Sign agreements you understand and know what a round does to your ownership, with a clear line on what is worth paying a lawyer for.",
      "skills": [
        "contract-check",
        "cap-table"
      ]
    }
  },
  "retired": {
    "tech-comparison-matrix": { "in": "0.16.13", "why": "On evals it was never revised against, the agent without it did as well, and its weighted totals were wrong in 4 of 8 runs." },
    "db-schema-design": { "in": "0.16.13", "why": "On evals it was never revised against, the agent without it met as many checks (73% against 71%) and got types, time zones and constraints right unprompted." },
    "metric-definition": { "in": "0.16.13", "why": "On evals it was never revised against, the agent without it did everything the skill teaches unprompted and won 13 of 16 blind verdicts." },
    "contribution-wizard": { "in": "0.16.13", "why": "It prescribed a skill layout this catalogue no longer uses and imposed it on other repos. To add a skill to skilldrop, follow AGENTS.md and run validate.py." },
    "md-to-html": { "in": "1.2.0", "why": "On its held-out evals, in each of two trials and with both blind judges, the agent without it made the better page: the skill's script showed raw HTML as text and its security policy blocked embeds, and it adds no rule the agent breaks." },
    "mermaid-render": { "in": "1.2.0", "why": "On its held-out evals, in each of two trials and with both blind judges, the agent without it fixed the same diagrams, ran the Mermaid CLI itself and said plainly what it had not rendered; the skill adds no rule it breaks." },
    "marketing-flyer": { "in": "1.2.0", "why": "On its held-out evals, in each of two trials and with both blind judges, the agent without it built the whole flyer with placeholders where the skill stopped or used a generic template; it adds no rule the agent breaks." },
    "deck-builder": { "in": "1.2.0", "why": "On its held-out evals the agent without it built the better deck in each of two trials; rebuilt rule-first, with its script able to run, it still lost on fresh evals (judges 2 and 1 of 4; 69% of checks against 81%).", "instead": "md-to-pptx" },
    "ai-usage-report": { "in": "1.4.0", "why": "On its held-out evals, over three trials and with both blind judges, the agent without it made the better report: it kept every rule the skill teaches (counts show activity, not quality; missing data is not zero; no leaderboard), while the skill refused to rank when asked, hid names the manager had supplied, and its script read neither eval's export." },
    "lean-canvas": { "in": "1.4.0", "why": "On its held-out evals, in each of three trials and with both blind judges, the agent without it made the better canvas: it caught the same errors and went further, while the skill's lead on checks came from its own format and its script's break-even left out the cost of replacing lost customers.", "instead": "business-case" },
    "adopt": { "in": "1.5.0", "kind": "loop", "why": "On its held-out evals its own four skills, installed without the loop, were preferred in every pair by both blind judges: the loop narrowed the policy to the first use case when the team had no rules at all, its gate swapped out the use case the sponsor had chosen, and its reply carried gate jargon. Install ai-use-case-triage, ai-readiness-assessment, ai-usage-policy and ai-adoption-rollout and run them in the pack's order." },
    "apply": { "in": "1.5.0", "kind": "loop", "why": "On its held-out evals its own skills, installed without the loop, were preferred in every pair by both blind judges: its fit gate stopped before writing anything even when the candidate had already decided to apply, and its confirm gate left form answers blank. Use job-fit-analysis to decide, then resume-tailor, cover-letter and application-form-answers." },
    "discover": { "in": "1.5.0", "kind": "loop", "why": "On its held-out evals the plain agent was preferred in every pair and its own skills in three of four: its ratification gate refused to record an approval the requester had already given, and its reply carried gate jargon. Use feedback-synthesis on raw signal, then prd-draft." },
    "operate": { "in": "1.5.0", "kind": "loop", "why": "On its held-out evals its own skills, installed without the loop, were preferred in every pair by both blind judges: the skills already link instrumentation, runbook, comms and postmortem, and the loop added gate jargon and broke its own one rule. Use observability-plan, runbook-generator, incident-comms and postmortem-generator in that order." }
  }
}
