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

dt-oficial

Skill4 starsChanged 4 days agoMITView on GitHub

[Framework] Marcar este checkout como el único que puede publicar al remoto oficial del DT. Use when the user invokes /oficial.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No marcar una carpeta distinta de la que muestra el script.

    line 49
  2. Very specific:

    No copiar vitals/ops/canonical-checkout.yaml a otro clone.

    line 50
  3. Distinctive:

    No commitear ese archivo.

    line 51
  4. Very specific:

    No tratar mode: canonical ni /yo como sustituto de este comando.

    line 52

≈ “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-oficial

Spec: vitals/specs/canonical-publish.md.

Por defecto ninguna carpeta publica al DT. Este comando escribe una marca local, gitignored, en la carpeta que el dueño confirma.

Lo que se publica es el framework. No viaja la sesión, el roster con personas, la postura de esta máquina ni el cuaderno vitals/work/inbox/. roster.yaml en Git se queda con team: []. Si el gate sale 50, esos rastros están en el árbol: no se commitean.

Invocaciones

ComandoAcción
/oficialMostrar la ruta y pedir confirmación. Sin el sí, no marcar.
/oficial y en el mismo mensaje ya confirmaron esta rutaActivar
/oficial offBorrar la marca
/oficial statusDecir si esta carpeta puede publicar

Activar

  1. Corré sin escribir la marca:

    ./scripts/dt-oficial.sh activate
  2. Si el exit es 2, mostrale al usuario la carpeta, el origin y el login, y preguntá: ¿Marco esta carpeta como el checkout oficial del DT? Esperá el sí. No pases --yes en el mismo turno salvo que ese mensaje ya haya confirmado esa ruta.
  3. Con el sí:

    ./scripts/dt-oficial.sh activate --yes
  4. Exit 0 y la salida ya dice que el checkout está activo: no vuelvas a preguntar.
  5. Exit 1: mostrá el motivo y pará. No ofrezcas pedir acceso, ni invitación, ni gh auth para publicar el DT con otra cuenta.

Apagar

./scripts/dt-oficial.sh off

No hacer

  • No marcar una carpeta distinta de la que muestra el script.
  • No copiar vitals/ops/canonical-checkout.yaml a otro clone.
  • No commitear ese archivo.
  • No tratar mode: canonical ni /yo como sustituto de este comando.

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.