cf-integrations

Solid

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.

AI & Automation 28 stars 5 forks Updated 3 weeks ago MIT

Install

View on GitHub

Quality Score: 84/100

Stars 20%
49
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# /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** —...

Details

Author
indranilbanerjee
Repository
indranilbanerjee/contentforge
Created
6 months ago
Last Updated
3 weeks ago
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

cf-integrations

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.

1 Updated 3 weeks ago
teachskillofskills-ai
AI & Automation Solid

cf-connect

Set up a specific MCP connector from the ContentForge registry with step-by-step instructions tailored to its transport — verified endpoint URL for HTTP connectors, env vars plus a ready-to-paste .mcp.json entry for npx connectors, credential acquisition guidance, and post-setup verification. Triggers on "/contentforge:cf-connect", "connect WordPress", "set up the Notion connector", "how do I add Google Sheets", "a skill says a connector is missing". Status always comes from scripts/connector-status.py (never memory) and endpoints from .mcp.json.connectors-reference; fuzzy-matches names like wp or gsheets. Setup guidance only — for services not in the registry it hands off to /contentforge:cf-add-integration, and /contentforge:cf-integrations shows the full status dashboard.

28 Updated 3 weeks ago
indranilbanerjee
Data & Documents Listed

cf-connect

Set up a specific MCP connector from the ContentForge registry with step-by-step instructions tailored to its transport — verified endpoint URL for HTTP connectors, env vars plus a ready-to-paste .mcp.json entry for npx connectors, credential acquisition guidance, and post-setup verification. Triggers on "/contentforge:cf-connect", "connect WordPress", "set up the Notion connector", "how do I add Google Sheets", "a skill says a connector is missing". Status always comes from scripts/connector-status.py (never memory) and endpoints from .mcp.json.connectors-reference; fuzzy-matches names like wp or gsheets. Setup guidance only — for services not in the registry it hands off to /contentforge:cf-add-integration, and /contentforge:cf-integrations shows the full status dashboard.

1 Updated 3 weeks ago
teachskillofskills-ai