CtrlK
BlogDocsLog inGet started
Tessl Logo

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; Inventory Java cursor rule skills; List available Java system prompt skills. Part of Plinth Toolkit

63

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

57%

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

The skill body is well-organized with a clear workflow and good progressive disclosure to a single verified reference, but it carries redundant trigger/constraint text and lacks both an in-body output example and an explicit validation feedback loop. Tightening the duplication and adding a concrete row example with a retry step would lift it toward the top anchors.

Suggestions

Remove the standalone "When to use this skill" section (or replace it with a one-line pointer) since its trigger phrases already appear verbatim in the frontmatter description, and de-duplicate the id-derivation rules between the Constraints section and Workflow step 1.

Add a short in-body example of one or two populated inventory rows so the expected output format is actionable without opening the reference file.

Extend the Validate step into a feedback loop: state explicitly what to do when rows are missing or extra (re-read skills.xml, fix the rows, re-run validation) before finishing.

DimensionReasoningScore

Conciseness

The body avoids explaining concepts Claude already knows, but the "When to use this skill" section repeats the trigger phrases already in the frontmatter and Workflow step 1 restates constraints from the Constraints section, so not every token earns its place.

2 / 3

Actionability

It gives concrete files, paths, and id-derivation rules, but the actual row template lives only in the reference and no in-body output example is provided, leaving the guidance incomplete without the referenced file.

2 / 3

Workflow Clarity

A clear 3-step sequence includes an explicit validation step (verify coverage, no extra rows, preserved sections), but it lacks a fix-and-retry feedback loop on validation failure, which the rubric caps at 2 for batch operations.

2 / 3

Progressive Disclosure

The body is a concise overview with a single clearly-signaled one-level-deep reference to references/003-skills-inventory.md (a real file), with content appropriately split and easy navigation.

3 / 3

Total

9

/

12

Passed

Description

90%

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 communicates both purpose and trigger conditions with explicit, natural-sounding trigger phrases and a well-scoped niche. Its only weakness is that it describes a single concrete action rather than a comprehensive set of multiple actions, leaving specificity just below the top anchor.

DimensionReasoningScore

Specificity

The description names the concrete action ("generate a checklist document with Java system prompts from skills.xml ... producing INVENTORY-SKILLS-JAVA.md") with source, template, and output specifics, but it is a single action rather than the multiple concrete actions the score-3 anchor requires.

2 / 3

Completeness

It explicitly answers "what" (generate the checklist from skills.xml into INVENTORY-SKILLS-JAVA.md) and "when" ("Use when you need to generate..." plus "This should trigger for requests such as..."), satisfying both halves.

3 / 3

Trigger Term Quality

Five explicit trigger phrases are listed ("Create Java system prompts checklist", "Generate INVENTORY-SKILLS-JAVA.md", "List available Java system prompt skills"), giving good coverage of natural terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

A narrow niche anchored to a specific source file (skills.xml) and a specific output filename (INVENTORY-SKILLS-JAVA.md) makes it clearly distinguishable and unlikely to trigger for the wrong skill.

3 / 3

Total

11

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
jabrena/plinth
Reviewed

Table of Contents

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.