The 3 Claude Skills That Make Operations Actually Repeatable
Operations problems are usually documentation problems. The process works because one person knows how it works. The moment that person is unavailable, or you try to hand it off, or you want to run it consistently — it falls apart. Not because it was a bad process. Because it was never written down.
The Operations pack has 4 skills. Here are the three that solve the documentation problem before it becomes a bottleneck.
/sop-writer
Most people know how to do the things they do. Very few people know how to write down how they do them in a way someone else can follow without asking three follow-up questions. The brain dump you do when someone asks you to document a process is almost always too vague in some places and too detailed in others.
/sop-writer takes a brain dump — rough notes, a voice memo transcript, a quick description — and turns it into a clean, delegatable SOP. It auto-flags steps that are ambiguous or missing information, so you're not handing off a document that will generate more confusion than it prevents.
--ai-agent formats the SOP specifically for AI agent execution, with the level of precision and explicit decision rules that agents need to run a process reliably without human intervention.
A process that lives only in your head is a single point of failure. This gets it out.
/vendor-comparison
Vendor decisions are slow when the comparison isn't structured. You have four tools you're evaluating, three people with opinions, and no agreed-upon criteria. The conversation goes in circles, someone argues for their favorite, and you either pick the loudest voice or delay the decision indefinitely.
/vendor-comparison scores any set of tools or vendors against your specific requirements and picks a winner. Not a balanced pros-and-cons list — a mandatory recommendation with the reasoning behind it. The constraint is the point: forcing a decision requires actually committing to what matters most.
--budget weights cost as a primary factor when price is the binding constraint. --integration focuses the evaluation on how well each option fits into your existing stack.
The best vendor decision is the one you actually make and move on from.
/process-doc
Multi-person workflows break at handoff points. Someone finishes their part and assumes the next person knows what to do. They don't. Or they do it differently every time. Or they skip a step because they didn't know it existed. None of this is visible until something goes wrong downstream.
/process-doc documents any multi-person workflow with roles, steps, decision points, and KPIs — everything needed to run the process consistently without the person who designed it in the room.
--swimlane formats the output as a swimlane diagram showing who owns each step, useful for processes where handoffs between people or teams are where the errors happen. --wiki formats it for pasting directly into Notion, Confluence, or any internal wiki.
You can't improve a process you can't see. This makes it visible.
All four skills in the Operations pack — including /meeting-agenda for structured agendas with time, owner, and outcome per item — are available to Skills Pack members. They ship as SKILL.md files — drop them into ~/.claude/skills/ and invoke with the slash command in Claude Code, Cursor, or Codex.
Next up: the Customer Success pack — onboarding plans, churn risk diagnosis, case studies, and QBR prep.