low convictionactive · updated 2026-08-23T00:00:00.000Z
Grok-only skill path → AGENTS.md does not inject → repo `.cursor/skills` symlink → Cloud / Grok Bot load the pack
Grok App Builder auto-lists `.grok/skills`; Cursor / Cloud / Grok Bot do not. AGENTS.md instructs a consult but does not inject skill bodies. A committed `.cursor/skills` → `.grok/skills` symlink plus an alwaysApply rule is what makes Cloud and Grok Bot clones auto-list the same UI doctrine. Machine-local `~/.cursor/rules` do not follow the cloud walk.
The chain
1
Grok App Builder auto-lists `.grok/skills/`; Cursor, Cursor Cloud Agents, and Grok Bot coding agents auto-list `.cursor/skills/` (and user skill dirs), not `.grok/skills/`.
From 2026-08-23-session-cursor-paper-grok-app-builder-workflow: "Grok App Builder and Cursor do not share a skill-discovery path."
From 2026-08-23-session-cursor-paper-grok-app-builder-workflow: "Cursor, Cursor Cloud Agents, and Grok Bot coding agents auto-list `.cursor/skills/`, `.agents/skills/`, and user skill dirs — **not** `.grok/skills/`."
2
Repo `AGENTS.md` tells agents to consult Grok skills but does not inject the skill bodies; without a Read, the agent restyles from memory or Paper skills alone.
From 2026-08-23-session-cursor-paper-grok-app-builder-workflow: "`AGENTS.md` in the repo *tells* agents to consult Grok skills; it does not inject the skill bodies."
From 2026-08-23-session-cursor-paper-grok-app-builder-workflow: "Without a Read, the agent restyles from memory or Paper skills alone."
3
Exposing `.grok/skills` into git as a `.cursor/skills` symlink (plus an alwaysApply rule, installed at clone time by `/link-grok-skills`) lets Cloud / Grok Bot clones auto-list the same UI doctrine.
From 2026-08-23-session-cursor-paper-grok-app-builder-workflow: "Expose `.grok/skills` into git as `.cursor/skills` so Cloud / Grok Bot clones load the same UI doctrine."
From 2026-08-23-session-cursor-paper-grok-app-builder-workflow: "`.cursor/skills` → symlink `../.grok/skills` (git mode `120000`)"
From 2026-08-23-session-cursor-paper-grok-app-builder-workflow: "After clone of a fresh App Builder repo: invoke `/link-grok-skills`, commit, push. Then Cloud / Grok Bot coding agents on that repo auto-list Grok skills."
4
Machine-local `~/.cursor/rules` are not walked by Cloud Agents (discovery starts at `/workspace`); account User Rules are the documented cloud-synced channel.
From 2026-08-23-session-cursor-paper-grok-app-builder-workflow: "Home **rules** (`~/.cursor/rules`) are **not** walked — rule discovery starts at `/workspace` and never reaches `/home/ubuntu`."
From 2026-08-23-session-cursor-paper-grok-app-builder-workflow: "`~/.cursor/rules` is machine-local and currently **not** loaded by cloud rule-walk."
From 2026-08-23-session-cursor-paper-grok-app-builder-workflow: "Account **User Rules** in Cursor Settings are documented as applying across cloud sessions."
What would falsify this
- Step 1: Cursor / Cloud / Grok Bot begin auto-listing `.grok/skills/` without a `.cursor/skills` symlink.
- Step 2: `AGENTS.md` alone injects Grok skill bodies onto the available-skills list.
- Step 4: Cloud Agents load the operator’s laptop `~/.cursor/rules` without account User Rules or a repo rule.
Contradictions / tensions
- Single source. Cursor docs and a forum note are named in the log’s provenance for the `/workspace` walk; those pages were not fetched as separate vault sources.
- Account User Rules “are documented as applying” is the log’s reading of Cursor Settings docs, not a reproduced cloud test in this source.
Implications
- A fresh Grok App Builder checkout needs `/link-grok-skills` → commit `.cursor/` → push before Cloud / Grok Bot consumers will auto-list Grok skills.
- The Mac installer skill is not on the Cloud VM unless copied or committed; cloud agents consume the git result.
- One first-party session on ion-wake (`95d1206`). Treat as a practitioner wiring note, not a Cursor product guarantee.
Companies
Concepts
Open questions
none