Skip to content

majiayu000/spellbook / skills/skill-audit

skill-audit

Verified

Audit, design, categorize, distribute, and measure agent skills using lessons from Anthropic's Lessons from building Claude Code: How we use skills. Use when reviewing an existing skill, deciding whether a workflow deserves a skill, planning a skill library, turning team knowledge into skills, choosing skill categories, writing trigger descriptions, designing progressive disclosure, or planning skill marketplace and usage measurement.

FileKindSize
SKILL.mdskill md6.3 KB
assets/skill-brief-template.mdmarkdown1.3 KB
references/skill-taxonomy.mdmarkdown3.7 KB
references/writing-and-operations.mdmarkdown3.4 KB

assets/skill-brief-template.md

View on GitHub
# Skill Brief

## Decision

- Create / improve / split / merge / do not create:
- Reason:

## Candidate Skill

- Proposed name:
- Primary category:
- Secondary category:
- Target users:
- Trigger contexts:

## Description Draft

Write the frontmatter description here. Include concrete phrases and contexts
that should trigger the skill.

## High-Signal Knowledge

- TBD

## Gotchas

- TBD

## Operating Contract

- Direct actions:
- Escalate before:
- Evidence-backed pushback:
- Feedback loop:

## Progressive Disclosure Map

| File / Folder | Purpose | Load When |
|---|---|---|
| `SKILL.md` | Trigger, main workflow, output format | Always after trigger |
| `references/` |  |  |
| `scripts/` |  |  |
| `assets/` |  |  |
| `evals/` |  |  |

## Setup

- Required tools:
- Required config:
- Missing information to ask user:
- Secrets handling:

## Verification

- Commands:
- Example prompts:
- Expected artifacts:
- Failure signals:

## Reliable Skill Contract

- Negative examples:
- Verification checkpoints:
- Machine-checkable done conditions:
- Replay or smoke hooks:
- Log-to-patch loop:
- Drift signals:

## Distribution

- Repo-local / shared plugin / marketplace / experimental:
- Promotion criteria:

## Measurement

- Usage signals:
- Undertriggering signals:
- Overtriggering signals:
- Maintenance owner:
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall