005-agents-installation

$npx mdskill add jabrena/plinth/005-agents-installation

Install embedded robot agents into a selected target directory interactively.

  • User needs to bootstrap agent definitions into .github, .claude, .cursor, or .codex.
  • Depends on project assets in assets/agents and reference file references/005-agents-installation.md.
  • Asks user to choose target directory from four predefined options before copying.
  • Copies all embedded agent files deterministically and reports any overwrites.

SKILL.md

.github/skills/005-agents-installationView on GitHub ↗
---
name: 005-agents-installation
description: Use when you need to install the embedded robot agents into .github/agents, .claude/agents, .cursor/agents, or .codex/agents, selecting the destination interactively and copying the embedded agent definitions from project assets. This should trigger for requests such as Install embedded agents; Bootstrap .github/agents; Bootstrap .cursor/agents; Bootstrap .claude/agents; Bootstrap .codex/agents; Copy robot agents. Part of Plinth Toolkit
license: Apache-2.0
metadata:
  author: Juan Antonio Breña Moral
  version: 0.17.0
---
# Embedded agents installer

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

**What is covered in this Skill?**

- Interactive target selection (`.github/agents`, `.claude/agents`, `.cursor/agents`, or `.codex/agents`)
- Deterministic copy of all embedded agents defined via XInclude from `assets/agents`
- Idempotent re-installation with clear overwrite reporting

## Constraints

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

- **MUST** ask the user to choose `.github/agents`, `.claude/agents`, `.cursor/agents`, or `.codex/agents` before installing
- **MUST** copy all embedded agent files defined in `references/005-agents-installation.md`
- **MUST** preserve file names from the reference content and report overwrite actions

## When to use this skill

- Install embedded agents
- Bootstrap .github/agents
- Bootstrap .cursor/agents
- Bootstrap .claude/agents
- Bootstrap .codex/agents
- Copy robot agents

## Workflow

1. **Choose destination**

Ask exactly one question to choose `.github/agents`, `.claude/agents`, `.cursor/agents`, or `.codex/agents` and wait for an explicit answer before copying files.

Step constraints:
- Do not copy any file until destination is explicitly confirmed
- If destination is ambiguous, ask a clarification question

2. **Install embedded agents**

Create the destination directory if needed, then copy all embedded agent files defined in the reference content, preserving filenames and warning before overwriting existing files.

3. **Report installation result**

Return a concise checklist with selected destination, created/updated files, overwrite actions, and an optional verification command.

## Reference

For detailed guidance, examples, and constraints, see [references/005-agents-installation.md](references/005-agents-installation.md).

More from jabrena/plinth

SkillDescription
001-commands-inventoryUse 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
002-agents-inventoryUse when you need to generate a checklist document with embedded agents inventory, following the embedded template exactly and producing INVENTORY-AGENTS-JAVA.md in the project root. This should trigger for requests such as Create embedded agents inventory checklist; Generate INVENTORY-AGENTS-JAVA.md; Use @002-agents-inventory; Inventory embedded Java agent definitions; List generated agent roles for Java development. Part of Plinth Toolkit
003-skills-inventoryUse 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
004-commands-installationUse 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
012-agile-epicGuides the creation of agile epics with comprehensive definition including business value, success criteria, and breakdown into user stories. Use when the user wants to create an agile epic, define large bodies of work, break down features into user stories, or document strategic initiatives. This should trigger for requests such as Create an agile epic; Write an epic; I need to create an epic; Define an epic; Epic definition. Part of Plinth Toolkit
013-agile-featureGuides the creation of detailed agile feature documentation from an existing epic. Use when the user wants to split an epic into feature files, derive features with scope and acceptance criteria, or plan feature documentation for stakeholders or engineering. This should trigger for requests such as Create features from an epic; Split epic into features; Feature files from epic; Derive features from epic; Break down an agile epic into deliverable features. Part of Plinth Toolkit
014-agile-user-storyGuides the creation of agile user stories and Gherkin feature files. Use when the user wants to create a user story, write acceptance criteria, define Gherkin scenarios, or author BDD feature files. This should trigger for requests such as Create a user story; Write a user story; I need to write a user story; Create Gherkin scenarios for a user story; Split feature requirements into user stories. Part of Plinth Toolkit
030-architecture-adr-generalUse when you need to generate Architecture Decision Records (ADRs) for a Java project through an interactive, conversational process that systematically gathers context, stakeholders, options, and outcomes to produce well-structured ADR documents. This should trigger for requests such as Generate ADR; Create Architecture Decision Record; Document architecture decision; Architecture Decision Record for Java. Part of Plinth Toolkit
031-architecture-adr-functional-requirementsFacilitates conversational discovery to create Architectural Decision Records (ADRs) for functional requirements covering CLI, REST/HTTP APIs, or both. Use when the user wants to document command-line or HTTP service architecture, capture functional requirements, create ADRs for CLI or API projects, or design interfaces with documented decisions. This should trigger for requests such as Create ADR for functional requirements; Document functional requirements; Capture functional requirements; Generate functional requirements in an ADR; Decide CLI versus REST functional requirements for an ADR. Part of Plinth Toolkit
032-architecture-adr-non-functional-requirementsFacilitates conversational discovery to create Architectural Decision Records (ADRs) for non-functional requirements using the ISO/IEC 25010:2023 quality model. Use when the user wants to document quality attributes, NFR decisions, security/performance/scalability architecture, or design systems with measurable quality criteria. This should trigger for requests such as Create ADR for Non-functional requirements; Document Non-functional requirements; Capture Non-functional requirements; Generate Non-functional requirements in an ADR; Create ADR for performance scalability or security requirements. Part of Plinth Toolkit