agentsclimarketplace

Profit growth audit

Skill intelligems-io/intelligems-mcp-skills/skills/profit-growth-audit

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 profit-growth-audit

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 asks for a profit-focused Intelligems audit that ranks test wins, profit traps, and implementation opportunities from MCP or API data.

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

2.1 KB, 409 tokens by cl100k_base, as published. Nobody here has run it

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-audit

Workflow

  1. Load MCP context if the session has Intelligems MCP access.
  2. Confirm organization, date range, and whether the user wants running tests, ended tests, or both.
  3. Discover relevant experiences with search_experiences or search_experiments.
  4. For each candidate, fetch configuration and metric context with get_experience, get_experience_metrics_config, and analyze_experience.
  5. Pull audience views only when they help explain the profit outcome.
  6. 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:

  1. Executive summary.
  2. Ranked profit opportunities.
  3. Profit traps or warnings.
  4. Segment findings.
  5. Recommended next actions.
  6. 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.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.