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.
Send this to Claude Code, Codex or Cursor. The agent checks the Skill for safety first and installs it only after you confirm.
读取 https://funcoding.ai/skills/hyhmrright/brooks-lint/new-skill/install.md ，按里面的步骤帮我安装这个 Skill。
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:
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).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._shared/ files (common.md for Iron Law + Report Template, plus
decay-risks.md / test-decay-risks.md as applicable) — _shared/ is NOT
auto-loaded.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.npm run validate (structure + step continuity + Process-section
presence) and npm run evals (eval schema). Fix until both pass.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.
anthropics/skills180kCreate 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.
Testing
DietrichGebert/ponytail158kQuality audit of a whole repo: bugs, security holes, what breaks under real load, risky code without tests, slow paths, and what to delete, merge or split. Ranked, each finding explained in plain English. One-shot report, changes nothing. Use for "audit this codebase", "review the whole repo", "find bloat", "what can I delete", /ponytail-audit.
Testing
DietrichGebert/ponytail158kQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.
Testing
DietrichGebert/ponytail158kQuality review of a diff: bugs, security, real load, missing tests, speed, and what to delete. Each finding says what goes wrong and how to fix it.
Testing
addyosmani/agent-skills103kAutomates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
Testing
addyosmani/agent-skills103kRefines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when an idea is still vague, when you need to stress-test assumptions before committing to a plan, or when you want to expand options before converging on one. Triggers on "ideate", "refine this idea", or "stress-test my plan".
Testing