checking-skill-quality

Audit SKILL.md files against the AIDB Skills Masterclass quality framework.

16|4|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/rianvdm/product-ai-public --skill checking-skill-quality
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: checking-skill-quality
Source: https://github.com/rianvdm/product-ai-public/tree/main/.opencode/skills/check-skill
Command: npx skills add https://github.com/rianvdm/product-ai-public --skill checking-skill-quality

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits a Skill Unit's SKILL.md against the AIDB Skills Masterclass framework to ensure loud, specific frontmatter, complete anatomy, correct scoping, and robust Gotcha content.

Core Features & Use Cases

  • Validates presence and quality of the frontmatter (name, description) and the SKILL's structure against the defined best-practices guidelines.
  • Checks for the 5 Skill Killers (vague description, over-defined process, stating the obvious, missing gotcha, monolithic blob) and ensures substantive gotcha content and constraints.
  • Verifies anatomy completeness (Steps, Output, Gotcha Section, Constraints) and scoping, context binding, and identity/role considerations.
  • Produces a structured audit report highlighting strengths and actionable improvements for any Skill Unit.

Quick Start

Review a target SKILL.md by running the audit to generate a formal report.

Frequently Asked Questions about checking-skill-quality

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a SKILL.md file for quality and completeness?

To audit a SKILL.md file, validate its frontmatter, numbered Steps section, Gotcha section, and Constraints against the AIDB Skills Masterclass framework to produce a structured quality report.

What are the 5 Skill Killers to check for when reviewing skill frontmatter?

The 5 Skill Killers to check are vague descriptions, over-defined processes, stating the obvious, missing gotchas, and monolithic blobs. Auditing catches these to ensure robust skill anatomy.

How do I validate frontmatter and step structure in a skill document?

You validate frontmatter by checking for loud, specific name and description fields, and validate step structure by ensuring a numbered Steps section exists with explicit Constraints and context binding.

Can I check in-folder references and scoping when auditing a skill?

Yes, the audit verifies in-folder references, scoping, and identity/role considerations to ensure the skill's context binding is accurate and properly constrained within the repository.

What is the best way to fix a monolithic blob in a skill definition?

To fix a monolithic blob, run a quality audit to identify missing anatomy elements like Steps, Output, and Gotcha sections, then refactor the skill into a structured, scoped format.