agentleFS
jabrenajabrena/cursor-rules-java/skills/001-commands-inventory/SKILL.md

001-commands-inventory

Skill452 starsChanged 3 months agoApache-2.0View on GitHub

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

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 10 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create a comprehensive checklist document for embedded commands inventory by following the embedded template exactly.

    line 11
  2. Distinctive:

    Follow the template exactly without adding or removing sections, rows, or command entries.

    line 21
  3. Distinctive:

    DO NOT: create additional rows beyond what the template defines

    line 23
  4. Distinctive:

    DO NOT: add command entries not explicitly listed in the template

    line 24
  5. Distinctive:

    ONLY: use exact wording and structure from the embedded template

    line 25
  6. Distinctive:

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

    line 26
  7. Distinctive:

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

    line 27
  8. Distinctive:

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

    line 28
  9. Distinctive:

    Create embedded commands inventory checklist

    line 32
  10. Very specific:

    Read references/001-commands-inventory.md and assets/java-commands-inventory-template.md before generating output and use the asset as the …

    line 42
  11. Distinctive:

    Do not use cached or partial template content

    line 45
  12. Very specific:

    Create INVENTORY-COMMANDS-JAVA.md in the project root using the exact wording and ordering from the reference template.

    line 50

≈ “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 embedded commands inventory for Java

Create a comprehensive checklist document for embedded commands inventory by following the embedded template exactly.

What is covered in this Skill?

  • Exact-template checklist generation
  • Output file creation as INVENTORY-COMMANDS-JAVA.md
  • Strict adherence to listed sections and content

Constraints

Follow the template exactly without adding or removing sections, rows, or command entries.

  • DO NOT create additional rows beyond what the template defines
  • DO NOT add command entries not explicitly listed in the template
  • ONLY use exact wording and structure from the embedded template
  • 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 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

Workflow

  1. Read the embedded template

Read references/001-commands-inventory.md and assets/java-commands-inventory-template.md before generating output and use the asset as the authoritative template.

Step constraints:

  • Do not use cached or partial template content
  • Preserve exact table rows, headings, and structure from the reference
  1. Generate inventory document

Create INVENTORY-COMMANDS-JAVA.md in the project root using the exact wording and ordering from the reference template.

  1. Validate template fidelity

Confirm no extra command rows were introduced and all required reference sections are present in the generated file.

Reference

For detailed guidance, examples, and constraints, see references/001-commands-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.