mcpbeat Sign in

New Skill for Claude

by hyhmrright

> Scaffold a new brooks-lint analysis skill so it passes `npm run validate` and `npm run evals` on the first try — generates skills/{name}/SKILL.md (with the ranges) plus skills/{name}/{name}-guide.md (sequentially numbered steps), then appends paired eval scenarios. Triggers when the maintainer asks to "add a new skill", "scaffold a skill", or "create a brooks-lint mode". an existing skill, or authoring skills for some other plugin.

723 tokens
context cost
SKILL.md, read when the skill is used
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
1 313
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/hyhmrright/brooks-lint --skill new-skill

The instruction itself

1 sections, as written by the author

brooks-lint — New Skill Scaffold

Skill name comes from $ARGUMENTS (kebab-case, e.g. brooks-security). If empty,

ask for the name and a one-line purpose first.

Follow the repo's "Adding a New Skill" checklist exactly:

  • Create skills/{name}/SKILL.md with frontmatter — name, a description

that ends with a Do NOT trigger for: clause (validate-enforced for shipped

skills; omitting it causes false triggering), and a Process section of 3–6

bullets that cite the guide's step ranges inline (e.g. `Scan risks (Steps 1–6 of

the guide)`). Mirror the structure of an existing skill such as

skills/brooks-review/SKILL.md (Setup → Process → Mode line).

  • Create skills/{name}/{name}-guide.md with sequentially numbered steps —

no gaps, no duplicates. Sub-steps like Step 2a are allowed. The guide owns the

detailed steps; the SKILL.md Process is just an orientation skeleton.

  • Wire the framework. The new SKILL.md Setup section must Read the relevant

_shared/ files (common.md for Iron Law + Report Template, plus

decay-risks.md / test-decay-risks.md as applicable) — _shared/ is NOT

auto-loaded.

  • Add eval coverage to evals/evals.json: append with the next sequential

id at least one happy-path scenario (with the relevant risk code in

expected_output) and at least one false-positive scenario flagged

no_risk_codes: true. Each scenario needs id, name, prompt,

expected_output, mode, files.

  • Validate. npm run validate (structure + step continuity + Process-section

presence) and npm run evals (eval schema). Fix until both pass.

  • Local-test. cp -r skills/* ~/.claude/skills/brooks-lint/ (if you've

symlinked ~/.claude/skills/brooks-lint to the repo, skip this — edits are

already live), trigger the new skill in a Claude session, verify the Iron Law

output, then restore the marketplace copy: /plugin marketplace update →

/plugin install brooks-lint@brooks-lint-marketplace.

Do NOT register a slash command by hand — short forms are auto-installed by the

session-start hook. Report the files created and the validate/evals results.

How to use it

Copy the folder

Take hyhmrright/new-skill from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.