audit

Audit nuthouse repository definitions against template standards and report drift.

1|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/g-bastianelli/nuthouse --skill audit-g-bastianelli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/g-bastianelli/nuthouse/tree/main/.claude/skills/audit
Command: npx skills add https://github.com/g-bastianelli/nuthouse --skill audit-g-bastianelli

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill scans the nuthouse repository to verify the consistency and compliance of skills, agents, personas, and banners with defined standards and templates.

Core Features & Use Cases

  • Conventions Check: Reviews SKILL.md, AGENT.md, persona.md, banner references, and asset files against template guidelines.
  • Report Generation: Provides a detailed report highlighting missing or incorrect elements, such as missing sections, non-compliant formats, or outdated assets.
  • Early Drift Detection: Helps identify deviations from the source of truth before they propagate throughout the repository.

Quick Start

Run the audit skill in the nuthouse repo to validate all files against the _templates/ source of truth.

Frequently Asked Questions about audit

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

FAQPage Schema
How do I check repository files for convention compliance and template adherence?

To check convention compliance, you audit skill, agent, and persona definitions against a designated set of template standards. This process detects drift and highlights missing sections, non-compliant formats, or outdated assets.

What is the best way to detect convention drift across multiple markdown definitions?

Detecting convention drift involves comparing SKILL.md, AGENT.md, persona.md, and banner references against source templates. Early detection prevents deviations from propagating throughout the repository.

How do I verify brand consistency and asset files in a repository?

You verify brand consistency by scanning the repository to compare asset files and banners against defined template guidelines. This generates a detailed report highlighting missing or incorrect elements.

Does the audit process require specific dependencies to review markdown files?

No specific dependencies are required to review markdown files. The audit process uses internal scripts and references to validate definitions without external package installations.

Can I generate a report for missing sections in skill and persona definitions?

Yes, you can generate a detailed report for missing sections. The audit evaluates definitions against template guidelines, producing a report that highlights incorrect elements and outdated assets.

When should I run a template verification check on my repository?

You should run template verification checks before deviations propagate throughout the repository. Frequent auditing ensures definitions remain aligned with the source of truth and prevents early drift.