# / Commands and Skills

Nimbalyst supports Claude Code and Codex out-of-the-box slash commands, custom commands, and skills.

### Actions vs Commands vs Skills

**Actions** are reusable prompt presets defined in a single `nimbalyst-local/ai-actions.md` file and surfaced as a dropdown in the composer. Pick one and the prompt drops into your draft. Best for "I copy-paste this prompt all the time." See [AI Actions](/session-management/ai-actions.md).

**Commands** are simple markdown files that provide a prompt template. They live in `.claude/commands/` as markdown files. When you type `/command-name`, the contents of that file are sent as a prompt to the agent.

**Skills** are richer integrations that can include instructions, workflows, and tool usage patterns. Nimbalyst ships with built-in skills (like `/commit`), plugins can provide skills, and you can create your own. Skills can define how the agent should behave for specific workflows — for example, a skill that tells the agent how to manage your tracker state when working on blog posts.

### Using Slash Commands and Skills

Type `/` in the AI chat to see all available commands and skills. The typeahead shows all skills — user-created, plugin, and extension skills — so you can quickly find what you need.

Plugin skills are namespaced consistently with commands so the inserted command matches what the agent SDK routes. For example:

* `/excalidraw:excalidraw`
* `/planning:design`
* `/feedback:bug-report`

Skills and commands written for one agent run in the other — workflow discovery is unified across Claude Code and Codex.

### @ Mentions

Type `@` in the AI chat to reference files and folders. The picker opens immediately, with suggestions sorted by **recency** so the files you've most recently opened or edited are at the top. Keep typing to filter, or scroll to find older files. You can mention individual files or entire directories (shown with a folder icon).

Mentioning a file gives the agent direct context about which files you want it to work with, instead of relying on the agent to search for them.

### @@ Session Mentions

Type `@@` in the AI chat to reference another session. The picker shows your sessions in recency order so the conversation you were just in is one keystroke away.

Mentioning a session pulls its context into your current conversation. It's useful when you want the agent to build on prior work, reuse research from an earlier session, or understand decisions made elsewhere — without having to re-explain everything.

### Built-in Example

**`/commit`** - Creates a git commit:

1. Runs `git status` and `git diff`
2. Reviews recent commits for style
3. Drafts a commit message with type prefix (`feat:`, `fix:`, etc.)
4. Stages and commits

### Create Your Own Commands

Custom commands live in `.claude/commands/` as markdown files. Go to the `.claude` directory in your project, then the `commands` folder. Edit or add your own commands there.

You can also go to Settings (click the Gear on the bottom left), then Project Settings to add commands.

### Create Your Own Skills

Skills are a powerful way to teach the agent how to handle recurring workflows. For example, you can create a skill that integrates with the tracker system — telling the agent to update tracker state whenever you're working on certain types of tasks. See [project-wide-plan-task-management.md](broken://pages/SR3dgfjEnZdIBTuLRmdE) for an example.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.nimbalyst.com/session-management/commands-and-skills.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.