---
id: "claim-procedural-over-abilities"
type: "claim"
source_timestamps: ["00:17:04", "00:20:02"]
tags: ["agent-design", "control-systems"]
related: ["concept-procedural-vs-ability-skills", "contrarian-disable-model-skills", "action-blank-slate-agents"]
confidence: "medium"
testable: true
speakers: ["Matt Pocock"]
---
# Procedural Skills Beat Autonomous Abilities

## Claim

Giving AI models the autonomous *ability* to invoke tools whenever they see fit leads to unpredictable behavior and wasted compute. It is more effective to design *procedural* skills that explicitly disable model invocation, forcing the human to trigger the skill and maintain strict control over the agent's workflow and state transitions.

See [[concept-procedural-vs-ability-skills]] for the underlying distinction and [[contrarian-disable-model-skills]] for the contrarian framing.

## Confidence

**Medium.** Strong evidence that unconstrained autonomy causes tool spam and runaway loops; equally strong evidence that well-designed autonomous tool use (AutoGen, LangGraph, ReAct, Toolformer) is productive in many settings. The claim's truth is **context-dependent**.

## Testability

**Testable.** Compare two harness configurations on identical tasks:
- All skills auto-invocable by the model.
- Same skills, model auto-invocation disabled, human triggers via slash commands.

Measure: task success rate, token spend, time to completion, defect rate.

## Where Pocock's view holds

- Safety-critical software engineering.
- Long-form workflows with discrete checkpoints (plan → grill → PRD → implement).
- Workflows where human judgment is the bottleneck on correctness.

## Where the opposite may hold

- High-volume, low-risk environments (internal tools, batch pipelines).
- Exploratory prototyping where speed > control.
- Tasks with many cheap micro-decisions.