001 Commands Inventory Agent Skill
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
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/jabrena/plinth --skill 001-commands-inventoryThe instruction itself
5 sections, as written by the authorCreate 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
- 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
- Generate inventory document
Create INVENTORY-COMMANDS-JAVA.md in the project root using the exact wording and ordering from the reference template.
- 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.
Other skills for the same job
different authors, same section of the catalogue
Create time-boxed technical spike documents for researching and resolving critical development decisions before implementation.
Automatically convert Confluence specification documents into structured Jira backlogs with Epics and implementation tickets. When an agent needs to: (1) Create Jira tickets from a Confluence page, (2) Generate a backlog from a specification, (3) Break down a spec into implementation tasks, or (4) Convert requirements into Jira issues. Handles reading Confluence pages, analyzing specifications, creating Epics with proper structure, and generating detailed implementation tickets linked to the Epic.
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
Guidelines for clinical decision support (CDS) documents: biomarker-stratified cohort analyses and GRADE-graded treatment reports. Covers structure, executive summaries, evidence grading (1A–2C), stats (HR, CI, survival), and biomarker integration. Use for pharma research docs, clinical guidelines, regulatory submissions.
Generate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
Guides through Trail of Bits' 5-step secure development workflow. Runs Slither scans, checks special features (upgradeability/ERC conformance/token integration), generates visual security diagrams, helps document security properties for fuzzing/verification, and reviews manual security areas.
Document architecture decisions with ADR (Architecture Decision Records). Use when making significant technical decisions, choosing between alternatives, or when onboarding needs context on past decisions.
Plan-approval workflow patterns for user control over AI actions in Claude Code Waypoint Plugin. Use when planning complex changes, need user approval before execution, want to prevent mistakes, or need to document proposed changes. Covers plan creation, approval checkpoints, plan deviation tracking, revision management, and learning from approved/rejected plans.
How to use it
Take jabrena/001-commands-inventory from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.