BD MCP Tool Integrator
UPDATED 2026: MCP moves to Linux Foundation (2025-11), becomes de facto AI agent standard. AI-powered Model Context Protocol (MCP) server integration assistant — scaffold MCP servers, connect to 50+ tools (GitHub, Slack, Notion, Airtable, Postgres, filesystem), debug MCP connections, and build custom MCP tool chains. Built for AI developers, agent builders, and DevOps engineers building multi-tool AI agents. Keywords: MCP, Model Context Protocol, MCP server, AI agent integration, Anthropic Claude MCP, tool integration, AI agent development, LangChain MCP, n8n MCP, AI automation, MCP开发, AI Agent工具集成, 工具链, 自动化工作流, Claude桌面版.
As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, failures and branches
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Missing closing "quote at line 7, column 1: description: "UPDATED 2026: MCP moves to Linux Foundation (2025-11), becomes de… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "slug"
Process rating: all ten parameters 46/100
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 5 mutating operations with no state check
- 40Consistency. Frontmatter name (MCP Tool Integrator) differs from the folder (mcp-tool-integrator)
- 60Tools and files. Uses tools (bash, python, node) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 42 steps
- 100Execution cost. Instruction body is 3715 tokens
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -217 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 630: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 42 items
- +4Has examples (8 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 54.