inventory-content

Systematic cataloging of information assets. Creates comprehensive inventories of all content with metadata and characteristics.

Quality

57%

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 ./skills/inventory-content/SKILL.md

Quality

Content

65%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.

The body is well-organized and reasonably concise with a clear four-step workflow and well-specified inputs/outputs. Its main weaknesses are the absence of concrete tooling/commands and the lack of any validation or verification checkpoint for what is inherently a batch operation.

Suggestions

Add a verification step (e.g. confirm the report row count matches the scanned file count, and spot-check metadata extraction) so the batch workflow clears the validation gate for workflow_clarity.

Provide at least one concrete, executable example such as a shell command (find/walk) or a short snippet showing how to enumerate files and extract frontmatter.

Trim the duplicated Quick Reference section and the 'to support content governance and strategic planning' justification to tighten conciseness toward a 5.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with clear sections and no padding of concepts Claude already knows, though phrases like 'to support content governance and strategic planning' and the duplicated Quick Reference could be trimmed.	4 / 5
Actionability	Inputs and outputs are concretely specified and the steps are actionable at a high level, but no concrete commands, tools, or code (e.g. find, exiftool, a parsing snippet) are given, leaving the 'how' incomplete.	3 / 5
Workflow Clarity	A clear four-step sequence is present (Discover, Extract, Analyze, Report), but this batch operation over a directory tree lacks any validation/verification checkpoint, capping workflow clarity at 3.	3 / 5
Progressive Disclosure	The skill is a single-purpose document under 50 lines with no bundle files, and it is organized into clearly labeled sections (Inputs, Workflow, Required Outputs, Quick Reference) requiring no external references.	5 / 5
	Total	15 / 20 Passed

Description

50%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.

The description clearly states what the skill does but omits any 'when to use it' guidance, capping completeness. It is concise and in third person but uses generic language and lacks distinct trigger phrases that would differentiate it from adjacent skills.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger situations, e.g. 'Use when auditing content, planning a migration, or preparing a content consolidation.'

Replace generic phrasing ('comprehensive inventories of all content') with more concrete actions like 'recursively scans a directory, extracts frontmatter/metadata, and compiles a CSV/JSON report'.

Include natural synonyms and output-relevant terms users say (inventory, catalog, audit, content map) to strengthen trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('cataloging of information assets') and one concrete action ('Creates comprehensive inventories... with metadata and characteristics'), but the actions remain generic and coverage is not comprehensive.	3 / 5
Completeness	The 'what' is clear ('Creates comprehensive inventories of all content with metadata and characteristics') but the 'when' is entirely absent with no 'Use when...' clause, capping completeness at 3.	3 / 5
Trigger Term Quality	Contains some relevant natural keywords ('cataloging', 'inventories', 'content', 'metadata') a user might say, but misses common variations, synonyms, or file-type/extension triggers.	3 / 5
Distinctiveness Conflict Risk	The 'content inventory' niche is somewhat specific, but the broad phrasing ('all content', 'information assets') leaves meaningful overlap risk with related content/document skills.	3 / 5
	Total	12 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: dandye/ai-runbooks
Path: skills/inventory-content/SKILL.md
Commit: 72a6863

Reviewed: 6 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.