Grok Build¶
Validates Grok Build project configuration, hooks, subagents, and plugin packages. These rules ensure that project settings in .grok/config.toml parse cleanly and contain only project-scoped tables, lifecycle hooks in .grok/hooks/*.json use supported events and valid handler options, and subagents in .grok/agents/*.md define required frontmatter for task delegation. For plugin authors and marketplace maintainers, they verify .grok-plugin/plugin.json manifests, directory structures, and marketplace catalogs (marketplace.json and plugin-index.json).
Grok reads AGENTS.md for portable project instructions and standard Agent Skills from .grok/skills/, which automatically receive skillsaw's shared content and security checks.
Project rules enable automatically when a .grok/ directory is present; plugin and marketplace rules enable when .grok-plugin/ manifests or catalogs are detected.
| Rule ID | Description | Default Severity | Autofix |
|---|---|---|---|
grok-agent-valid |
.grok/agents/*.md must declare a name and a description in frontmatter | error (auto) | - |
grok-config-project-scope |
.grok/config.toml must only carry settings a project file contributes | warning (auto) | - |
grok-config-valid |
.grok/config.toml must parse, and its servers and permissions must load | error (auto) | - |
grok-hooks-valid |
.grok/hooks/*.json must use Grok's hook events, handler types and fields | error (auto) | - |
grok-marketplace-index-parity |
plugin-index.json must agree with its marketplace catalog | warning (auto) | - |
grok-marketplace-json-valid |
.grok-plugin/marketplace.json must be valid JSON with installable entries | error (auto) | - |
grok-plugin-json-valid |
.grok-plugin/plugin.json must be valid JSON with a name Grok's loader accepts | error (auto) | - |
grok-plugin-structure |
A Grok plugin directory needs a manifest or a component Grok installs | warning (auto) | - |