skill-audit

Audit exported skills against sources to detect stale and orphaned exports.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/edri2or/project-life-132 --skill skill-audit-edri2or
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-audit
Source: https://github.com/edri2or/project-life-132/tree/main/exported-skills/skill-audit
Command: npx skills add https://github.com/edri2or/project-life-132 --skill skill-audit-edri2or

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits all exported skills against their sources to detect drift between exports and their origins, highlighting stale or orphaned exports and surfacing portability metrics.

Core Features & Use Cases

  • Detect stale exports (source modified after last export) and orphaned exports (no local source found)
  • Verify export-portability and generate a concise quality score for each skill
  • Integrate with existing push-skills workflows to maintain a clean export layer
  • Use case: before publishing a skills bundle, run the audit to ensure consistency with sources and prevent drift

Quick Start

Run the Skill Audit to verify that exported skills align with their sources.

Frequently Asked Questions about skill-audit

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

FAQPage Schema
How do I detect stale skill exports after modifying source files?▼

A source-sync audit detects stale exports by verifying the last-modified timestamps of source files against the exported versions, reporting a consolidated status if the source was modified after the last export.

What is an orphaned export in a skill publication workflow?▼

An orphaned export occurs when no local source file can be found for an exported skill. Auditing exported skills identifies these orphaned artifacts to help maintain a clean and synchronized export layer.

How do I check the portability score of exported skills?▼

You can check the portability score of exported skills by running an audit that reads the portability metric directly from the export frontmatter, generating a concise quality score for each item.

Can I integrate a quality assurance audit into my existing push-skills workflow?▼

Yes, you can integrate this quality assurance audit into existing push-skills workflows to verify consistency with source definitions before publishing a bundle, preventing drift and ensuring a clean export layer.

What is the best way to prevent drift between exported skills and their sources?▼

The best way to prevent drift is to run an audit after editing skills and before publication, verifying that the export layer remains clean and in sync with source definitions by checking last-modified timestamps and portability scores.

Do I need any external dependencies to run an audit for stale exports?▼

No external dependencies are required. The audit runs as a standalone process to verify export frontmatter portability scores and source file timestamps without needing additional modules or external components.