client-brief
Skill1 starsChanged 9 days agoNo licenceView on GitHub
Build a pre-meeting brief on a prospect before a call. Use this skill whenever the user invokes /client-brief, or asks to "prep me for my call with [company/person]", "what do I need to know before this meeting", "build a brief on [prospect]", "research this client before we talk", or anything about getting ready for a sales or pitch conversation. Pull from connected tools (CRM, Notion, email, calendar), web research on the company and person, and anything the user pastes. Always run the anti-AI writing rules on the prose.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- grw-lab/skillstheir own version, first seen Oct 17, 2026
- promptadvisers/claude-code-next-stepstheir own version, first seen Sep 7, 2026
- kshyam/opencode-and-claude-skillsword for word, first seen Aug 30, 2026
- alejopijuan/Claude-Code-Agency-Co-Foundertheir own version, first seen Jul 9, 2026
- coopersimson96/ai-content-systemtheir own version, first seen Jun 25, 2026
Other versions5 projects use a version of this.
Word for word · 1
- kshyam/opencode-and-claude-skills★ 0100% same
Edited · 0
None found.
Wrote their own version · 4
- alejopijuan/Claude-Code-Agency-Co-Founder★ 19same name
- coopersimson96/ai-content-system★ 17same name
- promptadvisers/claude-code-next-steps★ 5same name
- grw-lab/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 repository27 other files it gives its agents.
- be-a-damn-humanSkill
- decideSkill
- deck-builderSkill
- deep-research-synthesizerSkill
- devils-advocateSkill
- fact-checkerSkill
- go-deeperSkill
- grill-meSkill
- handoffSkill
- how-toSkill
- humanizerSkill
- i-have-adhdSkill
- infographic-builderSkill
- linkedin-hookSkill
- linkedin-post-reportSkill
- negotiationSkill
- personal-voiceSkill
- prompt-masterSkill
- reddit-researcherSkill
- red-penSkill
- skill-auditSkill
- write-a-skillSkill
- steSkill
- tc-social-carouselSkill
- tightenSkill
- viral-recipeSkill
- xlsxSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 9 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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.