metrics-definition
Skill0 starsChanged 7 months agoMITView on GitHub
Define, instrument, and track key data points that measure product success, transforming business goals into a quantified feedback loop.
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
- Distinctive: line 16
Proxy Metrics (Behavioral): Search frequency, Share rate.
- Distinctive: line 22
Data Consistency: Ensure that the logical meaning of backend tracking aligns with frontend tracking.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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.
Files
Metrics Definition: Quantitative Metrics and Feedback Loops
What cannot be measured cannot be optimized.
Checklist
- Define Core Events — Which user actions reflect the delivery of core value?
- Develop Instrumentation Plan (Tracking) — Event names, properties, and trigger conditions.
- Categorize Metric Attributes —
- Outcome Metrics: Retention, Revenue.
- Proxy Metrics (Behavioral): Search frequency, Share rate.
- Establish Dashboards — Ensure real-time visibility of data.
Core Mandates
- Prevent Noise: More tracking is not necessarily better. Every data point tracked must correspond to a specific decision.
- Data Consistency: Ensure that the logical meaning of backend tracking aligns with frontend tracking.
- Interpretability: Metrics must be understandable to team members without a data background.
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- launchapp-dev/animus-cli★ 39same name
- miovrag/claude-skills★ 1same name
- nbirkner/digital-brain★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository34 other files it gives its agents.
- agile-scrum-masterySkill
- artifact-provenanceSkill
- brainstormingSkill
- business-acumenSkill
- cross-functional-collaborationSkill
- customer-discoverySkill
- customer-empathySkill
- data-analysisSkill
- gtm-launch-managementSkill
- lean-experimentationSkill
- market-researchSkill
- negotiation-conflict-resolutionSkill
- north-star-metricSkill
- opportunity-mappingSkill
- outcome-ownershipSkill
- presentation-storytellingSkill
- prioritizationSkill
- problem-solvingSkill
- product-definitionSkill
- product-vision-strategySkill
- project-managementSkill
- prototypingSkill
- qa-quality-mindsetSkill
- roadmappingSkill
- spec-driven-designSkill
- stakeholder-managementSkill
- subagent-driven-discoverySkill
- technical-acumenSkill
- user-interviewingSkill
- using-pmpowersSkill
- ux-design-awarenessSkill
- validation-guardSkill
- writing-plansSkill
- written-communicationSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.