eve-learning-loop: agent-authored skills that resurface as native skills, plus self-curated memory (Turso/Postgres)

[BowTiedSwan]

I built an extension that closes the procedural self-improvement loop for eve agents: the agent writes its own skills, and they come back next session as native, load-on-demand skills.

Repo: https://github.com/BowTiedSwan/eve-learning-loop · npm: npm i eve-learning-loop

What it does

• Agent-authored skills — the agent saves reusable procedures with a skill_manage tool; a dynamic skill resolver surfaces them next session as <namespace>__<name>, loadable through the framework load_skill tool like any static skill.
• Bounded, self-curated memory — a character-budgeted agent notebook + user profile (Hermes-style), injected once per session via dynamic instructions (frozen snapshot, so the prefix cache stays stable), edited by the agent through a memory tool.
• Full-text session recall — a capture hook mirrors every message into an FTS index; session_search returns ranked snippets from past conversations.
• Curator lifecycle — a copy-in schedule ages skills active→stale→archived (never deletes, pinning protects), plus an optional weekly LLM pass that consolidates duplicates.

Everything is scoped per principal, and the store is bring-your-own-database: Turso/libSQL (FTS5) or Postgres (tsvector + GIN).

Two things I liked about eve while building it

1. Skill loads are observable today. I originally assumed I'd need a skill.loaded event for usage telemetry — turns out loads are first-class runtime actions, so a hook on actions.requested / action.result narrowing kind === "load-skill" gives per-skill use counts with no framework changes. The curator ages skills by last use or last edit, whichever is later.
2. Extensions carrying their own npm dependencies is what made this shippable as one package — the DB drivers live in my dependencies, not the consumer's.

One gap worth flagging: extensions can't declare schedules, so the curator ships as copy-in templates (cp node_modules/eve-learning-loop/templates/agent/schedules/*.ts agent/schedules/). If extension-contributed schedules land someday, that step disappears.

Feedback very welcome, especially on the memory-as-prompt-injection guardrails and whether the frozen-per-session snapshot is the right default.