Skip to main content
Glama
superpowers-mcp

superpowers-mcp

by erophames

get_skill_file

Loads a supporting file from a superpowers skill by specifying the skill directory and filename, such as a markdown reference doc, so an LLM can retrieve skill details on demand.

Instructions

Load a supporting file from a superpowers skill

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": "<skill>",
      "file": "<file>"
    },
    "name": "get_skill_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesThe filename to load (e.g. 'testing-anti-patterns.md')
skillYesThe skill directory name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read operation by saying 'Load,' but does not disclose what is returned, whether the skill must already exist, what happens with missing files, or any path-safety constraints.

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?

The description is a single front-loaded sentence with no filler or repetition. Its brevity is appropriate for a simple two-parameter retrieval tool, though it is arguably too terse to be maximally 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 low-complexity tool with fully described parameters, the definition is adequate but incomplete. Because there is no output schema, the description should ideally explain that the file contents are returned and clarify how this tool relates to use_skill and list_skills.

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 coverage is 100%, so both parameters are already documented as a skill directory name and a filename. The description adds only light context by tying them to a 'superpowers skill' and a 'supporting file,' which is useful but does not go meaningfully beyond the schema.

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?

The description states a specific verb and resource: 'Load a supporting file from a superpowers skill.' That is clear enough to distinguish loading a file from loading or using the skill itself, but it does not explicitly differentiate this tool from siblings such as use_skill or list_skills.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. An agent can infer that it retrieves supporting files, but nothing says when use_skill or list_skills should be preferred.

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