Creates listing and search-content fields together
The source covers product or listing copy alongside SEO-related fields such as keywords, metadata, or image text when those fields are requested.
IntermediateAlireza Rezvani
Marketing Ops
Marketing Ops is an ecommerce AI skill for Alireza Rezvani, built for teams working with Codex, Claude Code, OpenClaw. Use it to you are preparing a formal launch for…
- Views
- 0
- Installs
- 0
- Favorites
- 0
What this Skill does
You are preparing a formal launch for a product, feature, or campaign. The first decision to test is whether Routing a marketing question to the correct specialist skill when unsure which to… and Orchestrating a full product launch campaign across content, copy, email, social,…… Start with a small test around “Routing a marketing question to the correct specialist skill when unsure which to use”, then check whether “Orchestrating a full product launch campaign across content, copy, email, social, and paid channels” fits the way your team actually works.
What makes it different
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 senior marketing operations leader. Route marketing questions to the right specialist skill, orchestrate multi-skill campaigns, and ensure quality. First, check for product marketing context; recommend running marketing-context if absent. Three modes: Route a Question (map trigger phrases to skills via routing matrix), Campaign Orchestration (sequence skills — launch: context→strategy→content→copy→email→social→ads→tracking→analytics), Marketing Audit (cross-functional assessment). Use the routing matrix across content, SEO, CRO, channels, growth, intelligence, and sales/GTM pods. Verify output: context was checked, bottom-line-first format, actions have owners/deadlines, related skills referenced, cross-domain needs flagged.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 Marketing Ops can help you plan campaigns, produce channel-ready material, and control advertising work. Use this when the input boundary, owner, and one primary measure from conversion rate, cost per acquisition, contribution margin, and unsubscribe rate 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 Marketing Ops can help you plan campaigns, produce channel-ready material, and control advertising work. Use this when the input boundary, owner, and one primary measure from conversion rate, cost per acquisition, contribution margin, and unsubscribe rate 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 Marketing Ops can help you plan campaigns, produce channel-ready material, and control advertising 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 the offer, audience, approved claims, brand voice, channel limits, and budget 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 the offer, audience, approved claims, brand voice, channel limits, and budget 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 the offer, audience, approved claims, brand voice, channel limits, and budget 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 Marketing Ops to a separate test project. Keep commands and Skill text exactly as published. Use this when you have a campaign brief or marketing asset 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 Marketing Ops to a separate test project. Keep commands and Skill text exactly as published. Use this when you have a campaign brief or marketing asset 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 Marketing 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 conversion rate, cost per acquisition, contribution margin, and unsubscribe rate 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 conversion rate, cost per acquisition, contribution margin, and unsubscribe rate 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.
Keep claims tied to verified product facts
When this instruction drafts marketing or product content, review specifications, comparisons, performance claims, and testimonials against approved evidence before publishing.
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.