skills CLI into any spec-compliant agent, or as Claude Code plugins.
Prerequisites
- An agent runtime that loads skills. Either:
- Any agentskills.io-compliant agent (used with the
skillsCLI), or - Claude Code, updated to a version that supports the
/plugincommand.
- Any agentskills.io-compliant agent (used with the
- The Narrative MCP server connected to that agent. See Connecting to the Narrative MCP Server if you haven’t set this up yet.
- A Narrative account with access to the active company you want the skills to operate against.
Skills run inside your agent and call the MCP server on your behalf. Without an active MCP connection, skills can’t reach your Narrative data.
Install skills
Each skill’s detail page in the Skills catalog shows an Installation picker with the two options below. Pick whichever matches your agent.- skills CLI
- Claude Code
The standalone
skills CLI installs a skill’s rendered SKILL.md into any spec-compliant agent. No repo clone, no Bun runtime, no Claude Code required.Add the Narrative skills marketplace
Run the install command from any skill’s detail page, or globally for the whole marketplace:The CLI fetches the marketplace and installs every available skill into your active agent’s skills directory.
Use a skill
Once a plugin is installed, you invoke its skills with natural-language prompts. Claude routes the request to the matching skill and follows its instructions. For example, with thenarrative-common plugin installed:
narrative_attributes_search and narrative_attributes_describe MCP tools to resolve the description to a canonical attribute ID (sha256_hashed_email).
Each skill’s detail page in the Skills catalog lists example prompts, accepted arguments, and the use cases each one addresses.
Slash commands and arguments
Many skills also expose a slash-command form with explicit arguments. For example, Write NQL accepts--dataset, --run, and --limit:
Where skills run
Skills run on your machine inside the agent you installed them into. They reach Narrative through the MCP server using the OAuth credential you established when you connected the agent to the server. Skills never bypass MCP — every action they take is a tool call you can inspect in the agent’s transcript. This also means skills inherit MCP’s company scoping: they operate against whichever company is active in your MCP session. Use thenarrative_context_set_company tool (or ask the agent to switch companies) before invoking a skill if you need to target a different account.
Update or remove a skill
If you used the skills CLI, rerun the add command to pick up newer versions, or use the CLI’s remove command to uninstall:/plugin:
SKILL.md frontmatter. Reinstall to pick up newer versions.
Next steps
Skills concepts
How skills relate to the MCP server, plugins, and runtimes.
MCP tool reference
The underlying tools that skills call.
Connect to the MCP server
Set up the OAuth connection skills depend on.
Browse the Skills catalog
Every published skill with example prompts and install commands.

