Skip to content

Self-learning & skill evolution

What this is for. Two operator surfaces sit behind this chapter. Self-Learning Insights (/self-learning) reports how runs are spending tokens and what patterns keep showing up. Skill Evolution (/skill-evolution) is the human gate for AI-suggested new skills. Neither writes behaviour until you approve. Enable the related autonomy loops only if you want background proposals — they make paid model calls.

Routes: /self-learning (sidebar Self-learning), /skill-evolution.

  • You want a weekly efficiency picture: tokens, cost, sessions, success rate.
  • Repeated work looks like it should become a skill, and you want the suggestion — not a silent auto-write.
  • Skill Evolution has pending candidates and you need to Approve or Reject them.
  • You already use Forge for identity/soul changes and want the skill-side equivalent.
  1. Open Self-learning (/self-learning). Read the four summary cards, then Execution Insights, Activity Patterns, and Skill Suggestions.
  2. Press Run Analysis when you want a fresh pass (POST /self-learning/analyze).
  3. Open Skill Evolution (/skill-evolution) for candidates with Pending / Approved / Rejected.
  4. Expand Show details, read reasoning and suggested content, then Approve (adopts into the catalogue, still subject to the auto-adoption gate) or Reject.
  5. Confirm the new skill under Skills → Inventory.
AreaMeaning
InsightsPatterns learned from usage
Skill suggestionsNames + reasons from the insights page — not yet candidates
Skill evolutionProposed skill files with content, confidence, and session count
Review / applyHuman gate before behaviour changes

Prefer reviewing Forge/skill proposals before apply. Generated skills still pass the Skills auto-adoption gate.

Which model writes them. Self-learning suggestions, Forge description proposals and skill authoring for Skill Evolution run on EYAS’s background model, one isolated call each: the Heartbeat routing tier (primary, then fallback), then the install default, then API providers, then CLIs that can run isolated calls. They never go to a provider the gateway picks on its own. When no model qualifies (for example a Grok-only or Kimi-only install before their isolation is verified) or the budget is at stop, no model call is made: Self-learning shows its generic suggestion sentences, Forge keeps the concatenated description proposal, and Skill Evolution writes the template SKILL.md. The Autonomy feature flags still gate these calls. See Routing & budget — The background model.

Self-Learning Insights (`/self-learning`)

Subtitle: Efficiency reports, activity patterns, and optimization suggestions.

ControlMeaning
Run AnalysisTrigger a fresh analysis pass
Total TokensTokens in the weekly report
Total CostUSD in the weekly report
SessionsSession count
Success RateShare of successful sessions

Execution Insights — type badges Optimization / Cost / Quality / Speed, plus current vs suggested metric, confidence, and reasoning. Empty: No insights yet. Run an analysis to generate them.

Activity Patterns — name, category, seen N×, last seen. Empty: No activity patterns detected yet.

Skill Suggestions — name, description, reason, confidence. Empty: No skill suggestions yet. These are suggestions; they become reviewable candidates on Skill Evolution.

Skill Evolution (`/skill-evolution`)

Subtitle: Review AI-suggested skill candidates based on usage patterns.

ControlMeaning
StatsPending / Approved / Rejected counts, Avg Confidence
SearchSearch candidates…
Filter All / Pending / Approved / RejectedStatus filter
N sessionsHow many sessions the suggestion is based on
Show details / Hide detailsReasoning + suggested skill content
Approve / RejectHuman decision; pending only

Empty: No skill evolution candidates yet. The system will suggest new skills based on your usage patterns.