From factory floor to agent context

The factory SOP hung on a wall. The agent skill lives in a context window. The medium changed; the engineering problem did not. This lesson maps the differences so you know which ones actually matter.

What this actually is

A "skill" in the agent context is executable instructions loaded into Claude's working memory before a task begins. When you run npx skills add deploy-production, the skill file is injected into the system prompt and Claude has access to every step, every conditional, and every gotcha before you type a single word.

The factory card and the agent skill share the same design requirement: explicit enough that the reader — human or model — does not need to infer anything. But the agent skill has three additional constraints the paper card does not.

What is different

The factory SOP assumes a human reader with common sense, pattern recognition, and the ability to ask a supervisor when something looks wrong. An agent skill assumes none of those things.

No inference. If the step says "check the database," the agent will check something called a database. If you meant a specific table in a specific schema, say so. "Check the users table in production_db — row count should be greater than zero" is a step. "Check the database" is an ambiguous instruction.

No memory across sessions. Every time an agent loads a skill, it starts from the beginning. You cannot write "as we discussed last time" in a skill file. The skill must be self-contained.

Conditional logic must be explicit. A human SOP can say "if something looks wrong, use judgment." An agent skill must enumerate the conditions. "If the API returns a status code other than 200 or 201, stop and report the status code and response body" is something the agent can act on.

What is the same

The order problem is identical. If step four depends on step three, that dependency must be stated. The agent is not smarter than a new hire about implicit sequencing — it will run step four first if you leave the order ambiguous.

The gotchas problem is identical. The most valuable part of any SOP is the failure handling section. On the factory floor this is "if the pressure drops below X." In an agent skill this is "if the build fails with exit code 1, run npm run clean and retry once before reporting failure."

Walk-through

Here is the same task expressed as a factory SOP versus an agent skill. The difference in specificity is the point.

Factory SOP (written for a human):

3. Upload the report to the shared drive.

Agent skill (written for Claude):

3. Upload `reports/weekly-summary.csv` to Google Drive folder `Team Reports / Weekly`.
   - Use `gdrive upload --parent 1aBcDeFgHiJkLmNoP reports/weekly-summary.csv`
   - Confirm upload succeeded: command should print "Uploaded [filename]"
   - If it fails with "permission denied," the service account token may have expired — report the error and stop

The human reader of step three knows what "the shared drive" means, which file to upload, and what success looks like. The agent needs all of that written out.

If you get stuck

If the agent executes the wrong step or skips a step: add sequence numbers and re-read the file for ambiguous pronouns ("it," "this," "the file"). Replace pronouns with specific nouns.

If the agent handles an error incorrectly: find the step where the error can occur and add an explicit conditional. "If X, then Y. If not X, continue."

If the skill file is getting long: split it. A skill over thirty steps is two skills. Split at the natural boundary and list the dependency in each file's frontmatter.

Cross-reference

L3 (Anatomy of a skill file) covers the structural conventions — frontmatter, procedure section, gotchas section — that make a skill machine-parseable as well as human-readable.

Deliverable

Take an SOP you already have — a team wiki page, a Notion doc, a README — and rewrite one section of it as an agent skill. The success criterion: the steps are specific enough that replacing every pronoun with a proper noun makes no ambiguity appear, because there are no pronouns left to replace.