Produces the requested working draft
The source is designed to produce the specific draft or structured output described in its instruction, using the information supplied in the conversation.
AdvancedAlireza Rezvani
Knowledge Ops
Knowledge Ops is an ecommerce AI skill for Alireza Rezvani, built for teams working with Codex, Claude Code, OpenClaw. Use it to improve from reviews and customer…
- Views
- 0
- Installs
- 0
- Favorites
- 0
What this Skill does
You are deciding what to improve from reviews and customer feedback. Do not change every step at once: test Quarterly wiki cleanup sprints with prioritized top-20 doc fix list alongside Validating incident runbooks before they go into rotation, then consider letting the team… Start with a small test around “Quarterly wiki cleanup sprints with prioritized top-20 doc fix list”, then check whether “Validating incident runbooks before they go into rotation” 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.
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 Knowledge Operations specialist. Three deterministic Python tools: (1) kb_ingester.py on KB export—ranks top-20 docs to fix, flags orphan pages, stale pages (>12mo), glossary drift, missing owners, cross-link gaps. (2) runbook_validator.py on each runbook—scores steps against 6 checks: named owner, expected duration, observable success signal, observable failure signal, rollback path, escalation contact. ≥80=SAFE, <60=NOT-SAFE. (3) sop_generator.py with --profile (ops|support|finance|hr|it|regulated)—produces 5W2H SOPs with regulatory overlays. Never bulk-generate SOPs without named owners. Fix glossary drift immediately. Metrics that matter: unfindable docs and unsafe runbooks.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 Knowledge Ops can help you handle customer questions, retention signals, and follow-up work. Use this when the input boundary, owner, and one primary measure from resolution quality, reopen rate, response time, and customer satisfaction 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 Knowledge Ops can help you handle customer questions, retention signals, and follow-up work. Use this when the input boundary, owner, and one primary measure from resolution quality, reopen rate, response time, and customer satisfaction 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 Knowledge Ops can help you handle customer questions, retention signals, and follow-up work.
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 current policies, representative conversations, order context, and escalation 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 current policies, representative conversations, order context, and escalation 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 current policies, representative conversations, order context, and escalation 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 Knowledge Ops to a separate test project. Keep commands and Skill text exactly as published. Use this when you have a customer-service or retention 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 Knowledge Ops to a separate test project. Keep commands and Skill text exactly as published. Use this when you have a customer-service or retention 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 Knowledge Ops 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 resolution quality, reopen rate, response time, and customer satisfaction 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 resolution quality, reopen rate, response time, and customer satisfaction 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 minimum customer data needed
The workflow may need an order reference or case facts. Do not paste payment details, full addresses, or unrelated order history into a model conversation; redact them unless they are essential to the decision.
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.