forge-status
Show all forged tools and their usage stats
Best use case
forge-status is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Show all forged tools and their usage stats
Teams using forge-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
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/forge-status/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How forge-status Compares
| Feature / Agent | forge-status | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Show all forged tools and their usage stats
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
Read the file `registry.json` in the project root. Display a formatted summary of all forged MCP tool servers including: - Server name - Description - Tools provided - When it was created - What user request triggered the forge - How many times it has been used If the registry is empty, say "No tools have been forged yet. Use the Forge agent to get started: claude --agent forge"
Related Skills
longrun-status
Inspect the latest or a specified long-running Copilot CLI mission under .copilot-mission-control/ and report state, profile, current phase, delivered artifacts, blockers, evidence coverage, and the next likely step.
~aod-status
On-demand backlog snapshot and lifecycle stage summary. Regenerates BACKLOG.md from GitHub Issues and displays item counts per stage. Use this skill when you need to check backlog status, view stage counts, regenerate BACKLOG.md, or get a lifecycle overview.
prd-status
Check and update PRD status through lifecycle
forge-help
Show all available Product Forge agents, skills, and commands
tech-spec-status
Show Tech Spec details or update status through lifecycle
rfc-status
Show RFC details or update RFC status through lifecycle
propose-forge-improvement
Propose improvements or new components for Product Forge
flow-sync-status
Use when syncing Beads state to markdown, checking Flow status, refreshing context docs, validating task markers, or reporting ready/blocked Flow work.
exploiting-server-side-request-forgery
在授权渗透测试中识别并利用 SSRF 漏洞，访问内部服务、云元数据及受限网络资源。
shark-status
Check status of shark-exec background jobs, .shark-done, and SHARK_LOG.md
sdd-workflow — Workflow Status Dashboard
## Slash Command
status-workflow
Performs GitHub Projects v2 status transitions for issue workflow. Use when you need to "move issue to status", "transition status", "update project status", "set status field", or "change issue state". Handles status field mutations, GraphQL verification, and comment attribution. Works with cached board-scanner environment variables.