connect

Featured

Configure or diagnose access to a requested source using available host tools. Use for source MCP setup; source configuration needs no engagement record and credentials stay with the host.

AI & Automation 948 stars 104 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 90/100

Stars 20%
99
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
66
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# connect <!-- Generated by bin/generate-skills.js; edit the canonical references and catalog. --> ## Purpose Configure or diagnose access to a requested source using available host tools. Use for source MCP setup; source configuration needs no engagement record and credentials stay with the host. Before investigating or acting: 1. Read [the task context contract](references/task-context.md). 2. Read [the method](references/connect.md). Load further references only when the task needs them. Everything linked is included in this skill; no other skill pack is required. ## Principles - Source configuration and capability checks do not require an engagement record. Use available host tools and source documentation. Any later record staging or application follows the ingest method and its binding and confirmation requirements. - If called by @fde, reuse its current sanitized packet and scope. Do not restart setup, discovery or questions already answered. - The task context contract controls persistence and authority in both modes. Preserve unknowns and distinguish implementation, verification, deployment and acceptance. - Use the customer's repository instructions and available tools. Report a missing capability or unrun check honestly; do not claim that installing a skill provisions infrastructure.

Details

Author
suboss87
Repository
suboss87/FDEOps
Created
3 months ago
Last Updated
yesterday
Language
JavaScript
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

integrate

Build or change a customer-system integration with explicit data mapping, permissions, retries and reconciliation. Use for connectors, imports, write-back and upstream APIs.

948 Updated yesterday
suboss87
AI & Automation 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.

30 Updated 1 months ago
indranilbanerjee
AI & Automation Featured

connect

Guide the connection of a known MCP integration to the plugin — looks up the connector registry via connector-status.py, checks current status, and returns transport-specific setup steps (OAuth for HTTP connectors, env-var credentials plus the exact .mcp.json block for npx connectors), verification steps, and the skills each connector unlocks. Triggers on "/digital-marketing-pro:connect", "connect Google Ads", "hook up Slack to the plugin", "set up the HubSpot integration", "how do I add Mailchimp". Guidance and status checks only — the user adds credentials themselves; unknown or custom servers route to /digital-marketing-pro:add-integration.

835 Updated 2 weeks ago
indranilbanerjee