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

astra-testnet

Skill2 starsChanged 2 months agoMITView on GitHub

Fase 4 de ASTRA (Ensayo). Despliega a TESTNET con un alias de claves, valida y registra la direccion en .astra/deployments.json, corre tests de integracion contra la red real y mide costos. Usar cuando el usuario dice "desplegar a testnet", "probar en la red", "ensayo", "friendbot", "faucet" o "registrar la direccion".

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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 pegar una clave en ningún comando ni archivo (A2).

    line 27

≈ “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-testnet — Fase 4: Ensayo

Cuándo

Con Construcción verde. Produce la entrada network: testnet en .astra/deployments.json y los costos medidos.

Pasos

  1. astra chain probe <id-testnet>: chainId o passphrase confirmados hoy. Si falla, no despliegues.
  2. Alias de testnet (lo crea la persona; tú solo usas el nombre): Stellar stellar keys generate --global <alias> --network testnet --fund; EVM cast wallet import <alias> --interactive. Fondos: friendbot (stellar keys fund) o faucet de astra chain info <id>.
  3. Deploy con el CLI nativo, firmando con el alias:
    • Soroban: stellar contract deploy --wasm <ruta.wasm> --source-account <alias> --network testnet [-- --arg valor]
    • EVM: forge create <ruta:Contrato> --rpc-url <rpc> --account <alias> --broadcast
  4. Valida la dirección: astra address <id-testnet> <dirección>. Regístrala: astra deployments add --chain <id-testnet> --address <dirección> --tx <hash> --label <nombre> [--wasm-hash <hash>].
  5. Integración contra testnet: cada función de la interfaz, cada rol, cada invariante, caminos de error. Conformidad con el estándar (interfaz completa de SEP-0041 / ERC-20, etc.).
  6. Mide el costo real por operación (fees, recursos, gas) y anótalo en la Carta, sección Economía (A10).
  7. astra check en OK; astra check --gate mainnet tiene que mostrar testnet-desplegada en OK.

No hacer

  • Nada de mainnet (A1, A3, A7).
  • No pegar una clave en ningún comando ni archivo (A2). Si la testnet de Stellar se reseteó, se redespliega; las entradas viejas no prueban nada.

Done

Entrada testnet registrada y validada, integración documentada, costos medidos, testnet-desplegada OK.

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.