Commands & Skills

Commands are reusable prompt templates that you invoke in AI chat using the / slash syntax. They let your team codify repeatable workflows like bug triage, spec writing, standup summaries, and more — so anyone can get consistent, high-quality AI assistance without crafting the perfect prompt each time.

How Commands Work

1. Type / in the AI chat input to open the command palette
2. Select a command from the dropdown (or keep typing to filter)
3. Add any additional context to your message
4. Press Enter to send

The command's prompt is injected as system context for the AI, guiding its response. You can combine commands with regular text, file attachments, and references to people or records.

Referencing People and Records

Commands support three types of inline references that provide the AI with additional context:

Syntax	What It Does	Example
@member	References a team member — the AI receives their name, role, and organization	@alice
#DISPLAY-ID	References a record — the AI receives the full record content	#TSK-001
/command	Chains another command — its prompt is included alongside the current one	/triage-issue

These references work in both your chat messages and inside command prompt bodies. When the AI processes your message, all references are resolved into rich context automatically.

Built-in Commands

Every workspace comes with a set of built-in command templates:

Command	What It Does
/add-bug	Creates a structured bug report from your description
/feature-request	Drafts a feature request with user stories and acceptance criteria
/summarize-week	Generates a weekly progress summary across all project activity
/triage-issue	Analyzes and triages an issue with priority and assignment recommendations
/write-spec	Generates a technical specification from requirements
/standup	Creates a daily standup update based on your recent activity

Built-in commands cannot be edited directly. To customize one, click Duplicate to Customize to create your own version.

Creating Custom Commands

From Space Settings

Space administrators can create commands available to all workspace members:

1. Go to Settings and select the Commands / Skills section
2. Click + New to create a new command
3. Fill in the command details:
   • Name: A descriptive name (e.g., "Sprint Retrospective")
   • Slug: Auto-generated from the name (e.g., /sprint-retrospective) — this is what users type in chat
   • Description: A short summary shown in the command palette (max 120 characters)
   • Prompt Body: The full prompt template with formatting, references, and instructions
4. Set the visibility (Space, Organization, Team, or Private)
5. Click Create Command

Writing Effective Prompts

The prompt body editor supports rich formatting:

• Text formatting: Bold, italic, underline, strikethrough
• Structure: Headings (H1-H3), bullet lists, numbered lists, blockquotes
• References: @member mentions, #record references, /command chains

Tips for writing good command prompts:

• Be specific about the role: Start with "You are a [role]" to set context
• Define the output format: Describe what the response should look like
• Reference AI tools: Mention which tools the AI should use (e.g., "Use searchRecords to find related issues")
• Keep it focused: One command should do one thing well
• Use chaining: Reference other commands with / to compose complex workflows

Command Chaining

Commands can reference other commands using the / syntax in their prompt body. When a command is invoked, any referenced sub-commands are resolved recursively (up to 3 levels deep) and their prompts are included in the AI context.

For example, a /weekly-review command could reference /summarize-week and /triage-issue to combine their capabilities.

Managing Commands

Editing

Select any command from the list to edit its name, description, or prompt body. Changes take effect immediately for all users who can see the command.

Editing the slug will update references in other commands you have access to, but may break references in commands you cannot see.

Archiving and Deleting

• Archive: Soft-deletes the command. It will no longer appear in the command palette.
• Delete: Permanently removes the command and cannot be undone.

Access Control

Commands support granular access control:

• Space: Visible to all workspace members
• Organization: Visible to members of your organization
• Team: Visible to members of your team
• Private: Visible only to you

After creating a command, you can fine-tune access using the sharing controls.

Frequently Asked Questions

Can I use commands without the AI chat? Commands are currently available through the AI chat interface. External tools can also access commands via the MCP integration (Enterprise plan).

What happens if I reference a command that does not exist? The /slug text remains in your message but is treated as plain text. The AI will not receive any special context for unresolved commands.

Is there a limit to how many commands I can create? There is no hard limit on the number of commands. Commands are available on plans that include AI capabilities.

Can I see what context the AI receives? The resolved system prompt is logged in the Convex function logs for debugging. Contact your workspace administrator for access.