Turns customer feedback into structured output
The source asks the model to group, classify, answer, or prioritize review feedback rather than treating every comment as an isolated case.
IntermediateAlireza Rezvani
Analytics Tracking
Analytics Tracking is an ecommerce AI skill for Alireza Rezvani, built for teams working with Codex, Claude Code, OpenClaw. Use it to decide the next budget, product,…
- Views
- 0
- Installs
- 0
- Favorites
- 0
What this Skill does
You need operating data to decide the next budget, product, or channel investment. Validate one concrete path first: Building a GA4 + GTM tracking plan from scratch with event taxonomy and parameter…; Auditing existing analytics for missing events, duplicate tracking, and… Start with a small test around “Building a GA4 + GTM tracking plan from scratch with event taxonomy and parameter definitions”, then check whether “Auditing existing analytics for missing events, duplicate tracking, and consent gaps” 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 an analytics implementation expert. Gather context: GA4/GTM state, tech stack, CMP, existing events, conversions, micro-conversions, campaign needs. Run tracking_plan_generator.py for full tracking plan from funnel definition. Design event taxonomy with object_action naming (snake_case, verb at end): signup_started, checkout_completed, feature_activated. Standard parameters: page_location, user_id, plan_name, value, currency, content_group. Configure GA4 Enhanced Measurement — disable video/file-download if tracked via GTM. Implement via GTM data layer push. Mark key funnel events in GA4. For audits, verify every taxonomy event exists. For debugging, check GTM preview, GA4 DebugView, and consent state.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 Analytics Tracking can help you turn store, pricing, and performance data into operating decisions. Use this when the input boundary, owner, and one primary measure from data completeness, calculation accuracy, contribution margin, and decision follow-through 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 Analytics Tracking can help you turn store, pricing, and performance data into operating decisions. Use this when the input boundary, owner, and one primary measure from data completeness, calculation accuracy, contribution margin, and decision follow-through 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 Analytics Tracking can help you turn store, pricing, and performance data into operating decisions.
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 consistent exports, metric definitions, cost data, date ranges, and known data gaps 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 consistent exports, metric definitions, cost data, date ranges, and known data gaps 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 consistent exports, metric definitions, cost data, date ranges, and known data gaps 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 Analytics Tracking to a separate test project. Keep commands and Skill text exactly as published. Use this when you have a decision-ready analysis 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 Analytics Tracking to a separate test project. Keep commands and Skill text exactly as published. Use this when you have a decision-ready analysis 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 Analytics Tracking 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 data completeness, calculation accuracy, contribution margin, and decision follow-through 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 data completeness, calculation accuracy, contribution margin, and decision follow-through 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
Treat review patterns as hypotheses to test
The instruction can group and prioritize feedback, but repeated wording is not proof of a product defect or customer-wide preference. Check the underlying sample before changing a product, policy, or campaign.
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.