inventory-content

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

Quality

26%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/inventory-content/SKILL.md

Quality

Discovery

17%

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

This description suffers from abstract, technical language that users wouldn't naturally use and completely lacks trigger guidance for when Claude should select it. While it attempts to describe a cataloging/inventory function, the vague terms 'information assets' and 'metadata and characteristics' fail to communicate concrete capabilities or distinguish it from other organizational skills.

Suggestions

Add an explicit 'Use when...' clause with natural trigger terms like 'list all files', 'create inventory', 'catalog documents', 'what content do I have'

Replace abstract terms with concrete actions: instead of 'metadata and characteristics', specify 'file sizes, creation dates, file types, folder structure'

Clarify what 'information assets' means - specify if this is for files, databases, documents, media, or other content types

Dimension	Reasoning	Score
Specificity	Names the domain ('information assets', 'inventories') and some actions ('cataloging', 'creates inventories'), but uses abstract language like 'metadata and characteristics' without specifying concrete actions like 'extract file sizes, dates, types'.	2 / 3
Completeness	Describes what it does (creates inventories with metadata) but completely lacks any 'Use when...' clause or explicit trigger guidance. No indication of when Claude should select this skill.	1 / 3
Trigger Term Quality	Uses technical/abstract terms like 'information assets', 'cataloging', and 'metadata' that users are unlikely to naturally say. Missing common terms users might use like 'list files', 'inventory', 'catalog content', or 'document what I have'.	1 / 3
Distinctiveness Conflict Risk	'Information assets' and 'content' are broad terms that could overlap with documentation, file management, or data organization skills. 'Inventories' provides some distinction but 'metadata and characteristics' is vague enough to conflict with other skills.	2 / 3
	Total	6 / 12 Passed

Implementation

35%

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

This skill provides a clear conceptual framework for content inventory but lacks the concrete, executable guidance Claude needs to actually perform the task. The workflow is well-structured but missing validation steps and error handling. The biggest gap is the absence of any code examples, file parsing patterns, or specific commands.

Suggestions

Add executable code examples for asset discovery (e.g., Python using os.walk or pathlib) and metadata extraction (e.g., parsing YAML frontmatter)

Include a concrete output example showing what the JSON/CSV/Markdown inventory should look like

Add validation checkpoints such as 'verify PATH exists and is readable before scanning' and error handling for inaccessible files

Provide specific patterns for extracting embedded metadata from common file types (Markdown frontmatter, PDF metadata, image EXIF)

Dimension	Reasoning	Score
Conciseness	The skill is reasonably efficient but includes some unnecessary elaboration like 'to support content governance and strategic planning' and verbose section headers. Could be tightened while preserving clarity.	2 / 3
Actionability	The skill describes what to do at a high level but provides no concrete code, commands, or executable examples. Steps like 'Recursively scan the PATH' and 'extract metadata' are vague without implementation details.	1 / 3
Workflow Clarity	Steps are clearly sequenced (1-4) with logical progression, but there are no validation checkpoints or error handling. No guidance on what to do if metadata extraction fails or files are inaccessible.	2 / 3
Progressive Disclosure	Content is reasonably organized with clear sections, but everything is inline in one file. For a skill of this complexity, examples of output formats or a separate reference for metadata extraction patterns would improve navigation.	2 / 3
	Total	7 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Repository: dandye/ai-runbooks
Commit: 4d132c7

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