Index of every page on this site: llms.txt
All skills
deanpeters avatar

/usage-data-investigation

@476ae12
Run it yourself

Investigate what customers actually do from product analytics, with every claim labeled Fact, Inference, or Assumption. Use when you need behavior evidence, not opinions, before deciding.

Use this Skill: https://skilld.dev/gh/deanpeters/product-manager-skills/usage-data-investigation

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

template.md

≈413 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Usage Data Investigation Template

Numbers come from supplied data or are [NEEDS SOURCE]. Every statement carries a label. Quality checks at the bottom.


1. The question

Question: · Unit (account / user / unit): · Window: · Decision it informs: Key event definitions: [exactly what counts as activated, active, commissioned...]

2. Data check

Check Result Limits what we can say
Tracking fires correctly?
Definition stable over the window?
Who is missing?
Enough sample to read?

3. Funnel

Step (a behavior) Count Conversion to next Notes
Biggest drop:

4. Cohorts

Cohort (shared start) Count Month 1 Month 3 Month 6 Metric
Show counts with rates. No conclusions from a cohort of three.

5. Segments

Segment Count Behavior Differs from others?

6. Findings (labeled)

# Statement Label (Fact / Inference / Assumption) Basis

7. What people must answer

Question the data raised Who can answer Interview question or test

8. Next

[Interview / fix tracking / recheck / experiment]


Quality checks

  • A question and a decision were written first
  • The data was checked before it was read
  • Key events are defined and stable
  • Counts appear beside every rate
  • Every statement is labeled Fact, Inference, or Assumption
  • No correlation is presented as cause
  • The "why" questions are handed to people
  • Nothing invented: every number traces to supplied data

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning6d3 checks · Risk SAFE
  • Gen Agent Trust Hub6d

    This skill is a collection of markdown-based workflow instructions for analyzing product usage data. It contains no executable code, scripts, or network-capable operations and is safe to use.

  • Socket6d

    No alerts

  • Snyk6d

    Risk: MEDIUM · 1 issue

Signed by skilld at 476ae12. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated last week
argument-hint
[the question about customer behavior, and what data you can reach]
type
workflow
theme
discovery-research
Other metadata
intent
Turn a question about customer behavior into a disciplined read of product usage data: define the question and the unit of analysis, check the data's trustworthiness, look at funnels, cohorts, and segments, separate what the data shows from what you conclude, and name the follow-up that qualitative research must answer. Quantitative discovery that points to the "why" without claiming it.
best_for
[
  "Finding where customers drop off, and who, before deciding what to build",
  "Checking a belief about behavior against what the product data shows",
  "Reading a launch or trial funnel, cohorts, and segments honestly",
  "Knowing which question the numbers can't answer and a conversation must"
]
scenarios
[
  "Trials start but few reach a first optimized route. Where do they stall?",
  "Leadership says feature X is popular. What does the usage data actually show?",
  "Do customers who onboarded after the fix retain better than those before?",
  "Commissioned units report faults early. Which unit configurations, and when?"
]
estimated_time
45-90 min

README badge

README badge for deanpeters/product-manager-skills/usage-data-investigation