log-promises
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 “Log Promises”. A useful skill states the six fields from Skills and routines. After a customer call or thread, commitments must be written down before the next meeting — owner, due date, source quote. Every row has a quote. Dates not in the source are marked unknown, not guessed. Updated promise table and a list of commitments that are already overdue.
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
- package-evidenceSkill
- plan-tripSkill
- prep-meetingSkill
- 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
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
- Distinctive: line 11
After a customer call or thread, commitments must be written down before the next meeting — owner, due date, source quote.
- Distinctive: line 16
Call notes, transcript, or thread
- Distinctive: line 28
Every row has a quote. Dates not in the source are marked unknown, not guessed.
- Distinctive: line 38
Do not send the recap to the customer.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Log Promises
Paste this into Grok Bot after a successful run:
Save the process we just used as a skill called “Log Promises”.
A useful skill states the six fields from Skills and routines.
1. When to use it
After a customer call or thread, commitments must be written down before the next meeting — owner, due date, source quote.
2. Required inputs and access
- Call notes, transcript, or thread
- Existing promise log if any (workspace file)
3. Sequence of work
- Extract statements that bind the company ("we'll send", "by Friday", "included").
- Ignore vibes and sales adjectives.
- For each row record quote, owner if named, date if named, and source link.
- Append to /workspace/promise-log.md. Do not email the customer a recap unless asked.
4. How to validate the result
Every row has a quote. Dates not in the source are marked unknown, not guessed.
5. What to return
Updated promise table and a list of commitments that are already overdue.
6. What requires approval
Do not send the recap to the customer. Do not change CRM stages.
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.