jabrena/plinth / skills/004-commands-installation
004-commands-installation
VerifiedUse 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
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.9 KB |
| assets/commands/benchmark.md | markdown | 2.0 KB |
| assets/commands/close-spec.md | markdown | 1.7 KB |
| assets/commands/create-acceptance-criteria.md | markdown | 6.2 KB |
| assets/commands/create-adr.md | markdown | 1.3 KB |
| assets/commands/create-diagram.md | markdown | 1.4 KB |
| assets/commands/create-feature-branch.md | markdown | 3.0 KB |
| assets/commands/create-spec.md | markdown | 3.5 KB |
| assets/commands/create-worktree.md | markdown | 3.1 KB |
| assets/commands/explore-design.md | markdown | 4.6 KB |
| assets/commands/explore-problem.md | markdown | 6.7 KB |
| assets/commands/implement-spec.md | markdown | 11.6 KB |
| assets/commands/onboarding.md | markdown | 5.9 KB |
| assets/commands/profile.md | markdown | 1.9 KB |
| assets/commands/update-issue.md | markdown | 1.8 KB |
| references/004-commands-installation.md | markdown | 3.5 KB |
assets/commands/benchmark.md
View on GitHub---
description: 'Design and coordinate a reproducible Java performance test.'
argument-hint: '[target]'
model: 'inherit'
agent: 'plinth-java-performance'
tools:
- 'Read'
- 'Write'
- 'Edit'
- 'Bash'
metadata:
author: 'Juan Antonio Breña Moral'
version: '0.19.0'
---
# benchmark
Select and coordinate an appropriate Java performance test with reproducible workload, environment, thresholds, and result artifacts.
## Usage
```text
/benchmark <target> [objective-or-threshold] [workload] [environment] [preferred-tool]
```
## Accepted inputs
- Target application, endpoint, workflow, method, or component
- Performance objective or threshold
- Expected workload and environment
- Optional preferred tool
## Owner and skills
- Owner: `@plinth-java-performance`
- Associated skills: `@151-java-performance-jmeter`, `@152-java-performance-gatling`, and existing Maven/JMH guidance
## Tool selection
| Need | Tool |
| --- | --- |
| HTTP/API load and performance test | JMeter or Gatling |
| Scenario-oriented load model and reports | Gatling |
| Isolated JVM method or component microbenchmark | JMH |
## Workflow
1. Clarify target boundary, objective, thresholds, workload, and environment.
2. Select JMeter, Gatling, or JMH and record the rationale.
3. Define warm-up, duration, concurrency, data setup, and result artifacts.
4. Generate or coordinate the reproducible performance workflow using the selected skill or Maven/JMH guidance.
5. Evaluate results against explicit thresholds.
6. Report limitations, environment metadata, and whether results are comparable.
## Output
- Selected tool and rationale
- Reproducible test configuration
- Baseline or result artifacts
- Threshold assessment
- Limitations and environment metadata
## Safeguards
- Do not present non-equivalent runs as valid before/after comparisons.
- Do not use JMeter or Gatling for isolated JVM microbenchmarks when JMH is the correct boundary.
- Do not use JMH for end-to-end load behavior.
- Keep workload, environment, and threshold assumptions explicit.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| 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: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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 available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |