asset-audit

Audit project artifacts for compliance gaps with read-only scans.

18|5|Updated Nov 25, 2025
One-click install
npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill asset-audit-wsman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asset-audit
Source: https://github.com/wsman/MY-DOGE-MICRO/tree/main/.agents/skills/asset-audit
Command: npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill asset-audit-wsman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps catch compliance issues in project artifacts before they cause release, pipeline, or documentation problems, reducing manual review effort and missed violations.

Core Features & Use Cases

  • Game asset audits: Checks art, audio, VFX, shader, and data files for naming, format, budget, and reference integrity.
  • Product artifact audits: Reviews build outputs, API schemas, CLI docs, config samples, migrations, and release bundles for contract and packaging compliance.
  • Use Case: Use it when you need a read-only inspection of repository artifacts to find orphaned files, missing references, or standards violations and turn them into a structured audit report.

Quick Start

Ask the assistant to run the asset-audit skill for the relevant category and return a compliance report for the target files.

Frequently Asked Questions about asset-audit

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

FAQPage Schema
How do I audit project artifacts for compliance gaps and missing references?

Auditing release bundles and API schemas requires validating packaging compliance and contract integrity. This process scans build outputs and config samples to find standards violations and missing references, turning them into a structured compliance report.

What is the best way to check game assets for naming and format violations?

Checking game assets for naming and format violations involves scanning art, audio, VFX, shader, and data files. This read-only inspection validates file formats and reference integrity to ensure assets meet budget and compliance standards before release.

How do I find orphaned files in my repository before a release?

Finding orphaned files in your repository before a release requires a read-only directory scan of your artifacts. This inspection checks for missing references and standards violations across docs, migrations, and build outputs, generating a structured compliance report.

Does the artifact compliance audit process modify files in my directory?

No, the artifact compliance audit process does not modify files in your directory. It requires read-only directory scanning to perform naming and format validation, ensuring your build outputs, migrations, and schemas remain untouched during the inspection.

Can I review database migrations and config samples for packaging compliance?

Yes, you can review database migrations and config samples for packaging compliance. The audit process inspects these product artifacts for contract standards and reference integrity, identifying gaps and generating a structured report without writing changes.