---
id: "concept-skill-vs-process"
type: "concept"
source_timestamps: ["00:08:38", "00:09:50"]
tags: ["ai-agents", "workflow-automation", "system-design"]
related: ["contrarian-agents-need-rails", "action-hardwire-processes", "quote-skill-vs-process", "quote-ripping-up-railroad"]
definition: "The architectural distinction between a discrete, bounded agentic action (a skill) and a deterministic, multi-step business workflow (a process)."
sources: ["s53-agent-100x-review-3x"]
sourceVaultSlug: "s53-agent-100x-review-3x"
originDay: 53
---
# Skill vs. Process Distinction

## The Distinction

A critical failure mode in agent deployment is **mistaking a discrete skill (or tool call) for a comprehensive business process**. The speaker [[entity-nate-b-jones]] makes this rule explicit in [[quote-skill-vs-process]]: *"Do not mistake a skill or a tool call for a process."*

| Skill | Process |
|-------|---------|
| Bounded action an LLM excels at | Multi-step deterministic workflow |
| Drafting an email | Triaging → routing → responding → logging a ticket |
| Summarizing a document | End-to-end customer-onboarding sequence |
| Making a single API call | The chain that decides which API to call and when |

## Why Processes Must Be Hardwired

Processes must be **deterministic**. You should not rely on an agent to remember or infer the sequence of a complex workflow. Doing so is, in the speaker's analogy from [[quote-ripping-up-railroad]], like *"ripping up your railroad and sticking your train on the ground and saying, kind of go that way."*

Instead:

- The **"in-between glue"** (routing, data passing, retries) must be hardcoded
- The agent is **triggered at specific, hardwired points** to execute its skills
- This ensures reliability, predictability, and prevents hallucinated workflow steps

This is the contrarian stance defended in [[contrarian-agents-need-rails]] and the practical action item in [[action-hardwire-processes]].