Terms, licenses, and sources
Look up fields and provenance, distinguishing originals, English adaptations, and external references.
Glossary
| Term | Meaning in this handbook |
|---|---|
| Agent | An executor that uses a model, instructions, and available tools in a host to handle tasks; its capabilities depend on actual configuration and authorization |
| Bot role | Configuration of responsibilities, methods, and prerequisites |
| Host | The application or runtime that runs a Bot or Agent and manages available tools and account authorization |
| Model | The component providing generation and reasoning; available tools and account permissions are configured separately in the host |
| Task workflow | Steps organized around a specific output |
| Fleet | Configuration file for host import review |
| Canonical manifest | Role manifest preserving published version bytes |
| Localized projection | Localized content and download of the same source role |
| Configuration digest | SHA-256 identifying exact download bytes |
| Trust anchor | Independently pinned publisher-verification basis, not bundled here |
| Acceptance | Checking a task output against explicit criteria |
Find licenses and attribution
The 315 roles include 223 source-adapted roles; there are also 56 task workflows. Shared Bots are source links and are excluded from this site’s importable configuration count. For each entry, check license / references in data/entries and the applicable license files.
Original site content and code use MIT. Among 223 attributed roles, mergisi/awesome-grokbot uses CC0-1.0; cobusgreyling/grok-bot-templates and PramodDutta/botskills use MIT. Adaptations retain original instructions, provenance, digests, and applicable notices. Upstream names and brands remain their owners' property.
- Read author, source URL, and template version in details.
- Before redistribution, read applicable licenses and third-party notices and retain required attribution.
- Check each external project's license; a reference link does not grant permission to copy software or assets.
Further reading
How this handbook uses sources
This handbook learns from grokbot-guide's learning paths, scenario acceptance, and layered troubleshooting. Its text and exercises are original. Grok cloud computers, routines, app connections, and approval menus are platform-specific and are not presented as connected OpenBot capabilities. Feature facts rely on this repository's documentation and data contracts; account tasks still need separate acceptance.
Sources
Sources checked: