AgentPlaybooks

Get skill

get_skill

Read-onlyIdempotent

Retrieve a skill's full definition from an AgentPlaybooks playbook using its UUID or kebab-case name, returning content, priority, attachments, and resolved demonstrations.

Instructions

Return the full definition of one skill in this playbook, including name, description, content, priority, and attachments. Identify the skill with skill_id, which may be a UUID or the skill's kebab-case name. When the skill's frontmatter declares demonstrations, they come back as a resolved list with a link per recording and per timestamped segment, in the order they are performed. This lookup does not modify the skill. Use list_skills first to discover IDs and names. Do not use list_skill_versions (historical revisions) or get_playbook (persona and summaries, not full skill content). Pass playbook_id as the UUID or GUID of the playbook this call should target.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`skill_id`	Yes	Skill ID or name
`playbook_id`	Yes	UUID or GUID of the target playbook

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No
`name`	No
`content`	No
`licence`	No
`priority`	No
`created_at`	No
`description`	No
`playbook_id`	No
`publisher_id`	No
`demonstrations`	No
`skill_attachments`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 15, 2026

TDQS

A4.6/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so 'this lookup does not modify the skill' is largely redundant. However the description adds genuine behavioral value by explaining how demonstrations are returned (resolved list, link per recording and per segment, in performance order).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, then identifier semantics, return shape, and routing guidance in a logical order. Slightly long, and the return-shape sentence partially duplicates the output schema, but every sentence carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given an output schema exists, the description need not restate returns, yet it goes further by describing demonstration resolution and ordering. Routing, identifier format, and mutation behavior are all covered, so nothing an agent needs is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description nevertheless adds meaning beyond the schema: skill_id 'may be a UUID or the skill's kebab-case name' (the schema only says 'Skill ID or name') and clarifies playbook_id is the UUID/GUID target.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Return) and resource (full definition of one skill), and enumerates the returned fields (name, description, content, priority, attachments). It explicitly distinguishes itself from list_skill_versions and get_playbook, so an agent can route correctly without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit when-to-use (use list_skills first to discover IDs) and when-not (do not use list_skill_versions for historical revisions, nor get_playbook for persona/summaries). Names alternatives with the condition that selects them.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.