How do I install the Forge Registry skill?

Run npx skillmds@latest add forgeyclap/forge-registry-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Forge Registry safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Forge Registry?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Forge Registry free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Forge Registry?

ForgeyClap (@forgeyclap) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Forge Registry by forgeyclap — Agent Skill

Name: Forge Registry
Author: ForgeyClap

Forge Registry

Build the GLOBAL, opt-in, read-only Forge Project Registry — a cross-project index of every Forge project (status, last run, open tickets, port) plus a self-contained home-view HTML. Use when the owner wants a bird's-eye view across all their Forge projects.

ForgeyClap Updated Sep 22, 2026

File contents

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.
Opt-in only: it never runs on require, only via the scan command.

---name: forge-registry-2description: Build the GLOBAL, opt-in, read-only Forge Project Registry — a cross-project index of every Forge project (status, last run, open tickets, port) plus a self-contained home-view HTML. Use when the owner wants a bird's-eye view across all their Forge projects.---# 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 neverchanges 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 registrynode .claude/forge-bin/forge-registry.cjs scan --json # also print the aggregate to stdoutnode .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.- Opt-in only: it never runs on `require`, only via the `scan` command.

Frequently asked questions