Plan which agent skills to turn on

Auto-Workflow Builder is an aeon skill: Two-mode aeon.yml workflow builder - analyze inspects URLs and emits a tiered, signal-verified skill-enablement plan plus an aeon.yml diff; enable flips slugs to enabled:true and opens a PR. Like every aeon skill it is one SKILL.md prompt file that runs unattended on your own GitHub Actions, on a schedule or when you trigger it, and sends what it finds to Telegram, Discord, Slack or email.

One skill, two ends of the same loop: analyze decides what to enable for a new watch target; enable actually flips the switch. Dispatch enable: with the slugs the analyze run put in its MUST tier and you close the loop - recommendation to merged PR - without a second skill.

Analyze mode verifies every recommendation is backed by an observed signal on the URL, tiers output into MUST (2-3 max) / SHOULD / NICE with a one-line concrete "why", emits a delta against the current aeon.yml rather than a full config dump, stays silent when existing config already covers the URL, and anchors skill names in skills.json (authoritative), not a stale mapping table. It writes an article + updates a ledger; it never edits aeon.yml.

Enable mode does the mechanical part analyze deliberately leaves to the operator: a slug-scoped enabled: false → true substitution in aeon.yml, gated by directory presence / current-disabled-state / chain-conflict checks, committed on a fresh branch and shipped as a PR with per-skill rationale. Explicit opt-in only - the operator names the slugs; nothing flips on main until they click merge.

Every aeon skill takes one optional text input, var, set in aeon.yml or typed in when you run it by hand. It picks the target or the mode for that run.

Selects the mode:

• Analyze (default): a URL to analyze (GitHub repo, X account, blog, project site, API docs, etc.). Multiple URLs comma-separated. Prefix a URL with force: to re-analyze one already in the ledger. Produces a tiered recommendation article + an aeon.yml diff - it does not mutate aeon.yml.
• Enable: enable:slug1,slug2,… - flip those skills' enabled: false → true in aeon.yml, validate each against skills/, then commit + open a PR. enable:dry-run:slug1,slug2 validates and reports without editing, committing, or opening a PR.

Example values: https://example.com/blog · @vitalikbuterin, github.com/foundry-rs/foundry · force:https://mirror.xyz/somedao · enable:rss-digest,github-monitor · enable:dry-run:price-alert

No extra API keys or MCP servers. It runs on the model you connected to aeon (a Claude subscription token, an API key, or another login).

Easiest: open Aeon Connect, sign in with GitHub and turn on Auto-Workflow Builder. No clone, no terminal. To add it to an existing aeon repo from a shell, run:

Then switch it on in aeon.yml (the default schedule is filled in):

skills:
  auto-workflow: { enabled: true, schedule: "workflow_dispatch", var: "" }

New to aeon? Read the docs for how skills, schedules and memory fit together, or browse all skills.