Skill Tracer
Skills › Knowledge Work Plugins › process-optimization

process-optimization

skill · 39 lines · Apache-2.0 · operations/skills/process-optimization/SKILL.md

The facts

Its description

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.

The description the agent reads to decide when to use it.

From its settingsline 3

When it starts

The agent would pick this skill when someone complains that an existing business process is slow, bloated, or full of bottlenecks and wants it analyzed and improved. It is chosen from the description alone, which lists trigger phrases about inefficiency and streamlining.

Things a person might say (the model's guesses)

  • “Our invoice approval process takes two weeks end to end — can you figure out why and fix it?”
  • “This onboarding workflow has way too many steps and handoffs.”
  • “How can we streamline the way we handle customer refund requests?”

A model's summary of when it is used.

A model's reading

Licence

Apache-2.0, from LICENSE

The terms its author shares it under, which let it be shown here.

From the repositorylicence text

The text

Open on GitHub
1---
2name: process-optimization
3description: 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.
4---
5
6# Process Optimization
7
8Analyze existing processes and recommend improvements.
9

Process Optimization

Analyze existing processes and recommend improvements.

Raw lines 1 to 9
10## Analysis Framework

Analysis Framework

Raw lines 10 to 11
12### 1. Map Current State
13- Document every step, decision point, and handoff
14- Identify who does what and how long each step takes
15- Note manual steps, approvals, and waiting times

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
Raw lines 12 to 16
17### 2. Identify Waste
18- **Waiting**: Time spent in queues or waiting for approvals
19- **Rework**: Steps that fail and need to be redone
20- **Handoffs**: Each handoff is a potential point of failure or delay
21- **Over-processing**: Steps that add no value
22- **Manual work**: Tasks that could be automated

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
Raw lines 17 to 23
24### 3. Design Future State
25- Eliminate unnecessary steps
26- Automate where possible
27- Reduce handoffs
28- Parallelize independent steps
29- Add checkpoints (not gates)

3. Design Future State

  • Eliminate unnecessary steps
  • Automate where possible
  • Reduce handoffs
  • Parallelize independent steps
  • Add checkpoints (not gates)
Raw lines 24 to 30
31### 4. Measure Impact
32- Time saved per cycle
33- Error rate reduction
34- Cost savings
35- Employee satisfaction improvement

4. Measure Impact

  • Time saved per cycle
  • Error rate reduction
  • Cost savings
  • Employee satisfaction improvement
Raw lines 31 to 36
37## Output
39Produce a before/after process comparison with specific improvement recommendations, estimated impact, and an implementation plan.

Output

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

Raw lines 37 to 39

From anthropics/knowledge-work-plugins at 2574e29, 2026-10-27. Skills read by DeepSeek V4.1 Flash on 2026-11-04. Summary and techniques by Claude Opus 5.5 on 2026-11-06.