get-started

Files (1)

• SKILL.md

SKILL.md (first lines)

# Get started with Aeon

Aeon is an agent that runs skills on a schedule with GitHub Actions in the user's own GitHub repo. This plugin connects to their Aeon agent through Aeon Connect (`https://www.aeon.fun/connect/mcp`).

## 1. Check the connection

Call `list_skills`.

- **It works:** go to step 2.
- **It asks to sign in, or fails with an auth error:** tell the user to connect Aeon (sign in with GitHub, then pick their agent on the "Connect an app" screen), then try again.
- **They have no agent yet:** send them to https://www.aeon.fun/connect to create one (about two minutes: sign in with GitHub, create the repo, connect a model). Then connect the plugin again.

The connection works on one agent repo at a time. If the user allowed switching when they connected, `list_instances` shows their other Aeon repos and `switch_instance` moves to one. Only bring this up if they have more than one agent or ask about another repo.

## 2. Show what the agent does and what it still needs

From the `list_skills` result, tell the user in a few lines:

- which repo the plugin is connected to,
- how many skills are on, and the schedule of each one that is on,
- two or three skills that are off and look useful, with one line each.

Keep it short. Do not list every skill.

Then call `setup_status`. If a model is not connected, or enabled skills are missing API keys, name what is missing and say where to add it: the Keys tab for this agent at https://www.aeon.fun/connect. `setup_status` gives key names only. Never ask for the values.

## 3. Run one skill

If a model is connected, offer to run `heartbeat` (a quick check that the agent works; it needs no setup). If the user agrees:

1. Call `run_skill` with `skill: "heartbeat"`.
2. Follow the run. Some apps show a live runs view right in the chat; otherwise call `get_run` with the returned `run_id` every so often until `status` is `completed`. A run takes one to ten minutes; tell the user it is running and keep the chat useful meanwhile.
3. If it succeeded, call `read_output` with `skill: "heartbeat"` and summarize what it found in a few lines.
4. If it failed, `get_run` gives the likely reason (most often the model login is missing or expired). Explain it and the fix in plain words, and point to https://www.aeon.fun/connect to fix it.

If there is no `heartbeat` skill, offer any skill that is on instead. If no model is connected, skip this step and point back to the missing model from step 2.

## 4. Next steps

Tell the user what they can ask from now on, for example:

- "Turn on the digest skill every morning at 8"
- "Did anything fail today? Why?"
- "Show me what my last digest found"
- "What has my agent written down about this week?"
- "Add 'grow the newsletter' to my strategy"
- "What skill packs can I add?"
- "Open my Aeon dashboard"

## Rules

- `update_skill`, `update_strategy`, `update_soul`, `install_pack` (it opens a pull request), `switch_instance`, `update_instance_settings` and the settings switches change the user's setup. Say what will change and get a yes before calling them.
- Never ask for API keys, tokens or secrets. `setup_status` shows key names only; keys are added in Aeon Connect, not in chat.
- If an Aeon tool fails or answers wrong, `send_feedback` reports it to the Aeon team (pass `run_id` for a failed run). Tell the user what you sent; never include secrets.

From aeonfun/aeon, MIT.

More from aeonfun/aeon