{% extends "base.html" %} {% block title %}Playground — Ageri{% endblock %} {% block head %} {% endblock %} {% block body %}
Author your own skills here
The Playground is where you create new skills — describe what you want, demonstrate a workflow, import from GitHub, or write code by hand. Once it works, pack + publish to share it with others on the Marketplace.
No local skills yet.
Pick a skill on the left to inspect it,
or create a new one.
Saving changes…
Refresh from source:
No source files indexed.
Loading file...
Manifest invalid — not saved:
Pretend you're a user talking to your agent. Type what you'd say below and watch the skill respond — nothing real happens (no real messages sent, no real API calls), just a dry-run so you can verify the skill works before you install it.
Response
:
Tool calls
Claim a namespace on the Ageri marketplace — your published
skills will live under ageri://<namespace>/<skill>@<version>.
This is your Ageri namespace — you can only register your own. Change AGERI_NAMESPACE in setup if you need a different one.
Signed in as . Pick a tagged version to push to the marketplace.
Loading your skills…
Nothing to publish yet
Open a local skill in the playground and use Install as a new version › to create a tagged version. Tags are what get published.
Freezes the current snapshot as a new installable version + bumps the snapshot to the next development version. Same shape as the Jenkins Maven-release flow — both numbers are editable.
What you're freezing as an installable version — no
-snapshot suffix.
What the snapshot bumps to after the tag is created. Must end with
-snapshot. Auto-fills as you type
the release version — edit if you're jumping a major.
Pick how you want to start. Most paths land in ~/ageri/skills/local/<id>/. Lands in ~/ageri/skills/local/<id>/.
Tell Ageri what you want to automate. Be as specific as you can — the more detail you give, the less it has to ask.
Good examples:
Your description
Ageri has a few questions before scaffolding:
Files written:
Tools:
Category:
The starter is intentionally rough — open it in the editor to refine.
Five commands take you from blank to published. Run them in any shell where Ageri is installed.
1. Scaffold from a template
2. Edit boss.py in your editor (VS Code, Cursor, Claude Code, …)
3. Validate
4. Pack (after bumping version in skill.json)
5. Upload to the marketplace
Full author guide: docs.ageri.ai
Drop or pick a .ags bundle. Ageri validates the manifest then installs the skill into the right directory based on its declared trust level.
Lowercase, hyphens allowed. Becomes the directory name.
Records a workflow that crosses desktop and browser. Three capture sources:
Ctrl+Shift+R on the focused appCtrl+Shift+C after a Ctrl+C in any app; the value flows into the next browser pasteThe recorder opens a browser window — start it at the right page so you can drive straight in.
The recorder's browser window is open. Switch between it and your desktop app: browser clicks/typing capture automatically; press Ctrl+Shift+R before each desktop click; press Ctrl+Shift+C after a desktop Ctrl+C to lock in the clipboard value for the next browser paste.
No steps captured yet.
Append #<ref> to pin a branch/tag/commit. Private repos use your SSH key or git credential helper.