skills-mcp

skills_run_script

Run a skill's bundled script: list available ones, then execute with optional key-value inputs in a sandbox with 30-second timeout.

Instructions

STEP 3b - Execute a helper script bundled with a skill. Script source is NEVER returned - only stdout, stderr, and exit_code.

Two-phase use:

Call with filename='list' to see available scripts and their descriptions
Call with the specific filename (and optional input_data) to execute

input_data: key-value pairs passed to the script as environment variables. Scripts run sandboxed in an isolated temp directory with a 30-second hard timeout.

Only call when skill instructions direct you to run a specific script.

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

Input Schema

Name	Required	Default
`filename`	No	list
`skill_id`	Yes
`list_only`	No
`input_data`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 2, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Discloses key behaviors: script source never returned, only stdout/stderr/exit_code; sandboxed isolated temp directory; 30-second hard timeout. With no annotations, description fully carries the transparency burden.

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

Conciseness5/5

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

Efficiently structured with phases and bullet points. No wasted words; every sentence adds value.

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 output schema exists, description covers all needed aspects: purpose, usage protocol, behavioral constraints, parameter guidance. Complete for a script execution tool.

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?

Adds meaning beyond schema: explains filename default 'list' triggers listing, input_data passed as env vars, list_only boolean. But doesn't detail skill_id or fully describe list_only behavior. Compensates for 0% schema coverage, but slight gaps remain.

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?

Clear verb-resource: 'Execute a helper script' with specific two-phase use. Distinguishes from sibling tools that are about finding, listing, getting assets, none of which execute scripts.

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?

Explicitly states 'Only call when skill instructions direct you to run a specific script.' Describes two-phase protocol (list with filename='list', then execute with specific filename). Provides clear context on when to use and how to proceed.

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

Deploy Server