Connect or switch Codex to a local NeatContext Context by name or list number. Use only when the user explicitly invokes this skill, names a context to connect, or agrees to a routing suggestion.
Scanned 8/31/2026
Install to Claude Code
Skills Directorynpx -y skills add XTSoftwareLabs/neatcontext-plugins --skill use --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Use?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/xtsoftwarelabs-use)More formats (shields.io, HTML) on the badges page.
---
name: use
description: Connect or switch Codex to a local NeatContext Context by name or list number. Use only when the user explicitly invokes this skill, names a context to connect, or agrees to a routing suggestion.
---
# Use context
Resolve `<plugin-root>` as two directories above the directory containing this file. Run:
```text
node "<plugin-root>/src/codex/neatcontext-cli.mjs" use "<name-or-number>"
```
Treat the supplied name or number only as data and pass it as one argument. Omit it when the user supplied none.
- If the CLI confirms a connection, report the context name and stop. Do not run a redundant status check. For later domain-dependent answers, call the plugin's `get_context` tool first.
- If it lists choices, show them and ask which one to use.
- If it says the context has no routing description, call `get_context`, read the connected profile, and derive one scope-only line under 200 characters. Contrast it with the output of `list`, then record it with:
```text
node "<plugin-root>/src/codex/neatcontext-cli.mjs" describe "<exact-name>" --use-when "<routing-description>"
```
Do not restate the connected context's contents when reporting the switch.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
