003-skills-inventory

Use when you need to generate a checklist document with Java system prompts from skills.xml, following the embedded section template and producing INVENTORY-SKILLS-JAVA.md. This should trigger for requests such as Create Java system prompts checklist; Generate INVENTORY-SKILLS-JAVA.md; Use @003-skills-inventory. Part of cursor-rules-java project

Quality

70%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

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

Quality

Content

50%

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 reasonable structure for generating an inventory checklist from skills.xml, with clear constraints and a logical workflow. However, it lacks concrete examples (sample XML input, expected output rows, validation commands) that would make it truly actionable, and includes generic edge-case boilerplate that doesn't add value specific to this task. The validation step needs a concrete mechanism or feedback loop to be fully effective.

Suggestions

Add a concrete example showing a sample skills.xml entry and the corresponding row it should produce in INVENTORY-SKILLS-JAVA.md

Provide a specific validation mechanism in step 3 (e.g., a count comparison or a script) and describe what to do if validation fails

Remove or condense the generic edge-case bullets (ambiguous goal, missing context, conflicting changes) which are not specific to this skill and waste tokens

Include a brief example of the expected output format (even 2-3 rows of the checklist) so Claude knows exactly what to produce

Dimension	Reasoning	Score
Conciseness	The skill has some unnecessary verbosity — the 'What is covered in this Skill?' section restates what's already clear from the title and workflow, and the edge case bullets are generic boilerplate not specific to this task. However, the constraints and workflow sections are reasonably tight.	2 / 3
Actionability	The workflow describes what to do at a conceptual level (read files, generate document, validate coverage) but provides no concrete code, commands, or examples of the expected output format. There's no sample row, no XML parsing snippet, and no example of what INVENTORY-SKILLS-JAVA.md should look like.	2 / 3
Workflow Clarity	The three-step workflow is clearly sequenced and includes a validation step (step 3), but the validation is vague ('verify that the generated file contains every effective skill id') with no concrete mechanism or command for performing the check. The feedback loop for what to do if validation fails is missing.	2 / 3
Progressive Disclosure	The skill references `references/003-skills-inventory.md` for detailed guidance and examples, which is good progressive disclosure. However, since no bundle files were provided, we can't verify the reference exists or is well-structured. The main content includes some material that could be in the reference (like the generic edge cases) while lacking inline examples that would help without needing to read the reference.	2 / 3
	Total	8 / 12 Passed

Description

89%

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 is a reasonably well-crafted description that clearly identifies when to use the skill and provides distinct trigger terms tied to a specific project and output artifact. Its main weakness is that the 'what' portion could be more specific about the concrete actions performed beyond just 'generate a checklist document'. The description is distinctive enough to avoid conflicts with other skills.

Suggestions

Expand the specificity of actions — e.g., 'Parses skills.xml, extracts Java system prompts, formats them into a checklist using the embedded section template, and outputs INVENTORY-SKILLS-JAVA.md' to better describe the concrete steps.

Dimension	Reasoning	Score
Specificity	The description names a specific domain (generating a checklist document with Java system prompts from skills.xml) and mentions the output artifact (INVENTORY-SKILLS-JAVA.md), but the concrete actions are somewhat limited — it mainly says 'generate a checklist document' without listing multiple distinct operations.	2 / 3
Completeness	The description explicitly answers both 'what' (generate a checklist document with Java system prompts from skills.xml, producing INVENTORY-SKILLS-JAVA.md) and 'when' (opens with 'Use when...' and provides explicit trigger phrases like 'Create Java system prompts checklist').	3 / 3
Trigger Term Quality	The description includes several natural trigger terms users would say: 'Java system prompts checklist', 'Generate INVENTORY-SKILLS-JAVA.md', 'Use @003-skills-inventory', 'skills.xml', and 'cursor-rules-java'. These cover likely user phrasings well.	3 / 3
Distinctiveness Conflict Risk	The description is highly specific to a particular project (cursor-rules-java), a specific input file (skills.xml), and a specific output file (INVENTORY-SKILLS-JAVA.md), making it very unlikely to conflict with other skills.	3 / 3
	Total	11 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: jabrena/cursor-rules-java
Commit: b73c9d3

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