skilldrop-cli 0.16.3__py3-none-any.whl

skilldrop_cli/data/packs/dev-team/skills/accessibility-audit/reference.md

@@ -0,0 +1,69 @@
+# accessibility-audit reference — WCAG 2.2 AA catalog, AT map, severity, scanner gaps
+
+Run the catalog as a lens, not a transcript. Report only what the UI fails or what the input can't verify. Citations use the SC number + name + level.
+
+## The high-yield success criteria by POUR (WCAG 2.2, A + AA)
+
+### Perceivable
+- **1.1.1 Non-text Content [A]** — every image/icon/control has a text alternative; decorative images have empty alt; alt *says something useful* (not "image").
+- **1.3.1 Info and Relationships [A]** — structure conveyed visually is in the markup: headings are `<h*>`, lists are lists, labels are programmatically associated, tables have headers.
+- **1.3.2 Meaningful Sequence [A]** — DOM/reading order matches the intended order (CSS can lie; screen readers follow DOM).
+- **1.3.5 Identify Input Purpose [AA]** — inputs use `autocomplete` for known data (name, email).
+- **1.4.1 Use of Color [A]** — color is never the *only* way info is conveyed (errors, status, chart series, links in body text).
+- **1.4.3 Contrast (Minimum) [AA]** — text ≥ 4.5:1; large text (≥24px, or ≥19px bold) ≥ 3:1.
+- **1.4.4 Resize Text [AA]** / **1.4.10 Reflow [AA]** — usable at 200% text and 400% zoom with no loss of content/function, no horizontal scroll at 320px-equivalent.
+- **1.4.11 Non-text Contrast [AA]** — UI components and graphical objects (input borders, icons, focus rings) ≥ 3:1.
+- **1.4.12 Text Spacing [AA]** — no clipping when users override line/letter/word spacing.
+- **1.4.13 Content on Hover/Focus [AA]** — tooltips/popovers are dismissable, hoverable, persistent.
+
+### Operable
+- **2.1.1 Keyboard [A]** — all functionality available from the keyboard.
+- **2.1.2 No Keyboard Trap [A]** — focus can always move away.
+- **2.1.4 Character Key Shortcuts [A]** — single-key shortcuts can be turned off/remapped.
+- **2.4.3 Focus Order [A]** — tab order is logical and meaningful.
+- **2.4.4 Link Purpose [A]** — link text makes sense (no bare "click here"/"read more" islands).
+- **2.4.6 Headings and Labels [AA]** — descriptive; **2.4.7 Focus Visible [AA]** — a visible focus indicator on every focusable element.
+- **2.4.11 Focus Not Obscured (Minimum) [AA, new in 2.2]** — focused element isn't hidden behind sticky headers/footers.
+- **2.5.3 Label in Name [A]** — the accessible name contains the visible label text (voice control).
+- **2.5.7 Dragging Movements [AA, 2.2]** — drag actions have a single-pointer alternative.
+- **2.5.8 Target Size (Minimum) [AA, 2.2]** — targets ≥ 24×24 CSS px (or adequate spacing).
+
+### Understandable
+- **3.1.1 Language of Page [A]** — `lang` set.
+- **3.2.1 On Focus / 3.2.2 On Input [A]** — focus/input doesn't trigger surprise context changes.
+- **3.2.6 Consistent Help [A, 2.2]** — help mechanisms appear consistently.
+- **3.3.1 Error Identification [A]** — errors are described in text, programmatically associated with their field.
+- **3.3.2 Labels or Instructions [A]** — inputs have visible labels/instructions.
+- **3.3.3 Error Suggestion [AA]** — fixable errors offer a suggestion.
+- **3.3.7 Redundant Entry [A, 2.2]** / **3.3.8 Accessible Authentication (Minimum) [AA, 2.2]** — don't force re-entry; don't require a cognitive function test (e.g. solving a puzzle) with no alternative.
+
+### Robust
+- **4.1.2 Name, Role, Value [A]** — every UI component exposes a correct name, role, and state to AT (the #1 source of custom-widget failures).
+- **4.1.3 Status Messages [AA]** — dynamic status (toasts, validation, live results) announced via `role="status"`/`aria-live` without moving focus.
+
+## Affected-user / assistive-tech map (name the victim)
+
+| Barrier | Who it blocks | Tech that hits it |
+|---|---|---|
+| No keyboard access / trap / no focus ring | motor-impaired, power users, anyone without a mouse | keyboard-only, switch control |
+| Missing/wrong name-role-value, bad alt | blind, low-vision | VoiceOver, NVDA, JAWS |
+| Low contrast, color-only signal | low-vision, color-blind, sunlight/poor-screen users | screen magnifier, everyone outdoors |
+| No reflow / breaks at zoom | low-vision | 200–400% zoom, mobile |
+| Surprise context change, complex auth | cognitive, low-literacy, anxiety | all |
+| Tiny targets, drag-only | motor, tremor, touch | touch, switch, eye-tracking |
+| Unannounced dynamic updates | blind | screen readers |
+
+## Severity rubric (by task-completion impact)
+
+- 🟥 **blocker** — a group cannot complete the core task at all.
+- 🟧 **major** — significant barrier; a painful or non-obvious workaround exists.
+- 🟨 **minor** — friction or confusion, task still completable.
+- ⚪ **nit** — best practice / polish.
+
+Calibrate: a keyboard trap on the only submit path is 🟥; `alt` slightly verbose is ⚪. If everything is 🟥, recheck against "can the task be completed?"
+
+## What automated scanners catch vs miss (tag findings [auto] / [manual])
+
+**Caught by axe/Lighthouse [auto]** (~30–40% of issues): missing alt attribute, missing form label, low text contrast (computed), missing `lang`, duplicate IDs, ARIA attribute misuse, empty buttons/links, missing document title.
+
+**Human + AT only [manual]** (the majority): alt-text *quality*, label *accuracy* (right label on right field), logical focus *order*, meaningful reading sequence, keyboard *operability* of custom widgets, focus *visibility* in practice, error-recovery *usability*, whether color is the *only* signal, reflow at zoom, sensible heading *outline*, live-region *announcements* firing correctly, whether a context change is *surprising*. These don't stay fixed without a recurring manual pass — say so.

skilldrop_cli/data/packs/dev-team/skills/agents-md-generator/SKILL.md

@@ -0,0 +1,82 @@
+---
+name: agents-md-generator
+description: Generate or audit a repository's AGENTS.md — the agent-policy file Claude Code, Codex, Cursor, Copilot, Kiro and Antigravity read — with every command traced to real evidence in the repo, generic virtue instructions stripped, and forbidden actions named. Use when a repo has no AGENTS.md, when an existing one is stale or ignored, when onboarding a codebase to agentic coding, or when an agent keeps running commands that don't exist.
+---
+
+# agents-md-generator
+
+Produces the file agents read *before* the user's prompt. An `AGENTS.md` is not documentation — it is the context an agent spends on every turn, so a line that changes no decision is a line stolen from the task.
+
+The failure that makes these files worse than useless is an **invented command**. `npm test` in a repo with no test script sends every agent down a path that fails, and the agent trusts the file over the filesystem. So the rule this skill is built around: **every command traces to evidence in the repo, or it does not appear.**
+
+Two modes, chosen by what's already there:
+- **Generate** — no `AGENTS.md` exists. Produce one under the line cap.
+- **Audit** — one exists. Score it, name what can't be verified, emit a diff. Never silently rewrite a hand-tuned file.
+
+## How to respond
+
+1. **Inventory the real command surface before writing anything.** Read, in this order: `package.json` (`scripts`), `Makefile`, `pyproject.toml` / `setup.cfg`, `Cargo.toml`, `go.mod`, `composer.json`, `.github/workflows/*.yml`, `justfile`, `Taskfile.yml`, and any `CONTRIBUTING.md`. CI workflows are the highest-value source: they contain the commands that actually have to pass.
+
+   For each command record its **provenance** — the file and key it came from. Provenance is what makes audit mode possible later.
+
+2. **Apply the evidence rule without exception.** A command appears only if it traces to a file in the repo. Never infer from ecosystem convention: a Python repo does not necessarily run `pytest`, and a repo with `jest` in `devDependencies` may still have no test script.
+
+   When a section needs a command that doesn't exist, record the gap, not a guess. In the provenance table it is `[missing: no test script in package.json or CI]`. In the file itself it is a plain line an agent can act on: ✅ *"Test: none defined in this repo. Do not run `npm test`."* — ❌ *"Test: `npm test`"*. The stated gap is useful; the guess is a trap.
+
+3. **Derive file placement from the actual tree**, not from what the framework usually does. Name the directories that exist and what belongs in each. Two or three rows beat a full tree dump.
+
+4. **Extract only conventions an agent would otherwise get wrong.** The test is counterfactual: *would a competent agent, without this line, do the wrong thing?* Naming rules that are enforced somewhere, invariants that look arbitrary but aren't, a generated file that must never be hand-edited. If the answer is no, cut the line.
+
+   Generic virtue instructions — "write clean code", "be thorough", "follow best practices", "use good naming" — are **stripped, not softened.** They consume context and change no behaviour.
+
+5. **Name forbidden actions explicitly.** This is the section most files omit and the one that prevents the most damage: paths that must not be touched, commands that must never run unattended, files that are generated, secrets that must never be committed. Concrete and few.
+
+6. **Assemble under ~150 lines.** In generate mode this is a **hard cap** — go over and cut, lowest value first (background prose, then examples, then convention lines that failed the counterfactual test). In audit mode it is a **warning**: report the overage and name the sections you would cut, because an existing file may be long for good reason.
+
+7. **Satellites only on request, and only as a delta.** If asked to wire a specific tool, emit a satellite (`CLAUDE.md`, `.github/copilot-instructions.md`, `GEMINI.md`) that contains **only what is specific to that tool**, plus one line pointing at `AGENTS.md` for everything shared. **Refuse to copy shared content into a satellite** — four copies of a command list is four chances to be wrong, and the drift is invisible. See [`reference.md`](reference.md) for the per-tool shapes.
+
+8. **Emit.** Generate mode: the file, plus a provenance table showing where each command came from and what was marked `[missing]`. Audit mode: verdict, the unverifiable lines quoted, the virtue instructions to cut, the line-count position, and a concrete diff.
+
+**Non-interactive runs:** unstated conventions are simply omitted — an `AGENTS.md` is allowed to be short. If the repo cannot be read at all, emit `BLOCKED: need repo access — every command must trace to a file`. Never produce an `AGENTS.md` from a description of a repo; the whole artifact is a claim about what is in the tree.
+
+## Useful references in this skill
+
+- [`reference.md`](reference.md) — where each tool looks, the evidence-source table, the satellite shapes, and the strip-list of virtue phrasings
+- [`templates/agents-md.md`](templates/agents-md.md) — the output skeleton with the section order and the line budget per section
+
+## Quality bar
+
+- **Zero unverified commands.** Every one traces to a file and key, or is stated as a gap (`[missing: …]` in the provenance table, a plain "none defined" line in the file). This is the bar; a file that fails it is worse than no file.
+- **A newcomer agent could build and test from this file alone** — or can see plainly that the repo has no such command.
+- **Forbidden actions are named**, not implied.
+- **Every convention line passes the counterfactual test.** If an agent would do the right thing without it, it is padding.
+- **≤150 lines generated.** Over the cap means something was kept that should have been cut.
+- **No virtue instructions survive.** Search the output for "clean", "best practice", "thorough", "appropriate", "as needed" — each hit is a line that changes nothing.
+- **It does not restate the README.** Different reader, different job: the README sells and explains, `AGENTS.md` constrains.
+
+## When to use this skill
+
+- ✅ A repo is adopting agentic coding and has no `AGENTS.md`
+- ✅ An existing `AGENTS.md` is stale, ignored, or full of advice rather than facts
+- ✅ Agents keep running commands that don't exist in the repo
+- ✅ Onboarding a legacy codebase where the real commands live only in CI
+- ✅ After `reverse-architecture` — its extraction is good input for the conventions section
+
+## When NOT to use this skill
+
+- ❌ Writing human contributor docs — that's `CONTRIBUTING.md`, a different reader
+- ❌ Explaining what the project *is* — that's the README
+- ❌ Operating a running service — that's `runbook-generator`
+- ❌ Reviewing an existing document's prose quality — that's `doc-critique`, which takes documents; this one takes a repository
+
+## Anti-patterns to avoid
+
+- ❌ **Inventing a command that "should" exist.** The single most damaging thing this artifact can do. A `[missing]` marker is a finding; a guess is a fault the agent will trust.
+- ❌ **Virtue instructions.** "Write clean, maintainable code" is context spent on nothing. Agents already try.
+- ❌ **Dumping the file tree.** Placement rules earn their space; a directory listing does not — the agent can run `ls`.
+- ❌ **Restating the README.** If it's already there, link it.
+- ❌ **A satellite that duplicates `AGENTS.md`.** Guaranteed drift, invisible until an agent acts on the stale copy.
+- ❌ **Silently rewriting a hand-tuned file.** Audit mode emits a diff and lets a human choose; the file may encode decisions the repo can't show you.
+- ❌ **Writing to the cap.** 150 lines is a ceiling, not a target. Most repos need far less.
+- ❌ **Showing the machinery.** The reply and the artifact are for the person who asked. Don't mention this skill, its files, templates, caps or internal terms, or that the run is non-interactive. Name another skill once, at the end, as a suggested next step, never inside the artifact.
+- ❌ **A bare `BLOCKED` line.** Keep the `BLOCKED: need <X>` line, then write for a person: what is missing in plain words, what you will produce once you have it, and anything the request already lets you say.

skilldrop_cli/data/packs/dev-team/skills/agents-md-generator/evals/eval_queries.json

@@ -0,0 +1,15 @@
+[
+  { "query": "Write an AGENTS.md for this repo", "should_trigger": true },
+  { "query": "Our AGENTS.md is stale — review it", "should_trigger": true },
+  { "query": "The agent keeps running commands that don't exist in our project", "should_trigger": true },
+  { "query": "Set this codebase up for agentic coding", "should_trigger": true },
+  { "query": "Create a CLAUDE.md for this project", "should_trigger": true },
+  { "query": "What should go in an agent instructions file?", "should_trigger": true },
+
+  { "query": "Write a CONTRIBUTING.md for this repo", "should_trigger": false },
+  { "query": "Document what this service does for new hires", "should_trigger": false },
+  { "query": "Reverse-engineer the architecture of this codebase", "should_trigger": false },
+  { "query": "Write a runbook for this service", "should_trigger": false },
+  { "query": "Review this design doc for gaps", "should_trigger": false },
+  { "query": "Design a supervised agent loop", "should_trigger": false }
+]

skilldrop_cli/data/packs/dev-team/skills/agents-md-generator/evals/evals.json

@@ -0,0 +1,50 @@
+{
+  "skill_name": "agents-md-generator",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Write an AGENTS.md for this repo. It's a Python service: pyproject.toml declares pytest and ruff in dev dependencies, there's a Makefile with `run` and `migrate` targets, and .github/workflows/ci.yml runs `ruff check .` then `pytest -q`. No test script anywhere else. Migrations are in alembic/versions/.",
+      "assertions": [
+        "Commands are traced to their source — CI for ruff/pytest, Makefile for run/migrate — not inferred from the dependency list",
+        "The test command is `pytest -q` as CI runs it, not a guessed `pytest` or `make test` that does not exist",
+        "No command appears that cannot be traced to pyproject.toml, the Makefile, or the workflow",
+        "Alembic migrations produce a convention or forbidden-action line (append-only / never edit a committed migration)",
+        "A `Do not` section exists with concrete entries, not implied caution",
+        "Output is at or under ~150 lines",
+        "No virtue instructions appear — no 'clean', 'best practice', 'thorough', 'maintainable'",
+        "Conventions included would each change agent behaviour if removed"
+      ]
+    },
+    {
+      "id": 2,
+      "prompt": "Here's our AGENTS.md — audit it. It says: 'Run `npm test` to test. Write clean, maintainable code and follow best practices. Be thorough in reviews.' Our package.json has scripts for build and lint only, no test.",
+      "assertions": [
+        "Audit mode is used — a verdict and diff, not a silent rewrite",
+        "`npm test` is flagged as unverifiable: package.json has no test script",
+        "The three virtue instructions are named for removal, with the reason that they change no behaviour",
+        "What the file is missing is stated — real commands (build, lint), file placement, forbidden actions",
+        "The line-count position is reported rather than the file being failed for length",
+        "A concrete replacement or diff is offered, not just criticism"
+      ]
+    },
+    {
+      "id": 3,
+      "prompt": "Also wire it up for Claude Code and Copilot.",
+      "assertions": [
+        "Satellites are emitted as deltas only — each points at AGENTS.md for shared content",
+        "No satellite repeats the command table, file placement, or conventions",
+        "CLAUDE.md carries only Claude-Code-specific content; .github/copilot-instructions.md only Copilot-specific content",
+        "If there is no genuinely tool-specific content, that is said rather than a file padded to justify itself"
+      ]
+    },
+    {
+      "id": 4,
+      "prompt": "[Non-interactive run — no repo access] Generate an AGENTS.md for a typical Node microservice.",
+      "assertions": [
+        "No AGENTS.md is produced — the output is BLOCKED: need repo access",
+        "No commands are invented from ecosystem convention",
+        "The reason given is that every command must trace to a file in the tree"
+      ]
+    }
+  ]
+}

skilldrop_cli/data/packs/dev-team/skills/agents-md-generator/evals/files/1/Makefile

@@ -0,0 +1,5 @@
+run:
+	uvicorn booking.app:app --reload
+
+migrate:
+	alembic upgrade head

skilldrop_cli/data/packs/dev-team/skills/agents-md-generator/evals/files/1/alembic/versions/0001_create_bookings.py

@@ -0,0 +1,10 @@
+revision = "0001"
+down_revision = None
+
+
+def upgrade():
+    pass
+
+
+def downgrade():
+    pass

skilldrop_cli/data/packs/dev-team/skills/agents-md-generator/evals/files/1/booking/app.py

@@ -0,0 +1,8 @@
+from fastapi import FastAPI
+
+app = FastAPI()
+
+
+@app.get("/health")
+def health():
+    return {"ok": True}

skilldrop_cli/data/packs/dev-team/skills/agents-md-generator/evals/files/1/pyproject.toml

@@ -0,0 +1,11 @@
+[project]
+name = "northwind-booking"
+version = "0.4.0"
+requires-python = ">=3.11"
+dependencies = ["fastapi", "sqlalchemy", "alembic"]
+
+[project.optional-dependencies]
+dev = ["pytest", "ruff"]
+
+[tool.ruff]
+line-length = 100

skilldrop_cli/data/packs/dev-team/skills/agents-md-generator/evals/files/1/tests/test_health.py

@@ -0,0 +1,5 @@
+from booking.app import health
+
+
+def test_health():
+    assert health() == {"ok": True}

skilldrop_cli/data/packs/dev-team/skills/agents-md-generator/evals/files/2/AGENTS.md

@@ -0,0 +1,3 @@
+# AGENTS.md
+
+Run `npm test` to test. Write clean, maintainable code and follow best practices. Be thorough in reviews.

skilldrop_cli/data/packs/dev-team/skills/agents-md-generator/evals/files/2/package.json

@@ -0,0 +1,12 @@
+{
+  "name": "acme-portal",
+  "version": "1.2.0",
+  "scripts": {
+    "build": "tsc -p .",
+    "lint": "eslint src"
+  },
+  "devDependencies": {
+    "typescript": "^5.4.0",
+    "eslint": "^9.0.0"
+  }
+}

skilldrop_cli/data/packs/dev-team/skills/agents-md-generator/evals/files/2/src/index.ts

@@ -0,0 +1 @@
+export const main = (): string => "acme-portal";

skilldrop_cli/data/packs/dev-team/skills/agents-md-generator/manifest.json

@@ -0,0 +1,11 @@
+{
+  "name": "agents-md-generator",
+  "version": "0.1.1",
+  "description": "Generate or audit a repository's AGENTS.md — the agent-policy file Claude Code, Codex, Cursor, Copilot, Kiro and Antigravity read — with every command traced to real evidence in the repo, generic virtue instructions stripped, and forbidden actions named. Use when a repo has no AGENTS.md, when an existing one is stale or ignored, when onboarding a codebase to agentic coding, or when an agent keeps running commands that don't exist.",
+  "entrypoint": "SKILL.md",
+  "deps": { "npm": [], "pip": [] },
+  "env": { "required": [], "optional": [] },
+  "related": ["doc-critique", "reverse-architecture", "runbook-generator"],
+  "tags": ["agents-md", "agent-policy", "repo-onboarding", "context-engineering", "agentic", "conventions"],
+  "model": { "tier": "standard", "rationale": "Repo inspection plus synthesis against a fixed section order and line budget — the same shape as reverse-architecture. The judgment is the counterfactual test on each convention line, which is bounded; escalate via large-input on monorepos." }
+}

