quality-tools

Quick Review

The skill provides minimal actual content in SKILL.md, with only a brief statement about guidelines and best practices, then references REFERENCE.md for details. While the structure follows a clean pattern by delegating to another file (which we assume exists per instructions), the description is too vague for a CLI agent to understand when and how to invoke it. The description mentions 'setting up quality tools or CI' but provides no specifics about which tools (linters, formatters, static analyzers, test coverage, etc.) or languages are supported. Task knowledge scoring assumes REFERENCE.md contains useful content, but the lack of overview or index in SKILL.md makes discoverability poor. Novelty is moderate as quality tool setup could involve language-specific configurations and CI pipeline templates that might save tokens, though the generic nature suggests limited complexity.