agentleFS
Sign inStart free
ForgeyClapForgeyClap/Forge-Core/.claude/skills/forge-registry/SKILL.md

forge-registry

Skill2 starsChanged 6 days agoMITView on GitHub

User-invoked only: /forge-registry. Builds the opt-in, read-only registry of all Forge projects (status, last run, tickets, ports); manual because it reads other projects.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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:

    Before a portfolio-wide sweep, to see status/ports/last-run at a glance.

    line 14
  2. Distinctive:

    Every record is secret-redacted before writing (defense in depth) — never persists a raw key.

    line 33

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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-registry — global project registry (opt-in, read-only)

An opt-in aggregate across every Forge project on this machine. It never runs automatically and never changes any project — it only reads and writes one global index.

When to use

  • The owner asks "show me all my Forge projects" / "which projects have open tickets / failing tests".
  • Before a portfolio-wide sweep, to see status/ports/last-run at a glance.

How to run

node .claude/forge-bin/forge-registry.cjs scan            # scan ~/Documents, write the registry
node .claude/forge-bin/forge-registry.cjs scan --json     # also print the aggregate to stdout
node .claude/forge-bin/forge-registry.cjs scan --root <dir> --run <run_id>

Outputs (global):

  • ~/.claude/forge/registry/projects.json — machine-readable index.
  • ~/.claude/forge/registry/index.html — a self-contained home-view (open it directly in a browser; data is inlined, no server needed).

Each record: project_id, name, path, stack, status, last_run_id, last_run_status, last_run_at, open_tickets, test_status, port. test_status reads a run's doctor.json (from Forge Doctor) when present.

Hard rules (isolation + honesty)

  • Reads other projects' .claude/ read-only (that is the opt-in aggregation job); it NEVER writes into any scanned project. The only thing written is the global registry dir.
  • Every record is secret-redacted before writing (defense in depth) — never persists a raw key.
  • Real DASHBOARD_STATE.json / run.json data only; a missing/malformed file yields honest defaults (unknown), never a fabricated status. (: the retired per-project server.cjs that used to write DASHBOARD_STATE.json is removed, so a project synced since then will simply never have one — the same honest-default path a project that never started that old dashboard already went through.)
  • Opt-in only: it never runs on require, only via the scan command.

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