Agent skill · operations · aiskillstore
skill-check
Comprehensive testing and validation of Claude skills. Use this skill whenever the user wants to test, validate, audit, or quality-check a skill — whether they say "test my skill", "check this skill works", "validate my skill", "run skill-check", or anything similar. Also trigger when the user asks things like "does this skill handle edge cases?", "what's wrong with my skill?", "find problems in my skill", "is this skill secure?", "does my skill follow best practices?", or "how robust is this skill?". Even if they just say "check this" and point at a skill directory, use skill-check. This skill covers triggering tests, output quality tests, input/output contract validation, script execution checks, security review, best practices auditing, and multi-file skill analysis. Do NOT use for creating or editing skills (that's skill-creator) — skill-check is purely about testing and reporting on existing skills.
Why this skill is useful
Adds a comprehensive testing framework that evaluates skills for functionality, security, and best practices, which the AI wouldn't reliably generate on its own.
What it needs
Requires python installed locally. About 6k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
SkillCheck — Comprehensive Skill Testing SkillCheck audits an entire skill directory, understands every moving part, and generates targeted tests to verify the skill works as advertised. It doesn't just check "does it roughly work" — it tests every aspect: triggering, input handling, output quality, script correctness, security, best practices, and resource integrity. --- How it works Three phases: Discover → Test → Report. Discovery is always required. Testing depth depends on what the user wants. Reporting adapts to what was found. Depth What it covers --------------- --------------------------------------------------------------------------- Quick Static analysis — structure, syntax, integrity, security, best practices Standard Static + script execution + happy-path I/O + eval regression Deep Everything — edge cases, mock files, e2e workflows, stress If the user doesn't specify, default to Standard — it catches real functional problems without the time investment of Deep. If they seem in a hurry, go Quick. If they mention thoroughness, edge cases, or "test everything", go Deep. For a worked example of a Standard Check from start to finish, see references/example-run.md. --- Gotchas The evals.json format must match the skill-creator schema exactly (see references/eval-schema.md). Don't invent a new format — compatibility with skill-creator's benchmarking tools is the whole point. Mock file generation for binary formats (DOCX, XLSX, PPTX, PDF, images) requires third-party Python packages that may not be installed. Always check availability before generating and fall back to text-based equivalents if installation fails. See references/mock-files.md for the dependency list. Cross-reference mismatches between SKILL.md and scripts are often the root cause of multiple downstream test failures (script execution fails, eval regression fails, I/O tests fail — all for the same reason). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/skill-check