Agent skill · Documentation

process-mapper

Map workflows, extract SOPs, and identify automation opportunities through systematic process capture and AI tractability assessment. Use when documenting workflows, creating SOPs, conducting process discovery interviews, or analyzing automation opportunities. Grounds the SOP-first doctrine in tacit knowledge documentation and structured analysis.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill process-mapper-leegonzales-aiskills-2 --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 9 KB
Bundled scripts: none
Path: skills/analysis/process-mapper-leegonzales-aiskills-2/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Process Mapper Skill Systematic workflow for discovering, documenting, and analyzing processes. Implements user's SOP-first doctrine: **"You can't automate what you can't see."** ## Core Philosophy **From user's work:** > "When I sit with a person or team to start working through how they can work out where and how to apply AI into their job, I often like to start with a common task or value stream, and talk through—or more often than not, document—the SOP for that value stream." **Three truths:** 1. **Shadow processes are real processes** (what actually happens ≠ org chart) 2. **Tacit knowledge is documentable** (capture decision *points*, not decision *logic*) 3. **Structure enables automation** (visibility → AI opportunities) --- ## Core Workflow ### 1. Diagnostic: Assess Current State **Determine SOP state:** Load `references/discovery-methodology.md` for framework **State 1: Fiction** - SOPs exist but nobody follows them - Beautiful docs, zero usage - Aspirational not actual **State 2: Nonexistent** - No documentation - Tribal knowledge - "Just ask Sarah" **State 3: Accurate** - Docs match reality - Referenced regularly - Updated when process changes **Action by state:** - F

What's inside
Steps it walks through
  1. Core Philosophy
  2. Core Workflow
  3. 1. Diagnostic: Assess Current State
  4. 2. Process Discovery Interview
  5. 3. Process Documentation
  6. 4. Complexity Classification
  7. 5. Automation Opportunity Analysis
  8. 6. Prioritization & ROI
  9. 7. Output Delivery
  10. The Labeled Black Box Pattern
  11. Movement Strategy
  12. Quality Signals
  13. Integration Points
  14. Common Process Types
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the process-mapper skill do?

Map workflows, extract SOPs, and identify automation opportunities through systematic process capture and AI tractability assessment. Use when documenting workflows, creating SOPs, conducting process discovery interviews, or analyzing automation opportunities. Grounds the SOP-first doctrine in tacit knowledge documentation and structured analysis.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill process-mapper-leegonzales-aiskills-2 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going