Skill Quality Optimization Expert

The Problem

Many SKILL.md files still lack a practical quality gate after drafting: section coverage, trigger clarity, directory structure, frontmatter completeness, and version consistency are often checked manually. @user_6bedba2d/skillfaq organizes those checks into a developer-facing static workflow for pre-release review and remediation.

How It Works

It follows a RED, GREEN, and REFACTOR loop:
- RED: reads the target Skill path, establishes the current documentation state, target score, and success criteria.
- GREEN: runs a TRACE evaluation across Trust, Reliability, Adaptability, Convention, and Effectiveness, then flags P0/P1/P2 issues.
- REFACTOR: proposes fixes, prioritizes release-blocking P0 problems, and verifies whether the score approaches target_score.

It also includes SkillHub compliance checks for frontmatter, required files, version consistency, and directory structure. Evaluation depth can range from minimal to deep, supporting quick scans or fuller review.

Boundaries

The skill performs static documentation analysis rather than runtime testing. It does not detect code logic errors or runtime behavior. Remote Git repositories, encrypted content, and non-standard structures should be prepared locally first. Scores depend on documentation completeness, so final release decisions should still include manual review.