agentleFS
intelligems-iointelligems-io/intelligems-mcp-skills/skills/client-performance-review/SKILL.md

client-performance-review

Skill0 starsChanged 5 months agoMITView on GitHub

Use when preparing a monthly or quarterly Intelligems performance review for an agency client, customer, account, or stakeholder meeting.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is 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.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to turn completed and active Intelligems tests into a meeting-ready performance review.

    line 9
  2. Very specific:

    Search for completed tests in the period with search_experiences or search_experiments using status: "ended".

    line 14
  3. Distinctive:

    Keep the narrative honest if the data is inconclusive.

    line 35
  4. Distinctive:

    Do not hide tests with negative results.

    line 36
  5. Distinctive:

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

    line 40

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

Client Performance Review

Use this skill to turn completed and active Intelligems tests into a meeting-ready performance review.

Steps

  1. Resolve organization, review period, and audience for the review.
  2. Search for completed tests in the period with search_experiences or search_experiments using status: "ended".
  3. Include running tests only if the user asks or they materially affect the review.
  4. Analyze each completed test with get_experience, get_experience_metrics_config, and analyze_experience.
  5. Pull segment breakdowns only for tests where they change the story.
  6. Summarize revenue, profit, and learning impact separately.

Review Structure

Return:

  1. Executive summary.
  2. Completed tests: winners, losers, inconclusive tests.
  3. Estimated revenue or profit impact where supported by data.
  4. Strategic learnings by theme.
  5. Tests that should be implemented, repeated, extended, or retired.
  6. Recommended next tests.
  7. Appendix with organization, dates, experience IDs, and caveats.

Quality Bar

  • Explain what happened, why it matters, and what the client should do next.
  • Keep the narrative honest if the data is inconclusive.
  • Do not hide tests with negative results. Convert them into learnings when possible.

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.