New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Skill Status

by nyldn in nyldn/claude-octopus

Show where you are in the workflow and what to do next — use for progress checks and orientation

MITAuto-check: notesAgent Workflows

Install Skill Status

skills CLI
$ npx skills add nyldn/claude-octopus --skill skill-status -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install nyldn/claude-octopus skill-status --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/nyldn/claude-octopus.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/skill-status .claude/skills/skill-status && rm -rf skills-src

Use ~/.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/

Facts

Skill name
skill-status
GitHub stars
4.2k
Used in
1 other repo
Token cost
~2.9k tokens
SKILL.md length
708 words
Files
2
Skills in repo
62
Repo updated
First seen
Licence
MIT

At a glance

Show where you are in the workflow and what to do next — use for progress checks and orientation

  • Works in 9 steps: Check Project Initialization → Read Current State → Read Roadmap → …
  • Progress checks and orientation
  • SKILL.md covers Overview, When to Use, The Process and Example Outputs, plus 5 more sections
  • Calls git

What it does

Skill Status is an agent skill from nyldn/claude-octopus. Show where you are in the workflow and what to do next — use for progress checks and orientation

Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Agent Workflows. The repository describes itself as: Run multiple AI models against the same research, design, or coding task. Surface disagreements before you ship. The licence is MIT.

When your agent uses it

  • Progress checks and orientation

Example prompts

  • “/skill-status”

Workflow steps

9 steps, taken from the step headings in SKILL.md.

  1. Check Project Initialization
  2. Read Current State
  3. Read Roadmap
  4. Display Dashboard
  5. Intelligent Routing
  6. Recent Activity Summary (Cross-Session)
  7. Always Check for .octo/ First
  8. Use octo-state.sh for State Reading
  9. Provide Actionable Next Steps

What it can do on your machine

Read from SKILL.md and the folder at commit 4d152db. 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

    Shell commands in SKILL.md call:

    • git

    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

Skill Status loads about 2.9k tokens when it runs. Until then it costs about 27 tokens; SKILL.md has 708 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~27
When it runs · the whole SKILL.md, loaded when a task matches
~2.9k

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:319
    1. Configure OAuth credentials in .env

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from nyldn/claude-octopus at commit 4d152db, republished under its MIT licence (© nyldn). 708 words, ~2,941 tokens.

Download SKILL.mdSave it as .claude/skills/skill-status/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
skill-status
description
Show where you are in the workflow and what to do next — use for progress checks and orientation
disable-model-invocation
true

Host: Codex CLI — This skill was designed for Claude Code and adapted for Codex. Cross-reference commands use installed skill names in Codex rather than /octo:* slash commands. Use the active Codex shell and subagent tools. Do not claim a provider, model, or host subagent is available until the current session exposes it. For host tool equivalents, see skills/blocks/codex-host-adapter.md.

Project Status Dashboard

Overview

Display current project status, roadmap progress, blockers, and intelligent next-action suggestions based on workflow state.

Core principle: Read state → Display dashboard → Route intelligently.

When to Use

Use this skill when user asks:

  • "What's the status?" or "Show me progress"
  • "Where am I in the workflow?"
  • "What should I do next?"
  • "What's the current phase?"
  • "Are there any blockers?"
  • "What have I been working on?" or "Summarize recent work"
  • "Update project memory" or "Update CLAUDE.md"

Do NOT use for:

  • Creating new projects (use /octo:embrace)
  • Modifying state (use octo-state.sh write_state)
  • Detailed phase planning (use flow-* skills)

The Process

Phase 1: Check Project Initialization
Step 1: Verify .octo/ Directory Exists
bash
# Check if project is initialized
if [[ ! -d ".octo" ]]; then
    echo "No project initialized"
    exit 1
fi

If .octo/ does not exist:

markdown
## Project Status

**Status:** Not initialized

No Claude Octopus project found in this directory.

### Get Started

Run `/octo:embrace [your project description]` to initialize a new project and start the Double Diamond workflow.

**Example:**

/octo:embrace build a user authentication system


This will:
1. Create .octo/ directory structure
2. Initialize STATE.md, PROJECT.md, ROADMAP.md
3. Begin Discover phase (research and exploration)

Stop here - do not proceed to Phase 2.

Phase 2: Read Current State
Step 1: Execute octo-state.sh read_state
bash
# Read current state from STATE.md
./scripts/octo-state.sh read_state

Expected output format:

schema=1.0
last_updated=2026-02-02T10:30:00Z
current_phase=2
current_position=define-requirements
status=in_progress
Step 2: Parse State Variables

