Skill

/new-skill

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 mandatory "Do NOT trigger for:" clause and a Process section citing guide step ranges) plus skills/{name}/{name}-guide.md

One skill from brooks-lint.

shell

$ npx -y skills add hyhmrright/brooks-lint --skill new-skill --agent claude-code

Installs just this skill. Get the whole plugin for auto-invocation.

How it fires

How this skill gets triggered: by you, by Claude, or both.

Fires itselfClaude auto-loads it when your prompt matches the work.
You can call itInvoke it directly when you want it.
Slash command/new-skill

Context preview

The summary Claude sees to decide when to auto-load this skill.

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 mandatory "Do NOT trigger for:" clause and a Process section citing guide step ranges) plus skills/{name}/{name}-guide.md

Stats

Stars1,248

Forks59

LanguageJavaScript

LicenseMIT

Ships with brooks-lint

SKILL.md

new-skill.SKILL.md

---
name: new-skill
description: >
  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
  mandatory "Do NOT trigger for:" clause and a Process section citing guide step
  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".
  Do NOT trigger for: editing an existing skill's content, adding a single eval to
  an existing skill, or authoring skills for some other plugin.
disable-model-invocation: true
---

# 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:

1. **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