oper8r Docs

Agent Skills

Customer-facing implementation guide

Back to overview

Agent skills are installable instructions that help LLM clients use oper8r tools correctly. They are separate from MCP tool registration. MCP exposes capabilities; skills teach the client when to use them, what scope applies, and what not to store.

Included Skills

SkillPurpose
oper8r-employee-graph-curatorGuides source-backed curation of the shared organization-internal employee graph.
oper8r-workflows-search-explorerGuides use of oper8r workflow, search, graph exploration, and integration-status tools.

npm Installer

For filesystem-based clients:

npx @oper8r-io/agent-skills install all --client all

Install for Codex:

npx @oper8r-io/agent-skills install all --client codex --scope user

Install Cursor project rules from your project root:

npx @oper8r-io/agent-skills install all --client cursor --scope project

List available skills:

npx @oper8r-io/agent-skills list

Hosted Artifacts

The oper8r app exposes a skill manifest and downloadable artifacts:

/api/mcp/skills
/api/mcp/skills/:slug/zip
/api/mcp/skills/:slug/raw
/api/mcp/skills/:slug/cursor-rule
/api/mcp/skills/claude-marketplace

ChatGPT and Claude web-style installs usually use uploaded ZIP artifacts. Cursor can use generated .mdc rules. Claude Code can install from the oper8r marketplace endpoint.

Claude Code

/plugin marketplace add https://YOUR_OPER8R_HOST/api/mcp/skills/claude-marketplace
/plugin install oper8r-agent-skills@oper8r-io

Skill Scope

The employee graph curator skill is intentionally strict. It should guide the client to store only source-backed, durable, organization-internal knowledge.

Allowed:

  • Accounts, companies, contacts, employees, opportunities, owners, teams, vendors, documents, calls, and relationships that belong in shared internal operating context.
  • Trusted external IDs from systems such as Salesforce, HubSpot, Slack, Google Drive, Gong, Fathom, or approved internal systems.
  • Temporal corrections when newer evidence changes a mutable fact.
  • Reconciliation before overwriting conflicting facts.

Not allowed:

  • Private user memory.
  • Customer-facing or public graph data.
  • Passwords, API keys, OAuth tokens, refresh tokens, or raw credential metadata.
  • Personal preferences, private notes, unsupported summaries, guesses, or transient chat instructions.
  1. Enable the relevant oper8r MCP tools for the organization.
  2. Install the matching skill into the client.
  3. Test read-only workflows first.
  4. Add graph curation only for users who understand the employee graph scope.
  5. Review mutating workflows with a human before scaling.

Talk to oper8r

Bring us the workflow, integration, or deployment constraint. We can build it with you, run it for you, or advise your team.