Memory vs AGENTS.md vs Skills

Store in memory	Store in AGENTS.md / static docs	Store as Skills (web UI / skills.db)
Project-specific decisions, bug patterns, “we tried X and it failed”	Stable rules and workflows that rarely change	Reusable procedures the agent loads on demand
User preferences discovered over sessions	Always-on coding conventions and process	Team-editable skill packs shared via the same storage
Facts that should follow you across chats	Instructions every agent should see regardless of retrieval	OpenCode-native skill tool (V2 plugin bridge)

Rule of thumb: lasting always-on project instructions → AGENTS.md; growing work context → memory; reusable on-demand procedures → Skills.

Shared Skills (V2)

• Create/edit skills in the web explorer (Skills tab at /skill-library).
• Persisted in skills.db under the plugin storage path (not as memory vectors).
• On OpenCode V2, the plugin registers enabled skills via ctx.skill.transform so the agent can load them with the native skill tool.
• Optional HTTP catalog for other OpenCode instances: "skills": ["http://127.0.0.1:4747/skills/"] (serves /skills/index.json and /skills/<id>/<id>.md — separate from the UI path).
• REST: GET/POST /api/skills, GET/PUT/DELETE /api/skills/:id.