Skip to content

ericrisco/rsc-harness / skills/author-skill

author-skill

Verified

Use when authoring a NEW rsc skill or editing an existing one — scoping it to one job, writing the description that decides whether it ever loads, splitting the body into references/, writing its evals, auditing it against the rubric. NOT building a product feature (that is `specify`) and NOT designing an agent loop (that is `building-agents`).

FileKindSize
SKILL.mdskill md16.9 KB
evals/README.mdmarkdown4.1 KB
evals/cases.yamlconfig7.0 KB
references/description-recipe.mdmarkdown5.7 KB
references/eval-authoring.mdmarkdown8.1 KB
references/rsc-conventions.mdmarkdown5.5 KB

evals/cases.yaml

View on GitHub
skill: author-skill

# Cases for the rsc-core "author-skill" meta skill.
# author-skill authors or edits a SKILL.md to the rsc catalog bar: a discriminating
# third-person description (~350 chars, valid YAML, origin: risco), a focused body with
# progressive disclosure into references/, the best-practice rubric, and an
# evals/cases.yaml + README for the NEW skill, plus the rsc plumbing (tags,
# recommends, manifest.json, Knowledge map). It is NOT for building a
# product feature (the SDD chain), NOT for agent loops (building-agents), and NOT
# for generic project docs (harness).

should_trigger:
  - prompt: "I keep re-explaining how we do code reviews to the agent every session. Turn that into a skill."
    why: "Canonical 'born a skill' moment phrased as a symptom, no skill jargon — author-skill's core job is turning a recurring instruction into a SKILL.md with a triggering description and evals."

  - prompt: "Escribe una skill nueva para generar informes de incidencias."
    why: "Non-English (Spanish) verbatim 'write a new skill' request — the description must match the user's actual language, and author-skill owns new-skill authoring end to end."

  - prompt: "My skill never triggers even when it obviously should. What's wrong with it?"
    why: "Non-obvious symptom phrasing (no mention of 'skill authoring') pointing straight at the description craft — diagnosing/repairing a description that fails to route is exactly this skill's highest-leverage area."

  - prompt: "This SKILL.md is 600 lines and feels bloated. Help me restructure it."
    why: "Edit/refactor of an existing skill toward progressive disclosure — author-skill's body-vs-references decision table and the 400-line ceiling are the direct fix."

  - prompt: "Write the evals/cases.yaml for the skill I just drafted, with trigger and capability tests."
    why: "Eval authoring for a skill is squarely owned here (the should_trigger/should_not_trigger/route_to and capability rubric minimums) — a deliberately specific, non-obvious trigger."

  - prompt: "Audit this skill against our best-practice rubric before I add it to the catalog and run npm run manifest."
    why: "Combines the rubric audit and the rsc plumbing (tags, recommends, manifest) — both are author-skill responsibilities; this exercises the wiring + rubric surface."

  - prompt: "The frontmatter on my skill won't parse and the description is over 1024 chars. Fix it."
    why: "A concrete description/frontmatter defect (valid YAML, <=1024) — the description recipe and the YAML/length verifier are author-skill's, not any stack skill's."

should_not_trigger:
  - prompt: "I have a written spec for a new feature — turn it into an implementation plan."
    route_to: "plan"
    why: "Building a PRODUCT feature from a spec is the SDD chain (plan), not authoring a reusable skill. author-skill builds the tools that build product, not the product."

  - prompt: "Help me design an autonomous agent with a tool-calling loop and memory."
    route_to: "building-agents"
    why: "Designing an agent/tool-loop is building-agents. A 'skill' (a SKILL.md that loads into the agent) is a different artifact than an autonomous agent runtime."

  - prompt: "Bootstrap my workspace and figure out which rsc bundles I need."
    route_to: "init"
    why: "Profiling the user and recommending bundles is the front door (init). author-skill assumes a skill is being written; it does not gauge the user or recommend bundles to install."

  - prompt: "Consolidate my scattered project notes into a wiki article under 02-DOCS."
    route_to: "harness"
    why: "Generic docs/wiki consolidation is the harness 02-DOCS engine. author-skill writes SKILL.md + evals, not project knowledge articles, even though it persists the occasional design note via harness."

  - prompt: "Turn this fuzzy product idea into a clear spec of what and why."
    route_to: "specify"
    why: "Specifying a product's intent is the specify phase of the SDD chain. A spec is not a skill; author-skill would only be relevant if the artifact being authored were itself a skill."

capability:
  - scenario: "A user says: 'I keep telling the agent how to write our PR descriptions. Make that into a skill called pr-describe.' Show how author-skill produces it to the rsc bar."
    must_include:
      - "Reads technical_level from 02-DOCS/wiki/harness/user-profile.md (or asks once 'technical or with analogies?' if absent) and explains in that register, without any verbosity level"
      - "Confirms scope is one job and checks no existing sibling already owns PR-description authoring before creating a new skill"
      - "Drafts the description FIRST: third-person, 'Use when…' lead, only the capabilities that discriminate it from its nearest sibling, a 'NOT … (that is `sibling`)' boundary, valid single-line quoted YAML aiming <=350 chars (1024 hard limit), with origin: risco"
      - "Produces the smallest body that still routes (400 lines is a ceiling, not a target) with progressive disclosure — long/branch-specific detail pushed to references/ and pointed to inline, not an orphaned references/ folder"
      - "Language-tags every code/example fence and includes an anti-patterns table; adds a checklist/decision table only where a flow actually branches"
      - "Writes evals/cases.yaml meeting the minimums (>=5 should_trigger incl. non-obvious, >=4 should_not_trigger each with a real-sibling route_to, >=1 capability with a must_include rubric) plus an honest evals/README.md describing the two-axis run"
      - "Decides NO scripts/verify.sh because a PR-description skill is a process skill judged on its capability eval, OR includes verify.sh only if it emits a checkable artifact — and justifies the choice"
      - "States the rsc wiring: set tags + recommends in frontmatter, run npm run manifest to regenerate manifest.json, and confirm npm run validate / manifest:check / scripts/eval-lint.sh pass"
      - "Keeps the prose original in the rsc voice — does not reproduce another ecosystem's signature artifacts or phrasing"

  - scenario: "A user pastes a skill whose description is 'I help you with deployments' and says 'it fires on everything and also misses real deploy questions — fix the triggering.' Show the description repair."
    must_include:
      - "Diagnoses the two failure modes: first-person + no boundary causes hijacking; no situation clause causes misses"
      - "Rewrites to third-person with a 'Use when…' situation lead and concrete verb phrases"
      - "Keeps only the capabilities that discriminate deployment work from its nearest siblings, rather than padding a keyword list for coverage"
      - "Adds a 'NOT … (that is `sibling`)' boundary naming the real sibling(s) that own the excluded turns to stop hijacking"
      - "Verifies the result is valid single-line quoted YAML, aims <=350 chars against the 1024 hard limit, and keeps origin: risco"
      - "Recommends updating evals/cases.yaml (especially should_not_trigger with route_to) and re-running the triggering eval, since description edits are wording-sensitive"
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: 471kUpdated 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: 471kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 471kUpdated 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