skilldrop_cli/data/packs/dev-team/skills/agents-md-generator/reference.md

@@ -0,0 +1,89 @@
+# agents-md-generator — reference
+
+## Who reads what
+
+Confirmed in the July 2026 survey ([`docs/designs/ide-primitive-coverage.md`](../../../../docs/designs/ide-primitive-coverage.md)). A root `AGENTS.md` is the broadest single file; satellites are a reach fix for specific tools, not the norm.
+
+| Tool | Reads |
+|---|---|
+| Codex | root `AGENTS.md` |
+| GitHub Copilot | root `AGENTS.md`, `.github/copilot-instructions.md`, `.github/instructions/*.instructions.md`, and also root `CLAUDE.md` / `GEMINI.md` |
+| Claude Code | `CLAUDE.md` (auto-loaded) |
+| Cursor | root `AGENTS.md`, plus `.cursor/rules/*.mdc` for rules |
+| Kiro | root `AGENTS.md`, plus `.kiro/steering/` for always-on context |
+| Antigravity | root `AGENTS.md` |
+
+**Precedence matters more than reach.** Several of these load on every turn regardless of relevance. A file that is always in context should carry only what earns its place there — the same reason an always-included steering file is a poor home for a persona.
+
+## Evidence sources, in priority order
+
+Every command must trace to one of these. Record the file and key as provenance.
+
+| Source | What it proves |
+|---|---|
+| `.github/workflows/*.yml` (and other CI) | **Strongest.** These commands must pass or the build fails |
+| `Makefile` / `justfile` / `Taskfile.yml` | Named entry points the team actually uses |
+| `package.json` `scripts` | Node entry points; check the script body, not just the key |
+| `pyproject.toml` / `setup.cfg` / `tox.ini` | Python entry points and runners |
+| `Cargo.toml`, `go.mod`, `composer.json`, `Gemfile` | Ecosystem defaults *only if* the file confirms them |
+| `CONTRIBUTING.md`, `README.md` | Human-facing; **verify against the above before trusting** — docs go stale faster than CI |
+| Dev container / Dockerfile | Setup steps and version pins |
+
+**A dependency is not a command.** `jest` in `devDependencies` does not mean `npm test` exists. Check for the script.
+
+## What earns a line — the counterfactual test
+
+Ask: *without this line, would a competent agent do the wrong thing?*
+
+| ✅ Earns its place | ❌ Cut |
+|---|---|
+| "Generated — never hand-edit `src/api/types.ts`; run `make codegen`" | "Keep the codebase clean and well organised" |
+| "Migrations are append-only; never edit a committed migration" | "Follow database best practices" |
+| "Tests live beside the source as `*_test.go`, not in `tests/`" | "Write comprehensive tests" |
+| "`main` is protected; open a PR" | "Follow good git hygiene" |
+| "Do not run `terraform apply` — plan only, a human applies" | "Be careful with infrastructure" |
+
+## Strip list
+
+Search generated output for these; each hit is a line that changes no behaviour:
+
+`clean` · `best practice` · `thorough` · `appropriate` · `as needed` · `where possible` · `make sure to` · `try to` · `robust` · `maintainable` · `readable` · `well-structured` · `properly` · `high-quality` · `idiomatic` (unless a specific idiom is named)
+
+## Satellite shapes — delta only
+
+A satellite carries what is specific to its tool **and nothing else**. Every shared fact stays in `AGENTS.md` and is pointed at.
+
+**`CLAUDE.md`** — Claude Code auto-loads it:
+
+```markdown
+# CLAUDE.md
+
+The substantive guidance lives in [AGENTS.md](AGENTS.md). Read it first.
+
+This file exists because Claude Code auto-loads `CLAUDE.md`. Everything below is
+Claude-Code-specific and does not belong in the cross-IDE file.
+
+## <tool-specific section>
+…e.g. `${CLAUDE_SKILL_DIR}` semantics, `.claude/settings.json`, subagent delegation…
+```
+
+**`.github/copilot-instructions.md`** — same shape, Copilot-specific content only (custom agents in `.github/agents/`, `.github/hooks/*.json`).
+
+**`GEMINI.md`** — same shape, for Gemini/Antigravity specifics.
+
+**Refuse** to emit a satellite containing the command table, file placement, or conventions that already live in `AGENTS.md`. If a tool needs those, it reads `AGENTS.md` — and if it genuinely cannot, say so plainly rather than duplicating.
+
+## Line budget
+
+150 lines total. A workable split:
+
+| Section | Lines |
+|---|---|
+| Repo in one paragraph | 3–5 |
+| Commands (with provenance verified) | 15–30 |
+| File placement | 10–20 |
+| Conventions that pass the counterfactual test | 20–40 |
+| Forbidden actions | 5–15 |
+| Pointers to deeper docs | 3–5 |
+
+Over budget: cut background prose first, then examples, then convention lines that only *probably* pass the test.

