Product tracking implementation
Skill yigityildiz0/universal-ai-skill-library/skills/common/product-tracking-implementation
Implement approved product telemetry safely in a scoped codebase, preserving existing behavior and validating emitted event contracts. Use when a reviewed tracking plan and implementation guide already exist and the user asks to add or repair instrumentation.From its SKILL.md
npx -y skills add yigityildiz0/universal-ai-skill-library --skill product-tracking-implementationAssembled 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.6 KB, 251 tokens by cl100k_base, as published. Nobody here has run it
Product Tracking: Implement
Implement only the reviewed telemetry contract. Treat telemetry as non-blocking evidence collection, not business logic.
Preconditions
- An approved plan and repository-specific guide exist, or the user explicitly accepts a narrowly stated draft.
- The target runtime, test method, consent boundary, and destination configuration are known.
Workflow
- Snapshot the relevant source and tests. Restate the exact events and files in scope.
- Reuse the project’s existing telemetry boundary where it exists; do not install or switch vendors without approval.
- Add the smallest changes that emit required events after the underlying action succeeds.
- Pass only schema-approved, minimized properties. Keep identifiers and consent logic consistent with the plan.
- Add or update tests for event name, properties, duplication, error isolation, and opt-out behavior.
- Verify that failed telemetry cannot block the user action. Report files changed and evidence.
Guardrails
- Never expose secrets or live customer data in tests or logs.
- Do not add tracking for unapproved events, hidden clicks, or sensitive content.
- Do not declare delivery verified without an authorized test destination or an observable local boundary.
- Hand off new feature work to
product-tracking-feature-update.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.