integrations
Show MCP integration status. Use when: checking active connectors, available integrations, or skill unlocks.
What this skill does
# /digital-marketing-pro:integrations ## Purpose Show a complete integration status dashboard — which MCP connectors are currently connected, which are available but not yet configured, and which skills each connector unlocks. This is the first thing users should check after installing the plugin to understand what capabilities are active and what additional connections they can set up. ## Input Required The user may optionally provide: - **Filter** (optional): A specific category to focus on — e.g., "crm", "seo", "advertising", "email-marketing", "social-media". If omitted, shows all categories - **Show** (optional): `connected` (only active connectors), `available` (only not-yet-connected), or `all` (default) ## Process 1. **Run connector status check**: Execute `python3 scripts/connector-status.py --action status` to get the full status dashboard. This reads the active `.mcp.json` configuration and checks environment variables for npx connectors to determine which are connected. 2. **Format the dashboard**: Present the results organized by category, with clear visual distinction between connected and available connectors: For each category (Chat, Design, CRM, SEO, Email Marketing, Advertising, Analytics, Social Media, etc.): - Show connected connectors with a checkmark indicator and the skills they power - Show available-but-not-connected connectors with what they would unlock - For available connectors, indicate whether they are HTTP (works everywhere, easy OAuth setup) or npx (Claude Code only, requires API keys) 3. **Highlight quick wins**: Identify the top 3 connectors the user should consider connecting based on which would unlock the most additional skill capabilities. Prioritize HTTP connectors (easier to set up) over npx connectors. 4. **Show coverage summary**: Display the overall integration coverage — X of Y connectors active, with a breakdown by category showing which areas have full coverage vs gaps. 5. **Provide next steps**: For each available connector, briefly explain how to connect it: - HTTP connectors: "Just use any skill that needs it — you'll be prompted to authorize via OAuth" - npx connectors: "Run `/digital-marketing-pro:connect <name>` for setup instructions, or `/digital-marketing-pro:add-integration <name>` for guided configuration" ## Output A structured integration dashboard containing: - **Coverage summary**: Total connected vs total available, percentage coverage, and per-category breakdown - **Connected integrations**: List of all active connectors grouped by category, with the skills each one powers and its transport type (HTTP/npx) - **Available integrations**: List of all not-yet-connected connectors grouped by category, with what skills they would unlock, transport type, and setup complexity (HTTP = easy/OAuth, npx = requires API keys) - **Quick wins**: Top 3 recommended connectors to add next, based on skill coverage impact and setup ease - **Category gaps**: Categories with zero connected connectors highlighted, with the most impactful connector to add in each gap category - **Next steps**: Clear guidance — "Run `/digital-marketing-pro:connect <name>` to set up any connector" and "Run `/digital-marketing-pro:add-integration` for custom MCP servers not in the registry" ## Agents Used - No specialized agent needed — this skill uses the `connector-status.py` script directly and formats the output
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.