test-roadmap
Skill0 starsChanged 5 months agoMITView on GitHub
Use when a user wants a prioritized Intelligems testing roadmap based on historical results, untested areas, customer segments, and profit opportunities.
In this repository9 other files it gives its agents.
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
- Distinctive: line 9
Use this skill to create a practical next-test plan.
- Distinctive: line 16
Look for patterns by test type, theme, audience, offer, price, page, and funnel step.
- Distinctive: line 17
Check current active tests so recommendations do not duplicate work.
- Distinctive: line 40
Do not suggest mutating live experiences.
- Distinctive: line 44
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
Test Roadmap
Use this skill to create a practical next-test plan.
Steps
- Resolve organization, planning horizon, and business goal.
- Review recent completed tests with
search_experiencesorsearch_experiments. - Analyze winners, losers, and inconclusive tests with
analyze_experience. - Look for patterns by test type, theme, audience, offer, price, page, and funnel step.
- Check current active tests so recommendations do not duplicate work.
- Prioritize test ideas by expected profit impact, learning value, confidence, effort, and risk.
Roadmap Format
Return:
- Strategy summary.
- Findings from historical tests.
- Prioritized test backlog.
- 30/60/90 day roadmap.
- Measurement plan and primary metrics.
- Data gaps and assumptions.
Each test idea should include:
- Hypothesis.
- Target audience or page.
- Primary metric.
- Expected impact.
- Required assets or implementation work.
- Risk and guardrail metrics.
Do not suggest mutating live experiences. This skill plans; it does not create or launch tests.
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.

