prep-meeting
Skill14 starsChanged 3 months agoMITView on GitHub
Paste this into Grok Bot after a successful run: Save the process we just used as a skill called “Prep Meeting”. A useful skill states the six fields from Skills and routines. A customer meeting is on the calendar and the owner needs an internal pre-call brief that leads with the last promise and who is in the room. Attendees match the invite. Every promise is a dated quote or explicitly absent. Brief is labeled INTERNAL. No mail or Slack…
4 other projects use a version of this.
Adopted by
Most recently taken up by
- pholbo/getting-things-adhdonetheir own version, first seen Sep 25, 2026
- alejopijuan/Claude-Code-Agency-Co-Foundertheir own version, first seen Jul 9, 2026
- timominkus/obsidian-para-gtd-aitheir own version, first seen Apr 4, 2026
- breethomas/bette-ostheir own version, first seen Mar 8, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- alejopijuan/Claude-Code-Agency-Co-Founder★ 19same name
- timominkus/obsidian-para-gtd-ai★ 9same name
- pholbo/getting-things-adhdone★ 7same name
- breethomas/bette-os★ 0same 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 repository49 other files it gives its agents.
- AGENTS.mdAGENTS.md
- convert/claude.mdCLAUDE.md
- docs/llms.txtllms.txt
- audit-subscriptionsSkill
- cited-researchSkill
- cloud-bill-noteSkill
- collate-feature-asksSkill
- coordinate-launchSkill
- daily-digestSkill
- defend-calendarSkill
- design-bot-templateSkill
- detect-docs-driftSkill
- diff-competitorsSkill
- draft-call-followupSkill
- draft-changelogSkill
- draft-issueSkill
- draft-newsletterSkill
- draft-security-answersSkill
- draft-sqlSkill
- draft-support-replySkill
- garden-memorySkill
- harden-repoSkill
- incident-timelineSkill
- install-teamSkill
- interrogate-assumptionsSkill
- investigate-perfSkill
- log-promisesSkill
- package-evidenceSkill
- plan-tripSkill
- queue-socialSkill
- ramp-new-hireSkill
- rank-account-healthSkill
- recommend-media-reallocSkill
- reconcile-expensesSkill
- remix-contentSkill
- reproduce-bugSkill
- research-accountsSkill
- review-pr-riskSkill
- route-workSkill
- sanitize-shareSkill
- scout-x-threadsSkill
- source-talentSkill
- sweep-ciSkill
- triage-inboxSkill
- vendor-renewalsSkill
- watch-aeoSkill
- watch-brandSkill
- weekly-saas-financeSkill
- write-win-lossSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
3
Distinctive
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
- Distinctive: line 26
Read mail and Slack for attendees.
- Distinctive: line 28
Write one walk-in line and a short "do not reopen" list.
- Distinctive: line 43
Do not send the brief or any pre-read to the customer.
“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.
Files
Prep Meeting
Paste this into Grok Bot after a successful run:
Save the process we just used as a skill called “Prep Meeting”.
A useful skill states the six fields from Skills and routines.
1. When to use it
A customer meeting is on the calendar and the owner needs an internal pre-call brief that leads with the last promise and who is in the room.
2. Required inputs and access
- Calendar event or named meeting
- CRM notes for the account when present
- Gmail threads with attendees
- Slack channels the owner named for that account
- Promise log in /workspace when present
3. Sequence of work
- Open the calendar event. If there is no upcoming customer meeting, stop and say so.
- Pull CRM stage and notes. Mark missing fields unknown.
- Read mail and Slack for attendees. Extract the last dated promise, or write "no promise found".
- List open issues with source links.
- Write one walk-in line and a short "do not reopen" list.
- Label the brief INTERNAL. Do not send it to the customer.
4. How to validate the result
Attendees match the invite. Every promise is a dated quote or explicitly absent. Brief is labeled INTERNAL. No mail or Slack was sent outward.
5. What to return
Internal pre-call brief plus an action log of sources opened.
6. What requires approval
Do not send the brief or any pre-read to the customer. Do not change the calendar event or create CRM records unless the owner names that later.
Type / in the composer to reference a saved skill. If it does not appear, open Settings → Plugins → Yours and enable it for this Bot.
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.