skilldrop_cli/data/packs/dev-team/skills/agents-md-generator/templates/agents-md.md

@@ -0,0 +1,48 @@
+# AGENTS.md — {project name}
+
+> {One line: what an agent needs to know it is working on.}
+
+## Repo in one paragraph
+
+{What this is, what it produces, and the one structural fact an agent must hold. 3–5 lines.}
+
+## Commands
+
+<!-- Every row traces to a file. No row may be inferred from ecosystem convention. -->
+
+| Task | Command | Source |
+|---|---|---|
+| Install | `{cmd}` | `{file}` → `{key}` |
+| Build | `{cmd}` | `{file}` → `{key}` |
+| Test | `{cmd}` *or* none defined in this repo; do not guess one | `{file}` → `{key}` |
+| Lint | `{cmd}` | `{file}` → `{key}` |
+| Run locally | `{cmd}` | `{file}` → `{key}` |
+
+{Drop the Source column from the final file if it crowds the budget — but only after every row has been verified with it present.}
+
+## File placement
+
+| Kind | Where |
+|---|---|
+| {thing} | `{path}` |
+
+## Conventions
+
+<!-- Each line must pass: without it, would a competent agent do the wrong thing? -->
+
+- **{Rule stated as a rule.}** {One clause of why, only if the why changes how it is applied.}
+
+## Do not
+
+- {Path, command, or action that must never happen unattended — concrete.}
+- {Generated artifacts that must not be hand-edited, and the command that regenerates them.}
+
+## Pointers
+
+- {Deeper doc}: `{path}`
+- {Architecture / design}: `{path}`
+
+<!--
+Line budget: 150. Provenance for every command was verified at generation time.
+A row that says "none defined" is a finding, not an omission — the repo has no such command.
+-->

