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

astra-orbit

Skill2 starsChanged 2 months agoMITView on GitHub

Fase 1 de ASTRA (Orbita). Elige y sondea la cadena, mide la capacidad del entorno con astra doctor, lista los estandares aplicables y escribe el modelo de amenazas inicial en docs/astra/orbit.md. Usar cuando el usuario dice "orbita", "que cadena usamos", "podemos construir en Stellar/Base/Syscoin desde aca", "perfil de cadena" o empieza un proyecto Web3 nuevo.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No inventar chainIds, RPC ni estándares: todo verificado en vivo o marcado "pendiente de verificar".

    line 25
  2. Distinctive:

    No pedir claves ni fondos de mainnet: en Órbita solo se necesita, como mucho, un alias de testnet.

    line 26

≈ “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
<!-- GENERADO por astra skills sync desde skills/astra-orbit/SKILL.md — no editar a mano; editar el canonico y re-correr el sync -->

astra-orbit — Fase 1: Órbita

Cuándo

Antes de diseñar. Produce docs/astra/orbit.md y el go/no-go que firma la persona.

Pasos

  1. Cadena y red: astra chain list; astra chain info <id>; astra chain probe <id>. Anota chainId o passphrase confirmados, bloque/ledger y fecha. Si la sonda falla, no sigas con esa cadena: busca otro RPC (--rpc <url>) o corrige el registro.
  2. Capacidad: astra doctor --chain <id>. Copia el veredicto (SAFE / CAUTION / AVOID) y lo que falta. Con AVOID, la respuesta es "instalar X" y nada más.
  3. Estándares: astra standards search "<tema>" y guides/standards-map.md. Para cada candidato: id, título, estado y fecha; confirma el estado en la URL oficial (A5).
  4. Lee guides/chains/<familia>.md entera; anota faucets, explorers y costos preliminares.
  5. Modelo de amenazas inicial: activos en juego, atacantes plausibles, superficies, supuestos que lo cambian todo.
  6. Escribe docs/astra/orbit.md desde templates/orbit.template.md (si no existe, astra init lo crea). Sin marcadores <...>.
  7. Pide a la persona el go/no-go con nombre y fecha.

No hacer

  • No inventar chainIds, RPC ni estándares: todo verificado en vivo o marcado "pendiente de verificar".
  • No pedir claves ni fondos de mainnet: en Órbita solo se necesita, como mucho, un alias de testnet.

Done

orbit.md completo, veredicto de capacidad distinto de AVOID, estándares fechados, modelo de amenazas escrito, go firmado por la persona.

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.