clean-skill

Validate canonical_version and last_updated fields to detect manifest drift.

1|Updated May 9, 2026
One-click install
npx skills add https://github.com/tonykoop/claude-skills --skill clean-skill-tonykoop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clean-skill
Source: https://github.com/tonykoop/claude-skills/tree/main/tests/fixtures/manifest-drift/pass/skills/clean-skill
Command: npx skills add https://github.com/tonykoop/claude-skills --skill clean-skill-tonykoop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fixture skill used by manifest drift tests to validate validator behavior and drift-detection tooling in CI.

Core Features & Use Cases

  • Lightweight fixture with complete manifest metadata used to exercise manifest validation pipelines.
  • Used in tests to verify drift detection and ensure consistency between manifest.yaml entries and per-skill metadata.

Quick Start

Run the manifest drift test against this fixture to confirm drift-detection logic.

Frequently Asked Questions about clean-skill

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

FAQPage Schema
What is manifest drift validation in CI pipelines?

Manifest drift validation detects inconsistencies between manifest.yaml entries and per-skill metadata. It verifies canonical_version and last_updated fields during CI validation and release processes to ensure consistency across skills.

How do I test manifest drift detection logic?

Run manifest drift tests against a fixture skill containing complete manifest metadata to exercise validation pipelines. This verifies drift detection tooling and ensures consistency between manifest.yaml entries and per-skill metadata.

What metadata is required in SKILL.md frontmatter for manifest validation?

Manifest validation requires a name and description in SKILL.md frontmatter, plus an informative SKILL body. Optional changelog and manifest entries can be added to support auditing during CI validation and release processes.

Does manifest drift validation work with YAML frontmatter and changelog entries?

Yes, manifest drift validation works with YAML frontmatter by requiring name and description fields. It also supports optional changelog entries to audit consistency between manifest.yaml and per-skill metadata during CI checks.

Why does manifest validation fail when canonical_version and last_updated fields are inconsistent?

Manifest validation fails on inconsistent canonical_version and last_updated fields because it detects manifest drift across skills. This ensures manifest.yaml entries match per-skill CHANGELOG and metadata during CI validation and release processes.