amw-skill-drift-audit

Detects content drift between pinned skill sources and upstream git repositories.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/Emasoft/ai-maestro-webdesign --skill amw-skill-drift-audit-emasoft
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: amw-skill-drift-audit
Source: https://github.com/Emasoft/ai-maestro-webdesign/tree/main/skills/amw-skill-drift-audit
Command: npx skills add https://github.com/Emasoft/ai-maestro-webdesign --skill amw-skill-drift-audit-emasoft

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Plugins built by distilling content from upstream sources pin each skill to a source commit, but upstream repos keep moving. This Skill audits every skill's source / source_version frontmatter against the current upstream HEAD and tells you which skills are still accurate, which only need a mechanical pin bump, and which need human re-distillation. ## Core Features & Use Cases - Drift classification: Labels every skill CLEAN, PIN-ONLY, STALE, UNPINNED, or DEGRADED by diffing pinned commits against upstream HEAD restricted to each skill's source paths. - Read-only audit: Never edits skills, bumps pins, commits, or fetches; it emits a markdown re-distillation plan a human acts on. - Actionable report: Writes a timestamped markdown plan with per-skill diff summaries, re-check pointers, and ordered next steps (author pins, re-distill STALE, bulk-bump PIN-ONLY). - Use Case: Before a plugin release, run the audit to discover that amw-shadcn-ui is STALE because components/ui/button.tsx changed upstream, while 40 other skills only need a pin bump. ## Quick Start Ask the agent to audit skill drift in this plugin and check all skill pins against their upstream sources, then write the re-distillation plan to the reports directory.

Frequently Asked Questions about amw-skill-drift-audit

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

FAQPage Schema
How do I check if my plugin skills are out of sync with upstream sources?▼

Run the skill drift audit, which reads each skill's source and source_version frontmatter, diffs the pinned commit against the upstream repo's HEAD, and classifies every skill as CLEAN, PIN-ONLY, or STALE in a markdown report.

What is the difference between PIN-ONLY and STALE skill drift?▼

PIN-ONLY means upstream HEAD moved but none of the skill's source files changed, so a mechanical pin bump suffices. STALE means at least one source file actually changed, so the distilled content may be wrong and needs human re-distillation.

Does the skill drift audit modify or fix my skills automatically?▼

No, the audit is strictly read-only. It never edits skill content, bumps version pins, commits, or fetches; it only emits a markdown plan describing what a human should change.

What happens when a skill has no source pin in its frontmatter?▼

Skills missing either source or source_version are flagged as UNPINNED and excluded from diff classification, since they can never be drift-audited. The report lists them with a note that pins must be authored first.

Why does the drift audit report DEGRADED for some skills?▼

A skill is DEGRADED when its upstream repo cannot be resolved on disk, the path is not a git repository, or the pinned commit is invalid (for example after a force-push). The audit reports the pin and reason instead of guessing.

When should I use drift audit instead of plugin structural validation?▼

Use drift audit for content-level questions about whether distilled skill content is still current against upstream. Structural validators like cpv-batch-validate check manifest correctness and frontmatter shape, which is an orthogonal concern.