From 7b483b42d17ad8481aa4be71c6f96123e5203ea5 Mon Sep 17 00:00:00 2001 From: "warp-agent-staging[bot]" <240773466+warp-agent-staging[bot]@users.noreply.github.com> Date: Thu, 24 Sep 2026 22:05:53 +0000 Subject: [PATCH 1/2] docs: expand Factory skill guidance Co-Authored-By: Oz --- src/content/docs/factories/factory-skills.mdx | 25 ++++++++++++++++--- 1 file changed, 22 insertions(+), 3 deletions(-) diff --git a/src/content/docs/factories/factory-skills.mdx b/src/content/docs/factories/factory-skills.mdx index 04a59627..65c51b65 100644 --- a/src/content/docs/factories/factory-skills.mdx +++ b/src/content/docs/factories/factory-skills.mdx @@ -13,9 +13,17 @@ Warp Factories is in **Early Access** and available to a limited set of teams. [ A skill tells an agent what to check, how to classify results, what to produce, and when to escalate. In a factory, skills are how you extend or override [default agents](/factories/factory-agents/), without editing their prompts directly. -## Factory-wide and per-agent skills +## Skill sources in a factory -A skill is a directory containing a `SKILL.md`. It's part of the factory's [definition](/factories/factory-as-code/), not an agent's settings. Where you place the directory decides who can use it: +A factory run can use skills from three sources: + +* **Factory role and integration skills** - Baseline procedures that come from the default agent roles and integrations you configure, such as GitHub, Slack, Linear, or Jira. +* **Warp-provided platform-bundled skills** - Product capabilities that Warp makes available when the run supports them, such as `oz-platform`, `factory-files`, and `factory-mcp`. +* **Custom file-based factory skills** - Team-owned `SKILL.md` files in the factory definition, available to every agent or scoped to one agent. + +## Custom file-based factory skills + +A custom skill is a directory containing a `SKILL.md`. It's part of the factory's [definition](/factories/factory-as-code/), not an agent's settings. Where you place the directory decides who can use it: ```text skills/ @@ -43,7 +51,18 @@ Every default agent starts with a baseline of role and integration skills so the These baseline skills aren't files in your definition; they come from the agent roles and integrations you choose. Anything you add under `skills/` or `agents//skills/` extends this baseline rather than replacing it. -Factory role and integration skills are separate from [skills bundled with Warp](/reference/api-and-sdk/#skill-actions-in-conversation-data). Platform-bundled skills include `oz-platform`, `factory-files`, and `factory-mcp`; their availability follows the Warp release and enabled product features. In Conversation API data, a `read_skill` action with `bundled_skill_id` identifies a platform-bundled skill. +## Warp-provided platform-bundled skills + +Platform-bundled skills are separate from factory role and integration skills. They provide Warp capabilities such as operating cloud agents with `oz-platform`, editing factory definitions with `factory-files`, and sending work through Factory MCP with `factory-mcp`. + +The bundled set available to a run depends on the Warp release, release channel, enabled product features, required files, and connected integrations. See the [bundled skill ID catalog](/reference/api-and-sdk/#skill-actions-in-conversation-data) for the authoritative list of stable IDs and availability details. + +## Attribute team-owned skill usage + +The [Conversation API](/api) returns skill loads as `read_skill` actions. Use the action's `input` to classify the skill: + +* **`input.bundled_skill_id` is present** - The action loaded a Warp-provided bundled reference. Exclude it when measuring usage of skills your team owns. +* **Only `input.skill_path` is present** - The value is the path used to resolve the skill. It can identify a file-based skill or a path-referenced bundled skill, including one from a remote host. Count it as team-owned only when the path is under a skill root your team manages, such as `skills/` or `agents//skills/` in the factory definition. ## When to add a custom skill From 67a69e0422f89ee96f465e211b863004a88fedcd Mon Sep 17 00:00:00 2001 From: "warp-agent-staging[bot]" <240773466+warp-agent-staging[bot]@users.noreply.github.com> Date: Thu, 24 Sep 2026 22:19:21 +0000 Subject: [PATCH 2/2] docs: include Factory bundled skill catalog Co-Authored-By: Oz --- src/content/docs/factories/factory-skills.mdx | 25 ++++++++++++++++--- 1 file changed, 22 insertions(+), 3 deletions(-) diff --git a/src/content/docs/factories/factory-skills.mdx b/src/content/docs/factories/factory-skills.mdx index 65c51b65..8af412ce 100644 --- a/src/content/docs/factories/factory-skills.mdx +++ b/src/content/docs/factories/factory-skills.mdx @@ -18,7 +18,7 @@ A skill tells an agent what to check, how to classify results, what to produce, A factory run can use skills from three sources: * **Factory role and integration skills** - Baseline procedures that come from the default agent roles and integrations you configure, such as GitHub, Slack, Linear, or Jira. -* **Warp-provided platform-bundled skills** - Product capabilities that Warp makes available when the run supports them, such as `oz-platform`, `factory-files`, and `factory-mcp`. +* **Warp-provided platform-bundled skills** - Product capabilities that Warp provides, such as `oz-platform`, `factory-files`, and `factory-mcp`. * **Custom file-based factory skills** - Team-owned `SKILL.md` files in the factory definition, available to every agent or scoped to one agent. ## Custom file-based factory skills @@ -55,14 +55,33 @@ These baseline skills aren't files in your definition; they come from the agent Platform-bundled skills are separate from factory role and integration skills. They provide Warp capabilities such as operating cloud agents with `oz-platform`, editing factory definitions with `factory-files`, and sending work through Factory MCP with `factory-mcp`. -The bundled set available to a run depends on the Warp release, release channel, enabled product features, required files, and connected integrations. See the [bundled skill ID catalog](/reference/api-and-sdk/#skill-actions-in-conversation-data) for the authoritative list of stable IDs and availability details. +Warp provides these stable bundled-skill IDs: + +| Bundled skill ID | Purpose | +| --- | --- | +| `add-mcp-server` | Add an MCP server to Warp configuration. | +| `change-keybinding` | Change or remove Warp keyboard shortcuts. | +| `claude-api` | Build and maintain applications that use the Anthropic SDK. | +| `create-skill` | Create, improve, and evaluate skills. | +| `create-tab-config` | Create a Warp tab configuration. | +| `factory-files` | Create and validate file-based Warp factory definitions. | +| `factory-mcp` | Send work to a factory and collaborate through Factory MCP. | +| `modify-settings` | View or change Warp settings using the bundled settings schema. | +| `oz-platform` | Run, configure, and inspect cloud agents through the API and CLI. | +| `pr-comments` | Fetch GitHub pull request review comments for the current branch. | +| `tab-configs` | Look up the tab configuration schema and validation rules. | +| `tui-migrate-setup` | Migrate supported settings into the Warp Agent CLI. | +| `update-tab-config` | Update an existing Warp tab configuration. | +| `warpctrl` | Control and inspect a running Warp app with Warp Control. | + +See [skill actions in conversation data](/reference/api-and-sdk/#skill-actions-in-conversation-data) for the API reference. ## Attribute team-owned skill usage The [Conversation API](/api) returns skill loads as `read_skill` actions. Use the action's `input` to classify the skill: * **`input.bundled_skill_id` is present** - The action loaded a Warp-provided bundled reference. Exclude it when measuring usage of skills your team owns. -* **Only `input.skill_path` is present** - The value is the path used to resolve the skill. It can identify a file-based skill or a path-referenced bundled skill, including one from a remote host. Count it as team-owned only when the path is under a skill root your team manages, such as `skills/` or `agents//skills/` in the factory definition. +* **Only `input.skill_path` is present** - A path alone doesn't identify the skill's owner. Count it as team-owned only when the path is under a skill root your team manages, such as `skills/` or `agents//skills/` in the factory definition. ## When to add a custom skill