forge-status
Skill9 starsChanged 35 days agoApache-2.0View on GitHub
This skill should be used when the user wants to "check Forge status", "verify the Forge plugin is running", "see if Forge is set up correctly", "check Forge configuration", "is Forge working", "Forge is running an older config", "the daemon is on an old config", or needs to diagnose why Claude Code sessions are not appearing in CoreWeave Forge AgentLens.
- Installs packages
11 other projects use a version of this.
Adopted by
Most recently taken up by
- TT-Wang/forgetheir own version, first seen Nov 1, 2026
- antonailog/forge-skillstheir own version, first seen Oct 25, 2026
- coreweave/forge-agent-lens-for-claude-codeword for word, first seen Oct 15, 2026
- yike-gunshi/forge-skillstheir own version, first seen Oct 13, 2026
- Dshamir/slm-forgetheir own version, first seen Oct 13, 2026
- wandb/forge-agent-lens-for-claude-codeword for word, first seen Oct 9, 2026
Used with
Projects with it also use forge-qa, forge-ship and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
lionshilovSkillforge-qa
Run an independent QA review on recent changes (or a given scope) via the read-only qa subagent, and enforce the pass/fail loop.
Also in 3 projects that use this
redteamlifeSkillforge-ship
Use when the user asks to merge, release, promote, reconcile, or close out work in a repo containing `docs/forge/` or governed by FORGE. Not for per-task commits; those complete inside forge-execute-task.
Also in 3 projects that use this
tonmoy007Skillforge-review
Run a multi-dimensional parallel code review over the current change.
Also in 3 projects that use this
Other versions11 projects use a version of this.
Word for word · 3
- coreweave/forge-agent-lens-for-claude-code★ 9100% same
- wandb/forge-agent-lens-for-claude-code★ 9100% same
- wandb/weave-claude-code★ 9100% same
Edited · 0
None found.
Wrote their own version · 8
- TT-Wang/forge★ 34same name
- ggombee/code-forge★ 18same name
- lorenzofamiglini/The-Forge-Protocol-Agent★ 15same name
- antonailog/forge-skills★ 13same name
- yike-gunshi/forge-skills★ 13same name
- lionshilov/Forge★ 5same name
- tonmoy007/forge-plugins★ 2same name
- Dshamir/slm-forge★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository3 other files it gives its agents.
- AGENTS.mdAGENTS.md
- forge-configSkill
- forge-installSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Check the current installation and configuration status of the Forge Agent Lens for Claude Code plugin.
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Forge Agent Lens for Claude Code Plugin — Status
Check the current installation and configuration status of the Forge Agent Lens for Claude Code plugin.
Run Status
Run:
forge-agent-lens-for-claude-code statusInterpret Results
Each status line indicates one of four states:
✓— component is present and correctly configured✗— component is missing or misconfigured (action required)⚠— component is working but has drifted from current settings (action recommended)-— component is absent but not an error (e.g., daemon not yet started)
Common issues and fixes:
| Symptom | Fix |
✗ Configuration: not found | Run /forge:forge-install to complete installation |
✗ CLI: not found in PATH | Run npm install -g @coreweave/forge-agent-lens-for-claude-code in a terminal |
✗ Project: not set | Run /forge:forge-config set project ENTITY/PROJECT |
⚠ Daemon is running an older config | A setting changed since the daemon started, so the live daemon is using stale config. Run forge-agent-lens-for-claude-code restart to apply the new settings. |
- Daemon socket: not running | Normal if no Claude Code session is active; daemon starts automatically on next hook event |
- Log file: not created yet | Normal before first session; no action needed |
Report
Summarize the status to the user. If all required items are ✓, confirm the plugin is ready and sessions will be traced automatically. If any ✗ items exist, provide the specific fix steps. If a ⚠ warning appears, surface it explicitly and run the recommended fix command.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.