design-bot-template
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 “Design Bot Template”. A useful skill states the six fields from Skills and routines. The owner describes a job, a pain, or a keyword and needs a share-safe Grok Bot operating contract that would pass this repository's schema and Bot Ready score, not a cute persona. Every required SPEC field is present. approval_never has at least three items including one of…
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
- 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
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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 26
Write PROFILE-ready description text with job, sources, how, deliverable, never-list, first task, no-data policy.
- Very specific: line 31
Every required SPEC field is present.
- Distinctive: line 41
Do not create Bots on the owner's account until they say to create them.
≈ “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
Design Bot Template
Paste this into Grok Bot after a successful run:
Save the process we just used as a skill called “Design Bot Template”.
A useful skill states the six fields from Skills and routines.
1. When to use it
The owner describes a job, a pain, or a keyword and needs a share-safe Grok Bot operating contract that would pass this repository's schema and Bot Ready score, not a cute persona.
2. Required inputs and access
- Outcome the Bot must own (one sentence)
- Sources and plugins that actually exist for this owner
- Autonomy target (default L1)
- Approval boundary (what must never happen)
3. Sequence of work
- Parse the outcome. Reject catch-all jobs such as general helper.
- Diagnose missing sources, missing deliverable shape, hallucination risk, and autonomy drift.
- Fill every required template.yaml field from SPEC.md.
- Write PROFILE-ready description text with job, sources, how, deliverable, never-list, first task, no-data policy.
- Score it mentally against Bot Ready. If under 80, rewrite before showing it.
4. How to validate the result
Every required SPEC field is present. approval_never has at least three items including one of send/pay/merge/publish/production. No secrets or internal URLs. First task is runnable on an empty chat.
5. What to return
A complete template.yaml (or PROFILE.md) the owner can paste, plus the Bot Ready checklist with pass/fail per item.
6. What requires approval
Do not create Bots on the owner's account until they say to create them. Do not enable routines. Do not attach a logo.
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.