Product tracking feature update
Skill yigityildiz0/universal-ai-skill-library/skills/common/product-tracking-feature-update
Update product telemetry when a new feature, flow, experiment, or lifecycle change is introduced. Use for instrument this feature, add analytics to a flow, update tracking plan, or telemetry delta review.From its SKILL.md
npx -y skills add yigityildiz0/universal-ai-skill-library --skill product-tracking-feature-updateAssembled 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, 224 tokens by cl100k_base, as published. Nobody here has run it
Product Tracking: Feature Update
Keep telemetry current as the product changes without accumulating unreviewed events.
Workflow
- Read the feature brief, acceptance criteria, relevant tracking plan, and current code boundary.
- Identify the user decision or value moment that the feature changes. If there is none, explain why new telemetry may be unnecessary.
- Propose a small delta: added, changed, deprecated, and intentionally unchanged events.
- Update event contracts, identity/consent implications, measures, and test cases.
- Implement only after the delta is reviewed, then verify source, tests, and documentation agree.
Output
Use a short change record:
Feature and decision link
Added / changed / deprecated events
Schema and privacy impact
Implementation locations
Validation evidence
Rollback or removal condition
Guardrails
- Do not duplicate an existing event under a new name merely because the UI changed.
- Preserve historical comparability or document a clean measurement break.
- Do not collect experimental, sensitive, or user-generated content without an explicit legal/privacy decision.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.