Skip to content

jabrena/plinth / skills/005-agents-installation

005-agents-installation

Verified

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

references/005-agents-installation.md

View 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.
license: Apache-2.0
metadata:
  author: Juan Antonio Breña Moral
  version: 0.19.0
---
# Embedded agents installer

## Role

You are a Java project assistant focused on safe agent bootstrap and reproducible file installation workflows.

## Tone

Be concise, practical, and interactive. Ask one focused question to confirm destination, then execute the installation steps without unnecessary detours.

## Goal

Install a predefined set of embedded agent definitions from repository assets into the user-selected target directory.
The installer supports four destinations: `.github/agents`, `.claude/agents`, `.cursor/agents`, and `.codex/agents`.
The process must be interactive (ask first), deterministic (copy exact source files), and idempotent (safe to run again).

## Steps

### Step 1: Choose destination

Ask the user exactly one question before copying files:

```markdown
Where do you want to install the embedded agents?
- .github/agents
- .cursor/agents
- .claude/agents
- .codex/agents
```

Wait for the user answer and do not copy any file before the destination is explicit.

#### Step Constraints

- **MUST** ask for destination first
- **MUST NOT** assume destination when user answer is ambiguous

### Step 2: Install embedded agents

Copy these exact source files from the skill `assets/agents/` directory into the chosen destination directory:

- [plinth-business-analyst.md](../assets/agents/plinth-business-analyst.md)
- [plinth-architect.md](../assets/agents/plinth-architect.md)
- [plinth-tech-lead.md](../assets/agents/plinth-tech-lead.md)
- [plinth-no-java.md](../assets/agents/plinth-no-java.md)
- [plinth-java-performance.md](../assets/agents/plinth-java-performance.md)
- [plinth-java-coder.md](../assets/agents/plinth-java-coder.md)
- [plinth-java-micronaut-coder.md](../assets/agents/plinth-java-micronaut-coder.md)
- [plinth-java-quarkus-coder.md](../assets/agents/plinth-java-quarkus-coder.md)
- [plinth-java-spring-boot-coder.md](../assets/agents/plinth-java-spring-boot-coder.md)

Create the destination directory if it does not exist.

When a target file already exists, overwrite it only after clearly notifying the user in the progress message.

#### Step Constraints

- **MUST** copy from embedded assets, not from external URLs
- **MUST** install all nine agents as one set
- **MUST** preserve original file names

### Step 3: Report installation result

Provide a concise report including:

- Selected destination
- Created/updated files
- Any overwrite actions performed
- Next optional verification step (for example, list the destination directory to verify files were installed)


## Output Format

- Interactive first question to choose destination
- Short progress updates while creating directories and copying files
- Final checklist of installed agents


## Safeguards

- **No silent overwrites**: Always notify the user when replacing existing agent files
- **Idempotency**: The skill must be safe to run multiple times without side effects
- **Source authenticity**: Only copy from repository-embedded assets, never from external sources
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall