Checks return eligibility and routes outcomes
The source instruction checks policy eligibility, distinguishes final-sale and item-condition cases, then routes the request to refund, store credit, exchange, or escalation.
IntermediateAlireza Rezvani
Business Operations Skills
Business Operations Skills is an ecommerce AI skill for Alireza Rezvani, built for teams working with Codex, Claude Code, OpenClaw. Use it to you are connecting…
- Views
- 0
- Installs
- 0
- Favorites
- 0
What this Skill does
You are connecting recurring work across several systems into one workflow. Validate one concrete path first: Routing 'where's the bottleneck?' inquiries to the process-mapper sub-skill; Triaging vendor SLA review requests to vendor-management with forked context. Once it holds… Start with a small test around “Routing 'where's the bottleneck?' inquiries to the process-mapper sub-skill”, then check whether “Triaging vendor SLA review requests to vendor-management with forked context” fits the way your team actually works.
What makes it different
Structures the analysis before making a recommendation
The source asks for analysis, classification, ranking, or scoring before it reaches a conclusion or next action.
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 domain orchestrator. Classify inquiries by signal: PROCESS (bottleneck, cycle time, BPMN) → process-mapper; VENDOR (SLA, contract) → vendor-management; CAPACITY (headcount, FTE) → capacity-planner; COMMS (all-hands, FAQ) → internal-comms; KNOWLEDGE (SOP, runbook) → knowledge-ops; PROCUREMENT (spend, SaaS audit) → procurement-optimizer. Two-signal threshold for confident routing; one signal triggers one clarifying question with recommended answer. Fork context to selected sub-skill for heavy ingestion. Return ≤200-word digest: what was analyzed, top 3 findings with canon citations, top 3 actions, artifact path, and one grill challenge. Never run all 6 — pick one, digest, chain on confirmation.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 Business Operations Skills 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 Business Operations Skills 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 Business Operations Skills 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 Business Operations Skills 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 Business Operations Skills 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 Business Operations Skills 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.
Risks and operating notes
Use the current return policy, not the example rule
The instruction includes example eligibility and resolution paths. Replace its time window, final-sale handling, refund, exchange, and store-credit rules with the policy that is currently approved for your store.
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.