@snippkit/mcp-server

snippkit_get_skill

Fetch an AI skill's complete SKILL.md instructions and procedural rules from SnippKit to guide agent execution with expert domain knowledge.

Instructions

Fetch the complete SKILL.md instructions and procedural rules for an AI skill from SnippKit. Use this to guide your execution with expert domain knowledge.

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": {
      "slug": "<slug>"
    },
    "name": "snippkit_get_skill"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	The slug or identifier of the skill (e.g. 'hello-world' or '@username/slug')
`username`	No	Author username if known

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 10, 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 behavioral burden. It implies a read-only retrieval and names the content type (markdown instructions and procedural rules), but says nothing about failure modes such as an unknown slug, whether private or unpublished skills are accessible, or whether the raw file or a parsed form is returned.

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?

Two short sentences, front-loaded with the retrieval action before the usage hint. The second sentence is somewhat generic but still earns its place as the only usage signal present.

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 two-parameter read tool with no output schema and no annotations, the description conveys what is returned at a high level (complete SKILL.md instructions). It stops short of covering error behavior and access rules, which an agent would still need to 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 coverage is 100%, so both parameters (slug and optional username) are already documented in the schema with an example format. The description adds no meaning beyond that, which matches the baseline for a fully documented 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 gives a specific verb and resource: it fetches the complete SKILL.md instructions and procedural rules for a skill. The resource type ('AI skill') distinguishes it from sibling tools such as snippkit_get_command and snippkit_get_snippet, though it never explicitly contrasts them.

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?

'Use this to guide your execution with expert domain knowledge' implies the situation in which the tool is useful, but there is no guidance on when to prefer it over snippkit_search_skills, and no prerequisites (for example, that a slug must first be found via search) are stated.

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

Deploy Server