Structures the analysis before making a recommendation
The source asks for analysis, classification, ranking, or scoring before it reaches a conclusion or next action.
IntermediateAlireza Rezvani
Process Mapper
Process Mapper is an ecommerce AI skill for Alireza Rezvani, built for teams working with Codex, Claude Code, OpenClaw. Use it to you are connecting recurring work…
- Views
- 0
- Installs
- 0
- Favorites
- 0
What this Skill does
You are connecting recurring work across several systems into one workflow. The first decision to test is whether Documenting procurement intake, vendor/employee onboarding, or expense… and Diagnosing 'too slow' processes where nobody can name the bottleneck hold up together… Start with a small test around “Documenting procurement intake, vendor/employee onboarding, or expense reimbursement processes”, then check whether “Diagnosing 'too slow' processes where nobody can name the bottleneck” fits the way your team actually works.
What makes it different
Before you use it
Source file or structured data
This instruction refers to file or tabular input. Prepare the requested file and confirm that the model you use can read it.
Python runtime
The source includes a Python command or script. A compatible local Python environment is required for that part of the workflow.
No installation needed
Copy and paste into a model chat
- Expand and copy the complete original Skill.md below.
- Open a new conversation in a compatible AI model, then paste it into the chat box.
- Add verified task details, run one low-risk example, and review the result before using it in store operations.
Original Skill.md
The complete source is shown below. Copy it from the top right to use it.
You are a BizOps process-improvement lead. Capture each stage as JSON: name, owner, type (value-add|wait|rework), duration_p50/p90. Run process_documenter.py for ASCII swim-lane diagram by owner. Run cycle_time_analyzer.py for P50/P90 cycle time and value-add ratio. VA% >25%=HEALTHY, 10-25%=TYPICAL, <10%=WASTE-HEAVY. Run bottleneck_detector.py --profile <saas|services|manufacturing|healthcare> with rules: stage P50>2× value-add mean, wait-state>40% of total, rework>15%. Output ranked bottlenecks with severity, root-cause hypothesis, and action. Recommend single constraint-focused intervention per Goldratt — never optimize non-constraint stages. Include rework loops in the map. Label stages honestly — mis-labeling waiting as value-add is the most common failure.Get started
Starter prompts for the main use cases—copy and use them directly.
01Start with one real task
Do not begin with a store-wide rollout. Pick one reversible task where Process Mapper can help you connect systems and automate a multi-step ecommerce workflow. Use this when the input boundary, owner, and one primary measure from successful runs, exception rate, recovery time, execution cost, and unauthorized writes are written down.
Show prompt and variablesHide prompt and variables
Start with one real task
Do not begin with a store-wide rollout. Pick one reversible task where Process Mapper can help you connect systems and automate a multi-step ecommerce workflow. Use this when the input boundary, owner, and one primary measure from successful runs, exception rate, recovery time, execution cost, and unauthorized writes are written down.
Use the Skill above to help me with this task: Start with one real task.
Task details: [TASK_DETAILS]
Constraints or policies to follow: [CONSTRAINTS]
Do not begin with a store-wide rollout. Pick one reversible task where Process Mapper can help you connect systems and automate a multi-step ecommerce workflow.
Return a practical result and clearly flag anything that needs human review.Replace these variables
[TASK_DETAILS]- The facts, context, or source material for this task.
[CONSTRAINTS]- Replace this placeholder with your verified store-specific information.
02Prepare the input and guardrails
Collect only the a process map, test accounts, field mappings, least-privilege credentials, and failure rules needed for this test. Remove unrelated personal data and state which actions must never run automatically. Use this when every input has a known source, sensitive fields are minimized, and the approver knows what the trial can read or change.
Show prompt and variablesHide prompt and variables
Prepare the input and guardrails
Collect only the a process map, test accounts, field mappings, least-privilege credentials, and failure rules needed for this test. Remove unrelated personal data and state which actions must never run automatically. Use this when every input has a known source, sensitive fields are minimized, and the approver knows what the trial can read or change.
Use the Skill above to help me with this task: Prepare the input and guardrails.
Task details: [TASK_DETAILS]
Constraints or policies to follow: [CONSTRAINTS]
Collect only the a process map, test accounts, field mappings, least-privilege credentials, and failure rules needed for this test. Remove unrelated personal data and state which actions must never run automatically.
Return a practical result and clearly flag anything that needs human review.Replace these variables
[TASK_DETAILS]- The facts, context, or source material for this task.
[CONSTRAINTS]- Replace this placeholder with your verified store-specific information.
03Inspect the source Skill, then run it
Read the source, installation method, and permission notes before adding Process Mapper to a separate test project. Keep commands and Skill text exactly as published. Use this when you have a monitored automation workflow that a responsible operator can inspect, and it stayed inside the approved boundary.
Show prompt and variablesHide prompt and variables
Inspect the source Skill, then run it
Read the source, installation method, and permission notes before adding Process Mapper to a separate test project. Keep commands and Skill text exactly as published. Use this when you have a monitored automation workflow that a responsible operator can inspect, and it stayed inside the approved boundary.
Use the Skill above to help me with this task: Inspect the source Skill, then run it.
Task details: [TASK_DETAILS]
Constraints or policies to follow: [CONSTRAINTS]
Read the source, installation method, and permission notes before adding Process Mapper to a separate test project. Keep commands and Skill text exactly as published.
Return a practical result and clearly flag anything that needs human review.Replace these variables
[TASK_DETAILS]- The facts, context, or source material for this task.
[CONSTRAINTS]- Replace this placeholder with your verified store-specific information.
04Review it against a baseline
Do not judge the result by fluency. Compare it with source data, the current SOP, and the pre-test baseline; record factual errors, omissions, and editing time. Use this when successful runs, exception rate, recovery time, execution cost, and unauthorized writes has a pre-test baseline, and errors and exceptions are logged separately.
Show prompt and variablesHide prompt and variables
Review it against a baseline
Do not judge the result by fluency. Compare it with source data, the current SOP, and the pre-test baseline; record factual errors, omissions, and editing time. Use this when successful runs, exception rate, recovery time, execution cost, and unauthorized writes has a pre-test baseline, and errors and exceptions are logged separately.
Use the Skill above to help me with this task: Review it against a baseline.
Task details: [TASK_DETAILS]
Constraints or policies to follow: [CONSTRAINTS]
Do not judge the result by fluency. Compare it with source data, the current SOP, and the pre-test baseline; record factual errors, omissions, and editing time.
Return a practical result and clearly flag anything that needs human review.Replace these variables
[TASK_DETAILS]- The facts, context, or source material for this task.
[CONSTRAINTS]- Replace this placeholder with your verified store-specific information.
Alireza Rezvani
HealthTech CTO and open-source maintainer focused on applied AI, agentic coding, and practical skills for product, research, growth, and operations teams.
Risk, permissions, and limitations
Review third-party permission scopes before providing store data. Never paste payment credentials, customer passwords, or unnecessary personal data into a model. Outputs must be checked by the operator responsible for the workflow.
Content checked:
No reviews yet.