001-commands-inventory

Use when you need to generate a checklist document with embedded commands inventory, following the embedded template exactly and producing INVENTORY-COMMANDS-JAVA.md in the project root. This should trigger for requests such as Create embedded commands inventory checklist; Generate INVENTORY-COMMANDS-JAVA.md; Use @001-commands-inventory; Inventory embedded Java project commands; List command files bundled for Java agents. Part of Plinth Toolkit

Quality

76%

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/001-commands-inventory/SKILL.md

Quality

Content

75%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 well-organized, mostly lean instruction skill with concrete file targets and a validation step. The chief gaps are duplicated trigger/constraint content and a missing explicit validate-fix-retry feedback loop.

Suggestions

Remove the duplicated 'When to use' list from the body since those triggers already live in the frontmatter description, or replace it with a one-line pointer.

Turn step 3 into an explicit feedback loop: 'If validation finds extra rows or missing sections, fix the generated file and re-validate until it passes.'

Deduplicate the Constraints section against the Workflow step constraints so each rule appears in one place only.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, but the 'When to use' list duplicates the frontmatter triggers and the Constraints/Workflow step constraints repeat each other, leaving minor trim opportunities short of the top anchor.	4 / 5
Actionability	Concrete, specific guidance names the exact files to read (references/001-commands-inventory.md, assets/java-commands-inventory-template.md) and the exact output (INVENTORY-COMMANDS-JAVA.md in project root); the actual generated content is delegated to the authoritative template asset rather than inlined.	4 / 5
Workflow Clarity	A clear three-step sequence (read template, generate document, validate fidelity) with a validation checkpoint and EDGE CASE handling; falls short of 5 because there is no explicit error-recovery loop stating what to do if validation fails.	4 / 5
Progressive Disclosure	Well-signaled one-level-deep references to a guidance file and an authoritative template asset with a Reference section linking back; mild duplication between the SKILL.md body and references/001-commands-inventory.md keeps it just below the top anchor.	4 / 5
	Total	16 / 20 Passed

Description

78%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 strong, trigger-rich description that clearly states what and when with concrete output artifacts. Its main weaknesses are second-person voice and minor overlap risk within a broader toolkit family.

Suggestions

Rewrite the description in third person (e.g. 'Generates a checklist document...') to avoid the second-person 'you need' voice and recover the specificity penalty.

Add file extensions or a synonym (e.g. '.md', 'command catalogue') to broaden natural trigger term coverage toward the top anchor.

Tighten distinctiveness by noting the Java/embedded scope earlier so it cannot collide with sibling Plinth Toolkit inventory skills.

Dimension	Reasoning	Score
Specificity	Names concrete actions ('generate a checklist document with embedded commands inventory', 'following the embedded template exactly', 'producing INVENTORY-COMMANDS-JAVA.md in the project root') but uses second-person voice ('Use when you need to generate'), which per the rubric penalizes specificity by 1 from a base of 4.	3 / 5
Completeness	Explicitly answers both what (generate a template-faithful checklist producing INVENTORY-COMMANDS-JAVA.md) and when (explicit 'Use when...' clause with concrete trigger phrases), matching the top anchor.	5 / 5
Trigger Term Quality	Lists five natural trigger phrases users would say ('Create embedded commands inventory checklist', 'Generate INVENTORY-COMMANDS-JAVA.md', 'Use @001-commands-inventory', 'Inventory embedded Java project commands', 'List command files bundled for Java agents') — good coverage, though a few synonyms/extensions are missing.	4 / 5
Distinctiveness Conflict Risk	The specific output filename, @001-commands-inventory invocation, and Java scope give it a clear niche, but being 'Part of Plinth Toolkit' implies sibling inventory skills, creating minor overlap risk with closely related skills.	4 / 5
	Total	16 / 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/001-commands-inventory/SKILL.md
Commit: 77b8825

Reviewed: about 23 hours 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.