agentleFS
Sign inStart free
lorenzofamiglinilorenzofamiglini/The-Forge-Protocol-Agent/skills/forge-status/SKILL.md

forge-status

Skill15 starsChanged 7 months agoMITView on GitHub

Show current Forge Protocol status — active mode, message count, violations, and audit reminders.

11 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use forge-config, forge-install and 3 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.
  • coreweaveSkill

    forge-config

    This skill should be used when the user wants to "configure Forge", "set Forge project", "change Forge project", "set wandb api key", "update Forge settings", "show Forge config", "change Forge configuration", "restart the Forge daemon", "apply Forge config changes", "restart Forge to pick up changes", or needs to read or update any Forge Agent Lens for Claude Code plugin settings.

    Also in 4 projects that use this

  • coreweaveSkill

    forge-install

    This skill should be used when the user wants to "install the Forge plugin", "set up Forge", "install forge-agent-lens-for-claude-code", "configure Forge for the first time", "get started with Forge tracing", or needs to complete the initial setup of the Forge Agent Lens for Claude Code plugin including dependency installation and project configuration.

    Also in 4 projects that use this

  • lionshilovSkill

    forge-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

  • redteamlifeSkill

    forge-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

  • tonmoy007Skill

    forge-review

    Run a multi-dimensional parallel code review over the current change.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Call the forge_get_state tool to retrieve the full state, then display it in a readable format.

    line 31

“Common” is measured: kept by at least 6 in 10 of the 8 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Forge Status

Show a dashboard of your current Forge Protocol state.

Usage

Say /forge-status to see:

  • Current mode (Forge, Anvil, Crucible, or Executor)
  • Message count in this session
  • Violation count (times the AI broke mode rules)
  • Mode history (which modes you've used and for how long)
  • Audit reminders (overdue weekly canary, monthly stress test, quarterly dependency audit)
  • Next checkpoint (messages until next metacognitive prompt)
  • Last canary score + trend — if the user has run a weekly canary, pull the latest trend (last score, change vs. previous, slope across attempts) so they can see whether their unassisted skills are drifting. Call forge_canary_list to see which prompts they've been taking; for the most recent, show the scored dimensions.

How to Check

Call the forge_get_state tool to retrieve the full state, then display it in a readable format.

Interpreting Results

  • High violation count → The AI is struggling to stay in mode. Consider reinforcing the SOUL.md.
  • Heavy executor usage → You may be delegating thinking tasks. Try switching to Forge mode.
  • Overdue audits → Time to test your unassisted skills. Run /forge-audit.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free