agentskills-mcp

Get Skill Reference

get_skill_reference

Reads a specific reference file from a skill's references/ directory by skill ID and filename, enabling agents to retrieve supporting documentation on demand.

Instructions

Read a specific reference file from a skill's references/ directory.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "skill_id": "<skill_id>",
      "name": "<name>"
    },
    "name": "get_skill_reference"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Filename within references/.
`skill_id`	Yes	Directory name of the skill.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.1Nov 4, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. 'Read' implies a non-mutating operation, but nothing is said about behavior when the skill or filename does not exist, whether paths outside references/ are rejected, or what the response contains.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity leaves little room for the routing and behavioral detail an agent would find useful.

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

Completeness3/5

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

For a simple two-parameter read tool with fully documented parameters and no output schema, the description covers the essential operation. However, it omits what is returned (file contents) and failure behavior, which an agent must guess.

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

Parameters3/5

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

Schema description coverage is 100%, with both skill_id ('Directory name of the skill') and name ('Filename within references/') documented in the schema itself. The description adds no syntax, format, or edge-case meaning beyond that, so the baseline 3 applies.

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

Purpose4/5

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

States a specific verb ('Read') plus a specific resource ('reference file') and scopes it to a skill's references/ directory, which clearly separates it from siblings like get_skill_body, get_skill_script, and get_skill_asset by resource type. It does not explicitly name those siblings, so it falls short of a 5.

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

Usage Guidelines3/5

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

Usage is only implied: an agent infers it should call this after listing references and before needing the file contents. There is no explicit when-to-use, when-not-to-use, or alternative-selection guidance versus get_skill_body or list_skill_references.

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

Deploy Server