Skip to main content
Glama

Compile a skill for other agents

compile_skill

Convert a Claude-style skill folder into formats read by Codex, Cursor, Copilot, Gemini, and Claude, then validate content, frontmatter, and size limits while writing output files.

Instructions

Convert one Claude-style skill folder into the format other agents read (claude, codex, cursor, copilot, gemini) and check the result: content kept, frontmatter valid, size limits. Writes files under the output folder only.

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": {
      "path": "<path>"
    },
    "name": "compile_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
outNoOutput folder inside the working folder. Default ".skillyard/compiled".
pathYesThe skill folder (holding SKILL.md).
targetsNoComma-separated: claude, codex, cursor, copilot, gemini, or "all". Default "all".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the write-capable, non-destructive, local profile is known. The description adds real value by scoping writes to the output folder ('Writes files under the output folder only') and by naming the checks performed, but it says nothing about overwrite behavior, error handling, or whether existing compiled output is replaced.

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?

A single front-loaded sentence with the action first and the validation checks appended after the colon; nothing is wasted. The trailing list of checks makes the sentence denser than ideal but it remains readable.

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?

With three simple parameters, full schema coverage, and no output schema, the definition covers what matters: what is converted, where output goes, and which validations run. Missing only edge-case behavior such as failure modes or re-run overwriting, which are minor for this complexity.

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 description coverage is 100%, so path, out and targets are already documented, including the '.skillyard/compiled' default and the comma-separated target list. The description repeats the target formats and reinforces the output-folder containment but adds no format or syntax detail beyond the schema, so the 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?

States a specific verb and resource: 'Convert one Claude-style skill folder into the format other agents read,' and enumerates the target formats plus the validation it performs. It is clear what the tool does, though it does not name a sibling such as review_skill to mark the boundary between compiling and reviewing.

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: the phrase 'check the result' hints this tool validates after converting, but there is no explicit when-to-use guidance, no statement of when to prefer review_skill or check_agents, and no prerequisites such as a required SKILL.md layout beyond 'holding SKILL.md'.

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