Adonis0123/adonis-skills / skills/agent-skill-evaluation
agent-skill-evaluation
FlaggedUse when comparing or trial-testing agent skills before installing — including GitHub/skills.sh URLs, 测试一下/值不值得装, package screening, and A/B artifact runs.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 30.3 KB |
| references/conceptual-multi-agent-skill-trial.md | markdown | 4.0 KB |
| references/image-producing-skill-trial.md | markdown | 2.7 KB |
| references/mattpocock-catalog-renames.md | markdown | 2.7 KB |
| references/mattpocock-shortlist-20260807.md | markdown | 3.2 KB |
| references/mattpocock-skills-screening.md | markdown | 15.3 KB |
| references/mattpocock-tdd-trial-20260807.md | markdown | 2.8 KB |
| references/mattpocock-tdd-trial-20260908.md | markdown | 2.5 KB |
| references/mattpocock-to-prd-trial-20260807.md | markdown | 1.8 KB |
| references/mattpocock-wayfinder-trial-20260909.md | markdown | 2.3 KB |
| references/output-style-skill-screening.md | markdown | 6.0 KB |
| references/peer-review-cli.md | markdown | 5.4 KB |
| references/single-skill-temp-trial.md | markdown | 7.7 KB |
| references/skill-eval-harness-trial.md | markdown | 3.6 KB |
| references/tdd-process-skill-trial.md | markdown | 2.9 KB |
| references/ui-design-ab-testing.md | markdown | 5.8 KB |
references/tdd-process-skill-trial.md
View on GitHub# TDD / process-law skill temp trial
Class recipe when evaluating any **red-green / TDD-law** skill (e.g. mattpocock `tdd`, superpowers-style TDD clones).
## Hard rules
1. **Temp only** until user chooses A — never `npx skills add -g` during 测试/评估.
2. **Do not score from SKILL.md prose alone.**
3. **Usable trial ≠ install.** A green temp exercise proves readability/runnability, not a gap.
4. **Never dual always-on** two TDD laws unless user explicitly swaps (unload A, install B).
## Dual-law map (required)
Before recommending install, write:
| Axis | Candidate | Local alternative |
| ------------------------ | --------- | ----------------- |
| When to test | … | … |
| RED verify mandatory? | … | … |
| Refactor in-loop or out? | … | … |
| Seams / ceremony | … | … |
| Mocking stance | … | … |
Hard conflicts (especially **refactor in-loop vs out-of-loop**) → default **B** if local already complete.
If the user later forces **keep exactly one**: keep the heavier complete local law (in-loop refactor + watched RED/GREEN). Do not swap to the thinner candidate unless they unload the local skill **and** accept its parked-refactor home (or install that companion). Steal unique bullets into the winner; never dual always-on.
## Exercise minimum
```text
/tmp/<skill>-eval-YYYYMMDD/
<skill-copy>/
trial-artifact/ # real package + tests
EVAL.md
```
1. Lock one **public seam** (pure function or narrow API). If candidate requires pre-agreed seams, write them in BRIEF.md first.
2. Prefer **vertical slices**: one test → implement → next test (not bulk-all-tests-first).
3. For each slice: **watch RED** (real fail for missing behavior), then **GREEN** (minimal code). Prefer 2–3 slices.
4. Stack default for trials (example): TypeScript + Vitest under temp (pnpm).
5. Record intervention cost: how much steering beyond the skill text.
## Name-mismatch trap
Local job may already exist under another name:
| Candidate name | Local heavier alternative |
| -------------- | -------------------------------------------- |
| `tdd` | `test-driven-development` (obra/superpowers) |
Name absent ≠ capability missing.
## Baseline pointer
`mattpocock/skills@tdd` → **B** (re-inventory 2026-09-08, still B). Latest: `references/mattpocock-tdd-trial-20260908.md`. Earlier: `references/mattpocock-tdd-trial-20260807.md`.
Catalog pages may still say “planning” / “red-green-refactor”; score the SKILL.md law (refactor out-of-loop) not the marketing blurb.
## Deliverable (chat-scannable)
```text
结论:B|C|A — …
状态:temporary-only | not installed | already present
证据:RED/GREEN 次数 + /tmp 路径
双法冲突:…
替代:≤3
风险:≤2
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |