Aim grok context
Context for the aim-grok vessel (A.I.M. engine on Grok CLI): layout, CLI, and first actions. Use when working in aim-grok or adapting engine code. Slash: /aim-grok-context.From its SKILL.md
npx -y skills add BrianV1981/aim-skill-library --skill aim-grok-contextAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
0.8 KB, 174 tokens by cl100k_base, as published. Nobody here has run it
aim-grok-context
Layout
- Work from the vessel project root.
- Engine tree: typically
aim-agy_os/(shared naming with aim-agy for path compat). - CLI:
./aim <cmd>or the project venv →.aim_core/aim_cli.py. - Engine upstream: aim-agy; this vessel is the Grok-host adaptation.
First actions (facts / status)
./aim map
./aim search "<query>"
./aim doctor
Do not
- Edit or commit
memory_lance/,venv/, or other generated stores unless the Operator asks. - Confuse this vessel with aim-agy (or others) without clear Operator scope.
- Invent Engram facts when search is empty.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.