weekly-test-pulse
Skill0 starsChanged 5 months agoMITView on GitHub
Use when a brand operator or agency asks for a quick weekly status report on running Intelligems tests and recommended next actions.
In this repository9 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 5 are distinctive, and 2 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Use this skill for a concise status report on tests that are currently running.
- Very specific: line 16
Use get_experience_metrics_config when you need the correct analytics view type or primary metric.
- Distinctive: line 21
Do not recommend ending a test solely from early conversion lift.
- Distinctive: line 22
Check RPV, GPV, net revenue, AOV, and confidence when available.
- Distinctive: line 23
Call out tests with low traffic, uneven traffic allocation, missing profit metrics, or suspicious segment concentration.
- Very specific: line 24
If a lifecycle action is needed, recommend it but do not run experience_action without explicit approval.
- Distinctive: line 28
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
Weekly Test Pulse
Use this skill for a concise status report on tests that are currently running.
Steps
- Resolve the organization. If ambiguous, use
list_organizationsand ask for the target. - Find running tests with
search_experimentsorsearch_experiencesusingstatus: "started". - For each running test, fetch details with
get_experienceand metrics withanalyze_experience. - Use
get_experience_metrics_configwhen you need the correct analytics view type or primary metric. - Group tests into: likely winner, likely loser, inconclusive, needs more data, and needs attention.
Watchouts
- Do not recommend ending a test solely from early conversion lift.
- Check RPV, GPV, net revenue, AOV, and confidence when available.
- Call out tests with low traffic, uneven traffic allocation, missing profit metrics, or suspicious segment concentration.
- If a lifecycle action is needed, recommend it but do not run
experience_actionwithout explicit approval.
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.
Output
Return:
- One-paragraph pulse summary.
- Table of running tests with status, leading variation, metric direction, confidence, and recommendation.
- Risks or anomalies.
- Exact next actions for the coming week.
- Source appendix with organization, date range, and tool calls.
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.

