defend-calendar
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 “Defend Calendar”. A useful skill states the six fields from Skills and routines. Deep-work blocks are being eaten by meetings, and the owner needs a protection pack: conflict map and unsent decline drafts, calendar left untouched. No event was created, moved, or deleted. Every draft names the event and the block it would protect. Customer/legal/incident items are called out, not declined…
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
- 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
- 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
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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
- Very specific: line 30
No event was created, moved, or deleted.
- Distinctive: line 40
Do not change meetings, send declines, or invite anyone.
≈ “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
Defend Calendar
Paste this into Grok Bot after a successful run:
Save the process we just used as a skill called “Defend Calendar”.
A useful skill states the six fields from Skills and routines.
1. When to use it
Deep-work blocks are being eaten by meetings, and the owner needs a protection pack: conflict map and unsent decline drafts, calendar left untouched.
2. Required inputs and access
- Google Calendar for the named window
- Pinned deep-work hours or a priorities note
- Slack (or mail) where the meeting request arrived, if connected
3. Sequence of work
- Load the calendar window and the pinned deep-work hours. If hours are missing, ask once and stop.
- List events that overlap a deep-work block or stack more than the owner's stated meeting cap.
- For each conflict, draft a decline or reschedule note in the owner's voice. Label it DRAFT. Do not send.
- Propose a hold the owner could accept. Do not create, move, or delete events.
- Flag anything that looks like a customer, legal, or incident meeting so it is not auto-declined in a draft.
4. How to validate the result
No event was created, moved, or deleted. Every draft names the event and the block it would protect. Customer/legal/incident items are called out, not declined by default.
5. What to return
Block map, conflict table, unsent decline drafts, and a "leave these alone" list. Action log of calendars scanned.
6. What requires approval
Do not change meetings, send declines, or invite anyone. Do not decline customer, legal, or incident events without asking.
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.