Immediate result: A step-by-step process map with handoffs, wait times, bottlenecks and a Mermaid diagram.
Problem it solvesNobody can see where a process wastes time, because it's never been mapped.
Purchase request: employee emails → manager approves → finance checks budget → procurement orders
Wait time: 4.5 days of 5 total are waiting in inboxes.
Bottleneck: finance budget check (2 days) — approve within budget automatically under ₹25,000.
flowchart LR; A[Request] --> B{Manager} --> C{Finance} --> D[Order]
Nobody can see where a process wastes time until it's mapped. This skill lists every step with its owner, working time and waiting time, marks handoffs, decisions and rework loops, and identifies the bottleneck and the waste — usually waiting, rework or unnecessary approvals. It produces a Mermaid flowchart you can paste into Notion, GitHub or Confluence, plus improvement ideas. Mapping a process this way is also the first step in deciding which parts an AI agent could take over. To use it, paste the skill into your assistant and send a description of how the process works today, who does each step and roughly how long it takes; the reply opens with “Step table”.
# Skill: Process mapper
You are running the "Process mapper" skill for me. I work as: Operations / business analyst. What I need from you: a step-by-step process map with handoffs, wait times, bottlenecks and a Mermaid diagram.
## When I send you a description of how the process works today, who does each step and roughly how long it takes
1. List steps with owner, time and wait time.
2. Mark handoffs, decisions and rework loops.
3. Identify the bottleneck and waste (waiting, rework, approvals).
4. Produce a Mermaid flowchart you can paste into docs.
## Reply in this format
- Step table
- Bottlenecks and waste
- Mermaid diagram (code)
- Improvement ideas
## Rules
- Use only the facts I give you; mark anything you had to assume with [ASSUMPTION].
- If something essential is missing, ask me one short question, then continue.
- No preamble or filler: start with the result.
Confirm you're ready in one line, then wait for me to send a description of how the process works today, who does each step and roughly how long it takes.Then sendA description of how the process works today, who does each step and roughly how long it takes. For example: Purchase request: employee emails → manager approves → finance checks budget → procurement orders
Upload it to Claude, add it to ChatGPT's Codex app, clone it into Claude Code, or download the SKILL.md for any agent. Full guide with screenshots →
Download the ZIP and upload it in Claude. Claude then uses the skill on its own whenever a request matches.
Download ZIP
OpenAI's Codex app reads the same SKILL.md format. Copy the skill into your Codex skills folder:
$ git -c http.version=HTTP/1.1 clone https://scienceofapps.com/skills/ai-skills.git
$ cp -r ai-skills/process-map ~/.codex/skills/
Clone the library and copy this skill into your Claude Code skills folder.
$ git -c http.version=HTTP/1.1 clone https://scienceofapps.com/skills/ai-skills.git
$ cp -r ai-skills/process-map ~/.claude/skills/~/.claude/skills/ for all projects, or .claude/skills/ inside one project.Download the skill file and put it in a folder named after the skill.
Download SKILL.md~/.claude/skills/process-map/SKILL.md.Repositoryscienceofapps.com/skills/ai-skills.git · all 200 skills, one folder each, plain git over HTTPS
Nobody can see where a process wastes time, because it's never been mapped. The skill fixes that: a step-by-step process map with handoffs, wait times, bottlenecks and a Mermaid diagram.
Copy the skill and paste it as the first message of a new chat, then send your input. To keep it, paste it into a ChatGPT Project or custom GPT, a Claude Project or a Gemini Gem, or upload the SKILL.md file as a Claude Skill.
Send a description of how the process works today, who does each step and roughly how long it takes. If something essential is missing, the skill asks you one short question and then continues.
Yes. It's free to copy, use and adapt, with no sign-up, and works in the free versions of ChatGPT, Claude, Gemini and Copilot.
ProblemOKRs end up as task lists with no measurable outcome.
Goal: make customer onboarding faster and better for our B2B tool
O: New customers see value in their first week.
KR1: Median time to first report 9 days → 3 days
Not a KR: 'launch onboarding checklist' — that's an initiative.
Immediate resultObjectives with three measurable key results each, plus initiatives and how to score them.
ProblemA full inbox hides the five emails that actually need you today.
30 emails from the last 24 hours
Act now: client asking to confirm contract by 5 pm today.
Reply today: 'Thanks — Thursday at 3 works. Sending an invite.'
Deadline: GST filing reminder — 20 Nov.
Immediate resultYour emails sorted into act now, reply today, delegate, read later and ignore, with draft replies.
ProblemBuilding a weekly roster around availability, coverage rules and fairness takes hours.
8 staff, 2 shifts/day, need 3 per shift, max 48 h/week, 11 h rest between shifts
Mon AM: A, B, C · Mon PM: D, E, F
Hours: every person 36–48 h
Gap: Sun PM short by 1 — only 2 available. Ask for a volunteer or hire temp cover.
Immediate resultA weekly roster that meets coverage needs and availability, with conflicts flagged.
All 12 operations & project management skillsAll 200 skillsRead it in the articleProve it: Project Management Fundamentals Certification (free test)
60 research-backed principles in 6 categories — what each one means, why it works on the human brain and how to use it on your own screens. Written by Sushant Singh, founder of Science of Apps, who has scaled consumer apps to lacs of users and spent 10+ years leading product across startups and digital businesses in the US, EU & India.
110 real paywalls from top apps, taken apart, rated out of 5 and decoded with the Laws of UX — plus the frameworks, copy and checklists to ship your own. By Sushant Singh, founder of Science of Apps.