nexus-agent

Answers Nexus CLI questions and corrects mistyped slash commands with valid alternatives.

1|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/rishikksh20/nexus-code-agent --skill nexus-agent-rishikksh20
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: nexus-agent
Source: https://github.com/rishikksh20/nexus-code-agent/tree/main/.agents/skills/nexus-agent
Command: npx skills add https://github.com/rishikksh20/nexus-code-agent --skill nexus-agent-rishikksh20

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Users of the Nexus CLI coding agent often forget exact slash commands, mistype them, or struggle to find the right configuration keys for providers, skills, MCP servers, sessions, and sub-agents. This Skill turns those moments into quick, accurate self-help answers instead of trial-and-error. ## Core Features & Use Cases - Command Typo Recovery: Maps common mistyped commands like /skils list or /ctx usage to the closest valid command such as /skills list or /context usage. - Configuration Guidance: Explains workspace and global config locations (.nexus/config.toml, ~/.nexus/config.toml), skill activation keys, and agent/sub-agent allowlist scoping. - Runtime Reference: Documents slash commands, subcommands, permission modes, MCP management, memory, sessions, and the ask_user clarification flow. - Use Case: A user types /models in the REPL; the unknown command reaches the agent, which responds with the correct /provider command plus a one-line explanation. ## Quick Start Ask the agent how to list active skills or what the correct command is for checking context usage in Nexus.

Frequently Asked Questions about nexus-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix an unknown slash command in the Nexus CLI?▼

Unknown slash commands are forwarded to the agent as natural language, which suggests the closest valid command first. For example, `/skils list` becomes `/skills list`. Run `/help` to see the full command list.

How do I activate or deactivate skills in Nexus?▼

Use `/skills activate <name>` or `/skills deactivate <name>` to persist activation in workspace config via the `enabled_skills` and `disabled_skills` keys. The CLI flag `--skill <name>` activates a skill for one run only without editing config.

Where does Nexus store workspace and global configuration?▼

Workspace config lives at `.nexus/config.toml` and global config at `~/.nexus/config.toml`. MCP server definitions stay in these protected files because they may contain credentials.

How do Nexus sub-agent allowlists work?▼

Sub-agent scopes are defined under `[[sub-agents]]` with `allowed_tools`, `allowed_mcps`, and `allowed_skills`. Empty lists preserve sub-agent defaults, while `"all"` grants every normal workspace tool, active skill, or active MCP server for that scope.

What happens when a Nexus sub-agent needs clarification?▼

The sub-agent returns `status: needs_clarification`; ask the user, then resume the same `subagent_*` tool with `resume_task_id` and a structured `clarification` answer. In non-TTY headless mode, `ask_user` exits with code 4 and a structured `needs_input` request.