Skip to content

docs: explain skills vs plugins vs MCP, and how to create/publish a skill - #3108

Merged
benjaminshafii merged 1 commit into
devfrom
docs/capability-concepts-tutorials
Jul 25, 2026
Merged

docs: explain skills vs plugins vs MCP, and how to create/publish a skill#3108
benjaminshafii merged 1 commit into
devfrom
docs/capability-concepts-tutorials

Conversation

@benjaminshafii

Copy link
Copy Markdown
Member

Why

Enterprise rollout feedback kept returning to the same three questions, and we had no documentation for any of them:

  1. "We know how to make a skill — when do we make a plugin instead?"
  2. "How do I turn what I just did into a reusable skill?"
  3. "Where does a published skill show up, and can I change a shared one without affecting everyone?"

What

Three short pages in the existing house style (title/description frontmatter, 10–30 lines, numbered steps, backticked UI paths), registered in docs.json:

Page Lines Answers
start-here/do-work-with-it/skills-plugins-and-mcp.mdx 19 MCP = the connector, skill = the instructions, plugin = the package. Includes the decision rule: creating a skill already makes a single-skill plugin; reach for a multi-skill plugin when several skills exist to make one system usable.
start-here/do-work-with-it/create-a-skill-from-chat.mdx 29 The real conversational flow — do the task, then ask for a skill.
start-here/do-work-with-it/publish-and-copy-a-skill.mdx 15 Org marketplaces, access scoping, and taking your own copy to customize safely.

Free win: the create-a-skill page uses screenshots that were already committed at packages/docs/images/skill-import-*.png and referenced by no page.

Also fixed

share-your-setup.mdx told readers to open Workspace -> Skills, a surface that no longer exists. Corrected to the live inventory (Settings > Extensions) and cross-linked to the new publish page.

Verification

  • docs.json parses; all five new/changed page paths resolve to real files on disk.
  • Every referenced image verified present with ls.
  • Every internal link target verified to exist.
  • Deliberately not documented: scheduled workflows/automations (removed in 53e0e1d11), and desktop marketplace creation/forking (the desktop app is read-only for marketplaces).

Docs-only, no runtime path — no fraimz.

@vercel

vercel Bot commented Jul 25, 2026

Copy link
Copy Markdown
Contributor

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

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

@mintlify

mintlify Bot commented Jul 25, 2026

Copy link
Copy Markdown
Contributor

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

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

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

@mintlify

mintlify Bot commented Jul 25, 2026

Copy link
Copy Markdown
Contributor

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

Project Status Preview Updated (UTC)
differentai 🟡 Building Jul 25, 2026, 1:00 PM

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

@benjaminshafii
benjaminshafii merged commit 0bbe89d into dev Jul 25, 2026
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant