002-agents-inventory

Use when you need to generate a checklist document with embedded agents inventory, following the embedded template exactly and producing INVENTORY-AGENTS-JAVA.md in the project root. This should trigger for requests such as Create embedded agents inventory checklist; Generate INVENTORY-AGENTS-JAVA.md; Use @002-agents-inventory; Inventory embedded Java agent definitions; List generated agent roles for Java development. Part of Plinth Toolkit

Quality

80%

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/002-agents-inventory/SKILL.md

Quality

Content

72%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 a concise, well-structured overview that delegates detail to a real template asset, but it lacks an explicit sequenced workflow and a validation checkpoint for its destructive overwrite behavior.

Suggestions

Add an explicit numbered workflow (read template -> generate INVENTORY-AGENTS-JAVA.md -> validate fidelity) instead of leaving the sequence implicit across Goal and Output Format.

Insert a validation checkpoint after generation that confirms all required template sections are present and no extra agent rows were introduced.

Guard the destructive overwrite: before replacing an existing INVENTORY-AGENTS-JAVA.md, confirm with the user or back up the prior file rather than silently overwriting.

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept over-explanation, but the template-adherence constraint is restated three times (MANDATORY line, four DO/ONLY bullets, and Output Format's Template Adherence bullet), which could be trimmed.	4 / 5
Actionability	Concrete instruction-only guidance with a specific filename, a real template asset path, project-root location, and explicit overwrite handling; the assembly step (read template then reproduce its content) is only implicit, leaving a minor gap.	4 / 5
Workflow Clarity	Steps are implicit across Goal/Output Format rather than sequenced, and the destructive overwrite operation has no validation checkpoint, capping this dimension at 3 per the rubric's destructive-operations rule.	3 / 5
Progressive Disclosure	Under 50 lines with well-organized sections and a single well-signaled one-level-deep reference to a real asset (../assets/java-agents-inventory-template.md) that holds the actual content, matching the simple-skill exception.	5 / 5
	Total	16 / 20 Passed

Description

87%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 is specific, well-triggered, and complete, clearly answering both what the skill does and when to invoke it with a distinctive niche. Minor room to add common synonyms for the trigger phrasing.

Dimension	Reasoning	Score
Specificity	Names several concrete actions — 'generate a checklist document with embedded agents inventory', 'following the embedded template exactly', and 'producing INVENTORY-AGENTS-JAVA.md in the project root' — which sits above the 3 anchor's 1-2 actions but short of 5's comprehensive coverage given the narrow single domain.	4 / 5
Completeness	Explicitly answers both what ('generate a checklist... following the embedded template exactly and producing INVENTORY-AGENTS-JAVA.md') and when ('Use when you need to generate...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good keyword coverage ('checklist document', 'agents inventory', 'embedded template', 'INVENTORY-AGENTS-JAVA.md') with a strong natural filename trigger, though common synonyms like 'list agents' or 'agent roles' are missing.	4 / 5
Distinctiveness Conflict Risk	Clear niche (embedded Java agents inventory with a distinct output filename) and specific triggers make overlap with other skills minimal.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: jabrena/plinth
Path: skills/002-agents-inventory/SKILL.md
Commit: 05bf9d1

Reviewed: 9 minutes 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.