Test roadmap

Skill intelligems-io/intelligems-mcp-skills/skills/test-roadmap

Ready-to-install Agent Skills for analyzing Intelligems experiments, segments, pricing, and reporting through MCP and API.

Install

npx -y skills add intelligems-io/intelligems-mcp-skills --skill test-roadmap

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when a user wants a prioritized Intelligems testing roadmap based on historical results, untested areas, customer segments, and profit opportunities.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.5 KB, 292 tokens by cl100k_base, as published. Nobody here has run it

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_experiences or search_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.