agentleFS
orlando-vazquez-careerorlando-vazquez-career/astra-protocol/skills/astra/SKILL.md

astra

Skill2 starsChanged 2 months agoMITView on GitHub

Punto de entrada del protocolo ASTRA (desarrollo Web3 agentico, multi-cadena). Determina en que fase esta el proyecto (Orbita, Carta, Construccion, Ensayo, Auditoria, Lanzamiento, Bitacora) leyendo .astra/ y docs/astra/, y propone el siguiente paso con el comando exacto. Usar cuando el usuario dice "astra", "en que fase estamos", "que sigue en el protocolo", "quiero desplegar un contrato", "vamos a mainnet" o empieza cualquier trabajo con contratos, tokens, dApps o despliegues en Stellar, Syscoin, Base u otra EVM.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 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.

  • 2

    Very specific

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

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

    No hay .astra/astra.json → Inicio: astra init --chain <id> --runtimes <runtime>.

    line 16
  2. Very specific:

    No hay orbit.md o no tiene go firmado → Órbita (skill astra-orbit).

    line 17

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

astra — ¿en qué fase estamos?

Cuándo

Al empezar cualquier trabajo que toque una cadena, o cuando no está claro qué sigue. Si el repo no tiene .astra/, el siguiente paso es siempre astra init.

Pasos

  1. Lee, si existen: .astra/astra.json, .astra/deployments.json, docs/astra/orbit.md, docs/astra/chart.md, docs/astra/audit.md, docs/astra/launch.md.
  2. Determina la fase con esta regla, en orden:
    • No hay .astra/astra.json → Inicio: astra init --chain <id> --runtimes <runtime>.
    • No hay orbit.md o no tiene go firmado → Órbita (skill astra-orbit).
    • chart.md no existe o no tiene la línea aprobada: YYYY-MM-DD → Carta / Gate 1 (skill astra-chart).
    • El registro no tiene ninguna entrada network: testnet → Construcción / Ensayo (skills astra-build, astra-testnet).
    • audit.md no existe o no dice veredicto: apto → Auditoría (skill astra-audit).
    • launch.md no tiene firmado_por y fecha_firma → Gate 2 (skill astra-launch).
    • El registro no tiene ninguna entrada network: mainnet → Lanzamiento (skill astra-launch).
    • Todo existe → Bitácora (skill astra-logbook).
  3. Corre astra check (y astra check --gate mainnet si estás en Auditoría o después) y lee la salida.
  4. Responde en este formato:
Fase: <nombre> · Cadena: <id> · Gate pendiente: <ninguno / G1 / G2>
Falta: <artefacto o condición concreta>
Siguiente paso: <comando exacto o skill>
Quién: <rol> (persona si es un gate)

Reglas que aplican siempre

  • Mainnet es irreversible (A1): nunca proponer un comando de mainnet si astra check --gate mainnet no está en OK.
  • Las claves no existen para el agente (A2): si el usuario pega una clave, decirle que la rote y no repetirla.
  • Testnet primero (A3). Los agentes no mueven fondos de mainnet (A7).

Done

El usuario sabe la fase, lo que falta, el próximo comando y quién lo ejecuta.

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.