Nelson skill
A Claude Code skill that runs multi-agent work by a naval metaphor: planning, parallel tasks with checkpoints, stand-down
- 424 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Spawns subagents and runs helper Python scripts
- Writes to a .nelson directory and coordinates changes in the project
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/nelsonDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Spawns subagents and runs helper Python scripts
- Writes to a .nelson directory and coordinates changes in the project
This is third-party code. Review the repository files before installing.
What it does
The skill gives the agent a workflow for coordinating several agents, framed as commanding a squadron. First it turns the user's brief into clear orders: outcome, metric, deadline, constraints and what is out of scope. Then it delegates work across agents, runs it in parallel with checkpoints and quality gates, and keeps a decision log. For failures it has ready procedures for rollback and session recovery. Every step leans on templates and references from the repository rather than improvisation.
Who it is for. For developers who run several agents on one task and want tight coordination with checkpoints.
Good fit when
- Work splits into parallel tasks for several agents
- You need quality gates and progress checkpoints
- You need a documented decision log as the task runs
Not a fit when
- The task is simple and a single agent needs no orchestration
- The agent is not Claude Code and does not support its plugin and hook format
Example request
Split the auth module refactor into parallel tasks and run them with checkpointsLimitations
The skill targets Claude Code and its plugin, hook and subagent model. It runs helper Python scripts for status and works with a .nelson directory in the project. It needs no keys or paid accounts. Its value depends on how well the task actually splits into parallel parts.
How to disable. Remove the nelson plugin via /plugin and optionally delete the .nelson directory from the project.
FAQ
Do I need a slash command?
No. Per the README the skill loads on its own when you describe the mission; a clear brief is enough.
What is the naval metaphor?
Roles, orders and procedures are framed in Royal Navy squadron terms: sailing orders, captain's log, damage reports. It is a wrapper over ordinary agent coordination.
Discussion
No questions or reviews yet.
Related
SkillsA skill that turns several Claude Code, Codex and Cursor windows into a team with a coordinator, shared registry and cross-review
31 skills for Claude Code and Codex: cross-vendor review, task handoff on low quota, a morning brief and a nightly retrospective
A skill that turns the main Claude Code session into a dispatcher: tasks go to background subagents and the chat never blocks.
Multi-agent orchestration for Claude Code: teams, roles, autopilot and task routing across skills and subagents
Anthropic skill for Claude Code that audits a multi-agent system and, by measurement, folds subagents into one loop with skills.
A skill that splits a task across twelve agents such as Codex, Claude Code and Cursor, sharing context and merging results.
README in short
The README presents Nelson as a work-organization process for Claude Code, inspired by Royal Navy procedures. The skill frames a task as sailing orders with outcome, metric and deadline, delegates work across agents, runs it in parallel with checkpoints and quality gates, and keeps a decision log. The repository holds report templates, role references and procedures for failures and recovery. It installs as a Claude Code plugin and loads automatically from a task description. MIT licensed.
README badge
Original SKILL.md
--- name: nelson description: Orchestrates multi-agent task execution using a Royal Navy squadron metaphor — from mission planning through parallel work coordination to stand-down. Use when work needs parallel agent orchestration, tight task coordination with quality gates, structured delegation with progress checkpoints, or a documented decision log. argument-hint: "[mission description]" paths: [".nelson/**"] --- # Nelson Execute this workflow for the user's mission. Write as Nelson's captains would write: concise, elegant, confident. ## 1. Issue Sailing Orders - Review the user's brief for ambiguity. If the outcome, scope, or constraints are unclear, ask the user to clarify before drafting sailing orders. - Write one sentence for `outcome`, `metric`, and `deadline`. - Set constraints: token budget, reliability floor, compliance rules, and forbidden actions. - Define what is out of scope. - Define stop criteria and required handoff artifacts.