skf-audit-skill

Audit compiled Skill artifacts against current source with file:line citations.

91|9|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/armelhbobdad/bmad-module-skill-forge --skill skf-audit-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skf-audit-skill
Source: https://github.com/armelhbobdad/bmad-module-skill-forge/tree/main/src/skf-audit-skill
Command: npx skills add https://github.com/armelhbobdad/bmad-module-skill-forge --skill skf-audit-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Drift auditing ensures you always know how a Skill's compiled artifact compares to its current source, surfacing provenance-backed drift with precise file:line citations.

Core Features & Use Cases

  • Deterministic, AST-backed structural drift detection for SKF skills.
  • Upstream-drift checks that adapt by forge tier and support stack-skill provenance.
  • End-to-end report generation including remediation suggestions and provenance metadata.

Quick Start

Audit a target skill to generate a drift report and provenance, then review and apply remediation steps.

Frequently Asked Questions about skf-audit-skill

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

FAQPage Schema
What is deterministic drift auditing for compiled artifacts?

Deterministic drift auditing identifies structural differences between a compiled artifact and its current source, reporting findings with provenance and precise file:line citations.

How do I detect source drift in compiled skills?

You detect source drift by running an audit against the target skill, which generates a structured drift report with provenance metadata, file:line citations, and remediation guidance.

Can I use AST-backed structural diff detection for forge tier skills?

Yes, AST-backed structural diff detection adapts to forge tier availability, applying Deep tier semantic diff when available or providing staged outputs for Quick and Forge tiers.

What is the best way to generate provenance reports for skill drift?

The best way to generate provenance reports is to audit the target skill, producing end-to-end findings that include remediation suggestions and provenance metadata for upstream drift.

Do I need dependencies to run upstream-drift checks on skills?

No dependencies are required to run upstream-drift checks, as the skill operates independently to adapt checks by forge tier and support stack-skill provenance reporting.

Why does my compiled skill artifact not match the current source?

Your compiled artifact does not match the current source due to drift, which deterministic auditing detects by comparing the compiled output against the latest source with file:line citations.