Skip to main content

Skills and MCP

A Skill is a method document (SKILL.md, plus scripts, references and templates) that an agent reads and follows. An MCP server gives agents tools that reach an outside system. Plugins combine them with inputs, workflows and review (Plugins).

Skills​

Create or improve a Skill​

Use the built-in Skill Authoring plugin. Choose it from the plugin picker (/) or choose Use now on its card in Plugins, then describe the work, the target platform and your business rules. Existing Skills and business files can be attached to the chat.

Skill Authoring produces:

  • a complete SKILL.md with real scripts, references and templates where needed;
  • packages for the general Agent Skills format, Codex, Claude Code, GitHub Copilot and SoduWork;
  • a local SoduWork install draft and an organization .soduwork-plugin;
  • file checksums, a change report and install notes.

It never rewrites the original package or overwrites earlier output. If a host's permissions can't be carried over without loss, that target is blocked until you decide how to handle it.

Import a Skill​

In the client, open Plugins → Skills → Add → Import skill. The pre-check shows every file: SKILL.md, scripts, references, images and templates. Long text pages to the end; binary files can be downloaded. Read-only preview never runs HTML, SVG or scripts. After you confirm, only you can use it.

Click a Skill's name to open its details. The switch next to it controls whether it's enabled.

Packages are rejected if they contain paths outside the package, symbolic links, reserved Windows file names, case conflicts, or a file and folder with the same name.

Share a Skill with your organization​

  1. In the Skill's details, expand Share with other clients, confirm the content can be shared, and submit it for review.
  2. An admin opens Capability catalog → Sharing review in the admin console, reviews each file, and publishes or returns it with comments.
  3. Other clients refresh their Skill catalog and choose it. The exact version is downloaded and cached the next time it runs.

Until it's reviewed, nobody else sees it. Importing a new copy yourself doesn't overwrite the organization version.

MCP servers​

Add a connection​

In the client, open Plugins → Connectors.

  • Import a configuration: JSON with mcpServers, mcp_servers or servers, or Codex TOML mcp_servers, up to 1 MB. The preview never shows secrets. Imported connections start disabled; a duplicate name doesn't overwrite an existing one.
  • Connector Setup: this built-in plugin generates mcp-config.json and mcp-check.json with real scripts. It doesn't install processes or read local keys.

Personal local stdio servers are limited to trusted templates. Custom processes are imported by an admin. Uploading a file never grants permission to run an arbitrary command.

Share a connection​

When you share a personal connection with the company, all authentication headers and environment values are removed and the fields to fill in are kept. An admin checks it in Capability catalog, adds company credentials, tests it and opens it. Other clients then find it and enable it when they need it; it isn't injected into every chat.

Company HTTP servers are tested and called from the Hub. Personal HTTP and stdio servers run on the user's own runner. Tool allow and deny lists, time limits and company disable policies stay in force.

In a plugin, a node lists the MCP servers it needs, and the binding approves individual tools (Capabilities and secrets).

Built-in Skills​

skills/ in the repository contains the Skills shipped with SoduWork. They are all part of the SoduWork project and released under the MIT license:

agent-product-design, app-developer, browser-use, computer-use, mcp-studio, mcp-tools, office, pptx, product-incubator, skill-studio, task

Third-party Skill bundles are not included. If you import one, it keeps its own license; see Third-party notices.

Edit this page