Submit an ARA
Submission happens from your own machine through the submit-ara agent skill. GitHub is the data layer — your artifact is published to your own public GitHub account, and ARA Hub fetches and renders it from there.
⏳ Publishing can take ~15 minutes. The skill may compile your input into the ARA format, generate the interactive visualization (figure rendering is the slow part), and create + push a GitHub repository. Keep the session open and let it finish.
1. Install the skills
npx @ara-commons/ara-skills2. Authenticate GitHub once
gh auth loginThe skill publishes to whichever account gh is logged into, so no org permissions are needed.
3. Run the skill
/submit-ara <path-to-your-ara-or-research-dir>It will, in order:
- Check the directory is a valid ARA; if not, compile (or update) it with the
compilerskill. - Ensure an interactive visualization exists; if not, generate
trajectory.htmlwith theresearch-visualizerskill. - Create a public repo
ara-<slug>on your account and push the artifact (includingtrajectory.html). - Register it here so it appears in Browse, and print all the links.
What you get back
- GitHub repo:
github.com/<you>/ara-<slug> - Hub viewer:
/ara?repo=<you>/ara-<slug> - Direct visualization (CDN):
cdn.jsdelivr.net/gh/<you>/ara-<slug>@main/trajectory.html
Coming soon: a backend database will replace the static registry, so the Hub lists every submitted ARA automatically. The skill already targets the same
POST /api/submit contract — wiring the database is a one-endpoint change.