mcpbeat Sign in

Integrations Skill for Claude

Show MCP integration status. Use when: checking active connectors, available integrations, or skill unlocks.

904 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
694
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/indranilbanerjee/digital-marketing-pro --skill integrations

The instruction itself

6 sections, as written by the author

/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

  • Run connector status check: Execute python "${CLAUDE_PLUGIN_ROOT}/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.
  • 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)
  • 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.
  • 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.
  • 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

Other skills for the same job

different authors, same section of the catalogue
Skill Creator
by anthropics
vendor ×10

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

56k tokens scripts
Skill Creator
by vercel-labs
vendor ×10

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

12k tokens scripts
Skill Creator
by JayZeeDesign
×9

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

10k tokens scripts
Template Skill
by JayZeeDesign
×7

Replace with description of the skill and when Claude should use it.

35 tokens
Dispatching Parallel Agents
by ZhanlinCui
×5

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

2k tokens
Skill Development
by anthropics
vendor ×4

This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.

9k tokens
Find Skills
by sanity-io
vendor ×4

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

1k tokens
Writing Skills
by ZhanlinCui
×4

Use when creating new skills, editing existing skills, or verifying skills work before deployment

26k tokens scripts

How to use it

Copy the folder

Take indranilbanerjee/integrations from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.

Install what it needs

The instructions reference npx. Without those the skill loads but fails at the first command.