agentleFS
intelligems-iointelligems-io/intelligems-mcp-skills/skills/profit-trap-detection/SKILL.md

profit-trap-detection

Skill0 starsChanged 5 months agoMITView on GitHub

Use when a user wants to find Intelligems tests where conversion rate improved but revenue per visitor, gross profit, or another profit metric declined.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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
  1. Distinctive:

    Use this skill to catch harmful winners before they are implemented.

    line 9
  2. Distinctive:

    Search ended and active experiments relevant to the request.

    line 14
  3. Distinctive:

    Never call a result safe if profit metrics are missing.

    line 39
  4. Distinctive:

    Use only the user's authenticated MCP or API context.

    line 43

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Profit Trap Detection

Use this skill to catch harmful winners before they are implemented.

Steps

  1. Resolve organization and date range.
  2. Search ended and active experiments relevant to the request.
  3. For each test, fetch overview metrics with analyze_experience.
  4. Compare conversion rate, RPV, GPV, AOV, net revenue, and confidence where available.
  5. Investigate audience breakdowns if the aggregate result hides a segment problem.

Profit Trap Definition

Flag a test when:

  • Conversion rate increases but RPV decreases.
  • Conversion rate increases but GPV or margin proxy decreases.
  • Order volume increases but AOV drops enough to reduce value.
  • A discount, offer, or shipping change wins on orders but loses on profit.
  • A strong segment winner masks broad underperformance.

Output

Return:

  1. Clear list of confirmed, likely, and possible profit traps.
  2. Metric evidence for each trap.
  3. Recommended action: do not implement, segment rollout, extend test, or investigate margin inputs.
  4. Missing data that would change confidence.
  5. Appendix with source tool calls and experience IDs.

Never call a result safe if profit metrics are missing. Mark it as "conversion-only evidence" instead.

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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.