skilldrop_cli/data/packs/dev-team/skills/bug-triage/SKILL.md

@@ -0,0 +1,67 @@
+---
+name: bug-triage
+description: Turn a vague bug report (Slack message, support ticket, "it's broken on mobile sometimes") into an actionable ticket — searchable symptom title, numbered repro steps from a clean state, expected vs actual, severity separated from priority, evidence tagged reported-vs-verified, and labeled hypotheses instead of root-cause guesses. Use when the user wants to triage a bug, write up a bug report, turn a complaint into a ticket, or make a flaky issue actionable.
+---
+
+# bug-triage
+
+Converts the bug report someone *sent* into the ticket an engineer can *start* — without a round of "can you clarify?" first. The discipline: separate what was reported from what's verified, separate severity from priority, and label every guess as a guess. Triage shapes the work; fixing it is `feature-implement-loop` (or a human) downstream.
+
+## How to respond
+
+1. **Ingest the raw report** — Slack thread, support ticket, user email, a teammate's "X is broken". Mine it for the six ticket fields before asking anything. Then ask **at most 3 questions, ranked by diagnostic value** — the answers that most shrink the search space (exact error text, when it last worked, does it reproduce on a second account/device). Everything unconfirmed proceeds with a tag, not a guess.
+
+2. **One bug per ticket.** A report with three symptoms becomes three tickets (or one ticket + a "split out" note naming the others). Multi-symptom tickets close half-fixed.
+
+3. **Write the title as symptom + condition, searchable.** ✅ *"Checkout button stays disabled after removing an expired coupon (Safari 17, guest cart)"* — ❌ *"Checkout broken"*, ❌ *"Coupon bug"*. Six months from now someone greps tickets for "disabled checkout" — that's who the title is for.
+
+4. **Tag every claim `[reported]` or `[verified]`.** What the reporter says happened vs what was confirmed by logs, a screenshot, or your own reproduction. Triage that presents `[reported]` as fact sends an engineer chasing a description instead of a behavior.
+
+5. **Number the repro steps from a clean state** — fresh session, named test account, stated starting URL — each step an observable action, ending in the failure. If reproduction is unknown, the ticket says **"No repro yet"** and lists the exact diagnostics to collect (error text verbatim, console/server log window with timestamp, HAR capture, screen recording) — never invented steps that "probably" trigger it.
+
+6. **Split expected vs actual into two concrete lines.** ✅ Expected: *"order total recalculates to pre-coupon price"* / Actual: *"total keeps the discount, button stays disabled"* — ❌ *"it doesn't work right"*. Attach the verbatim error message if one exists; paraphrased errors are unsearchable.
+
+7. **Call severity and priority separately** with one line of reasoning each, using the matrix in [`templates/bug-ticket.md`](templates/bug-ticket.md):
+   - **Severity** = worst plausible user impact: S1 data loss / security / payment broken · S2 core flow broken, no workaround · S3 degraded, workaround exists · S4 cosmetic
+   - **Priority** = business urgency: P1 drop everything · P2 this sprint · P3 backlog
+   A cosmetic bug on the pricing page during launch week is S4/P1 — the separation is the point. State the blast radius guess: who's affected (`all users` / `Safari only` / `one tenant`) and tag it.
+
+8. **Offer hypotheses as hypotheses.** Up to 3, each with a 5-minute check that would confirm or kill it. ✅ *"H1: expired-coupon validation leaves cart state locked — check: apply/remove a valid coupon, see if button recovers"*. Never present the leading hypothesis as the cause; that anchors the investigation on a guess.
+
+9. **Finish with duplicate-search hints** — 2–3 search strings for the tracker (error code, symptom phrasing, component name) so the ticket isn't the third copy.
+
+## Useful references in this skill
+
+- [`templates/bug-ticket.md`](templates/bug-ticket.md) — the ticket skeleton with the severity/priority matrix and the no-repro diagnostics list
+
+## Quality bar
+
+- **An engineer can start without contacting the reporter.** Either the repro stands alone or the no-repro diagnostics list says exactly what to collect.
+- **Title findable by symptom search.** If the words a future reporter would type don't appear in it, retitle.
+- **Zero untagged claims.** Every factual statement is `[reported]`, `[verified]`, or `[assumption]` — a triager's authority comes from the tags.
+- **Severity and priority each have a stated reason**, and they were judged independently — one line each, no shared justification.
+- **Hypotheses ≤ 3, each with a concrete check.** A hypothesis without a check is a vibe.
+- **The verbatim error text is present** when any error was shown — quoted exactly, not paraphrased.
+
+## When to use this skill
+
+- ✅ A Slack/support complaint needs to become a ticket an engineer can pick up
+- ✅ "Can you write this up properly?" for a vaguely described bug
+- ✅ Triaging an inbound bug queue into severity/priority order
+- ✅ A flaky, "sometimes" bug that needs a diagnostics plan instead of guesswork
+
+## When NOT to use this skill
+
+- ❌ Actually fixing the bug — hand the ticket to `feature-implement-loop` or a human
+- ❌ A production incident in progress — mitigate first; this is queue work, not response work
+- ❌ The post-incident analysis — that's `postmortem-generator`
+- ❌ A feature request wearing a bug costume ("bug: there's no dark mode") — route to `user-story-splitter`
+
+## Anti-patterns to avoid
+
+- ❌ **Root-cause cosplay.** "It's probably the cache" stated as fact in the ticket body — now the investigation starts at the guess instead of the evidence.
+- ❌ **Repro steps that skip state.** "1. Go to checkout 2. See bug" — which account, which cart, which browser? Steps that don't start clean don't reproduce.
+- ❌ **Severity inflated to get attention** (everything S1) or priority used as severity (P1 because a VP reported it — that's priority, write it as priority).
+- ❌ **The interrogation.** Ten questions back to the reporter before writing anything; three ranked ones, then proceed with tags.
+- ❌ **Paraphrased error messages.** "Some kind of permissions error" when the dialog said `ERR_TENANT_SCOPE_403` — the exact string is the most diagnostic fact available.
+- ❌ **The kitchen-sink ticket.** Three symptoms, two feature requests, and a screenshot dump under one title. Split it.

skilldrop_cli/data/packs/dev-team/skills/bug-triage/evals/eval_queries.json

@@ -0,0 +1,34 @@
+[
+  {
+    "query": "Turn this vague bug report into an actionable ticket",
+    "should_trigger": true
+  },
+  {
+    "query": "A customer says it's broken on mobile sometimes — triage it",
+    "should_trigger": true
+  },
+  {
+    "query": "Write up this Slack complaint as a proper bug with repro steps",
+    "should_trigger": true
+  },
+  {
+    "query": "Triage and prioritize this support ticket",
+    "should_trigger": true
+  },
+  {
+    "query": "Review this diff for bugs and edge cases",
+    "should_trigger": false
+  },
+  {
+    "query": "Write the blameless postmortem for the outage",
+    "should_trigger": false
+  },
+  {
+    "query": "Split this epic into user stories",
+    "should_trigger": false
+  },
+  {
+    "query": "Write a test plan for this release",
+    "should_trigger": false
+  }
+]

skilldrop_cli/data/packs/dev-team/skills/bug-triage/evals/evals.json

@@ -0,0 +1,17 @@
+{
+  "skill_name": "bug-triage",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Triage this report: 'checkout is broken on mobile sometimes, a customer complained in Slack this morning'.",
+      "assertions": [
+        "An engineer could start work without contacting the reporter — either the repro steps stand alone, or a no-repro diagnostics list states exactly what to collect",
+        "The title is findable by symptom search, containing the words a future reporter would type",
+        "Repro steps are numbered and start from a clean state",
+        "Expected versus actual behaviour are stated separately",
+        "Every factual claim is tagged [reported], [verified], or [assumption] — nothing is asserted untagged",
+        "Severity is assigned with a stated reason rather than inherited from the reporter's tone"
+      ]
+    }
+  ]
+}

