agentleFS
Sign inStart free
jabrenajabrena/cursor-rules-java/skills/003-skills-inventory/SKILL.md

003-skills-inventory

Skill452 starsChanged 3 months agoApache-2.0View on GitHub

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

We split this skill into the rules it gives an agent

15 rules. About 0 are common, 6 are distinctive, and 9 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 9

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Create a comprehensive step-by-step checklist document for Java system prompts by following the embedded section template and deriving rows …

    line 11
  2. Very specific:

    Follow the template sections exactly and use skills.xml as the single source of truth for skill rows.

    line 21
  3. Distinctive:

    DO NOT: create additional sections beyond what the template defines

    line 23
  4. Very specific:

    DO NOT: add skill rows absent from skills.xml

    line 24
  5. Very specific:

    ONLY: use the skillId attribute as the generated skill id when it exists

    line 26
  6. Very specific:

    ONLY: use the single reference-list/reference value as the generated skill id when skillId is absent

    line 27
  7. Distinctive:

    EDGE CASE: If the user goal is ambiguous, stop and ask a clarifying question before editing files or running project-wide commands

    line 28
  8. Distinctive:

    EDGE CASE: If required context, files, credentials, or tools are missing, report the blocker explicitly and ask whether to proceed with …

    line 29
  9. Distinctive:

    EDGE CASE: If requested changes conflict with project constraints or safety boundaries, explain the conflict and ask for user confirmation …

    line 30
  10. Distinctive:

    Create Java system prompts checklist

    line 34
  11. Very specific:

    Read references/003-skills-inventory.md and plinth-skills-generator/src/main/resources/skills.xml before generating output.

    line 44
  12. Distinctive:

    Do not use cached or remembered template content

    line 47
  13. Very specific:

    Use skillId when present; otherwise use the single reference name

    line 49
  14. Very specific:

    Create INVENTORY-SKILLS-JAVA.md at the requested output path, or in the project root when no explicit path is requested, with one row for …

    line 53
  15. Very specific:

    Verify that the generated file contains every effective skill id from skills.xml, contains no extra skill rows, and preserves all expected …

    line 57

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Create a Checklist with all Java steps to use with system prompts for Java

Create a comprehensive step-by-step checklist document for Java system prompts by following the embedded section template and deriving rows from plinth-skills-generator/src/main/resources/skills.xml.

What is covered in this Skill?

  • Inventory-driven checklist generation
  • Output file creation as INVENTORY-SKILLS-JAVA.md
  • Strict coverage of every effective skill id declared in skills.xml

Constraints

Follow the template sections exactly and use skills.xml as the single source of truth for skill rows.

  • DO NOT create additional sections beyond what the template defines
  • DO NOT add skill rows absent from skills.xml
  • DO NOT omit any skill declared in skills.xml
  • ONLY use the skillId attribute as the generated skill id when it exists
  • ONLY use the single reference-list/reference value as the generated skill id when skillId is absent
  • EDGE CASE: If the user goal is ambiguous, stop and ask a clarifying question before editing files or running project-wide commands
  • EDGE CASE: If required context, files, credentials, or tools are missing, report the blocker explicitly and ask whether to proceed with setup or fallback guidance
  • EDGE CASE: If requested changes conflict with project constraints or safety boundaries, explain the conflict and ask for user confirmation on the preferred trade-off

When to use this skill

  • 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

Workflow

  1. Read the template and inventory source

Read references/003-skills-inventory.md and plinth-skills-generator/src/main/resources/skills.xml before generating output.

Step constraints:

  • Do not use cached or remembered template content
  • Preserve exact section structure from the reference
  • Use skillId when present; otherwise use the single reference name
  1. Generate inventory document

Create INVENTORY-SKILLS-JAVA.md at the requested output path, or in the project root when no explicit path is requested, with one row for every effective skill id declared in skills.xml.

  1. Validate inventory coverage

Verify that the generated file contains every effective skill id from skills.xml, contains no extra skill rows, and preserves all expected sections from the reference.

Reference

For detailed guidance, examples, and constraints, see references/003-skills-inventory.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free