status

Use when the user returns to a session and asks about progress, current state, what happened, or where they left off. Provides status dashboard and execution recovery.

16 stars

Best use case

status is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Use when the user returns to a session and asks about progress, current state, what happened, or where they left off. Provides status dashboard and execution recovery.

Teams using status should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/status/SKILL.md --create-dirs "https://raw.githubusercontent.com/diegosouzapw/awesome-omni-skill/main/skills/development/status/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/status/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How status Compares

Feature / AgentstatusStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Use when the user returns to a session and asks about progress, current state, what happened, or where they left off. Provides status dashboard and execution recovery.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Status

Inspect and recover workflow state. Use this to check progress, find where a session left off, or resume interrupted execution.

## Resume Checks

Restore state from:

1. Beads status (`bd ready`, `bd list --status in_progress`)
2. Task list state if `CLAUDE_CODE_TASK_LIST_ID` is set
3. Last known plan/spec references in workspace
4. `.arc/state.json` persisted by `execute`

`CLAUDE_CODE_TASK_LIST_ID` source of truth:

1. Current shell env var
2. `.claude/settings.json` -> `env.CLAUDE_CODE_TASK_LIST_ID`

If missing from both locations, resume with Beads-only state and print a warning.

Prefer `.arc/state.json` for last known mode/source/paths, then reconcile with live Beads and task list.

Resume state read example:

```bash
if [[ -f .arc/state.json ]]; then
  cat .arc/state.json
else
  echo "ARC: no .arc/state.json found; resuming from live Beads/task state only"
fi
```

## Output

Report:
- Current execution mode
- Ready/blocked/in-progress counts
- Recommended next command

Related Skills

specs-status

16
from diegosouzapw/awesome-omni-skill

현재 프로젝트의 EARS 스펙 상태 현황 표시

generate-status-report

16
from diegosouzapw/awesome-omni-skill

Comprehensive system status report with services, infrastructure, performance metrics, and recommendations

conductor-status

16
from diegosouzapw/awesome-omni-skill

Display project status, active tracks, and next actions

architecture-status

16
from diegosouzapw/awesome-omni-skill

Reports on the health and state of architecture documentation (counts of ADRs, reviews, activity levels, documentation gaps). Use when the user asks "What's our architecture status?", "Show architecture documentation", "How many ADRs do we have?", "What decisions are documented?", "Architecture health check", or wants an overview/summary of documentation state. Do NOT use for listing team members (use list-members), creating new documents (use create-adr), or conducting reviews (use architecture-review or specialist-review).

asyncredux-action-status

16
from diegosouzapw/awesome-omni-skill

Checks an AsyncRedux (Flutter) action's completion status using ActionStatus right after the dispatch returns. Use only when you need to know whether an action completed, whether it failed with an error, what error it produced, or how to navigate based on success or failure.

lisa-epic-status

16
from diegosouzapw/awesome-omni-skill

Show detailed status for an epic

advanced-statusline

16
from diegosouzapw/awesome-omni-skill

Implement AI-powered statusline with session tracking, plan detection, workspace emojis, and intelligent caching for Claude Code

analyzing-branch-status

16
from diegosouzapw/awesome-omni-skill

Use when user wants detailed status report for single autonomy branch including iteration timeline and metrics progression

agentuity-cli-git-status

16
from diegosouzapw/awesome-omni-skill

Show GitHub connection status for current project. Requires authentication

api-provider-status

16
from diegosouzapw/awesome-omni-skill

API 供应商状态查询与模型切换助手。查询当前模型、供应商、用量、余额,列出可切换的模型。当用户询问"当前模型"、"用量"、"余额"、"切换模型"、"可用模型"时触发。支持通过浏览器自动化登录中转站后台查询余额。

bgo

10
from diegosouzapw/awesome-omni-skill

Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.

Coding & Development

ui-ux-pro-max

16
from diegosouzapw/awesome-omni-skill

UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: Component search and examples.