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
- LightconeResearch/agent-skillstheir own version, first seen Oct 25, 2026
- Lesani/skillstheir own version, first seen Oct 11, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- LightconeResearch/agent-skills★ 2same name
- Lesani/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository28 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- astra-auditSkill
- astra-buildSkill
- astra-chartSkill
- astra-launchSkill
- astra-logbookSkill
- astra-orbitSkill
- astraSkill
- astra-standardsSkill
- astra-testnetSkill
- astra-auditSkill
- astra-buildSkill
- astra-chartSkill
- astra-launchSkill
- astra-logbookSkill
- astra-orbitSkill
- astra-standardsSkill
- astra-testnetSkill
- astra-auditSkill
- astra-buildSkill
- astra-chartSkill
- astra-launchSkill
- astra-logbookSkill
- astra-orbitSkill
- astraSkill
- astra-standardsSkill
- astra-testnetSkill
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
- Very specific: line 17
No hay .astra/astra.json → Inicio: astra init --chain <id> --runtimes <runtime>.
- Very specific: line 18
No hay orbit.md o no tiene go firmado → Órbita (skill astra-orbit).
≈ “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.
Files
<!-- GENERADO por astra skills sync desde skills/astra/SKILL.md — no editar a mano; editar el canonico y re-correr el sync -->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
- 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. - Determina la fase con esta regla, en orden:
- No hay
.astra/astra.json→ Inicio:astra init --chain <id> --runtimes <runtime>. - No hay
orbit.mdo no tiene go firmado → Órbita (skillastra-orbit). chart.mdno existe o no tiene la líneaaprobada: YYYY-MM-DD→ Carta / Gate 1 (skillastra-chart).- El registro no tiene ninguna entrada
network: testnet→ Construcción / Ensayo (skillsastra-build,astra-testnet). audit.mdno existe o no diceveredicto: apto→ Auditoría (skillastra-audit).launch.mdno tienefirmado_poryfecha_firma→ Gate 2 (skillastra-launch).- El registro no tiene ninguna entrada
network: mainnet→ Lanzamiento (skillastra-launch). - Todo existe → Bitácora (skill
astra-logbook).
- No hay
- Corre
astra check(yastra check --gate mainnetsi estás en Auditoría o después) y lee la salida. - 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 mainnetno 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.
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
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.

