agentsclimarketplace

Product tracking audit

Skill yigityildiz0/universal-ai-skill-library/skills/common/product-tracking-audit

Audit what telemetry a codebase actually emits, including event calls, identity handling, properties, and dead instrumentation. Use for analytics inventory, tracking audit, event census, what is currently tracked, or before changing product telemetry.From its SKILL.md

Install
npx -y skills add yigityildiz0/universal-ai-skill-library --skill product-tracking-audit

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

3 things to look at

  • 22 days oldThe repository was created 22 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.9 KB, 314 tokens by cl100k_base, as published. Nobody here has run it

Product Tracking: Audit Current Reality

Describe the current implementation before recommending changes. The audit is a factual census, not a scorecard.

Workflow

  1. Confirm the repository, branches, and directories in scope. Do not inspect production dashboards, credentials, or external accounts unless explicitly authorized.
  2. Detect telemetry libraries and wrappers from dependencies and source calls without assuming a vendor.
  3. For every event definition or call, record exact name, properties, location, trigger context, client/server boundary, and identity/group behavior.
  4. Verify whether named event helpers have real call sites. Mark live, unused, or uncertain; do not guess from a definition alone.
  5. Capture initialization, consent gates, opt-out/reset behavior, error handling, queue/flush behavior, and environment configuration by observation only.
  6. Separate facts from hygiene observations. Recommendations belong in product-tracking-plan.

Output

Return a concise summary plus a machine-readable inventory if requested:

SDK or wrapper observed
Event inventory: name | location | trigger | properties | live status
Identity and organization context
Client/server routing
Observed naming and schema patterns
Unknowns, exclusions, and evidence locations

Guardrails

  • Preserve exact event/property names and casing.
  • Never print keys, tokens, raw identifiers, or customer payloads.
  • Do not install SDKs, alter source, or claim coverage is complete when generated code or unscanned modules remain.
  • Hand off to product-tracking-plan only after the factual baseline is clear.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,834. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.