Skip to main content
Glama

Review skills (grade A-F)

review_skill
Read-only

Grade SKILL.md files A-F with line-level findings and fixes, then check multiple skills for duplicate or overlapping triggers and contradictions before installing or publishing. Read-only.

Instructions

Grade every SKILL.md under a folder A-F with line-level findings and fixes (broken frontmatter, vague triggers, broken links, risky scripts), and check several skills together for duplicates, overlapping triggers and contradictions. Read-only. Use before installing or publishing a skill.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "review_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoA skill folder or a folder holding several. Relative paths resolve from the folder the server was started in. Default "."

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4/5.0
Behavior4/5

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

The annotations already cover readOnlyHint and openWorldHint, and the description reinforces read-only while adding real behavioral detail: what categories are inspected (frontmatter, triggers, links, risky scripts) and that it can evaluate several skills jointly for duplicates and contradictions. It does not describe output shape or runtime cost, but the added context is substantial.

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?

The purpose is front-loaded and the three sentences are dense but purposeful, covering scope, checks, and timing. The 'Read-only' fragment slightly duplicates the annotation rather than adding new information.

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?

For a single-parameter read-only analysis tool with no output schema, the description covers what is graded, the scale, the kinds of findings, the multi-skill comparison, and the recommended timing. Nothing an agent needs in order to choose and call it is missing.

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?

With one parameter at 100% schema coverage, the schema already explains path semantics including relative resolution and the default. The description only implies that the path may point to a folder holding several skills, adding little beyond the schema's own wording.

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: grade SKILL.md files A-F, with line-level findings and fixes, plus cross-skill duplicate/overlap/contradiction checks. That scope is distinctive enough to separate it from compile_skill or secure_scan, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear when-to-use signal: 'Use before installing or publishing a skill.' There are no when-not conditions and no named alternative tool, so it stops short of full routing guidance.

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