Product tracking implementation guide
Skill yigityildiz0/universal-ai-skill-library/skills/common/product-tracking-implementation-guide
Turn an approved product telemetry plan into a repository-specific implementation guide with file locations, sequencing, tests, rollout, and rollback. Use before implementing analytics instrumentation or when requesting a tracking implementation plan.From its SKILL.md
npx -y skills add yigityildiz0/universal-ai-skill-library --skill product-tracking-implementation-guideAssembled 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, 219 tokens by cl100k_base, as published. Nobody here has run it
Product Tracking: Implementation Guide
Map an approved telemetry contract to the actual codebase without changing source code.
Workflow
- Read the approved tracking plan and the factual audit; list missing inputs instead of inventing them.
- Locate initialization, existing wrappers, framework boundaries, authentication transitions, and representative feature paths.
- Prefer one established wrapper or boundary per runtime. Explain any intentional exception.
- Map every planned event to a file, lifecycle point, required data source, and testable acceptance criterion.
- Describe rollout order, feature flags if already available, monitoring, failure isolation, and rollback.
Deliverable
Provide a guide with:
Prerequisites and exclusions
Architecture and ownership
Event-to-code mapping
Identity and consent integration
Test plan and fixtures
Rollout, observability, rollback
Open decisions
Guardrails
- Do not generate provider credentials, secrets, or network calls.
- Do not propose broad refactors solely for telemetry.
- Treat generated events as unimplemented until a code review and representative tests pass.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.