agentleFS
MazalucasMazalucas/El-DT-Lightweight-Army/.agents/skills/dt-skills/SKILL.md

dt-skills

Skill4 starsChanged 4 days agoMITView on GitHub

[Framework] Estandariza las skills del DT y las copia a todos los IDE habilitados. Use when the user invokes /skills, asks to standardize skills across IDEs, or after creating or editing a skill.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    No duplicar SKILL.md a mano en cada IDE.

    line 29
  2. Very specific:

    No crear la skill solo en .claude/ o .agents/.

    line 30
  3. Very specific:

    No prender Gemini o Windsurf sin enabled: true en ide-targets.yaml.

    line 31

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

dt-skills

Una skill, todos los IDE. El canon es .cursor/skills/. Los espejos salen de vitals/config/ide-targets.yaml.

Spec: vitals/specs/skill-standard.md.

Flujo /skills

  1. Si el cambio está en .agents/skills/ o .claude/skills/, traerlo primero al canon. Esos directorios no se editan.
  2. Correr ruby scripts/audit-skills.rb. Corregir cada error antes de seguir.
  3. Correr ./scripts/sync-ide.sh para copiar el canon a cada IDE con receives_skills: true.
  4. Si hace falta un command nuevo: entrada en vitals/config/commands-meta.yaml y ./scripts/sync-commands-from-meta.sh.
  5. Volver a correr ruby scripts/audit-skills.rb y ruby scripts/sync-ide.rb --check.
  6. Decir cuántas skills quedaron y en qué IDE (Antigravity, Codex, Claude). Avisar los WARN de Use when sin reescribir skills ajenas al pedido.

Contrato (resumen)

  • name = carpeta. description con Use when.
  • Paso que cambia por IDE → tabla o spec, no un párrafo solo para Cursor.
  • /drive /gmail /calendar incluyen No recorras Google Cloud Console. Marketplace / Store primero. No citan el runbook de IT. No dictan el alta en Cloud.

No hacer

  • No duplicar SKILL.md a mano en cada IDE.
  • No crear la skill solo en .claude/ o .agents/.
  • No prender Gemini o Windsurf sin enabled: true en ide-targets.yaml.
  • No commitear session.yaml.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.