skill-forge-reviewlisted

# Skill Review & Validation ## Process ### Step 1: Locate Skill Files Accept input as: - Path to a skill directory - Skill name (search in `~/.claude/skills/`) - URL to a GitHub repository Read all `.md` files, scripts, and asset files. ### Step 2: Structure Validation Run `python scripts/validate_skill.py <path>` for programmatic checks. Manual verification: - [ ] SKILL.md exists (exact case) - [ ] No README.md inside skill folder - [ ] Folder name matches `name` field - [ ] Valid kebab-case naming (1-64 chars) - [ ] No "claude" or "anthropic" in name ### Step 3: Frontmatter Audit | Check | Pass Criteria | |-------|--------------| | Name format | kebab-case, 1-64 chars, no leading/trailing hyphens | | Description present | Non-empty, 1-1024 characters | | Description has WHAT | Explains capabilities | | Description has WHEN | Includes trigger phrases | | Description has keywords | Domain-specific terms included | | No XML tags | No < or > characters | | Optional fields valid | license, compatibility (<500 chars), metadata | ### Step 4: Triggering Analysis Assess the description for activation quality: **Under-triggering risks:** - Too generic ("Helps with projects") - Missing common paraphrases - No domain keywords - Missing file type mentions (if relevant) **Over-triggering risks:** - Too broad ("Processes documents") - Overlaps with built-in Claude capabilities - Missing negative triggers for disambiguation **Generate test queries:** - 5 queries that SHOULD t