lamina-quantitative-validation

Solid

Metrics discipline — use only real user-provided data; suggest what to measure post-launch. No invented A/B results.

Code & Development 65 stars 2 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 82/100

Stars 20%
61
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
34
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Metrics Discipline (agent-native) Agents **do not invent** analytics. Quantitative validation is **advisory** until real data exists. ## Allowed - Suggest metrics tied to workflows (completion rate, error rate, time-to-ticket) - Define success signals in `decisions.md` for post-launch - Incorporate user-provided dashboards or experiment results into scope ## Forbidden - Fabricated A/B outcomes - Made-up conversion rates - Claims of statistical significance without user data ## Verify tie-in Use **actor walk success/fail counts** as qualitative proxy pre-launch — not population statistics. ## Related - [Feedback Loops](../lamina-feedback-loops/SKILL.md)

Details

Author
aryaniyaps
Repository
aryaniyaps/lamina
Created
3 weeks ago
Last Updated
today
Language
TypeScript
License
Apache-2.0

Similar Skills

Semantically similar based on skill content — not just same category