Product tracking business case
Skill yigityildiz0/universal-ai-skill-library/skills/common/product-tracking-business-case
Write a concise, evidence-based business case for product telemetry or analytics instrumentation. Use when asked to justify tracking, telemetry ROI, an analytics investment, or a leadership brief before implementation.From its SKILL.md
npx -y skills add yigityildiz0/universal-ai-skill-library --skill product-tracking-business-caseAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
3 things to look at
- 26 days oldThe repository was created 26 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.4 KB, 223 tokens by cl100k_base, as published. Nobody here has run it
Product Tracking: Business Case
Frame telemetry as a decision-quality investment, not a promise that data automatically creates value.
Workflow
- Identify audience, decision, product outcome, current evidence gaps, and existing analytics capability.
- State the questions the organization cannot answer reliably today, with known evidence and uncertainty.
- Link a minimum telemetry scope to decisions such as activation, retention, adoption, reliability, or support prioritization.
- Describe required work, ownership, privacy review, maintenance, risks, and a bounded pilot.
- Define success evidence and a stop condition; avoid invented ROI or unsupported time savings.
Deliverable
Write a five-minute decision brief:
Decision requested
Current blind spots
Minimum viable telemetry scope
Expected decisions enabled
Cost, ownership, privacy and operational risks
Pilot, success measures, and next decision
Guardrails
- Separate facts, estimates, and assumptions.
- Do not claim that AI, a vendor, or instrumentation alone guarantees business outcomes.
- Do not use customer data or internal financial information outside the authorized scope.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.