Topic starter
18/08/2026 2:56 pm
TL;DR: Skills do not replace MCP, but they change how agents decide when to use tools, according to Obot’s coverage of Pedro Rodrigues’ MCP Dev Summit talk. The practical issue is governance: if agents can compose actions from stale context or unvetted instructions, the control plane must cover both protocol access and skill approval.
Editorial analysis by NHI Mgmt Group, based on content published by Obot: “Skills Aren’t the MCP Killer: Notes from the Best Talk at MCP Dev Summit”.
Key questions
Q: What breaks when agents have MCP access but no governed skill context?
A: The agent may use a valid tool path to produce an unsafe outcome because it lacks the instructions that tell it when to consult current policy or documentation.
Q: Why do Skills and MCP need to be governed together?
A: MCP governs how the agent reaches tools, while Skills govern how it chooses to use them.
Q: What are the signs that an agent is relying on stale context?
A: Look for repetitive outputs that mirror known patterns even when current documentation exists, tool calls that skip available search or reference steps, and workflows that ignore environment-specific defaults.
Practitioner guidance
- Govern MCP and skills together Define one control plane for tool access, instruction approval, provenance, and audit so the protocol layer and the context layer are reviewed as a unit.
- Approve skills before production use Require review for any skill that changes agent decisioning, especially if it can steer database writes, data retrieval, or policy-sensitive workflows.
- Force current-context checks in skills Embed explicit prompts to read current documentation or policy before acting when the task touches permissions, data exposure, or security defaults.
Bottom line: Agents can have valid tool access and still produce unsafe outcomes if the instruction layer is not governed with the same rigor as the protocol layer.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
18/08/2026 3:38 pm
Skills governance is now part of the agent control plane, not a separate content problem. Once skills determine when an agent consults documentation and how it uses tools, they become governance artefacts with real security impact. That means approval, provenance, and visibility must extend beyond connectors and into instruction packages. The practitioner conclusion is straightforward: if skills can change runtime decisions, they must be governed like production access paths.
A few things that frame the scale:
- 24,008 unique secrets were exposed in MCP configuration files in 2025 alone, the protocol's first year of widespread adoption, according to the State of Secrets Sprawl 2026.
A question worth separating out:
Q: How should security teams govern agent skills that can be loaded from external sources?
A: Treat externally loaded skills as privileged inputs, not ordinary content. Security teams should require provenance checks, approval gates, and runtime authorization before an agent can execute them. The key is to control what the agent may trust at the moment of use, because static review alone does not prevent malicious instructions from becoming active inside a live session.
👉 Read our full editorial: Skills and MCP are complementary, but governance is the gap