skilldrop_cli/data/packs/dev-team/skills/bug-triage/manifest.json

@@ -0,0 +1,14 @@
+{
+  "name": "bug-triage",
+  "version": "0.1.0",
+  "description": "Turn a vague bug report (Slack message, support ticket, \"it's broken on mobile sometimes\") into an actionable ticket — searchable symptom title, numbered repro steps from a clean state, expected vs actual, severity separated from priority, evidence tagged reported-vs-verified, and labeled hypotheses instead of root-cause guesses. Use when the user wants to triage a bug, write up a bug report, turn a complaint into a ticket, or make a flaky issue actionable.",
+  "entrypoint": "SKILL.md",
+  "deps": { "npm": [], "pip": [] },
+  "env": { "required": [], "optional": [] },
+  "related": ["feature-implement-loop", "postmortem-generator", "user-story-splitter"],
+  "handoff": [
+    { "to": "feature-implement-loop", "when": "the defect is reproduced and scoped", "purpose": "Fix the triaged defect through the same capped loop a story gets.", "fallback": "If feature-implement-loop is absent, fix inline with a regression test that fails before the fix." }
+  ],
+  "tags": ["bug-triage", "bug-report", "ticket", "qa", "repro", "severity"],
+  "model": { "tier": "standard", "rationale": "Extraction plus judgment calls (severity vs priority, hypothesis ranking) — same shape as brief-intake: above light, below heavy." }
+}