Extract key-value pairs:

  • current_phase - Phase number (1-4)
  • current_position - Specific position within phase
  • status - Current workflow status
  • last_updated - Last state modification timestamp
Phase 3: Read Roadmap
Step 1: Read ROADMAP.md
bash
# Read roadmap for phase overview
cat .octo/ROADMAP.md
Step 2: Extract Phase Information

Parse ROADMAP.md to identify:

  • Phase names (Discover, Define, Develop, Deliver)
  • Phase descriptions
  • Success criteria for each phase
  • Dependencies between phases
Phase 4: Display Dashboard
Step 1: Build Status Dashboard
markdown
## Project Status

**Phase:** Phase {current_phase} - {phase_name}
**Position:** {current_position}
**Status:** {status}
**Last Updated:** {last_updated}

### Roadmap Progress

- [x] Phase 1: Discover - complete
- [ ] Phase 2: Define - in_progress  <-- YOU ARE HERE
- [ ] Phase 3: Develop - not_started
- [ ] Phase 4: Deliver - not_started

### Current Phase Details

**Phase 2: Define (Grasp)**
- **Goal:** Clarify requirements and scope
- **Position:** {current_position}
- **Status:** {status}

### Blockers

{blockers or "None"}

### Suggested Next Action

{intelligent routing based on status}
Step 2: Determine Phase Completion Status

Map current_phase and status to completion markers:

PhaseStatusMarker
1complete[x] Phase 1: Discover - complete
2in_progress[ ] Phase 2: Define - in_progress <-- YOU ARE HERE
3not_started[ ] Phase 3: Develop - not_started
4not_started[ ] Phase 4: Deliver - not_started
Phase 5: Intelligent Routing
Step 1: Map Status to Suggestion

Use this routing table:

StatusSuggestion
ready"Run /octo:embrace [description] to start the workflow"
planning"Continue planning in current phase. Use /octo:define to refine requirements."
building"Continue implementation. Use /octo:develop to build features."
in_progress"Continue with current phase. Check .octo/phases/phase{N}/ for details."
blocked"Review blockers above. Use /octo:issues to track and resolve issues."
complete"Phase complete. Proceed to next phase or run /octo:ship to finalize."
complete_with_gaps"Phase complete with known gaps. Review .octo/ISSUES.md before proceeding."
shipped"Project delivered! Review .octo/LESSONS.md for retrospective."
paused"Project paused. Resume with /octo:embrace or check .octo/STATE.md for context."
Show full SKILL.md (292 more words)Show less
Step 2: Phase-Specific Routing

If status=in_progress, provide phase-specific guidance:

Phase 1 (Discover):

Continue research and exploration.
- Use `/octo:research [topic]` for multi-AI research
- Use `/octo:debate [question]` for decision support

Phase 2 (Define):

Continue requirements clarification.
- Use `/octo:prd` to write product requirements
- Use `/octo:define` to refine scope

Phase 3 (Develop):

Continue implementation.
- Use `/octo:develop` to build features
- Use `/octo:tdd` for test-driven development
- Use `/octo:review` for code quality checks

Phase 4 (Deliver):

Continue validation and delivery.
- Use `/octo:deliver` for final review
- Use `/octo:security` for security audit
- Use `/octo:ship` to finalize delivery

Example Outputs

Example 1: Project Not Initialized
markdown
## Project Status

**Status:** Not initialized

No Claude Octopus project found in this directory.

### Get Started

Run `/octo:embrace [your project description]` to initialize a new project and start the Double Diamond workflow.

**Example:**

/octo:embrace build a user authentication system

Example 2: Active Project in Define Phase
markdown
## Project Status

**Phase:** Phase 2 - Define (Grasp)
**Position:** define-requirements
**Status:** in_progress
**Last Updated:** 2026-02-02T10:30:00Z

### Roadmap Progress

- [x] Phase 1: Discover - complete
- [ ] Phase 2: Define - in_progress  <-- YOU ARE HERE
- [ ] Phase 3: Develop - not_started
- [ ] Phase 4: Deliver - not_started

### Current Phase Details

**Phase 2: Define (Grasp)**
- **Goal:** Clarify requirements and scope
- **Position:** define-requirements
- **Status:** in_progress

### Blockers

None

### Suggested Next Action

Continue requirements clarification.
- Use `/octo:prd` to write product requirements
- Use `/octo:define` to refine scope
- Check `.octo/phases/phase2/` for detailed plans
Example 3: Blocked Project
markdown
## Project Status

**Phase:** Phase 3 - Develop (Tangle)
**Position:** implement-auth
**Status:** blocked
**Last Updated:** 2026-02-02T14:15:00Z

