Create Harness
ruvnet/metaharness
Scaffold your own focused AI agent harness — pick host (Claude Code, Codex, pi.dev, Hermes), template, agents, skills, and ship a npm-publishable harness with its own npx CLI.
Scaffolds an OpenCode plugin for iPolloWork with the right async factory shape, zod-based tool definitions and hook registration, and explains where to place and register it.
Install OpenCode Plugin Creator
$ npx skills add Devin-AXIS/iPolloWork --skill create-plugin -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Devin-AXIS/iPolloWork create-plugin --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Devin-AXIS/iPolloWork.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.opencode/skills/create-plugin .claude/skills/create-plugin && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "create-plugin" agent skill from https://github.com/Devin-AXIS/iPolloWork/tree/main/.opencode/skills/create-plugin into .claude/skills/create-plugin/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-plugin", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Devin-AXIS/iPolloWork/tree/main/.opencode/skills/create-pluginType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Devin-AXIS/iPolloWork --skill create-plugin -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Devin-AXIS/iPolloWork create-plugin --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Devin-AXIS/iPolloWork.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.opencode/skills/create-plugin .agents/skills/create-plugin && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "create-plugin" agent skill from https://github.com/Devin-AXIS/iPolloWork/tree/main/.opencode/skills/create-plugin into .agents/skills/create-plugin/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-plugin", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Devin-AXIS/iPolloWork --skill create-plugin -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Devin-AXIS/iPolloWork create-plugin --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Devin-AXIS/iPolloWork.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.opencode/skills/create-plugin .cursor/skills/create-plugin && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "create-plugin" agent skill from https://github.com/Devin-AXIS/iPolloWork/tree/main/.opencode/skills/create-plugin into .cursor/skills/create-plugin/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-plugin", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Devin-AXIS/iPolloWork.git --path .opencode/skills/create-plugin--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Devin-AXIS/iPolloWork --skill create-plugin -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Devin-AXIS/iPolloWork create-plugin --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Devin-AXIS/iPolloWork.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.opencode/skills/create-plugin .gemini/skills/create-plugin && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "create-plugin" agent skill from https://github.com/Devin-AXIS/iPolloWork/tree/main/.opencode/skills/create-plugin into .gemini/skills/create-plugin/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-plugin", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Devin-AXIS/iPolloWork create-pluginInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Devin-AXIS/iPolloWork --skill create-plugin -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Devin-AXIS/iPolloWork.git skills-src && mkdir -p .github/skills && cp -r skills-src/.opencode/skills/create-plugin .github/skills/create-plugin && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "create-plugin" agent skill from https://github.com/Devin-AXIS/iPolloWork/tree/main/.opencode/skills/create-plugin into .github/skills/create-plugin/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-plugin", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Devin-AXIS/iPolloWork --skill create-plugin -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Devin-AXIS/iPolloWork create-plugin --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Devin-AXIS/iPolloWork.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.opencode/skills/create-plugin .opencode/skills/create-plugin && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "create-plugin" agent skill from https://github.com/Devin-AXIS/iPolloWork/tree/main/.opencode/skills/create-plugin into .opencode/skills/create-plugin/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-plugin", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
create-plugin- GitHub stars
- 6.8k
- Used in
- 1 other repo
- Token cost
- ~1.3k tokens
- SKILL.md length
- 323 words
- Files
- 1
- Skills in repo
- 30
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Scaffolds an OpenCode plugin for iPolloWork with the right async factory shape, zod-based tool definitions and hook registration, and explains where to place and register it.
- Works in 6 steps: Export default an async function that… → Tool args use zodSchema.shape (a… → execute returns a string or { output:… → …
- Asked to create or write a plugin for iPolloWork or OpenCode
- SKILL.md covers When to use, Plugin API, Anthropic / Claude plugin… and Example: plugin with multiple…, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
This skill covers writing an OpenCode plugin as an async factory function that returns a hooks object. It lists where plugins can live (a project .opencode/plugins folder, a global config folder, an npm package, or a file or https URL in the plugin array) and gives the key rules: tool arguments use a zod schema's .shape, execute returns a string or an output object with optional metadata, and tools are declared in the returned object rather than registered by calls.
It also shows how to register a plugin in opencode.json and compares OpenCode plugins with Anthropic's plugin format: factory function versus manifest, zod versus JSON Schema, in-process runtime versus sandboxed container. A short list explains how to adapt an Anthropic plugin by rewriting tool definitions in zod, moving auth to environment variables or provider config and exporting the factory function.
When your agent uses it
- Asked to create or write a plugin for iPolloWork or OpenCode
- Adding custom tools to an OpenCode setup
- Porting an Anthropic-style plugin to OpenCode
Example prompts
- “Create a plugin that adds a tool for looking up the current git branch.”
- “Write an OpenCode plugin that changes the system prompt for each chat.”
- “Port my Anthropic plugin manifest into an OpenCode plugin.”
Requirements
- An OpenCode or iPolloWork setup
- zod for the tool argument schemas
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Export default an async function that returns the hooks object.
- Tool args use zodSchema.shape (a ZodRawShape), not the ZodObject.
- execute returns a string or { output: string; metadata?: Record }.
- Tools are declared, not registered imperatively — return them in the hooks object.
- fetch() works — plugins run in-process inside the OpenCode runtime.
- process.env is accessible — use env vars for secrets/config.
What it can do on your machine
Read from SKILL.md and the folder at commit 71a74ad. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript and json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
OpenCode Plugin Creator loads about 1.3k tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 323 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 323 words (~1,295 tokens).
“Scaffold a working OpenCode plugin for use in iPolloWork.”
- name
- create-plugin
Files
Just SKILL.md in .opencode/skills/create-plugin of Devin-AXIS/iPolloWork.
Open the folder on GitHubat commit 71a74ad
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in Devin-AXIS/iPolloWork, which our catalogue first saw on October 7, 2026.
Compare with similar skills
OpenCode Plugin Creator next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| OpenCode Plugin Creator this skillDevin-AXIS/iPolloWork | 6.8k | 1 repos | ~1.3k | Automated safety check: Pass | Custom licence | |
| Create Harnessruvnet/metaharness | 690 | — | ~777 | Automated safety check: Pass | MIT | |
| Typescript MCP Server Generatorgithub/awesome-copilot | 40k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Upgrade Starter Kitworkadventure/map-starter-kit | 156 | — | ~1.3k | Automated safety check: Notes | Custom licence | |
| Create Saleor Packagesaleor/apps | 162 | — | ~608 | Automated safety check: Pass | Custom licence | |
| Deno Runtime and Package Managerdenoland/skills | 100 | — | ~2.7k | Automated safety check: Pass | MIT |
Similar skills
- Official
Typescript MCP Server Generator
github/awesome-copilot
Generate a complete MCP server project in TypeScript using the MCP TypeScript SDK v2 (@modelcontextprotocol/server) with tools, resources, and proper configuration
Upgrade Starter Kit
workadventure/map-starter-kit
Upgrade a WorkAdventure map repository to the latest version of the map-starter-kit (github.com/workadventure/map-starter-kit) - refreshes package.json dependencies, vite/tsconfig/build config, CI…
Create Saleor Package
saleor/apps
Scaffold a new shared package in the saleor-apps monorepo under ./packages/.
- Official
Deno Runtime and Package Manager
denoland/skills
Guides writing, running and configuring Deno 2.9+ projects: installing npm and JSR dependencies, permissions, config file precedence and the built-in fmt, lint, test and compile toolchain.
Create Service
TheDecipherist/claude-code-mastery-project-starter-kit
Scaffold a new microservice that follows the project's server/handlers/adapters architecture.
More from Devin-AXIS/iPolloWork
All 30 skills in this repoDaytona Windows Certificate Test
Devin-AXIS/iPolloWork
Reproduces iPolloWork enterprise TLS behavior in a Daytona Windows sandbox by installing a fake corporate CA and proving the app and its runtimes use the OS trust store.
Maintainable Code for iPolloWork
Devin-AXIS/iPolloWork
A code-change gate for the iPolloWork repository: search and reuse first, keep one source of truth, justify every new file or dependency, and audit the change.
Build iPolloWork Templates
Devin-AXIS/iPolloWork
Builds a reusable iPolloWork template for Design, Slides or PPT, or HyperFrames Video through conversation, keeping a manifest, reusable variables and a validated package current.
Agent-First Screenshots
Devin-AXIS/iPolloWork
Has an agent drive the real app through CDP and capture clean, defect-free product screenshots, gated by DOM, pixel and vision checks in a loop.
Daytona Chrome CDP
Devin-AXIS/iPolloWork
Launches a standalone Chrome or Chromium in a Daytona sandbox and drives it over CDP for web sign-in, OAuth and other flows that should bypass the Electron app.
Daytona Cloud Server Setup
Devin-AXIS/iPolloWork
Starts the hosted server side of iPolloWork in a Daytona sandbox, running Den Web, Den API, the worker proxy and MySQL for end-to-end cloud testing.
Related
Works with
Categories
Questions about OpenCode Plugin Creator
What does OpenCode Plugin Creator do?
Scaffolds an OpenCode plugin for iPolloWork with the right async factory shape, zod-based tool definitions and hook registration, and explains where to place and register it. This skill covers writing an OpenCode plugin as an async factory function that returns a hooks object.shape, execute returns a string or an output object with optional metadata, and tools are declared in the returned object rather than registered by calls.
When should I use OpenCode Plugin Creator?
OpenCode Plugin Creator fits situations like: asked to create or write a plugin for iPolloWork or OpenCode; adding custom tools to an OpenCode setup; porting an Anthropic-style plugin to OpenCode.
How do I install OpenCode Plugin Creator in Claude Code?
Run `npx skills add Devin-AXIS/iPolloWork --skill create-plugin -a claude-code`. Or copy the skill folder (.opencode/skills/create-plugin in Devin-AXIS/iPolloWork) into .claude/skills/create-plugin in your project. Claude Code loads it when a task matches its description.
How do I install OpenCode Plugin Creator in Codex?
Run `npx skills add Devin-AXIS/iPolloWork --skill create-plugin -a codex`. Or copy the skill folder (.opencode/skills/create-plugin in Devin-AXIS/iPolloWork) into .agents/skills/create-plugin in your project. Codex loads it when a task matches its description.
Can I use OpenCode Plugin Creator in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Devin-AXIS/iPolloWork --skill create-plugin -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/create-plugin, .gemini/skills/create-plugin, .github/skills/create-plugin and .opencode/skills/create-plugin in your project.
What does OpenCode Plugin Creator need to run?
SKILL.md names no scripts, command-line tools or credentials: OpenCode Plugin Creator is instructions for the agent only. Our summary lists: An OpenCode or iPolloWork setup; zod for the tool argument schemas.
Does OpenCode Plugin Creator access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is OpenCode Plugin Creator safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does OpenCode Plugin Creator use?
OpenCode Plugin Creator has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does OpenCode Plugin Creator use?
About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to OpenCode Plugin Creator?
Skills that share tags, products or a category with OpenCode Plugin Creator: Create Harness (ruvnet/metaharness, 690 stars), Typescript MCP Server Generator (github/awesome-copilot, 40k stars), Upgrade Starter Kit (workadventure/map-starter-kit, 156 stars) and Create Saleor Package (saleor/apps, 162 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains OpenCode Plugin Creator?
Devin-AXIS (a GitHub user) maintains it in Devin-AXIS/iPolloWork, which has 6,758 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 8, 2026.
Source: Devin-AXIS/iPolloWork on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.