cf-integrations
starsforks
How to install cf-integrations?
indranilbanerjee/contentforge/cf-integrations
$npx -y skills add indranilbanerjee/contentforge --skill cf-integrationsShow active and available MCP connectors with workflow impact. Integration status dashboard.
SKILL.md
| 1 | # /contentforge:cf-integrations — Integration Status Dashboard |
| 2 | |
| 3 | Show the complete integration status for your ContentForge installation — configured vs available connectors, grouped by category, with workflow impact analysis and quick-win recommendations. |
| 4 | |
| 5 | ## The ground truth about connectors |
| 6 | |
| 7 | 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. |
| 8 | |
| 9 | **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. |
| 10 | |
| 11 | ## When to Use |
| 12 | |
| 13 | Use `/contentforge:cf-integrations` when: |
| 14 | - You just installed ContentForge and want to see what's connected |
| 15 | - You're troubleshooting why a skill can't reach an external service |
| 16 | - You want to know which connectors to add next for maximum workflow coverage |
| 17 | - You need a quick overview before onboarding a new team member |
| 18 | - You're planning which integrations to set up for a new project |
| 19 | |
| 20 | ## What This Command Does |
| 21 | |
| 22 | 1. **Scan All Connectors** — Run the status script; it checks the connector registry against your `.mcp.json` and environment variables |
| 23 | 2. **Build Status Dashboard** — Group results by category with clear configured/available distinction |
| 24 | 3. **Calculate Coverage** — Report exactly the totals the script returns |
| 25 | 4. **Recommend Quick Wins** — Highlight the top 3 not-yet-configured connectors by workflow impact |
| 26 | 5. **Surface Category Gaps** — Identify categories with zero coverage |
| 27 | 6. **Provide Next Steps** — For each recommendation, point to `/contentforge:cf-connect <name>` |
| 28 | |
| 29 | ## Required Inputs |
| 30 | |
| 31 | **Optional:** |
| 32 | - **Category filter** — Show only a specific category (e.g., `--category=seo`) |
| 33 | - **Show filter** — `connected`, `available`, or `all` (default: `all`) |
| 34 | |
| 35 | ## What Happens |
| 36 | |
| 37 | ### Step 1: Connector Status Check |
| 38 | |
| 39 | ``` |
| 40 | python scripts/connector-status.py --action status |
| 41 | ``` |
| 42 | |
| 43 | This checks: |
| 44 | - `.mcp.json` for HTTP connector entries the user has added |
| 45 | - Environment variables for npx connectors (WordPress, Google Sheets, Semrush, DeepL, etc.) |
| 46 | - Returns JSON with configured/available status per connector, grouped by category, plus summary totals |
| 47 | |
| 48 | ### Step 2: Format Dashboard by Category |
| 49 | |
| 50 | Render the script JSON as a category-grouped dashboard. Each category shows the category name and description, connectors marked `[connected]` or `[available]`, transport type, and the skills each connector unlocks — all taken from the JSON. |
| 51 | |
| 52 | **SYNTHETIC EXAMPLE — fabricated for illustration. Always render your actual script output, never this block:** |
| 53 | |
| 54 | ``` |
| 55 | =========================================================== |
| 56 | ContentForge Integration Dashboard |
| 57 | Connected: 1 of 22 (5%) |
| 58 | =========================================================== |
| 59 | |
| 60 | KNOWLEDGE BASE — requirements, brand docs, reference material |
| 61 | ----------------------------------------------------------- |
| 62 | [available] Notion (HTTP) — content requirements, brand docs, editorial calendars |
| 63 | [available] Confluence (npx) — team wikis, brand guidelines |
| 64 | |
| 65 | CMS — content management and publishing |
| 66 | ----------------------------------------------------------- |
| 67 | [connected] Webflow (HTTP) — added by user to .mcp.json |
| 68 | [available] WordPress (npx) — needs WORDPRESS_SITE_URL, WORDPRESS_AUTH_TOKEN |
| 69 | |
| 70 | ... (remaining categories from script output) |
| 71 | =========================================================== |
| 72 | ``` |
| 73 | |
| 74 | A fresh install typically shows 0-2 connected. That is normal and expected — connectors are opt-in. |
| 75 | |
| 76 | ### Step 3: Highlight Quick Wins |
| 77 | |
| 78 | From the connectors the script reports as *not configured*, recommend the top 3 by workflow impact: |
| 79 | |
| 80 | 1. **Notion** — powers the most skills (content intake, brand docs, briefs, audits) |
| 81 | 2. **Google Sheets** — batch requirement intake, analytics tracking |
| 82 | 3. **CMS (Webflow or WordPress)** — end-to-end publish workflow |
| 83 | 4. **Design (Canva or Figma)** — featured images and social graphics |
| 84 | 5. **SEO (Ahrefs)** — real keyword data for briefs and audits |
| 85 | |
| 86 | For each quick win, show: what it unlocks (from script JSON), setup route (`/contentforge:cf-connect <name>`), and effort (HTTP = one `.mcp.json` entry + OAuth on first use; npx = env vars + entry, Claude Code only). |
| 87 | |
| 88 | ### Step 4: Show Coverage Summary |
| 89 | |
| 90 | Render the script's summary block verbatim (total, connected, available, coverage percent) plus which categories have zero configured connectors. |
| 91 | |
| 92 | ### Step 5: Provide Next Steps |
| 93 | |
| 94 | ``` |
| 95 | 1. Connect your top quick win: /contentforge:cf-connect <name> |
| 96 | 2. Setup guide for any connector: /contentforge:cf-connect <name> |
| 97 | 3. Custom service not in registry: /contentforge:c |
People who liked this also viewed
6 picksType
- seo-auditWhen the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tagSkillsJul 2026
- copywritingWhen the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user sSkillsJul 2026
- marketing-psychologyWhen the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,'SkillsJul 2026
- content-strategyWhen the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "conSkillsJul 2026
- programmatic-seoWhen the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions "programmatic SEO," "template pages," "pages at scale," "directory pages," "location pSkillsJul 2026
- marketing-ideasWhen the user needs marketing ideas, inspiration, or strategies for their SaaS or software product. Also use when the user asks for 'marketing ideas,' 'growth ideas,' 'how to market,' 'marketing stratSkillsJul 2026
