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
- agiea-brain/agency-skillstheir own version, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- agiea-brain/agency-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- api-integration-builderSkill
- mcp-contextSkill
- price-sensitivity-analysisSkill
- profit-growth-auditSkill
- profit-trap-detectionSkill
- segment-intelligenceSkill
- testing-strategy-health-checkSkill
- test-roadmapSkill
- weekly-test-pulseSkill
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
- Distinctive: line 9
Use this skill to turn completed and active Intelligems tests into a meeting-ready performance review.
- Very specific: line 14
Search for completed tests in the period with search_experiences or search_experiments using status: "ended".
- Distinctive: line 35
Keep the narrative honest if the data is inconclusive.
- Distinctive: line 36
Do not hide tests with negative results.
- Distinctive: line 40
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
Client Performance Review
Use this skill to turn completed and active Intelligems tests into a meeting-ready performance review.
Steps
- Resolve organization, review period, and audience for the review.
- Search for completed tests in the period with
search_experiencesorsearch_experimentsusingstatus: "ended". - Include running tests only if the user asks or they materially affect the review.
- Analyze each completed test with
get_experience,get_experience_metrics_config, andanalyze_experience. - Pull segment breakdowns only for tests where they change the story.
- Summarize revenue, profit, and learning impact separately.
Review Structure
Return:
- Executive summary.
- Completed tests: winners, losers, inconclusive tests.
- Estimated revenue or profit impact where supported by data.
- Strategic learnings by theme.
- Tests that should be implemented, repeated, extended, or retired.
- Recommended next tests.
- 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.
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.

