Menu
Explain how to use the Ix Memory Codex plugin, including $-prefixed skill invocation, when to use a specific skill, and example prompts for common workflows.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Analyze system design — structure, coupling, code smells, and high-risk hotspots. Purely graph-based, no code reads.
Root cause analysis — trace execution path to a failure, narrow candidates, read minimal source only at suspected failure points.
Generate narrative-first, importance-weighted documentation for a repo, system, or subsystem with a selective reference layer. Use --full for deeper module/class/method coverage.
Route to the right Ix skill or command for your task
Change risk analysis — blast radius, affected systems, and what to test. Depth scales with risk level; low-risk targets stop early.
Deep dive into a symbol, feature, or bug. Graph-first, minimal code reads, early stopping when sufficient evidence found.
| name | ix-tutorial |
| description | Explain how to use the Ix Memory Codex plugin, including $-prefixed skill invocation, when to use a specific skill, and example prompts for common workflows. |
| argument-hint | ["optional topic or workflow"] |
Do not run ix commands, read files, or inspect the repo. This skill is usage guidance only.
Explain how to use the Ix Memory plugin inside Codex in the way Codex currently supports:
$-prefixed skill invocationix commands only for exact lookupsBe explicit that local Codex plugins may not expose reliable slash-command popups or /skill autocomplete. Prefer $ix-* prompts the user can paste directly into chat.
If $ARGUMENTS is empty, return a short tutorial with:
$skill-nameix commands are best for exact symbol/file lookupsUse this example set, adapted only if the user asked for a narrower topic:
$ix-help how does the auth subsystem work?$ix-understand this repo$ix-investigate IxClient$ix-impact Ix/ix-cli/src/client/api.ts$ix-plan session_start.py common.py$ix-debug ContextService query flowRun ix locate IxClient --format llm.If $ARGUMENTS is non-empty, tailor the tutorial to that workflow. Keep it concise:
If the user asks about slash commands, say they are not the reliable primary UX for this local plugin setup and $skill-name prompts are the recommended path.