WebinarNotes/wiki/concepts/skills-as-memory.md

Skills as Memory

#concept

Summary

A skill is a directory + a gentleman's agreement: a SKILL.md describing what to do, plus optional tools (bash/python) and — Konstantin's key proposal — the data and usage history in the same git repo. Combined this way, skills become the new memory of AI agents: information about the user lives in skills, loaded exactly when a skill activates, rather than pre-fetched by RAG.

Current Understanding

The unlock is two-stage loading: a short description always sits in the system prompt (the agent knows the skill exists); the long SKILL.md loads only when the agent enters the directory. This lets a harness hold hundreds of skills without blowing context-as-scarce-resource — impossible with raw tools, where a couple of calls exhaust context. Skills also compose (one skill calls another) and are portable (plain markdown folders migrate Claude → Perplexity → Gemini).

A classic skill is "von Neumann without data" (code, no data). Adding data + history makes the skill self-contained; storing it in git enables skill-first architecture (many agents on one skill), CI/CD integration, team sharing, and merge-conflict resolution by models. Skills can auto-improve: create a skill after >5 tool calls on a task; a curator prunes unused skills (30/90 days) and consolidates weekly. See hermes.

The method for populating skills is solve-first-then-skillify: reach the final solution once, then freeze it (Eugene's variant of the heuristic: any correction loop longer than ~3 messages becomes a skill). The HR interviews add a social payoff: a packaged skill is a handoff/de-risking asset — a junior "with not even a third of your HR experience" can deliver a decent result, and the expert can take a vacation.

The negative case: built-in memory as anti-feature. The 2026-07-21-larysa-interview supplies the demand-side reason this architecture exists. Her core frustration is that the agent doesn't carry context between sessions — she re-explains, and re-pays in time and tokens. Eugene's answer is not "better memory" but no memory: "Memory is the worst thing agents have — it gives no benefit and confuses users to hell. Why even go there? … The memory exists, but the way it's implemented, it'd be better if it didn't." The claim is that an opaque, always-on memory that silently decides what to recall is worse than nothing, because the user can neither inspect nor correct it — whereas a skill is a file you can read, edit, version and delete. Skills are the memory you author.

Evidence

• Skill definition, two-stage loading, data-in-git proposal, curator, auto-creation — 2026-07-14-skills-based-on-git.
• Skill = folder with one MD + resources; skills compose and transfer across tools/models; built-in skill-creator — 2026-07-14-gap-between-ai-users-irreversible.
• Markdown-file-as-service (G-brain tier) is the same "executable prose" instinct — 2026-07-14-everything-we-knew-about-software-has-changed.
• Skill as zip-and-hand-over onboarding asset; "create a skill for this" — 2026-07-14-nina-interview.
• ~3-message correction-loop heuristic; skills as the non-programmer ceiling (with CLAUDE.md) — 2026-07-14-yulia-interview.
• Cross-session memory loss as the #1 practitioner pain; "memory is the worst thing agents have"; skills committed as the webinar remedy — 2026-07-21-larysa-interview.

Related Pages

• Concepts: evolution-of-agent-tooling (tools → MCP → skills), harness, context-as-scarce-resource, agentic-loops, personal-ai-operating-system, solve-first-then-skillify, levels-of-ai-usage, leave-less-room-for-imagination
• Tools: hermes, claude-code
• Entities: konstantin, allie-miller, eugene, larysa

Contradictions / Uncertainty

• No standards yet for what data to put in a skill or its size limit (Konstantin: 200 GB in one, 100 KB in another, both fine — "ceiling not found"). Status: tentative.
• "Built-in memory is a net negative" is Eugene's strong position, not a corpus consensus — allie-miller's personal-ai-operating-system happily uses persistent context docs and never condemns the memory feature. The two are reconcilable (both prefer authored context to inferred context), but the blanket "better if it didn't exist" is one voice. Status: tentative.

Next Questions

• What's a starter skill set for a non-engineer? Answered in 2026-07-14-best-first-skill-for-beginner (skill-creator as meta-skill; tone-of-voice + anti-AI-language as first content skill).
• Do skills actually solve cross-project context, or only per-procedure recall? Larysa's complaint may be the former, which skills don't obviously address.