skill-hyhmrright-brooks-lint-new-skill · by Install
$ agentstack add skill-hyhmrright-brooks-lint-new-skill ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-hyhmrright-brooks-lint-new-skill) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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.mdwith frontmatter —name, adescription
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.mdwith 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.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: hyhmrright
- Source: hyhmrright/brooks-lint
- License: MIT
- Homepage: https://hyhmrright.github.io/brooks-lint/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.