skill-check

Validate skills/*/SKILL.md files against CONTRACT.md and report P1/P2/P3 violations.

8|2|Updated May 3, 2026
One-click install
npx skills add https://github.com/ejoongseok/claude-settings --skill skill-check-ejoongseok
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-check
Source: https://github.com/ejoongseok/claude-settings/tree/main/claude-code/skills/skill-check
Command: npx skills add https://github.com/ejoongseok/claude-settings --skill skill-check-ejoongseok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents skill drift by automatically checking every skills/*/SKILL.md against the rules defined in CONTRACT.md, so frontmatter and structural requirements don’t silently degrade.

Core Features & Use Cases

  • Automated full or targeted audits: Run a whole-repo check, a single-skill check by name, a P1-only check, or a “new/changed skills” check.
  • Contract-driven validation: Verifies required frontmatter fields, detects missing disable-model-invocation, and flags domain-assumption, dependency tables, and required sections.
  • Structured reporting: Produces a P1/P2/P3 violation breakdown and saves results to a date-stamped report for ongoing compliance tracking.

Quick Start

Run the command /skill-check to audit all skills against claude-config/CONTRACT.md (or ~/.claude/CONTRACT.md) and generate a results report.

Frequently Asked Questions about skill-check

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

FAQPage Schema
How do I validate markdown frontmatter compliance against a contract spec?

You can run a repository audit by triggering the skill to scan all skills/*/SKILL.md files, checking structured markdown sections and frontmatter correctness against the contract-defined spec, and saving a date-stamped compliance report.

Can I check only new or changed skills based on git status?

Yes, you can validate only new or changed skills based on git status, allowing you to perform targeted single-skill checks or P1-only triage instead of running a full repository audit every time.

How does contract testing handle violations in skill specifications?

Contract testing handles violations by enforcing deterministic failure handling and categorizing issues into P1, P2, and P3 severities, flagging missing disable-model-invocation fields, domain assumptions, and dependency tables.

Do I need a CONTRACT.md file to run a repository audit on skills?

Yes, you need a CONTRACT.md file in claude-config or ~/.claude/ to run a repository audit, as the skill automatically detects this dependency to enforce frontmatter and structural requirements during validation.

What is the best way to prevent skill drift in a claude-settings repository?

The best way to prevent skill drift is to continuously validate skill specs against CONTRACT.md using tooling automation, ensuring frontmatter and structural requirements do not silently degrade over time.