- name
SKILL.md
El archivo de la skill permanece en el repositorio del publicador.
Pega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add hyhmrright/brooks-lint --skill new-skill -a cursor -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add hyhmrright/brooks-lint --skill new-skill -a claude-code -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add hyhmrright/brooks-lint --skill new-skill -a codex -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add hyhmrright/brooks-lint --skill new-skill -a grok -yEnvía el mensaje copiado en un chat de Grok Bot. El Bot obtiene este SKILL.md de GitHub y lo añade a las skills que comparten todos tus Bots.
Install this skill: https://github.com/hyhmrright/brooks-lint/tree/HEAD/.agents/skills/new-skillDel publicador
Skill name comes from the user request (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), metadata: with opencode/slash: "true", 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.skills/ into
.agents/skills/ alongside the _shared symlink, then invoke it with
$<skill-name> in a Codex session and verify the Iron Law output.Codex discovers repository skills directly; no command wrapper is needed. Report the files created and the validate/evals results.
>
---name: new-skilldescription: >---# .agents/skills/new-skill/SKILL.mdPreguntas frecuentes
Descarga .agents/skills/new-skill/SKILL.md desde el publicador, o copia la ruta y abre el repositorio. PlugMCP lista la skill y no aloja el archivo.
El publicador lo mantiene en https://github.com/hyhmrright/brooks-lint.
Claude, Cursor, Codex y Grok Build pueden leer un SKILL.md que añadas desde el repositorio del publicador. Grok Bot lo instala cuando envías en un chat el enlace a la carpeta de la skill en GitHub.