Create a plugin in chat
Goal: turn a way of working into a personal plugin without writing JSON by hand.
Before you start: the client is connected and a model is configured (Get started).
Plugin Developer is a built-in plugin. It asks about the method you want to keep, writes a plugin draft in the chat's working folder, checks it, and hands it to the client to install.
1. Start a chat with Plugin Developer
Type / in the message box and choose Plugin Developer. Then describe the work. Include:
- what goes in (a file, a link, a few fields);
- the steps, and which tools or systems they use;
- what a finished result looks like and how to check it;
- what must never happen.
Make a plugin that takes a supplier quote as a PDF, extracts line items into a table,
compares them with our last three quotes in the attached sheet, and flags any price
that rose more than 10%. A result is done when every line has a source page number.
If you just finished a task in another chat, paste the key steps or attach the files, and say "turn this into a plugin".
2. Answer only what changes the result
Plugin Developer drafts a complete plan first and asks only about missing facts that would change it. It chooses a plugin type for you (method, connector, workflow or app).
3. Check and install
The draft is written to soduwork-plugin-draft.json in the chat's working folder, together with any templates, examples, scripts or assets the plugin needs. Plugin Developer rereads the file from disk and checks it before it reports.
Choose Check and install next to the reply. The client collects the draft and its files, runs the pre-check and installs the plugin on this computer.
You don't need to open hidden folders, copy JSON or edit source.
4. Try it
Type / in a new chat and choose your plugin. For a workflow plugin, type / and choose Debug plugin to run it step by step (Debug and package).
What the draft contains
| Field | Purpose |
|---|---|
template | method, connector, workflow or app |
name, version, description, instructions | Identity and the method itself |
inputs | Public parameters filled in when the plugin starts: text, textarea, boolean, number, select |
setup | Non-sensitive preferences each user sets once after installing |
mcpServers, runtimeCapabilities | Connections and computer capabilities it needs |
evaluationInstruction, evaluationCriteria | A representative test and how to judge it |
resources | Files that ship with the plugin |
workflow | Steps, for workflow plugins |
Plugins never store passwords, tokens or API keys. inputs and setup reject them. Company credentials are connected when the plugin is published to an organization.
New and updated plugins should support at least Chinese and English through locales.
Next
- Share it: Publish to your organization
- Edit the workflow by hand: Write your first workflow