Skip to content
Back to skills

2784 Royal Marines 92007cea

ASecurity

Royal Marines are short-lived sub-agents a captain deploys for focused, independent objectives in service of the ship's task. They are doctrinally distinct from crew: crew subdivide the ship's deliverable, marines execute discrete sorties and return.

  • 9 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 11, 2026
devops

Security analysis

A100/100

Scanned October 11, 2026

npx -y skills add tools-only/X-Skills --skill 2784-royal-marines_92007cea --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of 2784 Royal Marines 92007cea?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for 2784 Royal Marines 92007cea
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tools-only-2784-royal-marines-92007cea/badge)](https://www.skillsdirectory.com/skills/tools-only-2784-royal-marines-92007cea)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

SKILL.md
# Royal Marines

Royal Marines are short-lived sub-agents a captain deploys for focused, independent objectives in service of the ship's task. They are doctrinally distinct from crew: crew subdivide the ship's deliverable, marines execute discrete sorties and return.

## Deploy-or-Escalate Decision

Choose the first condition that matches.

1. Quick recon of unfamiliar area → **Recce Marine**
2. Targeted fix or small implementation to unblock ship → **Assault Marine**
3. Quick config/build/infra task → **Sapper**
4. Sustained work, own deliverable, needs file ownership → **NOT a marine.** Request a new ship from the admiral.
5. Work that subdivides the ship's main deliverable → **NOT a marine.** Crew the role instead.

## Marine Specialisations

| Type | Function | subagent_type | Use case |
|---|---|---|---|
| Recce Marine | Reconnaissance & intel gathering | Explore (read-only) | Scout unfamiliar code, gather findings |
| Assault Marine | Direct action, targeted changes | general-purpose | Small fix, unblock a dependency |
| Sapper | Engineering support | general-purpose | Quick config, build, infra task |

### Read-Only Specialisation

Recce Marines use the `Explore` subagent type. They cannot modify files. They report findings to the captain, who decides how to act on them.

## Deployment Rules

- **Max 2 marines per ship at any time.** If the task needs more, it is crew work or a new ship.
- **Marines cannot deploy marines.** No recursion permitted.
- **Marines report only to their deploying captain.** They do not communicate with crew or other ships.
- **Captain must verify marine output** before incorporating it into the ship's deliverable.
- **Marines do not get ship names.** Identify them as: `RM Detachment, HMS [Ship] — [objective]`.

## Action Station Interaction

Marine deployments inherit the parent ship's station tier:

- **Station 0-1:** Captain deploys at discretion. No admiral approval required.
- **Station 2:** Captain must signal admiral and receive approval before deploying marines.
- **Station 3:** Marine deployment is not permitted. All Trafalgar-tier work requires explicit Admiralty (human) confirmation.

## Recovery

Marine recovery is simple. No separate damage-control procedure is needed.

- If a marine is stuck or unresponsive, captain **abandons the deployment**.
- Captain either redeploys a fresh marine or handles the objective directly.
- If the same marine objective fails twice, captain **escalates to admiral**.

## Deployment Template

When deploying a marine, use the briefing template at `admiralty-templates/marine-deployment-brief.md`.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.