skill tester

AI Community

Skill notes

When to Use

After adding or modifying a skill Before committing changes Before submitting the plugin for Anthropic review As part of the outer loop when eval-creator needs to verify skill quality

1. Anthropic Spec Validation

Run quick_validate.py on every skill in skills/ (excluding -ci variants): Pass criteria: Exit code 0 for every skill. Frontmatter has only allowed keys (name, description, license, allowed-tools, metadata, compatibility). Name is kebab-case, max 64 chars. Description max 1024 chars, no angle brackets.

2. Project Convention Checks

For each skill directory: Check · Rule · Severity Name matches folder · Frontmatter name == directory name · Error Line limit · SKILL.md under 500 lines (soft), under 600 lines (hard) · Warning / Error No README.md · Skill folders must not contain README.md · Error

3. Cross-Reference Validation

Verify that all skills listed in these files actually exist as directories: CLAUDE.md — Skill References section AGENTS.md — Skill References section .github/copilot-instructions.md — Skill References section README.md — Skills table

4. Hook Script Testing

For each skill with a scripts/ directory:

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@pskoett · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview skill-tester-pskoett.preview
# Skill Test Results

**Date:** YYYY-MM-DD **Skills tested:** N **Passed:** N **Warnings:** N **Failed:** N

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.