skill-qa-audit

Skill QA Auditor

Systematically verify plugin skill files against official documentation to ensure 100% correctness.

Audit Workflow

Follow these steps sequentially to complete a comprehensive audit:

1. Read and Parse the Skill File

• Locate and read the skill file (typically SKILL.md or skill.md)
• Extract all verifiable items:
  • Import statements
  • Code examples (with line numbers)
  • API calls and method signatures
  • Configuration patterns
  • Best practice recommendations
  • Documentation links
  • Claims about functionality or behavior
• Identify the technology/framework and version

2. Research Official Documentation

For EACH code example, import, and API call:

• WebSearch: "[tech] [API] documentation site:[official-domain] 2025 OR 2026"
  • Focus on recent documentation (2025/2026)
  • Target official domains only
• WebFetch: Retrieve and analyze official documentation
  • Verify exact API signatures, parameters, and usage
  • Document findings with verification status and source URL

Research Priority: Official docs → GitHub examples/tests → Official blog → Package registries

3. Systematic Verification

Verify each category of content:

Code Examples

For every code block, verify:

• ✅ Completeness: All required imports present
• ✅ Syntax: No syntax errors
• ✅ Executability: Code would run without errors
• ✅ Correctness: APIs called with correct parameters
• ✅ Currency: No deprecated APIs used
• ✅ Type hints: Accurate if present
• ✅ Error handling: Appropriate for the use case

Document: ✅ VERIFIED or ❌ ISSUE FOUND

Import Statements

For every import, verify:

• Package name is correct
• Import path is current (not deprecated)
• Import exists in the package
• Installation notes if needed

Create verification table with source documentation.

API Calls

For every API call/method/function, verify:

• Find official API documentation
• Compare signatures (skill vs official)
• Verify parameters are correct
• Check for missing required parameters
• Note optional parameters that should be mentioned