mcp-integration
Creates Storybook stories. Use this to generate varied component states and edge cases.
Install
mkdir -p .claude/skills/mcp-integration-siamese001 && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/18849" && unzip -o skill.zip -d .claude/skills/mcp-integration-siamese001 && rm skill.zipInstalls to .claude/skills/mcp-integration-siamese001
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use this skill when choosing among repository-configured MCP servers, diagnosing MCP availability, or coordinating a cross-server workflow. Use adg-sqlite directly for structural dependency analysis.Key capabilities
- →Classify user intent and select a primary authority
- →Confirm server configuration and tool exposure
- →Inspect current tool schema for parameters
- →Prefer read-only health or discovery calls before state-changing calls
- →Apply least privilege, bounded results, explicit timeouts, and rollback for mutations
How it works
This skill routes user requests to configured MCP servers based on intent, ensuring proper tool exposure and applying security best practices for interactions.
Inputs & outputs
When to use mcp-integration
- →Create new component stories
- →Generate component edge case tests
- →Define component args and controls
- →Setup Storybook accessibility
About this skill
MCP integration
Root .mcp.json is the configured-server source of truth. A declared server is not proven callable
until its tools are exposed and a suitable read-only health or discovery call succeeds in the current
session.
Routing table
| Need | Procedure |
|---|---|
| Filesystem batches or cross-root reads | sections/01-filesystem-mcp.md |
| Redis projection and cache state | sections/02-redis-cache.md |
| Third-party GitHub repository Q&A | sections/03-deepwiki.md |
| Versioned external package documentation | sections/04-context7.md |
| Browser interaction and UI evidence | sections/05-playwright.md |
| Semantic similarity retrieval | sections/06-vector-db.md |
| Notion page or database operations | sections/07-notion.md |
| Web search, extraction, mapping, or crawling | sections/08-tavily-research.md |
| Runtime spans, anomalies, or telemetry | sections/09-otel-telemetry.md |
| Structured pytest discovery and runs | sections/10-pytest-mcp.md |
| Git, branch, PR, or issue operations | sections/11-gitkraken.md |
| Optional cross-session knowledge graph | sections/12-memory-mcp.md |
| Explicit durable task tracking | sections/13-task-manager-mcp.md |
Load only the section needed for the current intent. Do not recreate per-server redirect skills in the active skill tree.
Workflow
- Classify the user intent and select one primary authority.
- Confirm the server is configured and the expected tool is currently exposed.
- Inspect the current tool schema; do not infer parameters from a stale skill example.
- Prefer a read-only health or discovery call before a state-changing call.
- Apply least privilege, bounded results, explicit timeouts, and a rollback or compensating action for mutations.
- Report the actual server/tool used and any degraded fallback.
Boundaries
- Structural imports, consumers, layers, and blast radius belong to
adg-sqlite/graph-analysis. - Runtime traces do not replace static dependency evidence, and static graphs do not prove runtime execution.
- Vector similarity does not establish a code dependency.
- Native file tools are preferred for ordinary single-file workspace reads and writes.
- File memory under
memory/remains project memory authority; a memory MCP is an optional graph projection. - A dormant section is documentation for restoration, not evidence that a server is callable.
Read agents-tier1-companion.md for the compact operator view and SUPPORTING.md only for legacy overflow that has not yet been retired.
Validation
python .codex/governance/scripts/sync_mcp_config.py --check
python ops_scripts/ci/check_agents_mcp_coverage.py
python ops_scripts/ci/run_skill_contract_gates.py
When not to use it
- →For structural imports, consumers, layers, and blast radius analysis
- →When runtime traces are expected to replace static dependency evidence
- →When vector similarity is expected to establish a code dependency
Limitations
- →Does not handle structural imports, consumers, layers, or blast radius analysis
- →Runtime traces do not replace static dependency evidence
- →Vector similarity does not establish a code dependency
How it compares
This skill provides a structured approach to interacting with various MCP servers, ensuring proper configuration, tool schema inspection, and secure practices, unlike direct, unmanaged server calls.
Compared to similar skills
mcp-integration side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| mcp-integration (this skill) | 0 | 15d | Review | Advanced |
| writing-registry-meta | 5 | 6mo | No flags | Beginner |
| tsx | 0 | 1mo | Review | Beginner |
| React + Ant Design Frontend | 0 | 4mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
writing-registry-meta
siriwatknp
Use this skill when writing meta file for MUI Treasury registry.
tsx
javimosch
TSX namespace for Netsnek e.U. TypeScript component toolkit. React component scaffolding, type-safe props, Storybook integration, and component docs.
React + Ant Design Frontend
daithang-organization
Complete guide for the SE104_VLEAGUE React frontend — pages, services, components, auth flow, i18n, and patterns
new-component
7sferry
Scaffold a new React component following project conventions
nextjs-developer
zenobi-us
Expert Next.js developer mastering Next.js 14+ with App Router and full-stack features. Specializes in server components, server actions, performance optimization, and production deployment with focus on building fast, SEO-friendly applications.
zustand
lobehub
Zustand state management guide. Use when working with store code (src/store/**), implementing actions, managing state, or creating slices. Triggers on Zustand store development, state management questions, or action implementation.