### Roadmap Progress

- [x] Phase 1: Discover - complete
- [x] Phase 2: Define - complete
- [ ] Phase 3: Develop - blocked  <-- YOU ARE HERE
- [ ] Phase 4: Deliver - not_started

### Current Phase Details

**Phase 3: Develop (Tangle)**
- **Goal:** Implement features
- **Position:** implement-auth
- **Status:** blocked

### Blockers

- Missing OAuth provider credentials
- Database schema not finalized
- API rate limiting not configured

### Suggested Next Action

Review blockers above. Use `/octo:issues` to track and resolve issues.

**To unblock:**
1. Configure OAuth credentials in .env
2. Finalize database schema with `/octo:define`
3. Set up rate limiting configuration
Phase 6: Recent Activity Summary (Cross-Session)

When the user asks "what have I been working on", "summarize recent work", or "update project memory", generate a cross-session activity summary.

Step 1: Gather Recent Activity
bash
# Recent git commits (last 7 days or last 20 commits)
git log --oneline --since="7 days ago" --no-merges 2>/dev/null | head -20

# Recent tags/releases
git tag --sort=-creatordate | head -5

# Recent branches worked on
git branch --sort=-committerdate | head -5

# Recent orchestration results (if any)
ls -lt ~/.claude-octopus/results/ 2>/dev/null | head -10
Step 2: Summarize Activity

Build a concise summary grouped by theme:

markdown
## Recent Activity (Last 7 Days)

### Commits
- [theme 1]: brief summary of related commits
- [theme 2]: brief summary of related commits

### Releases
- v8.10.0 - Antigravity CLI headless fix
- v8.9.0 - Contextual Codex model routing

### Active Branches
- main (current)

### Orchestration Sessions
- [count] workflows executed, [count] synthesis files generated
Step 3: Suggest CLAUDE.md Updates

If the recent activity reveals patterns not captured in CLAUDE.md, suggest specific additions:

markdown
### Suggested CLAUDE.md Updates

Based on recent activity, consider adding:
- [specific suggestion based on new patterns, conventions, or decisions]
- [specific suggestion based on new tooling or workflow changes]

Only suggest updates that reflect durable project knowledge (conventions, architecture decisions, provider configs) — NOT transient status like "currently working on X".

Integration with Other Skills

With flow-* skills
User asks "what's next?"
→ skill-status shows current phase
→ User runs /octo:develop to continue
With skill-task-management
User asks "show status"
→ skill-status displays dashboard
→ skill-task-management shows active todos
With /octo:embrace
User asks "status" but no .octo/ exists
→ skill-status suggests /octo:embrace
→ User initializes new project

Best Practices

1. Always Check for .octo/ First

Good:

bash
if [[ ! -d ".octo" ]]; then
    echo "Not initialized"
    exit 1
fi

Poor:

bash
# Assume .octo/ exists and fail later
cat .octo/STATE.md
2. Use octo-state.sh for State Reading

Good:

bash
./scripts/octo-state.sh read_state

Poor:

bash
# Parse STATE.md manually
grep "Current Phase" .octo/STATE.md
3. Provide Actionable Next Steps

Good:

Continue with `/octo:develop` to implement features.
Check `.octo/phases/phase3/` for implementation plan.

Poor:

You're in phase 3.

Red Flags - Don't Do This

ActionWhy It's Wrong
Modify STATE.md directlyUse octo-state.sh write_state instead
Skip .octo/ existence checkWill fail with confusing errors
Show status without next actionUser doesn't know what to do
Hardcode phase namesRead from ROADMAP.md for accuracy
Ignore blockersUser needs to know what's blocking progress

Quick Reference

User InputAction Required
"status"Check .octo/ → Read state → Display dashboard
"what's next"Read state → Route based on status/phase
"where am I"Display current phase and position
"show progress"Display roadmap with completion markers
"any blockers"Extract and display blockers from STATE.md
"what have I been working on"Git log + results → Cross-session activity summary
"update project memory"Activity summary → Suggest CLAUDE.md additions

The Bottom Line

Status check → Read state + roadmap → Display dashboard + intelligent routing
Otherwise → User doesn't know where they are or what to do next

Check initialization. Read state. Display clearly. Route intelligently.

© nyldn, 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 1 other file in skills/skill-status of nyldn/claude-octopus.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 4d152db

