agentleFS
Sign inStart free
MRCalderon3DMRCalderon3D/everything-game-dev-code/skills/engineering-common/telemetry-instrumentation/SKILL.md

telemetry-instrumentation

Skill105 starsChanged 8 months agoMITView on GitHub

Implement analytics and observability hooks that answer product questions without creating noise or privacy risk.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep this skill aligned with the relevant rules layer and current project documentation.

    line 58
  2. Distinctive:

    If engine-specific constraints materially change the workflow, hand off to the matching engine skill or engine-specific reviewer.

    line 59

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Telemetry Instrumentation

Purpose

Implement analytics and observability hooks that answer product questions without creating noise or privacy risk.

Use When

  • a system needs monitoring
  • design wants funnels or tuning data
  • release needs stronger operational visibility

Inputs

  • telemetry plan
  • feature boundaries
  • privacy constraints
  • dashboard or alert consumers

Process

  1. instrument stable behavioral boundaries rather than random low-value clicks
  2. version event schemas and document payloads
  3. route events by environment and consent rules
  4. validate event timing and duplication behavior
  5. connect instrumentation to dashboards or analysis consumers

Outputs

  • instrumented events
  • schema notes
  • validation checklist
  • consumer mapping

Quality Bar

  • makes ownership, state flow, and failure behavior explicit
  • improves maintainability without over-abstracting
  • supports testing, debugging, and safe iteration

Common Failure Modes

  • coupling systems through hidden globals or timing assumptions
  • writing logic that is hard to test or debug
  • optimizing the wrong layer before measuring

Related Agents

  • telemetry-analyst
  • gameplay-programmer
  • liveops-manager

Related Commands

  • telemetry-plan
  • verify
  • learn

Notes

  • Keep this skill aligned with the relevant rules layer and current project documentation.
  • If engine-specific constraints materially change the workflow, hand off to the matching engine skill or engine-specific reviewer.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free