codex-skills-mcp

load_skill_file

Read a skill's scripts, configs, or README by providing the skill name and relative file path.

Instructions

Read a specific file from within a skill's directory. Use this after read_skill when you need to access scripts, configs, README, or other resources referenced in the skill instructions.

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_name": "<skill_name>",
      "file_path": "<file_path>"
    },
    "name": "load_skill_file"
  }
}

Input Schema

Name	Required	Description	Default
`file_path`	Yes	Relative path within the skill directory, e.g. 'README.md' or 'scripts/run.py'
`skill_name`	Yes	Skill name, e.g. 'MediaCrawler'

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.6Aug 2, 2026

TDQS

A4.4/5.0

Behavior3/5

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

With no annotations present, the description carries the full transparency burden. It clarifies the read-only nature and the target within the skill directory, but it lacks details on return format, error handling for missing files, or path traversal limits.

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?

The description is exactly two sentences, front-loaded with the core purpose and followed by a single usage guideline. No word is wasted, and it maintains clarity.

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

Completeness4/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 operation, the description covers the what, when, and how to locate file paths via the skill instructions. It could mention discovering file paths with list_skill_files or error behavior, but the essentials are present.

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?

The schema covers both parameters with descriptions and examples, so the baseline is 3. The description adds meaningful context by specifying the types of files (scripts, configs, README) and that paths come from the skill instructions, enriching the file_path semantics beyond the schema.

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?

The description clearly states 'Read a specific file from within a skill's directory', with a specific verb and resource. It distinguishes itself from sibling tools by referencing usage after read_skill and targeting scripts, configs, README, and other resources.

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?

The description explicitly instructs to use this tool after read_skill when accessing referenced files, providing a clear use case. It implicitly names read_skill as the alternative for reading the skill's main instructions.

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

Deploy Server