cf-integrationslisted

Render a live integration status dashboard for ContentForge — configured vs available MCP connectors grouped by category, coverage totals, and the top 3 quick-win connectors to add next, all taken from scripts/connector-status.py output. Triggers on "/contentforge:cf-integrations", "what integrations are connected", "show connector status", "why can't a skill reach my CMS", "which connectors should I set up next". Reads .mcp.json and environment variables only — no network calls, no agent; it reports status but does not configure anything. Pairs with /contentforge:cf-connect for guided setup and /contentforge:cf-add-integration for services outside the registry.
teachskillofskills-ai/ContentForge-techshu · ★ 1 · AI & Automation · score 75

Install: claude install-skill teachskillofskills-ai/ContentForge-techshu

# /contentforge:cf-integrations — Integration Status Dashboard Show the complete integration status for your ContentForge installation — configured vs available connectors, grouped by category, with workflow impact analysis and quick-win recommendations. ## The ground truth about connectors ContentForge ships with an **empty `.mcp.json`** (`"mcpServers": {}`) by design (v3.9.0 Cowork-safety decision). On a fresh install, expect **0 connectors configured** (or 1-2 if the platform injects its own integrations). Nothing is pre-wired. **Every number in the dashboard must come from the live script output.** Never render counts, percentages, or connected/available labels that are not present in the JSON returned by `scripts/connector-status.py`. Do not copy numbers from the example in this file. ## When to Use Use `/contentforge:cf-integrations` when: - You just installed ContentForge and want to see what's connected - You're troubleshooting why a skill can't reach an external service - You want to know which connectors to add next for maximum workflow coverage - You need a quick overview before onboarding a new team member - You're planning which integrations to set up for a new project ## What This Command Does 1. **Scan All Connectors** — Run the status script; it checks the connector registry against your `.mcp.json` and environment variables 2. **Build Status Dashboard** — Group results by category with clear configured/available distinction 3. **Calculate Coverage** —