plugin-creator
Use this skill to create or debug a plugin that adds tools for yourself.
- License 许可
- Apache-2.0
- 所属仓库
- tschmz/imp
- 最近更新
- 2026-08-23
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- plugin-creator
- description
- Use this skill to create or debug a plugin that adds tools for yourself.
03 SKILL.md 正文
Plugin Creator
Use this skill to add local tools for yourself.
{{#if agent.home}}
Create these plugins under {{agent.home}}/.plugins/<plugin-id>.
{{else}}
Your home path is not available in this turn. Ask the user for the target directory before creating a plugin.
{{/if}}
Hard Rules
- Create plugins under
{{agent.home}}/.plugins/<plugin-id>. - Use
imp-plugin.jsonas the plugin manifest. - Do not hardcode secrets, tokens, API keys, auth file contents, or environment values.
- Keep plugin IDs and tool names to letters, numbers, hyphens, and underscores. Avoid
__in local tool names. - A newly created or changed tool is available on your next turn.
Location And Discovery
Use this plugin directory:
{{agent.home}}/.plugins/<plugin-id>
Directory shape:
{{agent.home}}/
.plugins/
my_tools/
imp-plugin.json
plugin.mjs
Runtime tool names are namespaced:
- Plugin ID:
my_tools - Local tool name:
summarize_file - Tool exposed to you:
my_tools__summarize_file - Alias accepted in configured tool references:
my_tools.summarize_file
Tools from {{agent.home}}/.plugins are automatically added to your available tools on each turn.
Minimal JavaScript Plugin
Create {{agent.home}}/.plugins/my_tools/imp-plugin.json:
{
"schemaVersion": 1,
"id": "my_tools",
"name": "My Tools",
"version": "0.1.0",
"description": "Local tools for me.",
"runtime": {
"module": "./plugin.mjs"
}
}
Create {{agent.home}}/.plugins/my_tools/plugin.mjs:
export function registerPlugin(context) {
return {
tools: [
{
name: "echo",
description: "Echo text back.",
parameters: {
type: "object",
properties: {
text: {
type: "string",
description: "Text to echo."
}
},
required: ["text"],
additionalProperties: false
},
executionMode: "sequential",
async execute(_toolCallId, params, signal) {
if (signal?.aborted) {
throw new Error("Tool call was aborted.");
}
const text = String(params?.text ?? "");
return {
content: [
{
type: "text",
text
}
],
details: {
pluginRoot: context.plugin.rootDir
}
};
}
}
]
};
}
Supported JS module exports:
export function registerPlugin(context) { return { tools: [...] }; }export default function (context) { return { tools: [...] }; }export default { tools: [...] }export const tools = [...]
context has:
{
plugin: {
id: "my_tools",
rootDir: "{{agent.home}}/.plugins/my_tools"
}
}
Tool objects must define:
name: local tool name, for exampleechodescription: clear user-facing descriptionparameters: JSON Schema object for argumentsexecute(toolCallId, params, signal, onUpdate): async function returning a tool result
Tool results should use this shape:
{
content: [
{
type: "text",
text: "Human-readable result"
}
],
details: {
structured: "optional machine-readable data"
}
}
Command Tool Alternative
Use command tools when the tool is better implemented as an executable script. Paths are relative to the plugin root, and the default working directory is the plugin root.
imp-plugin.json:
{
"schemaVersion": 1,
"id": "text_tools",
"name": "Text Tools",
"version": "0.1.0",
"tools": [
{
"name": "word_count",
"description": "Count words in text.",
"inputSchema": {
"type": "object",
"properties": {
"text": {
"type": "string"
}
},
"required": ["text"],
"additionalProperties": false
},
"runner": {
"type": "command",
"command": "node",
"args": ["./word-count.mjs"],
"timeoutMs": 10000
}
}
]
}
word-count.mjs:
const request = JSON.parse(await readStdin());
const text = String(request.input?.text ?? "");
const words = text.trim().length === 0 ? 0 : text.trim().split(/\s+/u).length;
process.stdout.write(JSON.stringify({
content: [
{
type: "text",
text: String(words)
}
],
details: {
words
}
}));
function readStdin() {
return new Promise((resolve, reject) => {
let data = "";
process.stdin.setEncoding("utf8");
process.stdin.on("data", (chunk) => {
data += chunk;
});
process.stdin.on("end", () => resolve(data));
process.stdin.on("error", reject);
});
}
Command tools receive one JSON request on stdin:
{
"schemaVersion": 1,
"pluginId": "text_tools",
"toolName": "text_tools__word_count",
"input": {
"text": "hello world"
}
}
If stdout is JSON with a content array, it is used as the tool result. If stdout is other JSON, it is returned as details and the trimmed JSON text is also exposed. If stdout is plain text, it is returned as text.
Manifest Reference
Common fields for local tool plugins:
{
"schemaVersion": 1,
"id": "plugin_id",
"name": "Human Name",
"version": "0.1.0",
"description": "Adds focused local tools for text processing.",
"runtime": {
"module": "./plugin.mjs"
},
"tools": []
}
Use runtime for JavaScript tools and tools for command tools. Relative paths are resolved from the plugin root. The top-level description describes the plugin. Each tool still needs its own clear description so you can decide when to use it.
Development Workflow
-
Pick a focused plugin ID and one small tool.
-
Create
{{agent.home}}/.plugins/<plugin-id>/imp-plugin.json. -
Add either
plugin.mjswithruntime.moduleor command tool scripts withtools[].runner. -
Validate syntax locally:
node --check {{agent.home}}/.plugins/<plugin-id>/plugin.mjs -
Use the new tool from the next turn.
-
If the tool does not appear, check recent runtime logs if they are available.
Troubleshooting
- Invalid manifest: ensure
schemaVersionis1, identifiers contain only letters, numbers, hyphens, and underscores, and duplicate tool names are not present. - JS plugin load failure: ensure the runtime file exists, is valid ESM, and exports one of the supported shapes.
- Tool name mismatch: call or look for the namespaced name
<plugin-id>__<tool-name>. - Command tool failure: check the subprocess exit code, stderr, and that stdout returns valid JSON with a
contentarray. - Missing new tool immediately after creation: wait for the next turn; tools are resolved before each turn starts.
04 同仓库更多 Skills
release-preparation
Use this skill when the user wants to prepare, document, version, tag, or validate a software release.
imp-administration
Use this skill to inspect, configure, diagnose, back up, restore, or manage the live Imp installation.
skill-creator
Use this skill to create a skill for yourself.
current-time
Use this skill to get the current local date and time.
commit
Use this skill when creating commits in this repository; enforce the repository commit message format.