Skills for version control

[crispyberry]

Problem

Current MCP is too coarse-grained:
• Mount once → all capabilities enabled
• No clear control over when, why, and how tools run
• Hard to add guardrails (read-only, phase control, budget, approvals)

This makes MCP risky and hard to scale in multi-agent or long-running workflows.

⸻

Proposal

Split MCP into Skills, and control them via Hooks.
• Skills = atomic, explicit capabilities
(e.g. memory.read, memory.write, snapshot.commit)
• Hooks = control points around execution
(before / after / block / transform)