Repository navigation
Document grok behavior in the README - #33
Conversation
Replace the leftover cursor-only sentences with the grok defaults, spawn types, bundled skills, plan mode, and benny wake the rest of the port already uses. Co-authored-by: Kaitian Xie <caelaxie@users.noreply.github.com>
caelaxie
left a comment
There was a problem hiding this comment.
pass. readme-only, and every replaced sentence matches #29's smallest fix verbatim (lines 40, 103–105, 214–218, 256–264, 266, 284); author voice and install block untouched. no plugin content touched, so green Validate plugin on 226fbcd is enough proof. Closes #29 present, not a draft. squash-merging.
|
Harness at head Installed checkout
Rest of CI, on this head: frontmatter check A live Installed that's it. the other skills are situational, and the mode skill uses them for you as needed. out of the box every role defaults to `grok-4.6` at `xhigh`. the default panel is `grok-4.6 xhigh` / `grok-4.5 high`. [`/setup-pstack`](./skills/setup-pstack/SKILL.md) changes any of it.
type `/poteto-mode` at the start of each task. the skill has `disable-model-invocation: true`, so it stays off until you invoke it. there is no custom mode to pin.
[`/poteto-mode`](./skills/poteto-mode/SKILL.md) works with `/loop`. each fire cannot see this chat, so the stored prompt must stand alone.
pstack also ships [`subagent_type: "pstack:poteto-agent"`](./agents/poteto-agent.md) as the wrapper for delegates spawned during a run. it reads `poteto-mode` in full, including its inline principles index, before doing any work. omitting `subagent_type` skips that read and drifts. do not spawn `poteto-agent` to run the playbook itself.
[`/poteto-mode`](./skills/poteto-mode/SKILL.md) and [`subagent_type: "pstack:poteto-agent"`](./agents/poteto-agent.md) route through the same wrapper.
pstack also ships [Comment Sicko](./agents/comment-sicko.md), a read-only comment reviewer available as `subagent_type: "pstack:comment-sicko"`. usually invoke it through [`/no-comments`](./skills/no-comments/SKILL.md), not directly.
`/deslop`, `control-cli`, and `control-ui` are bundled in this plugin. `/create-skill` is a Grok Build skill. `/loop` is a Grok Build built-in. inside `poteto-mode`, pr-status requests go to the [babysit playbook](./skills/poteto-mode/playbooks/babysit.md).
grok build plan mode works alongside pstack. but personally, i don't believe in planning. the best spec is code. if you do want to make a plan, [`/poteto-mode`](./skills/poteto-mode/SKILL.md) covers it, but it's not a default.
to set it up, point grok build at [`FOR_AGENTS.md`](./automations/benny/FOR_AGENTS.md). setup copies the pack into the target repository at `.grok/automations/benny/`, enables pstack there for shared skills, and keeps user configuration outside the copied pack. a live wake is `/loop` or `scheduler_create`, and only when you ask. |
Replaces the README sentences that still describe cursor-only behavior. Defaults are
grok-4.6atxhigh, and the panel isgrok-4.6 xhigh/grok-4.5 high./poteto-modestays off until invoked. Delegates usepstack:poteto-agentandpstack:comment-sicko.deslop,control-cli, andcontrol-uiare bundled. Benny copies to.grok/automations/benny/and wakes with/looporscheduler_create.Closes #29