AI startup idea generator and validator

Idea Forge is an aeon skill: Three-mode idea engine - generate collides the week's zeitgeist with what you can ship into scored wedges; validate viability-screens the idea backlog; memo writes evidence-backed startup memos. 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.

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.

Selector mode [theme/constraint]. First token picks the mode: generate (default) collides the zeitgeist with the capability surface into ranked wedges; validate screens the existing backlog for viability; memo writes 2 rigorous evidence-backed startup memos. Anything after the mode is a theme/constraint bias. A bare theme with no mode keyword (e.g. payments, crypto) = generate biased to that theme. dry-run anywhere skips the notify. Examples: ` (empty → generate, open-ended) · simulation (generate, themed) · validate crypto (screen crypto ideas) · memo solo founder (memos under a constraint) · generate payments dry-run (generate, no notify). A pick:<id|name> value (from the "build next?" force-reply - e.g. pick:Onchain reputation`) is intercepted before mode dispatch: it marks that idea as chosen-to-build in the shared backlog and ends - see "Force-reply interception" below.

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 Idea Forge. 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:
  idea-forge: { enabled: true, schedule: "0 9 * * 1", var: "" }

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