Process optimization

Skill w95/awesome-claude-corporate-skills/07-operations/process-optimization

166 production-ready Claude AI skills organized by corporate role — executive leadership, finance, HR, marketing, sales, legal, operations, engineering, product, data, customer success, procurement & document processing

Install

npx -y skills add w95/awesome-claude-corporate-skills --skill process-optimization

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

Analyze and improve business processes. Trigger with "this process is slow", "how can we improve", "streamline this workflow", "too many steps", "bottleneck", or when the user describes an inefficient process they want to fix.

SKILL.md

1.3 KB, 223 tokens by cl100k_base, as published. Nobody here has run it

Process Optimization

Analyze existing processes and recommend improvements.

Analysis Framework

1. Map Current State

Document every step, decision point, and handoff
Identify who does what and how long each step takes
Note manual steps, approvals, and waiting times

2. Identify Waste

Waiting: Time spent in queues or waiting for approvals
Rework: Steps that fail and need to be redone
Handoffs: Each handoff is a potential point of failure or delay
Over-processing: Steps that add no value
Manual work: Tasks that could be automated

3. Design Future State

Eliminate unnecessary steps
Automate where possible
Reduce handoffs
Parallelize independent steps
Add checkpoints (not gates)

4. Measure Impact

Time saved per cycle
Error rate reduction
Cost savings
Employee satisfaction improvement

Output

Produce a before/after process comparison with specific improvement recommendations, estimated impact, and an implementation plan.

Gives 0 of the 12 instructions most performance cost skills give in 223 tokens

Counted across 803 of the 1,058 authors here whose files we hold, read 2026-08-06

keep skill files under 500 linesin 82 of 803, across 17 files
use imperative form in instructionsin 81 of 803, across 10 files
draft assertions while test runs are in progressin 75 of 803, across 9 files
create two to three realistic test promptsin 74 of 803, across 8 files
write skill descriptions to be pushyin 72 of 803, across 7 files
save test cases to evals jsonin 72 of 803, across 6 files
ask questions about edge cases and input formatsin 71 of 803, across 6 files
save timing data immediately when runs completein 70 of 803, across 5 files
include all trigger conditions in the skill descriptionin 69 of 803, across 3 files
launch all test runs in a single turnin 69 of 803, across 3 files
capture intent before writing a skillin 67 of 803, across 1 file
import directly instead of barrel filesin 52 of 803, across 15 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.