tracked-skill

Identify missing canonical_version, last_updated, and changelog metadata in a skill manifest.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fixture for validating manifest drift detection by ensuring required versioning metadata is present or flagged.

Core Features & Use Cases

  • Validates presence of versioning-related metadata for a skill unit.
  • Serves as a test fixture for drift-check tooling.
  • Used in QA to verify validator behavior on incomplete metadata.

Quick Start

Run the drift test against the tracked-skill fixture.

Frequently Asked Questions about tracked-skill

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

FAQPage Schema
What is manifest drift detection in skill versioning?

Manifest drift detection identifies missing versioning metadata in a skill unit by checking for absent canonical_version, last_updated, and changelog fields to support auditing and remediation.

How do I validate missing versioning metadata in a skill manifest?

You validate missing versioning metadata by running drift checks against the skill manifest to confirm the absence or presence of canonical_version, last_updated, and changelog coverage.

What fields are required for manifest drift validation?

Required fields for manifest drift validation include canonical_version, last_updated, and changelog coverage, which are checked to report validation status and aid remediation.

Can I use a fixture to test manifest drift detection tooling?

Yes, you can use a test fixture to verify validator behavior on incomplete metadata by applying drift checks and confirming required versioning fields are properly flagged during QA.

Why does my skill manifest fail drift checks?

Skill manifests fail drift checks when canonical_version, last_updated, or changelog coverage is absent, causing the validation status to report missing required versioning metadata for remediation.

Do I need dependencies to run manifest drift tests?

No dependencies are required to run manifest drift tests against the skill fixture, allowing you to directly validate versioning metadata and report missing fields without external setup.