Skills

What skills do

A skill is a set of AI instructions packaged for reuse. Instead of typing the same prompt every time you want the AI to do something specific, you write the instructions once as a skill and invoke it whenever you need it. Skills can have parameters for dynamic inputs, making them adaptable to different contexts.

Skills are how you customize what the AI does for your team. A product team might create skills for "Write a PRD from meeting notes" or "Create a GitHub issue from this bug." A consulting team might create "Generate a client summary" or "Draft a follow-up email."

Creating a skill

Select "Skill" from the create menu. A skill has four parts:

• Title: The name that appears in search results and toolbar buttons
• Description: When and why to use this skill. Helps the AI decide whether to use it and helps teammates understand its purpose.
• Parameters: Optional inputs the skill needs at invocation time (see below)
• Body: The full instructions, written in a rich text editor with formatting support. This is the prompt the AI follows when the skill is invoked.

Skills live in spaces and are accessible from that space's context.

Parameters

Parameters let a skill accept dynamic inputs at invocation time. For example, a "Create GitHub issue" skill might have a parameter for which repository to target.

Each parameter has:

• Label: What the user sees when the skill asks for input
• Type: The kind of input. Text for freeform input, or integration-specific pickers (like a GitHub repository selector or Linear project picker)
• Required: Whether the skill can run without this input

When a skill with parameters is invoked from a toolbar button, the first parameter's picker appears inline. Selecting a value runs the skill immediately.

Invoking skills

Skills can be invoked from several places:

• Chat: Type / in the chat input to search and attach a skill. The AI follows the skill's instructions when responding.
• Type toolbar buttons: Skills attached to a type appear as buttons in the toolbar of every document with that type. Click the button to run the skill on that document.
• Meeting outcomes: Choose "Use Skill" from the outcomes panel to run any skill with the meeting transcript and context.
• @mention: Type @ in chat and select a skill to attach it.

Skills on types

When you configure a type, you can attach skills that appear as toolbar buttons on every document of that type. This is the most powerful pattern for skills: the button is always right where you need it.

For example, attach a "Create GitHub issue" skill to a Bug type. Every bug document gets a one-click button. After the issue is created, the button turns into a green link to the GitHub issue.

System skills

System skills are built-in and read-only. They handle common tasks like creating GitHub issues, creating Linear issues, extracting meeting outcomes, summarizing meetings, generating PRDs and product feedback, and handing off context to coding tools. System skills show a "System Skill" badge and cannot be edited.

The Open in coding tool system skill packages the current document or chat context as a self-contained prompt and hands it off to Claude Code, Cursor, Codex, GitHub Copilot, Lovable, or v0. It is triggered by phrasings like "create a PR", "open a pull request", or "send this to Cursor". When more than one coding tool is enabled, the skill asks you to pick. When the repo or project is not named in the source material, the skill asks where the change should land instead of guessing. See Integrations, Coding tools.

You can use system skills as-is or create your own skills that build on the same patterns.