agentleFS
Sign inStart free
jabrenajabrena/cursor-rules-java/skills/004-commands-installation/SKILL.md

004-commands-installation

Skill452 starsChanged 3 months agoApache-2.0View on GitHub

Use when you need to install the embedded project commands into command directories (.github/commands, .claude/commands, .cursor/command, .codex/commands), selecting the destination interactively and copying the embedded command definitions from project assets. This should trigger for requests such as Install embedded commands; Bootstrap .cursor/command; Bootstrap .claude/commands; Copy project commands; Install project command suite. Part of Plinth Toolkit

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    MUST: ask the user to choose one of four command destinations before installing

    line 24
  2. Distinctive:

    MUST: create the destination directory if it does not exist

    line 27

≈ “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

Embedded commands installer

Install a predefined set of embedded project commands from repository assets into a user-selected target directory. This is an interactive skill.

What is covered in this Skill?

  • Interactive target selection (.github/commands, .claude/commands, .cursor/commands, or .codex/commands)
  • Deterministic copy of all embedded commands defined via XInclude from assets/commands
  • Idempotent re-installation with clear overwrite reporting
  • Support for four command framework destinations

Constraints

This skill installs only the embedded project commands bundle and must ask for destination before writing files.

  • MUST ask the user to choose one of four command destinations before installing
  • MUST copy all embedded command files from skill assets/commands/
  • MUST preserve file names from the reference content and report overwrite actions
  • MUST create the destination directory if it does not exist

When to use this skill

  • Install embedded commands
  • Bootstrap .cursor/command from project assets
  • Bootstrap .claude/commands from embedded commands
  • Copy project commands into .codex/commands
  • Install command suite into .github/commands

Reference

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