Orca CLI
stablyai/orca
Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser…
Change-aware next step advisor. An agent skill from sd0xdev/sd0x-harness.
Install Next Step
$ npx skills add sd0xdev/sd0x-harness --skill next-step -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sd0xdev/sd0x-harness next-step --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/sd0xdev/sd0x-harness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/next-step .claude/skills/next-step && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "next-step" agent skill from https://github.com/sd0xdev/sd0x-harness/tree/main/skills/next-step into .claude/skills/next-step/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "next-step", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/sd0xdev/sd0x-harness/tree/main/skills/next-stepType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add sd0xdev/sd0x-harness --skill next-step -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sd0xdev/sd0x-harness next-step --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sd0xdev/sd0x-harness.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/next-step .agents/skills/next-step && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "next-step" agent skill from https://github.com/sd0xdev/sd0x-harness/tree/main/skills/next-step into .agents/skills/next-step/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "next-step", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sd0xdev/sd0x-harness --skill next-step -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sd0xdev/sd0x-harness next-step --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sd0xdev/sd0x-harness.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/next-step .cursor/skills/next-step && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "next-step" agent skill from https://github.com/sd0xdev/sd0x-harness/tree/main/skills/next-step into .cursor/skills/next-step/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "next-step", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/sd0xdev/sd0x-harness.git --path skills/next-step--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add sd0xdev/sd0x-harness --skill next-step -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sd0xdev/sd0x-harness next-step --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sd0xdev/sd0x-harness.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/next-step .gemini/skills/next-step && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "next-step" agent skill from https://github.com/sd0xdev/sd0x-harness/tree/main/skills/next-step into .gemini/skills/next-step/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "next-step", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install sd0xdev/sd0x-harness next-stepInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add sd0xdev/sd0x-harness --skill next-step -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/sd0xdev/sd0x-harness.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/next-step .github/skills/next-step && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "next-step" agent skill from https://github.com/sd0xdev/sd0x-harness/tree/main/skills/next-step into .github/skills/next-step/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "next-step", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sd0xdev/sd0x-harness --skill next-step -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install sd0xdev/sd0x-harness next-step --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sd0xdev/sd0x-harness.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/next-step .opencode/skills/next-step && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "next-step" agent skill from https://github.com/sd0xdev/sd0x-harness/tree/main/skills/next-step into .opencode/skills/next-step/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "next-step", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
next-step- GitHub stars
- 192
- Token cost
- ~1.6k tokens
- SKILL.md length
- 588 words
- Files
- 3 (incl. scripts, references)
- Skills in repo
- 91
- Repo updated
- First seen
- Licence
- MIT
At a glance
Change-aware next step advisor. An agent skill from sd0xdev/sd0x-harness.
- Works in 7 steps: Run bash scripts/run-skill.sh next-step… → Parse the JSON output — findings, gates,… → If P0/P1 findings exist → format top 3… → …
- : user asks what to do next
- SKILL.md covers When NOT to Use, Procedure, Script Integration and Dispatch Mode (--go flag), plus 7 more sections
- Runs JavaScript scripts from its folder; calls git, bash and node
What it does
Next Step is an agent skill from sd0xdev/sd0x-harness. Change-aware next step advisor. Use when: user asks what to do next, workflow progression is unclear, session just started with dirty worktree. Not for: executing the suggested command (user decides), auto-loop decisions (hooks handle that). Output: findings-based suggestions or session summary with commit seed.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts and reference files (for example `references/progression-tables.md` and `scripts/analyze.js`).
It sits in Agent Workflows, covering Session handoff and Git worktrees. The repository describes itself as: The harness layer for Claude Code — a reference implementation of harness engineering with hook-enforced dual review, state-machine gates that survive context compaction, and… The licence is MIT.
When your agent uses it
- : user asks what to do next
- Workflow progression is unclear
- Session just started with dirty worktree
Example prompts
- “/next-step”
Requirements
- Node.js
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Run bash scripts/run-skill.sh next-step analyze.js to collect deterministic findings
- Parse the JSON output — findings, gates, diff summary, phase, feature_context, next_actions, backlog
- If P0/P1 findings exist → format top 3 as actionable suggestions (Findings Mode)
- If mid-pipeline (gates not all passed, no P0/P1) → use progression tables to suggest next step
- If phase = post_precommit → suggest doc sync + request update (use next_actions)
- If phase = feature_complete → output feature complete summary with backlog
- If all gates pass and no P0/P1 → output session summary with commit seed (Summary Mode, P2/P3 shown as oversights)
What it can do on your machine
Read from SKILL.md and the folder at commit c9a2036. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (JavaScript), which the agent can run.
Shell commands in SKILL.md call:
gitbashnode
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Next Step loads about 1.6k tokens when it runs, and up to ~2.2k if it reads all its reference files. Until then it costs about 81 tokens; SKILL.md has 588 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from sd0xdev/sd0x-harness at commit c9a2036, republished under its MIT licence (© sd0xdev). 588 words, ~1,587 tokens.
Download SKILL.mdSave it as
.claude/skills/next-step/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- next-step
- description
- Change-aware next step advisor. Use when: user asks what to do next, workflow progression is unclear, session just started with dirty worktree. Not for: executing the suggested command (user decides), auto-loop decisions (hooks handle that). Output: findings-based suggestions or session summary with commit seed.
Next Step Advisor
When NOT to Use
- Auto-loop already handling review/precommit flow (hooks track and assist)
- User gave a clear, specific instruction (just do it)
- Mid-execution of a skill workflow (follow that skill's progression)
Procedure
- Run
bash scripts/run-skill.sh next-step analyze.jsto collect deterministic findings - Parse the JSON output — findings, gates, diff summary, phase, feature_context, next_actions, backlog
- If P0/P1 findings exist → format top 3 as actionable suggestions (Findings Mode)
- If mid-pipeline (gates not all passed, no P0/P1) → use progression tables to suggest next step
- If phase = post_precommit → suggest doc sync + request update (use next_actions)
- If phase = feature_complete → output feature complete summary with backlog
- If all gates pass and no P0/P1 → output session summary with commit seed (Summary Mode, P2/P3 shown as oversights)
Script Integration
The analyze script runs 18 deterministic heuristics against git state, review state, and feature context:
| Priority | Heuristics | Meaning |
|---|---|---|
| P0 | Gate missing (code review, doc review, precommit) | Required steps not completed |
| P1 | Test gap, security hotspot, migration risk, doc-sync-needed, request-stale, corpus-unreadable | Important oversights |
| P2 | README missing, skill-lint needed, locale drift, mixed concerns, ac-incomplete, intent-advisory (planning docs without exact intent-<key>.md) | Quality improvements |
| P3 | Main branch warning, requirements-advisory, feature-complete | Informational |
The script exits with code 0 (no P0/P1), 1 (has P1), or 2 (has P0).
Output Fields (v2)
| Field | Type | Description |
|---|---|---|
| phase | string | mid_development / post_precommit / ready_to_commit / feature_complete / clean |
| feature_context | object | { key, source, confidence, docs_path, has_tech_spec, has_requirements, has_requests } |
| next_actions | array | [{ id, command, args, reason, confidence }] sorted by confidence desc |
| backlog | object/null | { total_features, incomplete_features } — only when phase = feature_complete |
Script Failure Fallback
If the script fails or is unavailable, fall back to manual signal collection:
| # | Signal | How |
|---|---|---|
| 1 | Git branch | git branch --show-current |
| 2 | Git status | git status -sb |
| 3 | Changed files | git diff --name-only HEAD + git status --porcelain (for untracked) |
| 4 | Gate state | node scripts/review-state.js check --format=fact（installed copy first: .claude/scripts/review-state.js；checker 不在 → 不主張任何 verdict） |
Then use the Progression Tables below.
Show full SKILL.md (274 more words)Show less
Dispatch Mode (--go flag)
When --go is provided, auto-execute the top next_action IF:
next_actions[0]exists ANDconfidence >= 0.8- No P0 findings
- Command is not null
Output: "Auto-dispatching: [command] [args]" then invoke the Skill tool and report the result.
Safety constraints:
- NEVER dispatch on P0. Fall back to advisory mode if confidence < 0.8.
- Only skill slash-commands from
next_actionsare dispatched (via Skill tool). No arbitrary shell execution. - Arguments are limited to file paths and flags extracted by
buildNextActions— no user-supplied strings.
Progression Tables (mid-pipeline fallback)
See references/progression-tables.md for full work-type detection and step-by-step progression tables (Feature Dev, Bug Fix, Docs, Refactoring, Investigation).
Output Format — Findings Mode
When the script detects actionable findings, format the top 3:
📍 [work type] | [branch] | [current phase]
⚠️ Findings ([count]):
1. **[P0/P1/P2] [finding id]** — [message] → [suggestion]
2. **[P0/P1/P2] [finding id]** — [message] → [suggestion]
3. **[P0/P1/P2] [finding id]** — [message] → [suggestion]
[+N more if suppressed]
➡️ Next: [primary action based on highest priority finding]Output Format — Session Summary (all gates pass, no P0/P1)
When all gates pass and no actionable findings remain, summarize the session instead of suggesting "commit/push":
📍 [work type] | [branch] | all gates passed
✅ Session Summary:
- [what was accomplished, derived from diff summary and conversation]
- [key changes: N files changed, types of changes]
⚠️ Oversights (if any P2/P3 remain):
- [P2/P3 findings as optional improvements]
💬 Commit seed:
[type]: [concise description of all changes]The commit seed is a suggestion — the user decides the final message.
Output Format — Feature Complete (phase = feature_complete, backlog exists)
📍 [work type] | [branch] | feature complete
✅ Feature [key] Complete
- All gates passed, no sync issues remaining
📋 Backlog ([N] incomplete):
- [feature-key] — status: [status], unchecked AC: [count]
- ...
➡️ Next: Pick a feature from the backlog or start new workDocument Completeness Check
When a feature directory exists in docs/features/, cross-check document pairs:
| State | Suggest |
|---|---|
| tech-spec exists, no request | /create-request |
| request exists, no tech-spec | /tech-spec |
| Both exist, code changed | /update-docs + /create-request --update |
Non-Command Suggestions
When the best next step is NOT a slash command:
| Signal | Suggest |
|---|---|
| Requirements unclear | "Confirm requirements with PM/user before proceeding" |
| Affects other services | "Confirm upstream/downstream API contracts" |
| Security-sensitive change | /codex-security before proceeding |
| No clear task | "Clarify what to do — don't start without clear requirements" |
| Session just started, dirty worktree | "Handle uncommitted changes first" |
Verification
- Script ran successfully (or fallback used)
- Findings formatted with priority and actionable suggestions
- Session summary includes commit seed when all clear
- Non-command suggestions used when appropriate
© sd0xdev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (scripts, references) in skills/next-step of sd0xdev/sd0x-harness.
- SKILL.md
- references/progression-tables.md
- scripts/analyze.js
Open the folder on GitHubat commit c9a2036
Compare with similar skills
Next Step next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Next Step this skillsd0xdev/sd0x-harness | 192 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Orca CLIstablyai/orca | 87k | 2 repos | ~593 | Automated safety check: Pass | MIT | |
| Agent Manager Fleet TUIYoanWai/agent-manager | 572 | — | ~1k | Automated safety check: Pass | Apache-2.0 | |
| Ccmanager Configkbwo/ccmanager | 1.3k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Beads Task Memorygastownhall/beads | 28k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Using Git Worktreesjulianromli/opencode-template | 144 | 27 repos | ~1.4k | Automated safety check: Pass | None |
Similar skills
Agent Manager Fleet TUI
YoanWai/agent-manager
Runs several coding-agent CLIs as real tmux sessions in one terminal UI, color-coded by whether each is working, waiting, idle or blocked.
Ccmanager Config
kbwo/ccmanager
Set up, review, or repair a CCManager config — .ccmanager.json at a git repository root, or the global ~/.config/ccmanager/config.json.
Beads Task Memory
gastownhall/beads
Tracks multi-session work with dependencies in the bd issue tracker so the agent can find ready tasks and recover its context after conversation compaction.
Using Git Worktrees
julianromli/opencode-template
A skill your agent uses when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory…
Using Git Worktrees
farm-fe/farm
A skill your agent uses when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git…
More from sd0xdev/sd0x-harness
All 91 skills in this repoAdr
sd0xdev/sd0x-harness
Write an Architecture Decision Record (ADR) for a feature — Context / Decision / Status / Consequences / Alternatives, filed as docs/features/<feature/adr-<NNN-<title.md with a 3-digit zero-padded…
Load PR Review
sd0xdev/sd0x-harness
Load GitHub PR review comments into AI session — analyze, triage, plan.
Obsidian CLI
sd0xdev/sd0x-harness
Obsidian vault integration via official CLI. An agent skill from sd0xdev/sd0x-harness.
Orchestrate
sd0xdev/sd0x-harness
Agent-driven workflow orchestration (v1 report-only). An agent skill from sd0xdev/sd0x-harness.
PR Comment
sd0xdev/sd0x-harness
Post friendly review comments to a GitHub PR — prepare locally, preview, then submit as atomic review.
Project Audit
sd0xdev/sd0x-harness
Project health audit with deterministic scoring. An agent skill from sd0xdev/sd0x-harness.
Related
Categories
Questions about Next Step
What does Next Step do?
Change-aware next step advisor. An agent skill from sd0xdev/sd0x-harness. Next Step is an agent skill from sd0xdev/sd0x-harness. Change-aware next step advisor.
When should I use Next Step?
Next Step fits situations like: : user asks what to do next; workflow progression is unclear; session just started with dirty worktree.
How do I install Next Step in Claude Code?
Run `npx skills add sd0xdev/sd0x-harness --skill next-step -a claude-code`. Or copy the skill folder (skills/next-step in sd0xdev/sd0x-harness) into .claude/skills/next-step in your project. Claude Code loads it when a task matches its description.
How do I install Next Step in Codex?
Run `npx skills add sd0xdev/sd0x-harness --skill next-step -a codex`. Or copy the skill folder (skills/next-step in sd0xdev/sd0x-harness) into .agents/skills/next-step in your project. Codex loads it when a task matches its description.
Can I use Next Step in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sd0xdev/sd0x-harness --skill next-step -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/next-step, .gemini/skills/next-step, .github/skills/next-step and .opencode/skills/next-step in your project.
What does Next Step need to run?
Going by SKILL.md and its folder, Next Step needs JavaScript for the scripts in its folder and the command-line tools its instructions call (git, bash and node). Our summary lists: Node.js.
Does Next Step access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Next Step safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Next Step use?
Next Step is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Next Step use?
About 1.6k tokens (SKILL.md is roughly 6.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 570 tokens, read only when the agent opens those files.
What are the alternatives to Next Step?
Skills that share tags, products or a category with Next Step: Orca CLI (stablyai/orca, 87k stars), Agent Manager Fleet TUI (YoanWai/agent-manager, 572 stars), Ccmanager Config (kbwo/ccmanager, 1.3k stars) and Beads Task Memory (gastownhall/beads, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Next Step?
sd0xdev (a GitHub user) maintains it in sd0xdev/sd0x-harness, which has 192 GitHub stars. The repository holds 91 skills in this directory. The repository was last updated on October 6, 2026.
Source: sd0xdev/sd0x-harness on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.