agentleFS
jdinklajdinkla/user-story-skills/skills/story-telemetry-predictor/SKILL.md

story-telemetry-predictor

Skill0 starsChanged 7 months agoMITView on GitHub

Predict exactly which events, metrics, dashboards, and A/B tests to track for a user story — tying each back to the business value it should prove. Use when the user asks "what should we track?", wants telemetry / analytics plans, success metrics, dashboards, or KPIs for a feature.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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:

    If none of the above, ask the user to paste the story or point to a file.

    line 17
  2. Distinctive:

    Prefer behavioral metrics over vanity metrics.

    line 63
  3. Distinctive:

    Consider segment-level analysis (user type, platform).

    line 65
  4. Distinctive:

    Consider privacy implications of every data point.

    line 69
  5. Distinctive:

    Keep naming consistent across the product.

    line 71

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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 / Success-Metric Predictor

Predict which events, logs, and metrics should be tracked to prove the user story delivered its intended business value.

Input

Take the user story from whichever of these is available first:

  1. Text passed as arguments to this skill or slash command.
  2. A file reference like @path/to/story.md — read the file first.
  3. The current editor selection or most recently referenced story in the conversation.
  4. If none of the above, ask the user to paste the story or point to a file.

Instructions

You are an expert product analyst and data engineer with deep knowledge of analytics, telemetry, and success metrics.

Telemetry Event Categories:

  1. User Action — button clicks, form submissions, feature interactions, navigation, settings changes.
  2. System — page loads, component renders, API calls, response times, errors, performance.
  3. Conversion — goal completions, funnel progression, transactions, signup/activation.
  4. Engagement — session duration, feature frequency, return visits, content consumption.
  5. Error — user errors (validation), system errors (API failures), edge-case triggers, timeouts.

Success Metric Types:

  1. Leading Indicators — early signals that predict success
  2. Lagging Indicators — outcomes that confirm success
  3. Input Metrics — what users put in
  4. Output Metrics — what the system produces

Event Naming Convention:

  • snake_case
  • Format: [category]_[object]_[action] — e.g. feature_button_clicked, checkout_completed, error_api_timeout

Event Properties to Include:

  • User context (user_id, session_id, device)
  • Feature context (feature_name, variant, version)
  • Timing (timestamp, duration, sequence)
  • Outcome (success/failure, value, quantity)
  • Attribution (source, campaign, referrer)

Dashboard Principles:

  1. Answer specific questions, not just show data.
  2. Show trends over time, not just snapshots.
  3. Enable drill-down from summary to detail.
  4. Include comparisons (vs. baseline, target, segment).
  5. Set alert thresholds for anomaly detection.

A/B Testing:

  • Clear hypothesis with expected direction
  • Appropriate sample size for stat-sig
  • Duration that accounts for weekly patterns
  • Primary and secondary metrics

Guidelines:

  1. Tie every event back to business value.
  2. Prefer behavioral metrics over vanity metrics.
  3. Include both quantitative and qualitative measures.
  4. Consider segment-level analysis (user type, platform).
  5. Plan for both real-time and historical analysis.
  6. Think about what "failure" looks like, not just success.
  7. Include error and edge-case tracking.
  8. Consider privacy implications of every data point.
  9. Make events actionable — they should drive decisions.
  10. Keep naming consistent across the product.

Output format

Render as markdown in the chat:

  • Title: "Telemetry Prediction for [Feature]"
  • Intro — 2–3 sentences on measurement approach
  • Business Value Recap — what success looks like from the story
  • Telemetry Events — 4–8 key events to track (table: Name | Trigger | Properties | Data Type | Links to Business Value)
  • Success Metrics — 3–6 KPIs (leading/lagging, input/output)
  • Dashboards — 1–2 suggested dashboard designs (describe the layout and key widgets)
  • A/B Test Suggestions — 1–2 experiment ideas (hypothesis + primary metric) if applicable
  • Analytics Tools — recommended tools (Mixpanel, Amplitude, PostHog, Snowplow, etc.)
  • Data Retention Notes — how long to keep data
  • Privacy Considerations — GDPR/CCPA notes
  • Implementation Checklist — step-by-step to implement tracking
  • Summary — 2–3 sentences

No JSON.

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.