skills.rest
Chulf58
Chulf58COMMUNITY
Explore all skills by this author →
GitHub

forge:overview

Inventory and summarize FORGE plugin ecosystem components from project files.

1|Updated Apr 14, 2026
Search Tags:#hooks#agents#mcp#plugin#inventory#forge#board-state
One-click install
npx skills add https://github.com/Chulf58/FORGE --skill forge-overview
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: forge:overview
Source: https://github.com/Chulf58/FORGE/tree/main/skills/overview
Command: npx skills add https://github.com/Chulf58/FORGE --skill forge-overview

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a single, authoritative view of a FORGE project's plugin ecosystem so teams can understand scope, ownership, and gaps without manual spelunking.

Core Features & Use Cases

  • Inventory and document all components: agents, skills, hooks, MCP tools, board state, and enforcement mechanisms.
  • Support governance, onboarding, and architectural reviews by providing a consistent reference.

Quick Start

Generate a full FORGE plugin ecosystem overview for the current project configuration and repository files.

Frequently Asked Questions about forge:overview

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I inventory all FORGE plugins across agents, hooks, and MCP tools?▼

A FORGE plugin ecosystem overview summarizes agents, skills, hooks, MCP tools, board state, and enforcement mechanisms into a single reference. It reads project files like .claude-plugin/plugin.json, hooks/hooks.json, and mcp/server.js to support discovery and governance without manual file spelunking.

What is the best way to audit FORGE plugin configurations for architectural reviews?▼

You can inventory FORGE enforcement mechanisms and board state by reading .pipeline/board.json and project.json files. This summarizes all enforcement configurations and board state data to support governance, onboarding, and architectural reviews across your repository.

How do I generate a full plugin ecosystem overview for onboarding?▼

Generating a FORGE overview requires reading specific project files including .claude-plugin/plugin.json, mcp/lib/*, and .pipeline/project.json. It works with existing FORGE configurations containing agents, skills, hooks, MCP tools, and board state files to produce an authoritative ecosystem reference.

Does the FORGE overview support documenting MCP server tools and hooks?▼

The FORGE overview is limited to reading existing project files like .claude-plugin/plugin.json, agents/*.md, and .pipeline/board.json. It cannot modify configurations or execute plugins; it only assembles an inventory from available repository files to support discovery and governance.

Related Skills

Explore More Software Engineering Skills→
Chulf58Chulf58

forge:init

Scaffold a FORGE project workspace with configuration files and a CLAUDE launcher.

Community
Advanced
jack-michaudjack-michaud
7

Creating Hooks

Create event-driven hooks for Claude Code lifecycle events.

Community
Intermediate
srnicholssrnichols
5

forge-troubleshoot

Diagnoses Plan Forge failures including runs, environments, and code errors via MCP server.

Community
Advanced
shawn-sandyshawn-sandy
2

plugin-creator

Scaffold Claude Code plugins with manifest, commands, and MCP server setup.

Community
Advanced