[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D6DTYZMATGXS3BH5XBQ05W":3,"skill-same:01M7D6DTYZMATGXS3BH5XBQ05W":75},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M7D6DTYZMATGXS3BH5XBQ05W","aeon",null,"Set up and run an Aeon agent instance — get started from scratch, pick which skills to turn on or install more from packs, reschedule or change what runs, edit what an existing skill does, fix a skill that isn't firing, set the STRATEGY.md north star and soul\u002F voice, turn a coding-agent chat into a scheduled Aeon skill, and mine past coding-agent conversations for recurring work worth automating as a skill. Use when the user mentions Aeon, aeon.yml, an Aeon skill \u002F instance \u002F routine \u002F pack, asks to schedule, enable, edit, or debug an agent that runs on a cron, or asks what of their repeated\u002Fmanual work Aeon could take over.","LiamVisionary\u002Faeon-template","LiamVisionary","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F102138294?v=4","01M73379NZZ99TT4ZS17XR3Q9D","01M7D6D62V1SGGMKGT08Q1D2R8",0,"MIT","https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Faeon-template\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Faeon\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: aeon\ndescription: Set up and run an Aeon agent instance — get started from scratch, pick which skills to turn on or install more from packs, reschedule or change what runs, edit what an existing skill does, fix a skill that isn't firing, set the STRATEGY.md north star and soul\u002F voice, turn a coding-agent chat into a scheduled Aeon skill, and mine past coding-agent conversations for recurring work worth automating as a skill. Use when the user mentions Aeon, aeon.yml, an Aeon skill \u002F instance \u002F routine \u002F pack, asks to schedule, enable, edit, or debug an agent that runs on a cron, or asks what of their repeated\u002Fmanual work Aeon could take over.\n---\n\n# Aeon\n\nAeon is an agent that runs on the user's own GitHub repo via Actions. A skill is a Markdown file (`skills\u002F\u003Cname>\u002FSKILL.md`); `aeon.yml` says which ones run and when.\n\nPick the mode they're asking for:\n\n| | |\n|---|---|\n| **1 · Start** | No instance yet, or set one up from scratch |\n| **2 · Reschedule** | Change times, cadence, or what a skill focuses on |\n| **3 · Unblock** | \"It didn't run\" \u002F \"nothing happened\" |\n| **4 · Chat → skill** | Turn what we just did into a scheduled skill |\n| **5 · Edit a skill** | Change what an existing skill does |\n| **6 · What to turn on** | Pick skills, browse packs, install more |\n| **7 · Strategy & voice** | `STRATEGY.md` and `soul\u002F` — the north star and the tone |\n| **8 · Mine history → skill** | \"What of my repeated work could Aeon do for me?\" — surface it from past coding-agent chats |\n\n## Preflight (every mode)\n\n1. Find the repo: current dir → `gh repo set-default` → ask. Clone it if it isn't local.\n2. **Confirm `gh` points at THEIR instance, before any command that writes.**\n\n   ```bash\n   gh repo view --json nameWithOwner -q .nameWithOwner\n   ```\n\n   If that prints `aeonfun\u002Faeon` and they aren't working on upstream itself, stop and run `gh repo set-default \u003Cowner>\u002F\u003Crepo>`. `gh` prefers an `upstream` remote over `origin` when no default is pinned, and every Aeon write (`auth`, `secrets set`, `skills run`, config pushes) is a `gh -R \u003Cresolved>` call — so it will cheerfully put their API keys on the upstream repo and dispatch runs there. It looks like success: no error, a real run id, and the skill just never fires on their instance.\n3. `gh auth status` — everything routes through `gh`. If it fails, tell them to run `gh auth login` and stop.\n4. Use the `.\u002Faeon` CLI for all config writes. It preserves comments in `aeon.yml` and validates. Never hand-edit the YAML — with one exception: the CLI cannot *create* an entry for a brand-new skill (see Mode 4 step 4).\n\n**Don't trust \"disabled\" for a skill you just created.** The read path lists skills from disk and defaults a missing `aeon.yml` entry to `enabled: false`, so \"not configured\" and \"disabled\" look identical. One command tells them apart:\n\n```bash\ncomm -23 \u003C(ls skills\u002F*\u002FSKILL.md | cut -d\u002F -f2 | sort) \\\n         \u003C(grep -oE '^  [a-z0-9-]+:' aeon.yml | tr -d ' :' | sort)\n```\n\nAnything it prints is on disk but unconfigured. **Orientation — what's installed, what's on, and where everything lives: `references\u002Flayout.md`.**\n\n**Setting any key or token:** read `references\u002Fsecrets.md` — it has every secret and repo variable with the exact page to get it from. Always set secrets with `.\u002Faeon secrets set NAME --stdin`, never as a command argument.\n\n---\n\n## Mode 1 — Start on Aeon\n\nGoal: one real notification in their phone, fast. Do not configure a schedule first.\n\n1. **Get a repo. Ask public or private before you run anything** — it changes the command, and switching later means moving the repo.\n\n   **Public** (recommend this): Actions minutes are free, and upstream skill updates arrive with one command.\n\n   ```bash\n   gh repo fork aeonfun\u002Faeon --clone && cd aeon\n   gh repo set-default \u003Cowner>\u002Faeon        # REQUIRED — see below\n   ```\n\n   **Private**: a fork of a public repo is always public, so a private instance is a mirror, not a fork.\n\n   ```bash\n   gh repo create \u003Cname> --private\n   git clone --bare https:\u002F\u002Fgithub.com\u002Faeonfun\u002Faeon.git\n   git -C aeon.git push --mirror https:\u002F\u002Fgithub.com\u002F\u003Cowner>\u002F\u003Cname>.git\n   rm -rf aeon.git && git clone https:\u002F\u002Fgithub.com\u002F\u003Cowner>\u002F\u003Cname>.git && cd \u003Cname>\n   git remote add upstream https:\u002F\u002Fgithub.com\u002Faeonfun\u002Faeon.git\n   gh repo set-default \u003Cowner>\u002F\u003Cname>      # REQUIRED — see below\n   ```\n\n   Say both costs out loud before they pick private: Actions minutes bill against the account quota (2,000\u002Fmo on Free — scheduled skills burn it), and updates come from `git fetch upstream && git merge upstream\u002Fmain` instead of `gh repo sync`.\n\n   **Pin the default repo before any other command — both paths.** Both end up with an `upstream` remote (`gh repo fork --clone` adds one for you), and with no default pinned **`gh` prefers `upstream` over `origin`**. Everything in Aeon routes through `gh -R $(gh repo view …)`, so an unpinned checkout silently writes secrets to and dispatches runs against `aeonfun\u002Faeon` instead of their instance — with no error, because the commands genuinely succeed on the wrong repo. Verify:\n\n   ```bash\n   gh repo view --json nameWithOwner -q .nameWithOwner   # must print THEIR repo\n   ```\n\n   Everything after this step is identical either way.\n2. **Auth a model.** At least one is required. Fastest is `.\u002Faeon auth --oauth` (Claude Pro\u002FMax, opens a browser), or `.\u002Faeon auth --key \u003Ckey>`, which detects the provider **from the key prefix** — `sk-ant-oat` (OAuth), `sk-or-` (OpenRouter), `bk_` (Bankr), `inf_` (Surplus), `xai-` (Grok); anything else lands in `ANTHROPIC_API_KEY`.\n\n   **UsePod and Venice keys have no prefix** and are undetectable, so a bare `--key` files them as a plain Anthropic key and the run fails later with a confusing auth error. They must be named:\n\n   ```bash\n   .\u002Faeon auth --key \u003Ctoken> --provider usepod    # same for venice\n   ```\n\n   `--dry-run` prints the resolved `method=… → secret …` without calling `gh` or `claude` — worth running whenever the provider is in doubt.\n\n   **Don't assume they have a Claude subscription:** nine providers work, including OpenRouter, Grok, GLM, and crypto-settled gateways. See \"Providers and harnesses\".\n3. **Wire one channel.** Telegram is the fastest: create a bot with @BotFather, then `.\u002Faeon secrets set TELEGRAM_BOT_TOKEN --stdin` and `TELEGRAM_CHAT_ID`. Skip Discord\u002FSlack\u002Femail for now — one channel is enough to prove it works.\n4. **Run one skill now.** Pick it with Mode 6 — ask what they want handled, propose one — then `.\u002Faeon skills run \u003Cname>`. Wait for it, then `.\u002Faeon runs logs \u003Cid>`. They should get a Telegram message.\n5. **Only then, schedule it.** `.\u002Faeon skills enable \u003Cname>` and set a time (see Mode 2).\n\nGood first skills: `digest` (topic briefing), `github-monitor` (their repos), `heartbeat` (already on by default, reports only when something needs attention).\n\n---\n\n## Mode 2 — Reschedule \u002F change the routine\n\nShow them their day as a **timeline in their own timezone**, not a config file:\n\n```\n07:00  digest           \"solana\"\n09:00  pr-review        your repos\n18:00  heartbeat        health check\n```\n\nBuild it from `.\u002Faeon skills ls --enabled --json`. (`--enabled` matters: plain `ls` prints a `SCHEDULE` column for *disabled* skills too — that's their `aeon.yml` entry, not proof anything fires.) No CLI, or want the raw file? `references\u002Flayout.md` has grep-only equivalents. Then take plain-language edits and apply them:\n\n| They say | You do |\n|---|---|\n| \"move the digest to 7am\" | `.\u002Faeon skills schedule digest \"0 6 * * *\"` |\n| \"weekdays only\" | `... \"0 6 * * 1-5\"` |\n| \"too noisy, twice a week\" | `... \"0 6 * * 1,4\"` |\n| \"stop the crypto one\" | `.\u002Faeon skills disable token-movers` |\n| \"make it about rust instead\" | `.\u002Faeon skills set digest --var rust` |\n\nRules:\n- **All cron in `aeon.yml` is UTC.** Convert from their timezone, and say so: \"7am Paris = `0 6 * * *` UTC (5am in summer — want it pinned to local time?\" There is no local-time option, so if DST matters, tell them which half of the year is off by an hour.\n- Confirm back the **next 3 fire times in their timezone** after any change.\n- `--dry-run` first on anything ambiguous, show the diff, then apply.\n- Changes need a push to take effect. The CLI does it; confirm it landed.\n- **Then check the value came out quoted** — one grep, every time:\n\n  ```bash\n  grep '^  \u003Cskill>:' aeon.yml\n  ```\n\n  The scheduler only reads `schedule: \"…\"` **with double quotes**. The CLI writes a *new* key unquoted, so an entry that had no `schedule:` yet comes back as `schedule: 0 12 * * *` and the skill is skipped forever. Details below.\n\nSkills with `schedule: workflow_dispatch` are on-demand only — they never fire on cron. `reactive` ones fire on conditions, not time.\n\n---\n\n## Mode 3 — Unblock\n\n\"It didn't run.\" Check in this order and stop at the first hit:\n\n1. **Is it on?** `.\u002Faeon skills ls --enabled` — is it listed?\n2. **Duplicate key?** `node scripts\u002Fvalidate-config.js`. A repeated skill name in `aeon.yml` silently shadows the first one. Common after hand-edits.\n3. **Is it even cron?** `workflow_dispatch` and `reactive` never fire on a schedule.\n4. **Are Actions disabled?** `gh api repos\u002F{owner}\u002F{repo}\u002Factions\u002Fpermissions`. GitHub auto-disables scheduled workflows after 60 days of repo inactivity — this silently kills forks and nothing in Aeon surfaces it. Re-enable in repo Settings.\n5. **Is the schedule quoted?** `grep '^  \u003Cskill>:' aeon.yml` — the value must be `schedule: \"0 12 * * *\"`, **with double quotes**.\n\n   ```\n   schedule: \"0 12 * * *\"   ✅ fires\n   schedule: 0 12 * * *     ❌ never fires, no error anywhere\n   ```\n\n   `scheduler.yml` matches schedules with the bash regex `schedule: *\"([^\"]+)\"`. An unquoted value doesn't match, `$SCHED` is empty, and the match loop hits `[ -z \"$SCHED\" ] && continue` — skipped silently, every tick, forever.\n\n   How it gets that way: the CLI edits `aeon.yml` through a YAML document model that preserves an *existing* quoted node but writes a **newly added** key in plain style. So `.\u002Faeon skills schedule \u003Cname> \"0 12 * * *\"` is safe on an entry that already had a quoted `schedule:`, and quietly breaks one that didn't. Same for a first-time `--var`.\n\n   **Nothing else detects this.** The file is valid YAML, `validate-config.js` reports CLEAN, and `.\u002Faeon skills ls --enabled` lists the skill with its schedule — because they all parse YAML properly and only the scheduler uses a regex. Fix by adding the quotes by hand.\n6. **Did it run and fail?** `.\u002Faeon runs ls` then `.\u002Faeon runs logs \u003Cid>`. A failed skill retries after a 30-minute cooldown.\n\nThree more, if the above are clean:\n\n- **It ran against the wrong repo.** The giveaway is a command that reported success with a run id, but `.\u002Faeon runs ls` on their instance shows nothing. `gh` prefers `upstream` over `origin` when no default is pinned, so an unpinned checkout sends every write to `aeonfun\u002Faeon`.\n\n  ```bash\n  gh repo view --json nameWithOwner -q .nameWithOwner   # if this isn't their repo:\n  gh repo set-default \u003Cowner>\u002F\u003Crepo>\n  ```\n\n  Then **clean up what landed upstream** — re-running against the right repo does not undo it. Any key set while mispointed is now a secret on someone else's repo:\n\n  ```bash\n  gh secret list -R aeonfun\u002Faeon      # timestamps matching the misfire = theirs\n  ```\n\n  **Rotate it at the provider first, always** — it sat on a repo whose collaborators can land a workflow that reads it. Then re-set it on their instance with `.\u002Faeon secrets set NAME --stdin`.\n\n  **Don't blind-delete it.** `gh secret list` shows only *last-updated*, so it cannot tell you whether the upstream repo already had that secret and the misfire **overwrote** it. Ask before removing:\n  - Upstream never had it → `gh secret delete \u003CNAME> -R \u003Cupstream>`.\n  - Upstream had its own → deleting breaks *their* scheduled runs. The owner must re-set upstream's own value; the overwrite is not reversible from here.\n\n  If the delete 403s, they never had write access — nothing was ever written, and the earlier command failed while only *looking* fine.\n- **Missing secret.** Skills declare keys in `requires:`. Check them against `.\u002Faeon secrets ls --set`. A missing optional key (`KEY?`) means it degrades quietly, not that it breaks.\n- **\"No MCP tools available.\"** On the Claude harness a single unresolved `${VAR}` in `.mcp.json` disables **every** MCP server for that run, not just the broken one (`::warning::.mcp.json references secret(s) not set:` … `Skipping MCP this run.`). Grok degrades per-server instead. If an OAuth server broke a run *after* working, suspect a rotated refresh token that couldn't be saved — `references\u002Fmcp.md`.\n- **It ran but sent nothing.** That's usually correct. Aeon's convention is silence on no signal — a clean run sends nothing rather than an empty report.\n\nNote: GitHub only delivers ~10% of `*\u002F5` cron ticks, so the scheduler catches up missed slots for up to 12 hours. A skill firing 40 minutes late is normal.\n\n---\n\n## Mode 4 — Turn this chat into a skill\n\nThey just did something in this chat and want it to happen on a schedule.\n\n1. **Write the skill file.** `skills\u002F\u003Cname>\u002FSKILL.md` — frontmatter, then the prompt. Derive it from what actually happened in the session:\n   - the prompt body = what they asked for, plus the steps that worked\n   - `mode:` = `read-only` unless it needs to commit or open PRs\n   - `requires:` = any API key the work hit (`KEY?` if it can degrade without it)\n   - `category:` = one of `core evolution basics dev crypto productivity`\n   - if they liked the output, paste a trimmed sample into the body as the format spec\n\n2. **Fix the three things that break unattended runs:**\n   - **Nobody's there.** Any point where you asked them a question has to become a default or a rule.\n   - **Stay silent on nothing.** Add an explicit \"if there's nothing worth reporting, log and exit without notifying.\" Otherwise it gets muted in a week.\n   - **Don't repeat yesterday.** Add \"check the last 3 days of `memory\u002Flogs\u002F` and skip anything already reported.\"\n\n3. **Check it can actually run there.** No local filesystem, no logged-in tools. If the session read their home directory or used a local MCP server, say so plainly — that part won't work unattended unless it's wired as a repo secret \u002F `.mcp.json`. Wiring an MCP server for unattended use (dashboard Connect, OAuth refresh, the rotating-token PAT): `references\u002Fmcp.md`.\n\n4. **Add the `aeon.yml` entry yourself.** A new skill on disk has no entry, and `.\u002Faeon skills enable|schedule` **will not create one** — they only flip entries that already exist, and report `no change — already in that state`, which is false. Add it by hand, disabled, before the fallback `heartbeat:` line:\n\n   ```yaml\n     my-skill: { enabled: false, schedule: \"0 12 * * *\" }\n   ```\n\n   **Include the quoted `schedule:` even though it's disabled — the quotes are load-bearing.** Writing a bare `{ enabled: false }` and letting `.\u002Faeon skills schedule` add the key later produces an *unquoted* value the scheduler cannot read, and the skill never fires (Mode 3, check 5). Seeding a quoted node here means every later CLI edit preserves the quotes.\n\n   Match the inline `{ … }` form the other 61 entries use, on one line. `aeon.yml:367` reads per-skill `model:`\u002F`harness:` overrides with a single-line grep, so an entry split across lines takes the global default instead.\n\n   This is the one sanctioned exception to \"never hand-edit the YAML\". Validate after: `node scripts\u002Fvalidate-config.js` — but note it only checks structure, and will not catch an unquoted value.\n\n5. **Regenerate BOTH catalogs, then ship it as a PR.** A new skill trips three CI gates. Run them locally — **nothing blocks a merge on red**, `main` is unprotected and has no rulesets, so an unrun gate just fails after the fact:\n\n   ```bash\n   bash scripts\u002Fcheck-skill-categories.sh   # category is one of the six\n   bin\u002Fgenerate-skills-json                 # catalog\u002Fskills.json\n   bin\u002Fgenerate-packs-json                  # catalog\u002Fpacks.json — NOT optional\n   ```\n\n   `generate-packs-json` is the one everyone forgets: `catalog\u002Fskills.json` is itself a trigger path for `ci-packs-json`, so committing the skills catalog without the pack catalog goes red on a workflow you never touched. Commit both files.\n\n   Full gate list, triggers, and the `ci-tests` \u002F `ci-apps` commands: `references\u002Fci.md`.\n\n6. **Run it once** (`.\u002Faeon skills run \u003Cname>`), show them the output, then schedule it via Mode 2.\n\n### Skill file shape\n\n```yaml\n---\nname: my-skill\ndescription: One line — what it does and what it sends.\nmetadata:\n  title: My Skill\n  mode: read-only\n  category: basics\n  var: \"\"\n  tags:\n    - content\n  requires:\n    - SOME_API_KEY?\n---\n\nToday is ${today}. \u003Cthe prompt — plain instructions, including judgment calls>\n\n## Steps\n1. \u003Cthe procedure - 44 of 82 skills lead with this>\n\n## Network note\n\u003Ccurl \u002F WebFetch \u002F `.\u002Fsecretcurl` \u002F `gh api` — how this skill fetches>\n\n## Log\nReport via `.\u002Fnotify` (use `.\u002Fnotify -f file.md` for anything multi-line).\nSend nothing if there's nothing worth reporting.\nAppend what you did to `memory\u002Flogs\u002F${today}.md` under a `### \u003Cskill-name>` heading.\n```\n\nBodies run 133–757 lines (~306 median) — a skill is a prompt in prose, not a config file. `## Steps` \u002F `## Network note` \u002F `## Constraints` \u002F `## Log` is the house shape.\n\nFour things that bite when authoring — full detail in `references\u002Fskill-anatomy.md`:\n\n- **`requires:` is a least-privilege allowlist — the run exports only the keys named here.** Inline (`requires: [KEY?]`) and block (`- KEY` lines) both parse, top-level or nested under `metadata:`. The catch is the value: only names matching `^[A-Z][A-Z0-9_]{2,}$` (trailing `?` = optional) are injected; a lowercase or malformed entry is silently dropped.\n- **A typo'd `mode:` grants write.** Unknown values fall back to `write`, never to the safer tier. The exact string is `read-only`.\n- **`${today}` \u002F `${var}` are not templated.** Nothing rewrites `SKILL.md`; the workflow puts the date and var in the surrounding prompt and the model resolves them in context. Inventing `${my_thing}` yields a literal `${my_thing}`.\n- **Never put a secret on a command line.** Use `.\u002Fsecretcurl` with a `{ENV_NAME}` placeholder in braces — Claude Code's permission analyzer blocks `$SECRET` expansions at run time.\n\nSchedules do **not** go in `SKILL.md` — they live in `aeon.yml`. 10 upstream skills carry a `schedule:` or `cron:` frontmatter line anyway; **nothing reads it** (`scheduler.yml` parses `aeon.yml` only). Don't copy that pattern, and don't trust one you find — check `aeon.yml`.\n\n---\n\n## Mode 5 — Change what an existing skill does\n\n\"Make the digest shorter\", \"stop covering X\", \"add a source\". More common than authoring a new skill.\n\n**First, check whether it's a config change, not a file edit.** Most skills take a topic, filter, or mode through `var` — read the skill's `var:` line and the comment on its `aeon.yml` entry before touching the body. If `var` covers it, you're done:\n\n```bash\n.\u002Faeon skills set digest --var \"rust\"          # no file edit at all\n```\n\nOtherwise edit `skills\u002F\u003Cname>\u002FSKILL.md`:\n\n1. **Read the whole body first.** These files run long (200–750 lines) and carry judgment rules, exit taxonomies, and scoring rubrics that a targeted edit can silently contradict.\n2. **Don't strip the survival machinery.** Whatever else changes, the skill must keep: the `.\u002Fnotify` path, the silent-on-no-signal exit, the `memory\u002Flogs\u002F${today}.md` append under `### \u003Cskill-name>`, and any already-reported dedup. Edits that \"tighten\" a skill often delete these. The `### \u003Cskill-name>` heading is parsed by the health loop and the dedup rule reads the last 3 days of logs — breaking either makes the skill re-report until it gets muted. Conventions in `references\u002Fskill-anatomy.md`.\n3. **Update frontmatter if the behaviour moved.** A new data source that needs a key → add it to `requires:`. Now writes files or opens PRs → `mode: write`. Changed `description:`, `name:`, `category:` or `requires:` → regenerate **both** catalogs (`bin\u002Fgenerate-skills-json && bin\u002Fgenerate-packs-json`) and commit both; `skills.json` carries those fields and feeds `packs.json`. See `references\u002Fci.md`.\n4. **Warn if it's an upstream skill.** Anything shipped in `aeonfun\u002Faeon` will conflict on the next `git merge upstream\u002Fmain`. Fine, but say so — the two-repo convention is to keep local edits deliberate and few.\n5. **Run it once** (`.\u002Faeon skills run \u003Cname>`) and read the output before leaving.\n\nAutomated alternative: the in-repo `autoresearch` skill evolves a target skill by generating four scored variations and shipping the winner as a PR. Reach for it when the ask is \"make this better\" rather than a specific change.\n\n---\n\n## Mode 6 — \"What should I turn on?\"\n\nThe real first question during onboarding. **Don't dump the catalog.** Ask two or three questions about what they actually want handled while they're away, then propose **three** skills with a one-line reason each.\n\nThree at a time, not twelve. Every enabled skill is a recurring notification, and the fastest way to kill an instance is to make it noisy on day one. `heartbeat` is already on and stays silent unless something needs attention.\n\n```bash\n.\u002Faeon skills ls                 # all skills — SKILL \u002F ON \u002F SCHEDULE \u002F PACK \u002F DESC\n.\u002Faeon skills ls --enabled       # only what actually runs\n.\u002Faeon skills ls --pack crypto   # one pack\n.\u002Faeon skills \u003Cname>             # one skill's detail\n.\u002Faeon packs ls                  # the six first-party packs\n```\n\n`ls` footers with `82 skills · 1 enabled` — read it to them before proposing anything. First run installs the CLI runtime (tsx + yaml, ~12MB); the npm noise is one-time and expected. Grep-only equivalents: `references\u002Flayout.md`.\n\nPacks are a visibility filter, not a runtime switch — revealing one runs nothing. Core (12), Evolution (9) and Basics (18) show by default; Dev (13), Crypto (19) and Productivity (11) are on demand.\n\nReasonable starting sets:\n\n| They care about | Propose |\n|---|---|\n| Their repos | `github-monitor`, `pr-review`, `changelog` |\n| A topic \u002F research | `digest`, `article`, `mention-radar` |\n| Markets | `token-movers`, `defi-overview`, `monitor-polymarket` |\n| Shipping \u002F traction | `heartbeat`, `shiplog`, `bd-radar` |\n\n### Installing more\n\n```bash\nbin\u002Finstall-skill-pack --list             # browse the community registry\nbin\u002Finstall-skill-pack \u003Cowner>\u002F\u003Crepo>     # install a curated pack\nbin\u002Fadd-skill \u003Cowner>\u002F\u003Crepo> --list       # any repo containing SKILL.md files\n```\n\nEverything lands **disabled**, security-scanned, with provenance in `skills.lock`.\n\n**Read a community SKILL.md before enabling it.** Installing a pack means running a stranger's prompt with your secrets injected. The scanner is regex — it can't catch prompt injection. Check that `requires:` matches the stated job, that `capabilities:` is honest, and that nothing instructs the agent to send data somewhere unrelated.\n\n**Confirm explicitly before enabling anything with real-world blast radius:** `distribute-tokens` (sends USDC), `schedule-ads` (spends money), `send-email` and `vuln-scanner` (contact real people), `deploy-prototype` and `feature` (push to other people's repos).\n\n---\n\n## Mode 7 — Strategy and voice\n\nTwo files that ride in the context of **every** run. Neither is required, both are cheap, and they move output quality more than any per-skill tuning.\n\n### `STRATEGY.md` — the north star\n\nImported into `CLAUDE.md`, so it's in every skill's context: goal, priorities, audience, hard constraints. When a choice isn't otherwise determined, this breaks the tie. Keep it **tight** (it costs tokens on every single run) and **specific** (a vague strategy can't break a tie).\n\n```bash\n.\u002Faeon strategy show\n.\u002Faeon strategy set --file STRATEGY.md\n.\u002Faeon strategy build \"\u003Cone-line goal>\"    # dispatches the strategy-builder skill\n```\n\n`build` reads the brief plus the repo README and `memory\u002FMEMORY.md`, then commits a draft. It runs as an Action, so pull once it finishes. No API key needed.\n\n### `soul\u002F` — how it sounds\n\nBy default Aeon has no personality. `soul\u002FSOUL.md` (identity, worldview, opinions) and `soul\u002FSTYLE.md` (voice, vocabulary, anti-patterns) are read on every run, so notifications and content sound like the operator. `soul\u002Fexamples\u002F` holds 10–20 calibration samples.\n\n```bash\n.\u002Faeon soul show\n.\u002Faeon soul build --handle \u003Cx-handle> --name \"\u003CFull Name>\" --links \u003Curl,url>\n```\n\n`XAI_API_KEY` gives the richest read of a real X timeline; without it, `soul-builder` falls back to web search. There's also a gallery of complete example souls at github.com\u002Faeonfun\u002Fsoul.md to start from.\n\n**The quality bar: specific enough to be wrong.** *\"I think most AI safety discourse is galaxy-brained cope\"* is useful. *\"I have nuanced views on AI safety\"* is not. Push for the first kind — a soul that can't offend anyone won't sound like anyone.\n\n---\n\n## Mode 8 — Mine history for skills to automate\n\n\"What am I doing by hand over and over that Aeon could just do?\" Mode 4 turns *this* chat into a skill; Mode 8 mines *past* chats to find which chat is worth turning into one. It reads the operator's local coding-agent transcripts (`~\u002F.claude\u002Fprojects` or `~\u002F.codex\u002Fsessions`), so it only works on their own machine — never inside an Aeon run.\n\n1. **Scan.** Run the miner from the instance repo root:\n\n   ```bash\n   node \"${PLUGIN_ROOT:-$CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Faeon\u002Fscripts\u002Fmine-history.mjs\" --days 45 --top 15\n   ```\n\n   It parses every top-level session in the window (skips subagent sidechains), normalises shell commands to `binary subcommand`, groups session titles, and prints a digest ranked by **distinct sessions × distinct days** — recurrence and cadence, not raw volume. Flags: `--days N` (window, default 120), `--project SUBSTR` (only sessions whose cwd matches — scope to one repo\u002Ftopic), `--top N`, `--min-sessions N`, `--json`. It has no dependencies and reverts to a clean error if there's no history. Deeper reading of the tables and the candidate rubric: `references\u002Fhistory-mining.md`.\n\n2. **Read it as a human would.** The digest is raw signal, not a verdict — the judgment is yours:\n   - **Recurring command workflows** — a `binary subcommand` across many sessions *and* many days is a habit. Universal plumbing (`git status`, `gh auth`, bare `node`\u002F`python3`) is already filtered out, but `gh pr`\u002F`gh api`\u002F`npm run` are substrate too — high everywhere, weak as a skill idea. Look for the *distinctive* recurring call: a named script, a specific CLI (`x-cli`, `langfuse`, `raindrop`), a tight `gh api` pattern.\n   - **Recurring task themes** — grouped session titles are the strongest signal. A title you've hit across many days at a rough cadence (\"check X\", \"review Y\", \"digest Z\") is almost always the real automation candidate.\n   - **Tooling \u002F projects** — which MCP servers and repos the work lives in; tells you what a skill would need wired and where to scope `--project`.\n\n3. **Filter to genuine candidates.** A row is worth proposing only if it's all of:\n   - **Recurring** — spans several sessions across several days, not one busy afternoon.\n   - **Fetch\u002Fcompute\u002Freport-shaped** — pulls or checks something and reports. Interactive, decision-heavy, or one-off migration work does *not* automate.\n   - **Unattended-safe** — no dependence on local files, logged-in desktop apps, or a human answering mid-task (Mode 4 step 2\u002F3 covers hardening).\n   - **Not already a skill.** Dedup against the instance: `.\u002Faeon skills ls`. Much recurring `gh pr` work is already `pr-review`\u002F`pr-check`; a research cadence is already `digest`\u002F`mention-radar`. If an existing skill covers it, the move is Mode 2 (reschedule) or Mode 5 (edit its `var`), **not** a new skill.\n\n4. **Propose three, with evidence.** Don't dump the digest. Name **three** candidates, each with its recurrence count as proof (\"you did X across N sessions over D days\"), a one-line skill sketch (what it fetches, what it sends), a suggested `mode:` (`read-only` if it only fetches and reports) and a suggested `schedule:` inferred from the observed cadence (seen ~daily → daily; ~weekly → weekly). Ask which to build.\n\n5. **Hand off to Mode 4** to author the chosen one — the same skill-file shape, unattended-hardening, quoted-`schedule:` entry, and dual-catalog CI. Mode 8 finds the work; Mode 4 ships it.\n\n**Privacy:** the transcripts are read locally and only the aggregate digest is surfaced. Don't paste raw prompt bodies or anything sensitive from a session into a channel or a committed file; the counts and titles are enough to decide.\n\n---\n\n## Providers and harnesses\n\nTwo independent axes. Don't confuse them: the **gateway** decides which model answers; the **harness** decides which CLI runs the skill.\n\n### Gateway — what powers Claude Code\n\nSet a secret and it's live. `aeon.yml` ships `gateway: { provider: auto }`, which resolves at run time from whichever keys exist, in this priority order:\n\n```\nclaude → anthropic → openrouter → bankr → usepod → venice → surplus → grok → glm\n```\n\n`direct` is **not** a hop in that chain — it's the placeholder when *none* of the nine secrets is set. It requires nothing and configures nothing, so the run proceeds on whatever `ANTHROPIC_*` env happens to exist and otherwise fails at the first model call. \"Resolved to `direct`\" in a log means **no key was found**, not that a fallback worked.\n\n| Provider | Secret | Notes |\n|---|---|---|\n| Claude subscription | `CLAUDE_CODE_OAUTH_TOKEN` | One-click OAuth, included in Pro\u002FMax |\n| Anthropic API | `ANTHROPIC_API_KEY` | Pay-as-you-go |\n| OpenRouter | `OPENROUTER_API_KEY` | `sk-or-…` · Anthropic-native passthrough, lowest-risk |\n| Bankr | `BANKR_LLM_KEY` | `bk_…` · discounted Opus |\n| UsePod | `USEPOD_TOKEN` | No prefix — pass `--provider usepod`. Token sits in the base URL, keep it secret |\n| Venice | `VENICE_API_KEY` | No prefix — pass `--provider venice`. Privacy-first, bridged via a sidecar |\n| Surplus | `SURPLUS_API_KEY` | `inf_…` · settles USDC on Base — fund the wallet + `approve()` once first |\n| Grok (xAI) | `XAI_API_KEY` | `xai-…` · passthrough to `api.x.ai` |\n| GLM (Z.AI) | `GLM_API_KEY` | No prefix — pass `--provider glm`. Alias `ZAI_API_KEY`. Passthrough to `api.z.ai\u002Fapi\u002Fanthropic` |\n\nIt runs as a **cascade**, not a single choice: the highest-priority key goes first, and on *any* failure (no credits, rate limit, outage, dud response) the run falls over to the next provider whose key is set. It only errors if every one fails. The log prints `Routing attempt via '\u003Cprovider>'` per hop.\n\n- **Reorder:** repo variable `GATEWAY_ORDER` (space-separated names).\n- **Pin one** (disables failover): `.\u002Faeon config set gateway \u003Cname>`.\n- **Any Anthropic-compatible endpoint:** `ANTHROPIC_API_KEY` plus the repo variable `ANTHROPIC_BASE_URL` — e.g. `https:\u002F\u002Fapi.deepseek.com\u002Fanthropic`.\n\n### Harness — which CLI runs the skill\n\n`claude` (default) or `grok`. The Grok harness runs the `grok` CLI instead of Claude Code and **bypasses the gateway entirely** — it has its own auth.\n\n- **Set it:** `.\u002Faeon config set harness grok` globally, or `harness: \"grok\"` on a single skill's `aeon.yml` entry — **quoted, on the entry's one inline line**. Per-skill `model:` and `harness:` are read by a single-line grep that requires double quotes (`aeon.yml:367`, `:380`), so an unquoted or line-split override is silently ignored and the skill keeps running the global default — no error, and the log's `model=` line looks normal. After setting either by CLI, re-read the entry and add the quotes if they're missing.\n- **Auth:** `XAI_API_KEY`, or an X account (SuperGrok \u002F X Premium+) via the dashboard's **Connect X account**, which stores `GROK_CREDENTIALS`. There is no CLI flag for the X OAuth flow — send them to `.\u002Faeon` (the dashboard) for that one.\n- **Models:** `grok-4.5` (default, reasoning) or `grok-composer-2.5-fast` (cheap).\n- **No free tier.**\n\nTell them up front:\n- Grok runs report **0 tokens** — its JSON carries no token counts, so cost tracking reads blank. Not a bug.\n- The X OAuth session expires. If unattended runs start failing on auth, reconnect.\n- `mode: read-only` still applies (maps to `--sandbox read-only`), and MCP works.\n\nPer-skill grok knobs, in `SKILL.md` frontmatter (ignored on the Claude harness): `max_turns` (default 60), `best_of_n`, `verify`, and `effort` (`low|medium|high|xhigh|max` — reasoning models only; `grok-composer-2.5-fast` rejects it).\n","# Aeon\n\nAeon is an agent that runs on the user's own GitHub repo via Actions. A skill is a Markdown file (`skills\u002F\u003Cname>\u002FSKILL.md`); `aeon.yml` says which ones run and when.\n\nPick the mode they're asking for:\n\n| | |\n|---|---|\n| **1 · Start** | No instance yet, or set one up from scratch |\n| **2 · Reschedule** | Change times, cadence, or what a skill focuses on |\n| **3 · Unblock** | \"It didn't run\" \u002F \"nothing happened\" |\n| **4 · Chat → skill** | Turn what we just did into a scheduled skill |\n| **5 · Edit a skill** | Change what an existing skill does |\n| **6 · What to turn on** | Pick skills, browse packs, install more |\n| **7 · Strategy & voice** | `STRATEGY.md` and `soul\u002F` — the north star and the tone |\n| **8 · Mine history → skill** | \"What of my repeated work could Aeon do for me?\" — surface it from past coding-agent chats |\n\n## Preflight (every mode)\n\n1. Find the repo: current dir → `gh repo set-default` → ask. Clone it if it isn't local.\n2. **Confirm `gh` points at THEIR instance, before any command that writes.**\n\n   ```bash\n   gh repo view --json nameWithOwner -q .nameWithOwner\n   ```\n\n   If that prints `aeonfun\u002Faeon` and they aren't working on upstream itself, stop and run `gh repo set-default \u003Cowner>\u002F\u003Crepo>`. `gh` prefers an `upstream` remote over `origin` when no default is pinned, and every Aeon write (`auth`, `secrets set`, `skills run`, config pushes) is a `gh -R \u003Cresolved>` call — so it will cheerfully put their API keys on the upstream repo and dispatch runs there. It looks like success: no error, a real run id, and the skill just never fires on their instance.\n3. `gh auth status` — everything routes through `gh`. If it fails, tell them to run `gh auth login` and stop.\n4. Use the `.\u002Faeon` CLI for all config writes. It preserves comments in `aeon.yml` and validates. Never hand-edit the YAML — with one exception: the CLI cannot *create* an entry for a brand-new skill (see Mode 4 step 4).\n\n**Don't trust \"disabled\" for a skill you just created.** The read path lists skills from disk and defaults a missing `aeon.yml` entry to `enabled: false`, so \"not configured\" and \"disabled\" look identical. One command tells them apart:\n\n```bash\ncomm -23 \u003C(ls skills\u002F*\u002FSKILL.md | cut -d\u002F -f2 | sort) \\\n         \u003C(grep -oE '^  [a-z0-9-]+:' aeon.yml | tr -d ' :' | sort)\n```\n\nAnything it prints is on disk but unconfigured. **Orientation — what's installed, what's on, and where everything lives: `references\u002Flayout.md`.**\n\n**Setting any key or token:** read `references\u002Fsecrets.md` — it has every secret and repo variable with the exact page to get it from. Always set secrets with `.\u002Faeon secrets set NAME --stdin`, never as a command argument.\n\n---\n\n## Mode 1 — Start on Aeon\n\nGoal: one real notification in their phone, fast. Do not configure a schedule first.\n\n1. **Get a repo. Ask public or private before you run anything** — it changes the command, and switching later means moving the repo.\n\n   **Public** (recommend this): Actions minutes are free, and upstream skill updates arrive with one command.\n\n   ```bash\n   gh repo fork aeonfun\u002Faeon --clone && cd aeon\n   gh repo set-default \u003Cowner>\u002Faeon        # REQUIRED — see below\n   ```\n\n   **Private**: a fork of a public repo is always public, so a private instance is a mirror, not a fork.\n\n   ```bash\n   gh repo create \u003Cname> --private\n   git clone --bare https:\u002F\u002Fgithub.com\u002Faeonfun\u002Faeon.git\n   git -C aeon.git push --mirror https:\u002F\u002Fgithub.com\u002F\u003Cowner>\u002F\u003Cname>.git\n   rm -rf aeon.git && git clone https:\u002F\u002Fgithub.com\u002F\u003Cowner>\u002F\u003Cname>.git && cd \u003Cname>\n   git remote add upstream https:\u002F\u002Fgithub.com\u002Faeonfun\u002Faeon.git\n   gh repo set-default \u003Cowner>\u002F\u003Cname>      # REQUIRED — see below\n   ```\n\n   Say both costs out loud before they pick private: Actions minutes bill against the account quota (2,000\u002Fmo on Free — scheduled skills burn it), and updates come from `git fetch upstream && git merge upstream\u002Fmain` instead of `gh repo sync`.\n\n   **Pin the default repo before any other command — both paths.** Both end up with an `upstream` remote (`gh repo fork --clone` adds one for you), and with no default pinned **`gh` prefers `upstream` over `origin`**. Everything in Aeon routes through `gh -R $(gh repo view …)`, so an unpinned checkout silently writes secrets to and dispatches runs against `aeonfun\u002Faeon` instead of their instance — with no error, because the commands genuinely succeed on the wrong repo. Verify:\n\n   ```bash\n   gh repo view --json nameWithOwner -q .nameWithOwner   # must print THEIR repo\n   ```\n\n   Everything after this step is identical either way.\n2. **Auth a model.** At least one is required. Fastest is `.\u002Faeon auth --oauth` (Claude Pro\u002FMax, opens a browser), or `.\u002Faeon auth --key \u003Ckey>`, which detects the provider **from the key prefix** — `sk-ant-oat` (OAuth), `sk-or-` (OpenRouter), `bk_` (Bankr), `inf_` (Surplus), `xai-` (Grok); anything else lands in `ANTHROPIC_API_KEY`.\n\n   **UsePod and Venice keys have no prefix** and are undetectable, so a bare `--key` files them as a plain Anthropic key and the run fails later with a confusing auth error. They must be named:\n\n   ```bash\n   .\u002Faeon auth --key \u003Ctoken> --provider usepod    # same for venice\n   ```\n\n   `--dry-run` prints the resolved `method=… → secret …` without calling `gh` or `claude` — worth running whenever the provider is in doubt.\n\n   **Don't assume they have a Claude subscription:** nine providers work, including OpenRouter, Grok, GLM, and crypto-settled gateways. See \"Providers and harnesses\".\n3. **Wire one channel.** Telegram is the fastest: create a bot with @BotFather, then `.\u002Faeon secrets set TELEGRAM_BOT_TOKEN --stdin` and `TELEGRAM_CHAT_ID`. Skip Discord\u002FSlack\u002Femail for now — one channel is enough to prove it works.\n4. **Run one skill now.** Pick it with Mode 6 — ask what they want handled, propose one — then `.\u002Faeon skills run \u003Cname>`. Wait for it, then `.\u002Faeon runs logs \u003Cid>`. They should get a Telegram message.\n5. **Only then, schedule it.** `.\u002Faeon skills enable \u003Cname>` and set a time (see Mode 2).\n\nGood first skills: `digest` (topic briefing), `github-monitor` (their repos), `heartbeat` (already on by default, reports only when something needs attention).\n\n---\n\n## Mode 2 — Reschedule \u002F change the routine\n\nShow them their day as a **timeline in their own timezone**, not a config file:\n\n```\n07:00  digest           \"solana\"\n09:00  pr-review        your repos\n18:00  heartbeat        health check\n```\n\nBuild it from `.\u002Faeon skills ls --enabled --json`. (`--enabled` matters: plain `ls` prints a `SCHEDULE` column for *disabled* skills too — that's their `aeon.yml` entry, not proof anything fires.) No CLI, or want the raw file? `references\u002Flayout.md` has grep-only equivalents. Then take plain-language edits and apply them:\n\n| They say | You do |\n|---|---|\n| \"move the digest to 7am\" | `.\u002Faeon skills schedule digest \"0 6 * * *\"` |\n| \"weekdays only\" | `... \"0 6 * * 1-5\"` |\n| \"too noisy, twice a week\" | `... \"0 6 * * 1,4\"` |\n| \"stop the crypto one\" | `.\u002Faeon skills disable token-movers` |\n| \"make it about rust instead\" | `.\u002Faeon skills set digest --var rust` |\n\nRules:\n- **All cron in `aeon.yml` is UTC.** Convert from their timezone, and say so: \"7am Paris = `0 6 * * *` UTC (5am in summer — want it pinned to local time?\" There is no local-time option, so if DST matters, tell them which half of the year is off by an hour.\n- Confirm back the **next 3 fire times in their timezone** after any change.\n- `--dry-run` first on anything ambiguous, show the diff, then apply.\n- Changes need a push to take effect. The CLI does it; confirm it landed.\n- **Then check the value came out quoted** — one grep, every time:\n\n  ```bash\n  grep '^  \u003Cskill>:' aeon.yml\n  ```\n\n  The scheduler only reads `schedule: \"…\"` **with double quotes**. The CLI writes a *new* key unquoted, so an entry that had no `schedule:` yet comes back as `schedule: 0 12 * * *` and the skill is skipped forever. Details below.\n\nSkills with `schedule: workflow_dispatch` are on-demand only — they never fire on cron. `reactive` ones fire on conditions, not time.\n\n---\n\n## Mode 3 — Unblock\n\n\"It didn't run.\" Check in this order and stop at the first hit:\n\n1. **Is it on?** `.\u002Faeon skills ls --enabled` — is it listed?\n2. **Duplicate key?** `node scripts\u002Fvalidate-config.js`. A repeated skill name in `aeon.yml` silently shadows the first one. Common after hand-edits.\n3. **Is it even cron?** `workflow_dispatch` and `reactive` never fire on a schedule.\n4. **Are Actions disabled?** `gh api repos\u002F{owner}\u002F{repo}\u002Factions\u002Fpermissions`. GitHub auto-disables scheduled workflows after 60 days of repo inactivity — this silently kills forks and nothing in Aeon surfaces it. Re-enable in repo Settings.\n5. **Is the schedule quoted?** `grep '^  \u003Cskill>:' aeon.yml` — the value must be `schedule: \"0 12 * * *\"`, **with double quotes**.\n\n   ```\n   schedule: \"0 12 * * *\"   ✅ fires\n   schedule: 0 12 * * *     ❌ never fires, no error anywhere\n   ```\n\n   `scheduler.yml` matches schedules with the bash regex `schedule: *\"([^\"]+)\"`. An unquoted value doesn't match, `$SCHED` is empty, and the match loop hits `[ -z \"$SCHED\" ] && continue` — skipped silently, every tick, forever.\n\n   How it gets that way: the CLI edits `aeon.yml` through a YAML document model that preserves an *existing* quoted node but writes a **newly added** key in plain style. So `.\u002Faeon skills schedule \u003Cname> \"0 12 * * *\"` is safe on an entry that already had a quoted `schedule:`, and quietly breaks one that didn't. Same for a first-time `--var`.\n\n   **Nothing else detects this.** The file is valid YAML, `validate-config.js` reports CLEAN, and `.\u002Faeon skills ls --enabled` lists the skill with its schedule — because they all parse YAML properly and only the scheduler uses a regex. Fix by adding the quotes by hand.\n6. **Did it run and fail?** `.\u002Faeon runs ls` then `.\u002Faeon runs logs \u003Cid>`. A failed skill retries after a 30-minute cooldown.\n\nThree more, if the above are clean:\n\n- **It ran against the wrong repo.** The giveaway is a command that reported success with a run id, but `.\u002Faeon runs ls` on their instance shows nothing. `gh` prefers `upstream` over `origin` when no default is pinned, so an unpinned checkout sends every write to `aeonfun\u002Faeon`.\n\n  ```bash\n  gh repo view --json nameWithOwner -q .nameWithOwner   # if this isn't their repo:\n  gh repo set-default \u003Cowner>\u002F\u003Crepo>\n  ```\n\n  Then **clean up what landed upstream** — re-running against the right repo does not undo it. Any key set while mispointed is now a secret on someone else's repo:\n\n  ```bash\n  gh secret list -R aeonfun\u002Faeon      # timestamps matching the misfire = theirs\n  ```\n\n  **Rotate it at the provider first, always** — it sat on a repo whose collaborators can land a workflow that reads it. Then re-set it on their instance with `.\u002Faeon secrets set NAME --stdin`.\n\n  **Don't blind-delete it.** `gh secret list` shows only *last-updated*, so it cannot tell you whether the upstream repo already had that secret and the misfire **overwrote** it. Ask before removing:\n  - Upstream never had it → `gh secret delete \u003CNAME> -R \u003Cupstream>`.\n  - Upstream had its own → deleting breaks *their* scheduled runs. The owner must re-set upstream's own value; the overwrite is not reversible from here.\n\n  If the delete 403s, they never had write access — nothing was ever written, and the earlier command failed while only *looking* fine.\n- **Missing secret.** Skills declare keys in `requires:`. Check them against `.\u002Faeon secrets ls --set`. A missing optional key (`KEY?`) means it degrades quietly, not that it breaks.\n- **\"No MCP tools available.\"** On the Claude harness a single unresolved `${VAR}` in `.mcp.json` disables **every** MCP server for that run, not just the broken one (`::warning::.mcp.json references secret(s) not set:` … `Skipping MCP this run.`). Grok degrades per-server instead. If an OAuth server broke a run *after* working, suspect a rotated refresh token that couldn't be saved — `references\u002Fmcp.md`.\n- **It ran but sent nothing.** That's usually correct. Aeon's convention is silence on no signal — a clean run sends nothing rather than an empty report.\n\nNote: GitHub only delivers ~10% of `*\u002F5` cron ticks, so the scheduler catches up missed slots for up to 12 hours. A skill firing 40 minutes late is normal.\n\n---\n\n## Mode 4 — Turn this chat into a skill\n\nThey just did something in this chat and want it to happen on a schedule.\n\n1. **Write the skill file.** `skills\u002F\u003Cname>\u002FSKILL.md` — frontmatter, then the prompt. Derive it from what actually happened in the session:\n   - the prompt body = what they asked for, plus the steps that worked\n   - `mode:` = `read-only` unless it needs to commit or open PRs\n   - `requires:` = any API key the work hit (`KEY?` if it can degrade without it)\n   - `category:` = one of `core evolution basics dev crypto productivity`\n   - if they liked the output, paste a trimmed sample into the body as the format spec\n\n2. **Fix the three things that break unattended runs:**\n   - **Nobody's there.** Any point where you asked them a question has to become a default or a rule.\n   - **Stay silent on nothing.** Add an explicit \"if there's nothing worth reporting, log and exit without notifying.\" Otherwise it gets muted in a week.\n   - **Don't repeat yesterday.** Add \"check the last 3 days of `memory\u002Flogs\u002F` and skip anything already reported.\"\n\n3. **Check it can actually run there.** No local filesystem, no logged-in tools. If the session read their home directory or used a local MCP server, say so plainly — that part won't work unattended unless it's wired as a repo secret \u002F `.mcp.json`. Wiring an MCP server for unattended use (dashboard Connect, OAuth refresh, the rotating-token PAT): `references\u002Fmcp.md`.\n\n4. **Add the `aeon.yml` entry yourself.** A new skill on disk has no entry, and `.\u002Faeon skills enable|schedule` **will not create one** — they only flip entries that already exist, and report `no change — already in that state`, which is false. Add it by hand, disabled, before the fallback `heartbeat:` line:\n\n   ```yaml\n     my-skill: { enabled: false, schedule: \"0 12 * * *\" }\n   ```\n\n   **Include the quoted `schedule:` even though it's disabled — the quotes are load-bearing.** Writing a bare `{ enabled: false }` and letting `.\u002Faeon skills schedule` add the key later produces an *unquoted* value the scheduler cannot read, and the skill never fires (Mode 3, check 5). Seeding a quoted node here means every later CLI edit preserves the quotes.\n\n   Match the inline `{ … }` form the other 61 entries use, on one line. `aeon.yml:367` reads per-skill `model:`\u002F`harness:` overrides with a single-line grep, so an entry split across lines takes the global default instead.\n\n   This is the one sanctioned exception to \"never hand-edit the YAML\". Validate after: `node scripts\u002Fvalidate-config.js` — but note it only checks structure, and will not catch an unquoted value.\n\n5. **Regenerate BOTH catalogs, then ship it as a PR.** A new skill trips three CI gates. Run them locally — **nothing blocks a merge on red**, `main` is unprotected and has no rulesets, so an unrun gate just fails after the fact:\n\n   ```bash\n   bash scripts\u002Fcheck-skill-categories.sh   # category is one of the six\n   bin\u002Fgenerate-skills-json                 # catalog\u002Fskills.json\n   bin\u002Fgenerate-packs-json                  # catalog\u002Fpacks.json — NOT optional\n   ```\n\n   `generate-packs-json` is the one everyone forgets: `catalog\u002Fskills.json` is itself a trigger path for `ci-packs-json`, so committing the skills catalog without the pack catalog goes red on a workflow you never touched. Commit both files.\n\n   Full gate list, triggers, and the `ci-tests` \u002F `ci-apps` commands: `references\u002Fci.md`.\n\n6. **Run it once** (`.\u002Faeon skills run \u003Cname>`), show them the output, then schedule it via Mode 2.\n\n### Skill file shape\n\n```yaml\n---\nname: my-skill\ndescription: One line — what it does and what it sends.\nmetadata:\n  title: My Skill\n  mode: read-only\n  category: basics\n  var: \"\"\n  tags:\n    - content\n  requires:\n    - SOME_API_KEY?\n---\n\nToday is ${today}. \u003Cthe prompt — plain instructions, including judgment calls>\n\n## Steps\n1. \u003Cthe procedure - 44 of 82 skills lead with this>\n\n## Network note\n\u003Ccurl \u002F WebFetch \u002F `.\u002Fsecretcurl` \u002F `gh api` — how this skill fetches>\n\n## Log\nReport via `.\u002Fnotify` (use `.\u002Fnotify -f file.md` for anything multi-line).\nSend nothing if there's nothing worth reporting.\nAppend what you did to `memory\u002Flogs\u002F${today}.md` under a `### \u003Cskill-name>` heading.\n```\n\nBodies run 133–757 lines (~306 median) — a skill is a prompt in prose, not a config file. `## Steps` \u002F `## Network note` \u002F `## Constraints` \u002F `## Log` is the house shape.\n\nFour things that bite when authoring — full detail in `references\u002Fskill-anatomy.md`:\n\n- **`requires:` is a least-privilege allowlist — the run exports only the keys named here.** Inline (`requires: [KEY?]`) and block (`- KEY` lines) both parse, top-level or nested under `metadata:`. The catch is the value: only names matching `^[A-Z][A-Z0-9_]{2,}$` (trailing `?` = optional) are injected; a lowercase or malformed entry is silently dropped.\n- **A typo'd `mode:` grants write.** Unknown values fall back to `write`, never to the safer tier. The exact string is `read-only`.\n- **`${today}` \u002F `${var}` are not templated.** Nothing rewrites `SKILL.md`; the workflow puts the date and var in the surrounding prompt and the model resolves them in context. Inventing `${my_thing}` yields a literal `${my_thing}`.\n- **Never put a secret on a command line.** Use `.\u002Fsecretcurl` with a `{ENV_NAME}` placeholder in braces — Claude Code's permission analyzer blocks `$SECRET` expansions at run time.\n\nSchedules do **not** go in `SKILL.md` — they live in `aeon.yml`. 10 upstream skills carry a `schedule:` or `cron:` frontmatter line anyway; **nothing reads it** (`scheduler.yml` parses `aeon.yml` only). Don't copy that pattern, and don't trust one you find — check `aeon.yml`.\n\n---\n\n## Mode 5 — Change what an existing skill does\n\n\"Make the digest shorter\", \"stop covering X\", \"add a source\". More common than authoring a new skill.\n\n**First, check whether it's a config change, not a file edit.** Most skills take a topic, filter, or mode through `var` — read the skill's `var:` line and the comment on its `aeon.yml` entry before touching the body. If `var` covers it, you're done:\n\n```bash\n.\u002Faeon skills set digest --var \"rust\"          # no file edit at all\n```\n\nOtherwise edit `skills\u002F\u003Cname>\u002FSKILL.md`:\n\n1. **Read the whole body first.** These files run long (200–750 lines) and carry judgment rules, exit taxonomies, and scoring rubrics that a targeted edit can silently contradict.\n2. **Don't strip the survival machinery.** Whatever else changes, the skill must keep: the `.\u002Fnotify` path, the silent-on-no-signal exit, the `memory\u002Flogs\u002F${today}.md` append under `### \u003Cskill-name>`, and any already-reported dedup. Edits that \"tighten\" a skill often delete these. The `### \u003Cskill-name>` heading is parsed by the health loop and the dedup rule reads the last 3 days of logs — breaking either makes the skill re-report until it gets muted. Conventions in `references\u002Fskill-anatomy.md`.\n3. **Update frontmatter if the behaviour moved.** A new data source that needs a key → add it to `requires:`. Now writes files or opens PRs → `mode: write`. Changed `description:`, `name:`, `category:` or `requires:` → regenerate **both** catalogs (`bin\u002Fgenerate-skills-json && bin\u002Fgenerate-packs-json`) and commit both; `skills.json` carries those fields and feeds `packs.json`. See `references\u002Fci.md`.\n4. **Warn if it's an upstream skill.** Anything shipped in `aeonfun\u002Faeon` will conflict on the next `git merge upstream\u002Fmain`. Fine, but say so — the two-repo convention is to keep local edits deliberate and few.\n5. **Run it once** (`.\u002Faeon skills run \u003Cname>`) and read the output before leaving.\n\nAutomated alternative: the in-repo `autoresearch` skill evolves a target skill by generating four scored variations and shipping the winner as a PR. Reach for it when the ask is \"make this better\" rather than a specific change.\n\n---\n\n## Mode 6 — \"What should I turn on?\"\n\nThe real first question during onboarding. **Don't dump the catalog.** Ask two or three questions about what they actually want handled while they're away, then propose **three** skills with a one-line reason each.\n\nThree at a time, not twelve. Every enabled skill is a recurring notification, and the fastest way to kill an instance is to make it noisy on day one. `heartbeat` is already on and stays silent unless something needs attention.\n\n```bash\n.\u002Faeon skills ls                 # all skills — SKILL \u002F ON \u002F SCHEDULE \u002F PACK \u002F DESC\n.\u002Faeon skills ls --enabled       # only what actually runs\n.\u002Faeon skills ls --pack crypto   # one pack\n.\u002Faeon skills \u003Cname>             # one skill's detail\n.\u002Faeon packs ls                  # the six first-party packs\n```\n\n`ls` footers with `82 skills · 1 enabled` — read it to them before proposing anything. First run installs the CLI runtime (tsx + yaml, ~12MB); the npm noise is one-time and expected. Grep-only equivalents: `references\u002Flayout.md`.\n\nPacks are a visibility filter, not a runtime switch — revealing one runs nothing. Core (12), Evolution (9) and Basics (18) show by default; Dev (13), Crypto (19) and Productivity (11) are on demand.\n\nReasonable starting sets:\n\n| They care about | Propose |\n|---|---|\n| Their repos | `github-monitor`, `pr-review`, `changelog` |\n| A topic \u002F research | `digest`, `article`, `mention-radar` |\n| Markets | `token-movers`, `defi-overview`, `monitor-polymarket` |\n| Shipping \u002F traction | `heartbeat`, `shiplog`, `bd-radar` |\n\n### Installing more\n\n```bash\nbin\u002Finstall-skill-pack --list             # browse the community registry\nbin\u002Finstall-skill-pack \u003Cowner>\u002F\u003Crepo>     # install a curated pack\nbin\u002Fadd-skill \u003Cowner>\u002F\u003Crepo> --list       # any repo containing SKILL.md files\n```\n\nEverything lands **disabled**, security-scanned, with provenance in `skills.lock`.\n\n**Read a community SKILL.md before enabling it.** Installing a pack means running a stranger's prompt with your secrets injected. The scanner is regex — it can't catch prompt injection. Check that `requires:` matches the stated job, that `capabilities:` is honest, and that nothing instructs the agent to send data somewhere unrelated.\n\n**Confirm explicitly before enabling anything with real-world blast radius:** `distribute-tokens` (sends USDC), `schedule-ads` (spends money), `send-email` and `vuln-scanner` (contact real people), `deploy-prototype` and `feature` (push to other people's repos).\n\n---\n\n## Mode 7 — Strategy and voice\n\nTwo files that ride in the context of **every** run. Neither is required, both are cheap, and they move output quality more than any per-skill tuning.\n\n### `STRATEGY.md` — the north star\n\nImported into `CLAUDE.md`, so it's in every skill's context: goal, priorities, audience, hard constraints. When a choice isn't otherwise determined, this breaks the tie. Keep it **tight** (it costs tokens on every single run) and **specific** (a vague strategy can't break a tie).\n\n```bash\n.\u002Faeon strategy show\n.\u002Faeon strategy set --file STRATEGY.md\n.\u002Faeon strategy build \"\u003Cone-line goal>\"    # dispatches the strategy-builder skill\n```\n\n`build` reads the brief plus the repo README and `memory\u002FMEMORY.md`, then commits a draft. It runs as an Action, so pull once it finishes. No API key needed.\n\n### `soul\u002F` — how it sounds\n\nBy default Aeon has no personality. `soul\u002FSOUL.md` (identity, worldview, opinions) and `soul\u002FSTYLE.md` (voice, vocabulary, anti-patterns) are read on every run, so notifications and content sound like the operator. `soul\u002Fexamples\u002F` holds 10–20 calibration samples.\n\n```bash\n.\u002Faeon soul show\n.\u002Faeon soul build --handle \u003Cx-handle> --name \"\u003CFull Name>\" --links \u003Curl,url>\n```\n\n`XAI_API_KEY` gives the richest read of a real X timeline; without it, `soul-builder` falls back to web search. There's also a gallery of complete example souls at github.com\u002Faeonfun\u002Fsoul.md to start from.\n\n**The quality bar: specific enough to be wrong.** *\"I think most AI safety discourse is galaxy-brained cope\"* is useful. *\"I have nuanced views on AI safety\"* is not. Push for the first kind — a soul that can't offend anyone won't sound like anyone.\n\n---\n\n## Mode 8 — Mine history for skills to automate\n\n\"What am I doing by hand over and over that Aeon could just do?\" Mode 4 turns *this* chat into a skill; Mode 8 mines *past* chats to find which chat is worth turning into one. It reads the operator's local coding-agent transcripts (`~\u002F.claude\u002Fprojects` or `~\u002F.codex\u002Fsessions`), so it only works on their own machine — never inside an Aeon run.\n\n1. **Scan.** Run the miner from the instance repo root:\n\n   ```bash\n   node \"${PLUGIN_ROOT:-$CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Faeon\u002Fscripts\u002Fmine-history.mjs\" --days 45 --top 15\n   ```\n\n   It parses every top-level session in the window (skips subagent sidechains), normalises shell commands to `binary subcommand`, groups session titles, and prints a digest ranked by **distinct sessions × distinct days** — recurrence and cadence, not raw volume. Flags: `--days N` (window, default 120), `--project SUBSTR` (only sessions whose cwd matches — scope to one repo\u002Ftopic), `--top N`, `--min-sessions N`, `--json`. It has no dependencies and reverts to a clean error if there's no history. Deeper reading of the tables and the candidate rubric: `references\u002Fhistory-mining.md`.\n\n2. **Read it as a human would.** The digest is raw signal, not a verdict — the judgment is yours:\n   - **Recurring command workflows** — a `binary subcommand` across many sessions *and* many days is a habit. Universal plumbing (`git status`, `gh auth`, bare `node`\u002F`python3`) is already filtered out, but `gh pr`\u002F`gh api`\u002F`npm run` are substrate too — high everywhere, weak as a skill idea. Look for the *distinctive* recurring call: a named script, a specific CLI (`x-cli`, `langfuse`, `raindrop`), a tight `gh api` pattern.\n   - **Recurring task themes** — grouped session titles are the strongest signal. A title you've hit across many days at a rough cadence (\"check X\", \"review Y\", \"digest Z\") is almost always the real automation candidate.\n   - **Tooling \u002F projects** — which MCP servers and repos the work lives in; tells you what a skill would need wired and where to scope `--project`.\n\n3. **Filter to genuine candidates.** A row is worth proposing only if it's all of:\n   - **Recurring** — spans several sessions across several days, not one busy afternoon.\n   - **Fetch\u002Fcompute\u002Freport-shaped** — pulls or checks something and reports. Interactive, decision-heavy, or one-off migration work does *not* automate.\n   - **Unattended-safe** — no dependence on local files, logged-in desktop apps, or a human answering mid-task (Mode 4 step 2\u002F3 covers hardening).\n   - **Not already a skill.** Dedup against the instance: `.\u002Faeon skills ls`. Much recurring `gh pr` work is already `pr-review`\u002F`pr-check`; a research cadence is already `digest`\u002F`mention-radar`. If an existing skill covers it, the move is Mode 2 (reschedule) or Mode 5 (edit its `var`), **not** a new skill.\n\n4. **Propose three, with evidence.** Don't dump the digest. Name **three** candidates, each with its recurrence count as proof (\"you did X across N sessions over D days\"), a one-line skill sketch (what it fetches, what it sends), a suggested `mode:` (`read-only` if it only fetches and reports) and a suggested `schedule:` inferred from the observed cadence (seen ~daily → daily; ~weekly → weekly). Ask which to build.\n\n5. **Hand off to Mode 4** to author the chosen one — the same skill-file shape, unattended-hardening, quoted-`schedule:` entry, and dual-catalog CI. Mode 8 finds the work; Mode 4 ships it.\n\n**Privacy:** the transcripts are read locally and only the aggregate digest is surfaced. Don't paste raw prompt bodies or anything sensitive from a session into a channel or a committed file; the counts and titles are enough to decide.\n\n---\n\n## Providers and harnesses\n\nTwo independent axes. Don't confuse them: the **gateway** decides which model answers; the **harness** decides which CLI runs the skill.\n\n### Gateway — what powers Claude Code\n\nSet a secret and it's live. `aeon.yml` ships `gateway: { provider: auto }`, which resolves at run time from whichever keys exist, in this priority order:\n\n```\nclaude → anthropic → openrouter → bankr → usepod → venice → surplus → grok → glm\n```\n\n`direct` is **not** a hop in that chain — it's the placeholder when *none* of the nine secrets is set. It requires nothing and configures nothing, so the run proceeds on whatever `ANTHROPIC_*` env happens to exist and otherwise fails at the first model call. \"Resolved to `direct`\" in a log means **no key was found**, not that a fallback worked.\n\n| Provider | Secret | Notes |\n|---|---|---|\n| Claude subscription | `CLAUDE_CODE_OAUTH_TOKEN` | One-click OAuth, included in Pro\u002FMax |\n| Anthropic API | `ANTHROPIC_API_KEY` | Pay-as-you-go |\n| OpenRouter | `OPENROUTER_API_KEY` | `sk-or-…` · Anthropic-native passthrough, lowest-risk |\n| Bankr | `BANKR_LLM_KEY` | `bk_…` · discounted Opus |\n| UsePod | `USEPOD_TOKEN` | No prefix — pass `--provider usepod`. Token sits in the base URL, keep it secret |\n| Venice | `VENICE_API_KEY` | No prefix — pass `--provider venice`. Privacy-first, bridged via a sidecar |\n| Surplus | `SURPLUS_API_KEY` | `inf_…` · settles USDC on Base — fund the wallet + `approve()` once first |\n| Grok (xAI) | `XAI_API_KEY` | `xai-…` · passthrough to `api.x.ai` |\n| GLM (Z.AI) | `GLM_API_KEY` | No prefix — pass `--provider glm`. Alias `ZAI_API_KEY`. Passthrough to `api.z.ai\u002Fapi\u002Fanthropic` |\n\nIt runs as a **cascade**, not a single choice: the highest-priority key goes first, and on *any* failure (no credits, rate limit, outage, dud response) the run falls over to the next provider whose key is set. It only errors if every one fails. The log prints `Routing attempt via '\u003Cprovider>'` per hop.\n\n- **Reorder:** repo variable `GATEWAY_ORDER` (space-separated names).\n- **Pin one** (disables failover): `.\u002Faeon config set gateway \u003Cname>`.\n- **Any Anthropic-compatible endpoint:** `ANTHROPIC_API_KEY` plus the repo variable `ANTHROPIC_BASE_URL` — e.g. `https:\u002F\u002Fapi.deepseek.com\u002Fanthropic`.\n\n### Harness — which CLI runs the skill\n\n`claude` (default) or `grok`. The Grok harness runs the `grok` CLI instead of Claude Code and **bypasses the gateway entirely** — it has its own auth.\n\n- **Set it:** `.\u002Faeon config set harness grok` globally, or `harness: \"grok\"` on a single skill's `aeon.yml` entry — **quoted, on the entry's one inline line**. Per-skill `model:` and `harness:` are read by a single-line grep that requires double quotes (`aeon.yml:367`, `:380`), so an unquoted or line-split override is silently ignored and the skill keeps running the global default — no error, and the log's `model=` line looks normal. After setting either by CLI, re-read the entry and add the quotes if they're missing.\n- **Auth:** `XAI_API_KEY`, or an X account (SuperGrok \u002F X Premium+) via the dashboard's **Connect X account**, which stores `GROK_CREDENTIALS`. There is no CLI flag for the X OAuth flow — send them to `.\u002Faeon` (the dashboard) for that one.\n- **Models:** `grok-4.5` (default, reasoning) or `grok-composer-2.5-fast` (cheap).\n- **No free tier.**\n\nTell them up front:\n- Grok runs report **0 tokens** — its JSON carries no token counts, so cost tracking reads blank. Not a bug.\n- The X OAuth session expires. If unattended runs start failing on auth, reconnect.\n- `mode: read-only` still applies (maps to `--sandbox read-only`), and MCP works.\n\nPer-skill grok knobs, in `SKILL.md` frontmatter (ignored on the Claude harness): `max_turns` (default 60), `best_of_n`, `verify`, and `effort` (`low|medium|high|xhigh|max` — reasoning models only; `grok-composer-2.5-fast` rejects it).\n",{"name":5,"description":7},"main","fa8f75cd49adcad9214508fdb5d1ead8fab420be","plugin\u002Fskills\u002Faeon","https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Faeon-template","https:\u002F\u002Fgithub.com\u002FLiamVisionary","2026-11-15 04:34:04",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add LiamVisionary\u002Faeon-template --skill aeon",{"tool":35,"command":36},"bunx","bunx skills add LiamVisionary\u002Faeon-template --skill aeon",{"tool":38,"command":39},"pnpm","pnpm dlx skills add LiamVisionary\u002Faeon-template --skill aeon","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Faeon-template\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Faeon\u002FSKILL.md",true,[43,49,53,57,61,65,69],{"path":44,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":47,"sourceHtmlUrl":48},"references\u002Fci.md","REFERENCE","参考文档",5264,"https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Faeon-template\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Faeon\u002Freferences\u002Fci.md",{"path":50,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fhistory-mining.md",8265,"https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Faeon-template\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Faeon\u002Freferences\u002Fhistory-mining.md",{"path":54,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Flayout.md",4562,"https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Faeon-template\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Faeon\u002Freferences\u002Flayout.md",{"path":58,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fmcp.md",8921,"https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Faeon-template\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Faeon\u002Freferences\u002Fmcp.md",{"path":62,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fsecrets.md",9172,"https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Faeon-template\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Faeon\u002Freferences\u002Fsecrets.md",{"path":66,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fskill-anatomy.md",7984,"https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Faeon-template\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Faeon\u002Freferences\u002Fskill-anatomy.md",{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"scripts\u002Fmine-history.mjs","SCRIPT","脚本",17609,"https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Faeon-template\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Faeon\u002Fscripts\u002Fmine-history.mjs",[76,83,90,97,104,111],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":18},"01M7D6W8WRJH3JVJ2JQ674AD77","you-web-search","Web search using You.com Search API with high-quality, cited results and optional real-time web crawling","https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Faeon-template\u002Fblob\u002Fmain\u002Fskills\u002Fyou-web-search\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":18},"01M7D6W2XPBZZPPXPX76WMPSDA","write-tweet","Multi-format tweet studio - standalone drafts (10 across 5 size tiers), a 5-10 tweet thread, or 10 remixes of past tweets, selected via ${var}","https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Faeon-template\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-tweet\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":18},"01M7D6VZVWK4RATPHM90N71QZD","weekly-aeoncard","Build a weekly token-consumption recap image from memory\u002Ftoken-usage.csv - this week + all-time totals, top skills, rendered as a shareable SVG card.","https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Faeon-template\u002Fblob\u002Fmain\u002Fskills\u002Fweekly-aeoncard\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":18},"01M7D6VQ7H3DHAAP0BEWTC3HK4","vuln-tracker","One lifecycle poll over everything vuln-scanner produces - PR and advisory status, PVR triage transitions, and pending-disclosure aging, with a stars-secured impact headline and one action queue.","https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Faeon-template\u002Fblob\u002Fmain\u002Fskills\u002Fvuln-tracker\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":18},"01M7D6VDRA94RJKDPKJ65S47KT","vuln-scanner","Audit trending repos for real security vulnerabilities and disclose responsibly - scan and route findings (PVR \u002F dependency PR), re-submit queued advisories, and send armed email disclosures","https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Faeon-template\u002Fblob\u002Fmain\u002Fskills\u002Fvuln-scanner\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":18},"01M7D6V8BNPHCTPJBJD89H8DZF","video-script","Turn a repo, product page, or update into a recording-ready video script in a receipts-first format - verifies every claim against live sources, then writes timestamped VO + on-screen direction with a plain-language glossary, assets checklist, anti-tells, and a verify-before-recording list","https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Faeon-template\u002Fblob\u002Fmain\u002Fskills\u002Fvideo-script\u002FSKILL.md",[],[]]