asset-audit

Audit assets against naming conventions, file size budgets, format standards. Finds orphaned assets, missing references.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/asset-audit/SKILL.md

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-sequenced audit workflow with explicit validation checkpoints, deterministic verdict rules, and honest not-assessed handling for every unmeasurable condition. Its main weakness is repetition of the anti-fabrication messaging, which could be consolidated into one section.

Suggestions

Consolidate the repeated NOT ASSESSED/anti-fabrication doctrine (stated in the preamble, the 'Insufficient input' section, and the verdict rules) into a single section to save tokens.

Consider extracting the per-engine naming conventions and format standards into a reference file if the skill grows, keeping SKILL.md as the workflow overview.

Dimension	Reasoning	Score
Conciseness	Mostly efficient — the engine tables, glob patterns, and report template all earn their tokens — but the anti-fabrication doctrine is repeated across the preamble, the 'Insufficient input' section, and the verdict rules ('NOT ASSESSED, never an estimate', 'A verdict of NOT ASSESSED is a success', 'Absence of evidence is never evidence of absence'), and could be consolidated.	3 / 5
Actionability	Fully executable throughout: copy-paste-ready glob patterns per engine, concrete naming patterns (e.g. '[category]_[name]_[variant]_[size].[ext}'), exact format rules, a complete report template with table headers, and ordered first-match verdict rules covering the common cases.	5 / 5
Workflow Clarity	A clear Phase 1-5 sequence with explicit validation checkpoints (the FOUND/ABSENT input checklist, engine-resolution stop condition, per-section NOT ASSESSED fallbacks) and error-recovery routing to sibling skills; the skill is read-only, so the destructive/batch validation cap does not apply.	5 / 5
Progressive Disclosure	No bundle files exist and the content is single-pass workflow material appropriately kept inline, with clearly signaled one-level references to sibling skills (/art-bible, /content-audit, /setup-engine) and project docs; good structure with only minor organization gaps (the per-engine naming/format standards tables are borderline candidates for extraction).	4 / 5
	Total	17 / 20 Passed

Description

71%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, well-scoped description with concrete actions and good natural keywords, weakened by the complete absence of a 'when to use' trigger clause and missing synonyms. Adding an explicit 'Use when...' clause would move it to the top tier.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to audit, check, or clean up game assets, or mentions orphaned or unused assets.'

Include natural synonyms and file types users would say, such as 'unused assets', 'game assets', 'texture/audio/VFX files', and engine-specific terms (Godot, Unity, Unreal).

Clarify the game-asset scope explicitly to further reduce overlap with sibling skills like /content-audit.

Dimension	Reasoning	Score
Specificity	The description lists multiple specific concrete actions — 'Audit assets against naming conventions, file size budgets, format standards' and 'Finds orphaned assets, missing references' — covering the full compliance-audit domain, matching the comprehensive-coverage anchor rather than the minor-gaps anchor.	5 / 5
Completeness	The 'what' is clearly stated (audit assets against conventions, budgets, formats; find orphaned and missing assets), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Natural terms like 'assets', 'orphaned assets', 'missing references', and 'naming conventions' are present and would be said by users, but common synonyms ('unused assets', 'game assets') and file-type/extension terms are missing, so it falls short of the comprehensive-synonym anchor.	4 / 5
Distinctiveness Conflict Risk	The niche (asset compliance auditing with specific check dimensions) is clear and mostly distinct, but in a project with closely related sibling skills like /content-audit and /art-bible there is minor overlap risk, matching the 'mostly distinct; minor overlap risk' anchor.	4 / 5
	Total	16 / 20 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 5 missing	Warning

	Total	13 / 16 Passed

Repository: Donchitos/Claude-Code-Game-Studios
Path: .claude/skills/asset-audit/SKILL.md
Commit: b21fa0f

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.