docs: refresh create-a-skill-from-chat for the Cloud-first flow

[benjaminshafii]

Why

create-a-skill-from-chat.mdx described a flow that no longer matches the product, and it was the page most likely to be handed to a new user.

Current behavior, verified in code:

• apps/server/src/opencode-plugins/openwork-extensions-preview-steering.ts (~line 141) — Skill creation: Cloud. The agent retrieves and follows the remote create-skill skill and creates the skill in OpenWork Cloud as a private plugin, not in the workspace. add-to-marketplace / add-user-to-marketplace run only when the user asks. A workspace-local skill happens only when explicitly requested, and never both copies.
• apps/server/src/opencode-plugins/openwork-capabilities-knowledge.ts (~line 95) — same intent, agent-facing: do not default to creating a workspace file.

Changed by 72cbe2df8, 48cc26a45, e6f2c604b, f7b1bf585.

What was wrong

1. The page told readers to start from /skill-creator in the composer. That is legacy. The composer builds its slash list dynamically from commands and Connect skills (composer.tsx ~line 732) and there is an explicit assertion that the system prompt no longer ships ## Default Skill: skill-creator (openwork-extensions-preview.test.ts ~line 477). The only remaining path to /skill-creator is a legacy install route in dead settings code.
2. It never said where the skill ends up. That is the single most useful fact, and the one people worry about: it lands in your Cloud organization as a private plugin, visible only to you until you choose to share it.
3. It blurred creating and sharing, so a reader could reasonably think asking for a skill published it to their whole company.

What the page says now

Do the task in chat → ask in plain English to turn it into a reusable skill → it is saved privately in your organization, not written into your workspace → use it by name or let it trigger → refine by asking → share only when you choose, cross-linked to publish-and-copy-a-skill. Closes with a <Note> stating plainly that creating does not publish.

22 lines, non-technical throughout — no tool names, no capability names, no protocol talk.

Screenshots removed

All three were stale and are now deleted, after proving each was orphaned repo-wide:

• skill-import-skill-creator-command.png — depicts the legacy /skill-creator command
• skill-import-use-in-chat.png — local skill menu, not the Cloud private-plugin flow
• skill-import-reload-required.png — reload prompt tied to local skill installation

A screenshot of a command that no longer exists is worse than no screenshot. Fresh captures of the Cloud flow would be a good follow-up.

Verification

docs.json           unchanged (page already registered) + valid
internal link       publish-and-copy-a-skill resolves on disk
orphan check        all 3 deleted images unreferenced repo-wide
line count          22
git diff -- apps/ ee/ packages/types   (empty — docs only)

Slug unchanged, since the URL is already published.

Docs-only, no runtime path — no fraimz.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
openwork-app	Ready	Preview, Comment	Jul 25, 2026 5:05pm
openwork-den	Ready	Preview, Comment	Jul 25, 2026 5:05pm
openwork-den-worker-proxy	Ready	Preview, Comment	Jul 25, 2026 5:05pm
openwork-diagnostics	Ready	Preview, Comment	Jul 25, 2026 5:05pm
openwork-landing	Ready	Preview, Comment, Open in v0	Jul 25, 2026 5:05pm

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
differentai	🟢 Ready	View Preview	Jul 25, 2026, 5:05 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
differentai	🟡 Building	–	Jul 25, 2026, 5:05 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.