plugmcp

Official

by plugmcp-ai

Overview Schema Source Related Servers Discussions Admin

JavaScript

Hybrid

Get one agent skill

get_skill

Read-onlyIdempotent

Retrieves a skill's details by slug: what it does, its SKILL.md location, install commands for Cursor, Claude Code, Codex and Grok Build, plus the Grok Bot install message. Set include_body to add the trimmed SKILL.md text.

Instructions

One skill by slug: what it does, where the SKILL.md lives, and the install command for Cursor, Claude Code, Codex and Grok Build, plus the chat message that installs it in Grok Bot. include_body adds the SKILL.md text (trimmed).

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": "get_skill"
  }
}

Input Schema

Name	Required	Description
`slug`	Yes	Skill slug from search_skills.
`include_body`	No	Also return the SKILL.md text, trimmed to 6,000 characters.
`response_format`	No	json (default) or markdown for a human-readable text block. structuredContent is always JSON.

Output Schema

Name	Required	Description	Default
`url`	Yes
`body`	No
`file`	No
`name`	Yes
`slug`	Yes
`stars`	No
`install`	No
`summary`	Yes
`repo_url`	No
`publisher`	No
`categories`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.4Nov 6, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real behavioral detail beyond them: exactly which artifacts come back (definition, SKILL.md path, per-client install commands, Grok Bot install message) and that include_body returns trimmed SKILL.md text.

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 tight sentences with the resource and key payload front-loaded and no filler. The client enumeration makes it slightly list-heavy, but each clause conveys a distinct return element rather than padding.

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?

An output schema exists, so return values needn't be spelled out, and the description still sketches them. However, for a tool whose whole value is the returned install artifacts, it omits how response_format changes the result and gives no hint about failure when a slug is unknown.

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 slug, include_body and response_format are already documented, including the 6,000-character trim and the enum. The description restates include_body's effect but adds no semantics beyond the schema and says nothing about response_format, so 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?

The description states a specific verb and resource ('One skill by slug') and enumerates the payload — behavior, SKILL.md location, install commands per client, and Grok Bot chat message. It is clearly distinct from a plural search, but it never names search_skills as the sibling that supplies the slug, leaving that routing link to the schema.

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 once it has a slug, and the schema text ('Skill slug from search_skills') carries the prerequisite. The description itself offers no when-to-use or when-not-to-use statement and no alternative paths.

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

Deploy Server