testing-strategy-health-check
Skill0 starsChanged 5 months agoMITView on GitHub
Use when a user wants to evaluate the health of an Intelligems testing program, including velocity, win rate, test mix, learnings, and coverage gaps.
In this repository9 other files it gives its agents.
- api-integration-builderSkill
- client-performance-reviewSkill
- mcp-contextSkill
- price-sensitivity-analysisSkill
- profit-growth-auditSkill
- profit-trap-detectionSkill
- segment-intelligenceSkill
- test-roadmapSkill
- weekly-test-pulseSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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 9
Use this skill to assess whether an Intelligems testing program is producing useful learning and profit.
- Distinctive: line 21
Use a simple scorecard:
- Distinctive: line 28
Follow-through: winners implemented and learnings reused.
- Distinctive: line 45
Use only the user's authenticated MCP or API context.
≈ “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.
Files
Testing Strategy Health Check
Use this skill to assess whether an Intelligems testing program is producing useful learning and profit.
Steps
- Resolve organization and analysis period.
- Pull completed, active, paused, and pending tests as needed with
search_experiencesorsearch_experiments. - Categorize tests by type, theme, funnel area, metric, and status.
- Analyze outcomes for completed tests.
- Identify bottlenecks: too few launches, too many inconclusive tests, narrow test mix, missing profit metrics, or unimplemented winners.
Scorecard
Use a simple scorecard:
- Velocity: tests launched and completed per period.
- Quality: percent with clear hypothesis and metric fit.
- Win rate: winners, losers, inconclusive.
- Profit orientation: how often profit metrics are used.
- Coverage: pages, audiences, offers, pricing, content, and personalization.
- Follow-through: winners implemented and learnings reused.
Output
Return:
- Health grade with rationale.
- Scorecard.
- Biggest constraints.
- Recommended operating changes.
- Next tests or process improvements.
- Source appendix.
Be candid. A healthy program can have losses if it is learning quickly and avoiding profit traps.
Data Safety
Use only the user's authenticated MCP or API context. Do not save raw responses, exports, graph URLs, order data, customer data, or private store identifiers to the repository. Summarize findings and include experience IDs only when needed for the user's workflow.
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
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.

