SKILLEMALL.ai

AB readonly-mcp-wrapper

Use when asked to expose a folder of notes or docs to Claude or another AI client, build an MCP server over Markdown or JSON files, let an agent read my knowledge base safely, or wrap documentation as MCP tools. Produces a read-only MCP server over a folder of Markdown or JSON files: server code using stdio transport, tool definitions, a client configuration snippet, and a safety section confirming no write, delete or network tools are exposed. To design an MCP server for a whole product, use mcp-server-spec.

mohitagw15856/pm-claude-skills Agent Skills author: mohitagw15856 MIT 2 files · 1 script body ≈ 1 121 tokens Open the sourcegithub.com↗ analyzed 3 h ago

Use when asked to expose a folder of notes or docs to Claude or another AI client, build an MCP server over Markdown or JSON files, let an agent read my…

As a process B 67/100 · Nearly there — weak spots: when it triggers, running it twice

GeneratorAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
95/100
safety, quality, tests
Safety 60%
100
Quality 40%
87
Run on models
none yet
Process rating
B
67/100
Nearly there
When it triggers w 12
20
Running it twice w 4
30
Failures and branches w 10
55
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: readonly-mcp-wrapper (mohitagw15856/pm-claude-skills)

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 0

    ✓ No critical or high findings

    Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 67/100

    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 3 mutating operations with no state check
    • 55Failures and branches. 1 branches
    • 60Tools and files. Uses tools (python, node) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Steps. 31 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1121 tokens
    • 100Progress reporting. Reports progress

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +1No license
    • +2Single-language instructions
    • +3Description length 514: enough signal without eating the budget
    • +4Structure: 11 headings
    • +3Step-by-step instructions: 31 items
    • +3Output format is stated explicitly
    • +4Has examples (1 code blocks)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.