Skip to main content
Skills are Evermuse’s library of product-management and research methodologies: step-by-step guides for writing a PRD, analysing competitors, building personas, sizing a market and more. Each skill tells the agent how to gather customer evidence with the Evermuse tools, how to weigh it, and what a good result looks like. That’s what keeps answers grounded and cited rather than generic. Your agent can use skills in three ways:

Automatically

Workflow tools and search tools attach the relevant skill to their results when include_guidance is true (the default).

On demand

The agent finds skills with find_skills and loads them with read_skills. Both are free.

As prompts

Your client can list skills as MCP prompts, which many clients show as slash commands.

Prompts

The server exposes every enabled skill in your workspace through prompts/list. Each prompt:
  • is named after the skill id, for example create-prd or competitor-analysis (custom skills use their Evermuse skill id);
  • has the skill’s title and description;
  • takes one optional argument, input: what to run the skill on (a product, feature, competitor or question).
prompts/get returns the skill as a single user message: Evermuse’s citation rules, then the full skill and its references, with your input filled in. How prompts appear depends on your client. For example, Claude Code shows them as /mcp__evermuse__create-prd, and Claude shows them in the attachment menu under the Evermuse connector.
Skills that your workspace admin has disabled don’t appear as prompts. Custom skills your team adds in Evermuse appear alongside the built-in ones.

Built-in skills

Guidance in tool results

With include_guidance: true, these tools attach a skill to their result: Guidance is optional and never blocks a call: if a skill can’t be loaded, the tool returns its data without it. Once the agent has the methodology, it can pass include_guidance: false to fit more data into each page.