Used in 1 other repository

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in nyldn/claude-octopus, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Skill Status 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 Status compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Skill Status this skillnyldn/claude-octopus4.2k1 repos~2.9kAutomated safety check: NotesMIT
MCP Server Builderanthropics/skills180k64 repos~2.3kAutomated safety check: PassApache-2.0
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official38k11 repos~4.1kAutomated safety check: NotesApache-2.0
Using Superpowersfarm-fe/farm5.6k35 repos~1.4kAutomated safety check: PassMIT
Executing Plans Inlineobra/superpowers296k2 repos~5.1kAutomated safety check: PassMIT
Claude Code Agent Developmentanthropics/claude-plugins-official38k8 repos~2.8kAutomated safety check: PassApache-2.0

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 64 repos~2.3k tokens
    Agent WorkflowsAuto-check passed

  • Hook Development for Claude Code Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.

    38k GitHub starsUsed in 11 repos~4.1k tokens
    Agent WorkflowsAuto-check: notes

  • Using Superpowers

    farm-fe/farm

    A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

    5.6k GitHub starsUsed in 35 repos~1.4k tokens
    Agent WorkflowsAuto-check passed

  • Executing Plans Inline

    obra/superpowers

    Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.

    296k GitHub starsUsed in 2 repos~5.1k tokens
    Agent WorkflowsAuto-check passed

  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    38k GitHub starsUsed in 8 repos~2.8k tokens
    Agent WorkflowsAuto-check passed

  • Skill Creator

    Azure/azqr

    Official

    Create new skills, modify and improve existing skills, and measure skill performance.

    795 GitHub starsUsed in 89 repos~8.2k tokens
    Agent WorkflowsAuto-check passed

More from nyldn/claude-octopus

All 62 skills in this repo

  • Octopus Quick

    nyldn/claude-octopus

    Quick execution for ad-hoc tasks without full workflow overhead — use for small, self-contained requests

    4.2k GitHub starsUsed in 1 repo~2.2k tokens
    Auto-check passed

  • Octopus Research

    nyldn/claude-octopus

    Thorough research across multiple sources — use for complex topics needing broad synthesis

    4.2k GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed

  • Octopus Security Audit

    nyldn/claude-octopus

    OWASP compliance, vulnerability scanning, and adversarial red team testing — use for security reviews

    4.2k GitHub starsUsed in 1 repo~2.3k tokens
    Auto-check passed

  • Skill Audit

    nyldn/claude-octopus

    Audit codebases for quality, consistency, and broken patterns — use for pre-release or tech debt review

    4.2k GitHub starsUsed in 1 repo~3.2k tokens
    Auto-check passed

  • Skill Content Pipeline

    nyldn/claude-octopus

    Extract patterns and anatomy from URLs — use to reverse-engineer content strategies from live pages

    4.2k GitHub starsUsed in 1 repo~3.9k tokens
    Auto-check passed

  • Skill Context Detection

    nyldn/claude-octopus

    Auto-detect work context (Dev vs Knowledge) — use to tailor workflows based on current task type

    4.2k GitHub starsUsed in 1 repo~2.6k tokens
    Auto-check passed

Categories

Questions about Skill Status

What does Skill Status do?

Show where you are in the workflow and what to do next — use for progress checks and orientation. Skill Status is an agent skill from nyldn/claude-octopus.

When should I use Skill Status?

Skill Status fits situations like: progress checks and orientation.

How do I install Skill Status in Claude Code?

Run `npx skills add nyldn/claude-octopus --skill skill-status -a claude-code`. Or copy the skill folder (skills/skill-status in nyldn/claude-octopus) into .claude/skills/skill-status in your project. Claude Code loads it when a task matches its description.

How do I install Skill Status in Codex?

Run `npx skills add nyldn/claude-octopus --skill skill-status -a codex`. Or copy the skill folder (skills/skill-status in nyldn/claude-octopus) into .agents/skills/skill-status in your project. Codex loads it when a task matches its description.

Can I use Skill Status 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 nyldn/claude-octopus --skill skill-status -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/skill-status, .gemini/skills/skill-status, .github/skills/skill-status and .opencode/skills/skill-status in your project.

What does Skill Status need to run?

Going by SKILL.md and its folder, Skill Status needs the command-line tools its instructions call (git).

Does Skill Status 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 Skill Status safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Skill Status use?

Skill Status 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 Skill Status use?

About 2.9k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Skill Status?

Skills that share tags, products or a category with Skill Status: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 296k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Skill Status?

nyldn (a GitHub user) maintains it in nyldn/claude-octopus, which has 4,182 GitHub stars. The repository holds 62 skills in this directory. The repository was last updated on October 7, 2026.

Source: nyldn/claude-octopus on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.