Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
Fix - Apply auto-fixes if --fix (HIGH certainty only)
Detection Patterns
1. Tool Schema Design (HIGH)
Based on function calling best practices:
Required elements:
{"name":"verb_noun","description":"What it does. When to use. What it returns.","input_schema":{"type":"object","properties":{"param":{"type":"string","description":"Format and example"}},"required":["param"],"additionalProperties":false}}
The "Intern Test" - Can someone use this tool given only the description?
Issue
Certainty
Auto-Fix
Missing additionalProperties: false
HIGH
Yes
Missing required array
HIGH
Yes
Missing tool description
HIGH
No
Missing param descriptions
MEDIUM
No
Vague names (search, process)
MEDIUM
No
2. Description Quality (HIGH)
Tool descriptions must include:
What the function does
When to use it (trigger context)
What it returns
// Bad - vague"description":"Search for things"// Good - complete"description":"Search product catalog by keyword. Use for inventory queries or price checks. Returns matching products with prices."
Parameter descriptions must include:
Format expectations
Example values
Relationships to other params
// Bad"query":{"type":"string"}// Good"query":{"type":"string","description":"Search keywords. Supports AND/OR. Example: 'laptop AND gaming'"}
3. Schema Structure (MEDIUM)
Issue
Why It Matters
Deep nesting (>2 levels)
Reduces generation quality
Missing enums for constrained values
Allows invalid states
No min/max on numbers
Unbounded inputs
>20 tools per plugin
Increases error rates
Prefer flat structures:
// Bad - nested{"config":{"settings":{"timeout":30}}}// Good - flat{"timeout_seconds":30}
// Validate before executionfunctionvalidateToolInput(params, schema) {
// Type validation// Range validation (min/max)// Enum validation// Format validation (regex patterns)
}
