meko-skills
Off-the-shelf agent skills for Meko — the agent-native data layer for multi-agent systems.
Do I need this repo?
Meko works without skills. Once you connect the MCP server to any AI agent, the agent has access to tools for memory, conversations, knowledge base, datapacks, and database. You tell it what to save and when:
"Save to memory that I'm a backend engineer and we use Go."
"Search my memories for what we discussed about the auth migration."
That's on-demand mode — Meko is a tool your agent calls when you ask it to. Many users start here and it works fine.
Skills change what happens next. A skill is a markdown instruction file (SKILL.md) that teaches your agent to use Meko without being asked:
| Without skill | With skill installed |
|---|
| You say "save this to memory" | Agent calls memory_add the moment you mention your name, role, or preferences |
| You guess at tool parameters | Agent uses correct scope, agent_id, and datapack_id routing on the first try |
| You ask the same questions across sessions | Agent calls memory_search at session start and greets you with context |
| Conversations vanish when the window closes | Agent preserves exchanges via conversation_create + conversation_add_message |
Each layer builds on the previous:
| Layer | What you get | What you install |
|---|
| MCP only | Tools available on demand — you tell the agent when to save | MCP server connection (setup guide) |
| MCP + Skill | Agent proactively stores memories, classifies info, uses correct parameters | + a skill from this repo |
| MCP + Skill + Hooks | Full automatic conversation capture — every exchange persisted without prompting | + hooks (Claude Code, via the installer) |
What's in this repo
This repository has three public-facing surfaces with different consumers:
| Directory | Consumer | Purpose |
|---|
skills/ | Humans and harnesses that copy skills directly (Cursor, Codex, Copilot, Claude Desktop, claude.ai, etc.) | Browsable community skill source at stable paths |
plugins/meko-agent-skills/ | Claude Code /plugin and Connector Directory packaging | Self-contained plugin bundle with its own generated copy of skills/, hooks, hook handlers, and .mcp.json |
scripts/ | CI and publish verification | Token-free checks for generated public output, prompt-injection lint, and plugin readiness |
.claude-plugin/
└── marketplace.json # Marketplace catalog; metadata.pluginRoot points at ./plugins
plugins/
└── meko-agent-skills/
├── .claude-plugin/plugin.json
├── .mcp.json # Public Meko MCP connector config
├── skills/ # Generated copy; plugin must not ../ into root skills
├── hooks/
└── hooks-handlers/
skills/
├── meko-mcp-tools/ # Coding agents: Claude Code, Cursor, Codex, VS Code
└── meko-mcp-tools-desktop/ # Claude Desktop, claude.ai (no session hooks)
scripts/
The duplication between skills/ and plugins/meko-agent-skills/skills/ is intentional. Anthropic plugins are copied into a plugin cache and cannot reference files outside their plugin directory with paths like ../shared-utils, so the plugin must carry its own skill copy.
Both skills cover 20 MCP tools across memory, conversation, knowledge base, and datapack management. The difference is how they handle session lifecycle:
| Skill | Best for | Key difference |
|---|
meko-mcp-tools | Claude Code, Cursor, Codex CLI, GitHub Copilot (VS Code / CLI) | Designed for coding agents — includes hook-based conversation capture and subagent coordination |
meko-mcp-tools-desktop | Claude Desktop, claude.ai | Designed for chat-first clients — more aggressive proactive-memory rules, no hook dependency |
Install a skill
Prerequisites
You need a Meko account and an MCP server connection before installing a skill. If you haven't set that up yet:
