profit-growth-audit
Skill0 starsChanged 5 months agoMITView on GitHub
Use when a user asks for a profit-focused Intelligems audit that ranks test wins, profit traps, and implementation opportunities from MCP or API data.
In this repository9 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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 produce a profit-focused audit of Intelligems testing data.
- Distinctive: line 46
Do not call a test a profit win unless profit-oriented metrics support it.
- Distinctive: line 50
Use only the user's authenticated MCP or API context.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Profit Growth Audit
Use this skill to produce a profit-focused audit of Intelligems testing data.
The official public source for this artifact is:
https://github.com/intelligems-io/profit-growth-auditWorkflow
- Load MCP context if the session has Intelligems MCP access.
- Confirm organization, date range, and whether the user wants running tests, ended tests, or both.
- Discover relevant experiences with
search_experiencesorsearch_experiments. - For each candidate, fetch configuration and metric context with
get_experience,get_experience_metrics_config, andanalyze_experience. - Pull audience views only when they help explain the profit outcome.
- Rank opportunities by profit impact, confidence, and implementation readiness.
What To Look For
- Winners with meaningful RPV, GPV, or net revenue lift.
- "Conversion winners" that reduce RPV, GPV, or net revenue.
- Tests that are directionally promising but underpowered.
- Winners not yet implemented.
- Segment-specific opportunities that are stronger than aggregate results.
- Tests that should be extended, ended, or followed up.
Output
Return:
- Executive summary.
- Ranked profit opportunities.
- Profit traps or warnings.
- Segment findings.
- Recommended next actions.
- Source appendix with organization, date range, experience IDs, tool calls, and missing data.
Do not call a test a profit win unless profit-oriented metrics support it. If only conversion rate is available, label the finding as incomplete and ask for the missing metric path.
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.
References
Load references/profit-growth-framework.md when you need the audit rubric.
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.

