SkillsAdd

smithery/whoabuddy

quest-status

Show current quest progress and state

Installation

$ npx skills add smithery/whoabuddy --skill quest-status
View on skills.sh ↗ Website ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

status Similar name
parallel-web/parallel-agent-skills

Check running research task status by run ID

12K installs
status-report Similar name
anthropics/knowledge-work-plugins

Generate a status report with KPIs, risks, and action items. Use when writing a weekly or month…

2.7K installs
status Similar name
railwayapp/railway-skills

This skill should be used when the user asks "railway status", "is it running", "what's deploye…

1.5K installs
portfolio-status Similar name
anthropics/claude-for-legal

Roll up the portfolio from _log.yaml — risk distribution, upcoming deadlines, stale matters, ma…

497 installs
wiki-status Similar name
ar9av/obsidian-wiki

Show the current state of the wiki — what's been ingested, what's pending, and the delta betwee…

3.2K installs
localdata-business-status Similar name
nomadamas/k-skill

지방행정 인허가데이터(LOCALDATA)로 동네 사? 208? 상태, 인허가일자(?

2K installs

Also in this package

Other skills from smithery/whoabuddy.

npx skills add smithery/whoabuddy
quest-create 0 quest-complete 0 claude-hygiene 0 check-code-complete 0

Browse all from smithery/whoabuddy

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Allowed toolsBash, Read, Glob, Grep

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,718 B
  • docs SUMMARY.md 57 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Quest Status Skill

Display quest progress by reading directly from .planning/ files. No external scripts.

Usage

/quest-status

Behavior

  1. Find all quests:

- Active: Look for .planning//QUEST.md (non-archive directories) - Archived: Look for .planning/archive//QUEST.md

  1. For active quests, read and display:

- Quest name and status (from QUEST.md) - Progress: N/M phases completed (from PHASES.md) - Current phase: name and status - Recent activity (from STATE.md)

  1. For archived quests, list:

- Quest name and date (from directory name: YYYY-MM-DD-quest-name)

  1. If no quests found:

`` No quests found. Use /quest-create to start a new quest. ``

Output Format

With Active Quest

Active Quest: Cost Tracking
Status: active
Progress: 2/5 phases completed

Current Phase: 3 - Add margin query
Status: pending

Recent Activity:
- 2026-02-16: Phase 2 completed (3 commits, 1 retry)
- 2026-02-16: Phase 1 completed (2 commits)
- 2026-02-16: Quest created with 5 phases

Archived Quests:
- 2026-02-14-auth-system
- 2026-02-10-loop-hardening

No Active Quest

No active quest.

Archived Quests:
- 2026-02-14-auth-system
- 2026-02-10-loop-hardening

Use /quest-create to start a new quest.

Phase Status Display

Only three states shown:

  • pending — Not started
  • completed — Done
  • checkpoint — Stuck, needs human intervention

Related Commands

  • /quest-create — Start a new quest
  • /quest-run — Run phase automation
  • /quest-complete — Archive completed quest