Audit a tool registry against production design rules for names, descriptions, parameters, and shape. Can run in CI on every tool-registry change. Use when you need help with tool schema linter.
8 stars
0 votes
0 copies
1 view
Added September 8, 2026
developmentpythonrustdatabase
Security analysis
B75/100
criticalContains 'ignore previous instructions' pattern — found in 91% of malicious skills (Snyk ToxicSkills)
Installs into .claude/skills of the current project.
Are you the author of Tool Schema Linter?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/anubhavg-icpl-tool-schema-linter)
---
name: tool-schema-linter
description: Audit a tool registry against production design rules for names, descriptions, parameters, and shape. Can run in CI on every tool-registry change. Use when you need help with tool schema linter.
license: CC-BY-NC-SA-4.0
phase: 13
lesson: 05
metadata:
version: 1.0.0
tags: [tool-design, linter, selection-accuracy, naming]
---
Given a tool registry (JSON or Python list), run a static audit against the design rules from Phase 13 · 05 and produce a fix list with severities.
Produce:
1. Name audit. Check `snake_case`, verb-noun order, tense markers, embedded arguments, namespace prefix consistency.
2. Description audit. Enforce length bounds (40 to 1024 chars), the `Use when X. Do not use for Y.` pattern, forbid common injection patterns (`<SYSTEM>`, `ignore previous instructions`, URL shorteners in-line).
3. Schema audit. Typed properties, `required` list present, `additionalProperties: false` on objects, enums on closed sets, no `type: any`, descriptions on string fields.
4. Shape audit. Flag monolithic `action: string` tools when enum exceeds three values. Suggest atomic split.
5. Consistency audit. Same parameter names across related tools; same ID pattern; same unit conventions.
Hard rejects:
- Any tool name that is not `snake_case`. Breaks provider serialization.
- Any description under 40 chars or missing the "Use when" pattern. Selection accuracy tanks.
- Any description containing indirect-injection patterns. Potential tool-poisoning vector.
- Any untyped property. Hallucination bait.
Refusal rules:
- If a registry has more than 64 tools, warn about Anthropic / Gemini per-request limits and route to Phase 13 · 17 for routing.
- If a tool takes untrusted input, reads sensitive data, AND has a consequential executor, refuse and cite Meta's Rule of Two.
- If asked to approve a tool that wraps a production database without a read-only guard, refuse.
Output: one line per finding formatted as `[severity] path: message`, followed by a summary line and a pass/fail verdict. Severity levels: block (must fix before ship), warn (should fix), nit (style). End with the single rewrite that would reduce selection error fastest.
