plugin-store

Original：🇺🇸 English

Not Translated

2 scripts

This is the main on-chain DeFi skill. Use it for ALL of the following: Strategy discovery: 'how to make money on-chain', 'any profitable strategies', '链上有什么赚钱机会', '有什么盈利机会', '有什么套利机会', '怎么赚钱', '有什么好的策略', '帮我理财', '有什么收益机会', 'yield opportunities', 'how to earn', 'investment strategy', 'DeFi 策略推荐', '有什么自动化策略', 'automated strategies', 'passive income on-chain', '链上怎么赚币', '怎么玩链上', '怎么玩DeFi', '链上有什么玩法', '有什么赚钱项目', '推荐一些策略'. Plugin/project discovery: '插件商店有什么', '有什么插件', '有什么项目', '什么项目最火', '最热门的项目', '有哪些工具', '推荐一些项目', 'what plugins are available', 'show me plugins', 'what projects are hot', 'trending projects', 'plugin marketplace', '插件市场', '有什么好用的插件'. Capability discovery: '你能做什么', '你有什么能力', '你支持什么', '有什么技能', '都有什么功能', '支持哪些策略', '支持哪些 skill', 'what skills are available', 'what can you do', 'what strategies do you support', 'show me all strategies', 'list all skills'. DApp discovery: 'what dapps are available', 'any good dapps', '有什么好的dapp', '推荐一些dapp', 'recommend dapps', 'show me dapps', 'which protocols can I use', '有什么好的协议', '有什么DeFi协议', '推荐DeFi项目', '有什么链上应用'. Plugin management: 'install a plugin', 'uninstall a plugin', 'list plugins', 'search plugins', 'update plugins', 'show installed', '安装插件', '卸载插件', '更新插件'. Plugin development: 'I want to create a plugin', 'how to submit a plugin', '我想开发一个插件', '怎么提交插件', '如何贡献', 'contribute a plugin', 'build a plugin', 'create a skill', '创建插件', '开发插件', 'hackathon', 'submit my project', '提交我的项目'. Also activates when the skill has just been installed and the user has not yet chosen a direction.

2installs

Sourcemigokg/plugin-store

Added on2026-04-06

NPX Install

npx skill4agent add migokg/plugin-store plugin-store

SKILL.md Content

Plugin Store

A CLI marketplace for installing/uninstalling/updating Skills and MCP servers across Claude Code, Cursor, and OpenClaw. Also an open-source community platform where any developer can submit plugins.

Pre-flight Checks

Read
_shared/preflight.md
for common dependencies (onchainos CLI, skills, install report).

Available Plugins

Always run
plugin-store list
to get the current plugin list — never rely on a hardcoded table.

bash

plugin-store list

Parse the output and present it to the user as a clean table (name, category, downloads, description). The registry updates dynamically; this is the only source of truth.

Skill Routing

User Intent	Action
"What dapps / strategies / skills are available?"	Run `plugin-store list` , present results as a table
"What can you do?" / capability discovery	Run `plugin-store list` , explain capabilities based on live output
"插件商店有什么" / "有什么插件" / "有什么项目"	Run `plugin-store list` , present results as a table
"什么项目最火" / "最热门的项目" / "trending projects"	Run `plugin-store list` , sort by downloads, highlight top entries
"怎么玩DeFi" / "链上怎么赚币" / "链上有什么玩法"	Run `plugin-store list` , introduce categories and recommend starting points
"有什么好的策略" / "推荐策略"	Run `plugin-store list` , filter and highlight trading-strategy category
"有什么DeFi协议" / "推荐DeFi项目"	Run `plugin-store list` , filter and highlight defi-protocol category
"Install X" / "安装 X"	Run `plugin-store install <name> --yes`
"Uninstall X" / "卸载 X"	Run `plugin-store uninstall <name>`
"Update all" / "更新插件"	Run `plugin-store update --all`
"Show installed" / "已安装"	Run `plugin-store installed`
"Search X" / "搜索 X"	Run `plugin-store search <keyword>`
"I want to create/submit a plugin" / "我想开发插件"	Guide through the Developer Workflow below
"How to contribute" / "怎么提交插件" / "hackathon"	Guide through the Developer Workflow below

Command Index

CLI Reference: For full parameter tables, output fields, and error cases, see cli-reference.md.

User Commands


plugin-store list
plugin-store search <keyword>
plugin-store info <name>
plugin-store install <name>
plugin-store install <name> --yes
plugin-store install <name> --skill-only
plugin-store uninstall <name>
plugin-store update --all
plugin-store installed
plugin-store registry update
plugin-store self-update

#	Command	Description
1	`plugin-store list`	List all available plugins in the registry
2	`plugin-store search <keyword>`	Search plugins by name, tag, or description
3	`plugin-store info <name>`	Show detailed plugin info (components, chains, protocols)
4	`plugin-store install <name>`	Install a plugin (interactive agent selection)
5	`plugin-store install <name> --yes`	Install non-interactively (auto-detects agents)
6	`plugin-store install <name> --skill-only`	Install skill component only
7	`plugin-store uninstall <name>`	Uninstall a plugin from all agents
8	`plugin-store update --all`	Update all installed plugins
9	`plugin-store installed`	Show all installed plugins and their status
10	`plugin-store registry update`	Force refresh registry cache
11	`plugin-store self-update`	Update plugin-store CLI itself to latest version

Developer Commands

#	Command	Description
12	`plugin-store init <name>`	Scaffold a new plugin (creates plugin.yaml, SKILL.md, LICENSE, etc.)
13	`plugin-store lint <path>`	Validate a plugin before submission (30+ checks)

Operation Flow

Intent: Strategy / DApp / Capability Discovery

Run
```
plugin-store list
```
to fetch the live registry
Present results as a clean table (name, category, downloads, description)
Suggest next steps: "Want to install one? Just say
```
install <name>
```
"

Intent: Install a Plugin

Run
```
plugin-store install <name> --yes
```
- ```
--yes
```
  skips the community plugin confirmation prompt
- Agent selection is automatic in non-interactive mode (installs to all detected agents)
The CLI will:
- Fetch plugin metadata from registry
- Download and install skill, MCP config, and/or binary as applicable
Immediately after install succeeds, read the installed skill file directly — do NOT ask the user to restart:
```
Read file: ~/.claude/skills/<name>/SKILL.md
```
Then follow the instructions in that file (Pre-flight → onboarding flow). The skill is immediately usable in the current session.

Intent: Manage Installed Plugins

Run
```
plugin-store installed
```
to show current state
Run
```
plugin-store update --all
```
to update everything
Run
```
plugin-store uninstall <name>
```
to remove

Developer Workflow: Create and Submit a Plugin

Plugin Store is an open-source community platform. Any developer can submit a plugin through a Pull Request. The full workflow:

Overview

Two types of plugins:
  Type A: Pure Skill — just a SKILL.md that orchestrates onchainos CLI commands
  Type B: Skill + Source Code — SKILL.md + a CLI tool compiled/installed from your source repo

Five supported languages for source code:
  Rust, Go         → compiled to native binary (~1-20MB)
  TypeScript, Node.js → distributed via npm install (~KB)
  Python           → distributed via pip install (~KB)

Step 1: Fork and scaffold

bash

# Fork https://github.com/okx/plugin-store-community on GitHub, then:
git clone --depth=1 git@github.com:YOUR_USERNAME/plugin-store-community.git
cd plugin-store-community
plugin-store init <your-plugin-name>

This creates

submissions/<your-plugin-name>/

with a complete template:

submissions/<your-plugin-name>/
├── plugin.yaml           # Plugin manifest (fill in your details)
├── skills/<name>/
│   └── SKILL.md          # Skill definition (built-in onchainos demo)
│   └── references/
├── LICENSE
├── CHANGELOG.md
└── README.md

Step 2: Edit plugin.yaml

Pure Skill — just fill in the basics:

yaml

schema_version: 1
name: <your-plugin-name>          # lowercase + hyphens, 2-40 chars
version: "1.0.0"
description: "What your plugin does"
author:
  name: "Your Name"
  github: "your-github-username"  # must match PR submitter
license: MIT
category: utility                 # trading-strategy | defi-protocol | analytics | utility | security | wallet | nft
tags: [keyword1, keyword2]

components:
  skill:
    dir: skills/<your-plugin-name>

api_calls: []                     # external API domains your plugin calls

Skill + Source Code — add a

build

section pointing to your source repo:

yaml

# ... same as above, plus:
build:
  lang: rust                           # rust | go | typescript | node | python
  source_repo: "your-org/your-tool"    # your GitHub repo with source code
  source_commit: "a1b2c3d4e5f6..."     # full 40-char commit SHA (git rev-parse HEAD)
  binary_name: "your-tool"             # compiled output name
  # main: "src/index.js"              # required for typescript/node/python

How to get the commit SHA:

bash

cd your-source-repo
git push origin main
git rev-parse HEAD     # copy this 40-char string into build.source_commit

Step 3: Write SKILL.md

SKILL.md teaches the AI agent how to use your plugin. Required sections:

YAML frontmatter — name, description, version, author, tags
Overview — what the plugin does (2-3 sentences)
Pre-flight Checks — what needs to be installed before use
Commands — specific onchainos commands with When to use / Output
Error Handling — table of common errors and resolutions
Skill Routing — when to defer to other skills

Critical rule: All on-chain write operations (signing, broadcasting, swaps, contract calls) MUST use onchainos CLI. Querying external data sources (third-party APIs, price feeds) is freely allowed.

Step 4: Validate locally

bash

plugin-store lint ./submissions/<your-plugin-name>/

Fix all errors (❌), then re-run until you see ✓. Warnings (⚠️) are advisory.

Step 5: Submit via Pull Request

bash

git checkout -b submit/<your-plugin-name>
git add submissions/<your-plugin-name>/
git commit -m "[new-plugin] <your-plugin-name> v1.0.0"
git push origin submit/<your-plugin-name>

Then create a PR from your fork to

okx/plugin-store-community

. Each PR must contain exactly one plugin.

What happens after submission

Phase 2: Structure check (~30s) — bot validates plugin.yaml + SKILL.md
Phase 3: AI code review (~2min) — Claude reads your code, writes a 9-section report
Phase 4: Build check (if binary) — compiles your source code on 3 platforms
Phase 7: After merge — auto-publishes to registry, users can install immediately

Human review takes 1-3 days. Once merged, your plugin is live:

bash

plugin-store install <your-plugin-name>

Source code requirements by language

Language	Key requirements
Rust	`Cargo.toml` with `[[bin]]` matching `binary_name`
Go	`go.mod` with module declaration, `func main()`
TypeScript	`package.json` with `"bin"` field, entry file has `#!/usr/bin/env node` , must be JS (not .ts)
Node.js	`package.json` with `"bin"` field, entry file has `#!/usr/bin/env node`
Python	`pyproject.toml` with `[build-system]` + `[project.scripts]` , recommend also `setup.py`

Common lint errors

Error	Fix
E031 name format invalid	Use lowercase + hyphens only: `my-cool-plugin`
E052 missing SKILL.md	Put SKILL.md in the path specified by `components.skill.dir`
E110/E111 binary needs build	Add `build` section with `lang` , `source_repo` , `source_commit`
E122 source_repo format	Use `owner/repo` , not full URL
E123 commit SHA invalid	Must be full 40-char hex from `git rev-parse HEAD`

Full guide: https://github.com/okx/plugin-store-community/blob/main/PLUGIN_DEVELOPMENT_GUIDE.md

Supported Agents

Agent	Detection	Skills Path	MCP Config
Claude Code	`~/.claude/` exists	`~/.claude/skills/<plugin>/`	`~/.claude.json` → `mcpServers`
Cursor	`~/.cursor/` exists	`~/.cursor/skills/<plugin>/`	`~/.cursor/mcp.json`
OpenClaw	`~/.openclaw/` exists	`~/.openclaw/skills/<plugin>/`	Same as skills

Plugin Source Trust Levels

Source	Meaning	Behavior
`official`	Plugin Store official	Install directly
`dapp-official`	Published by the DApp project	Install directly
`community`	Community contribution	Show warning, require user confirmation

Error Handling

Error	Action
Network timeout during install	Retry once; if still failing, suggest manual install from https://github.com/okx/plugin-store
`plugin-store: command not found` after install	Try `~/.local/bin/plugin-store` or `~/.cargo/bin/plugin-store` directly; PATH may not be updated for the current session
Command returns non-zero exit	Report error verbatim; suggest `plugin-store self-update`
Registry cache stale / corrupt	Run `plugin-store registry update` to force refresh
`plugin-store lint` fails	Show error codes and fixes; refer to the lint error table above

Skill Self-Update

To update this skill to the latest version:

macOS / Linux:

bash

plugin-store install plugin-store --agent claude-code --skill-only

Or re-run the installer:

bash

curl -sSL https://raw.githubusercontent.com/okx/plugin-store/main/skills/plugin-store/install.sh | sh

<rules> <must> - Always run `plugin-store list` for capability/discovery questions — never use a hardcoded plugin list - Present plugin lists as clean tables (name, category, downloads, description); omit internal fields like registry URLs or file paths - Present capabilities in user-friendly language: "You can trade on Uniswap across 12 chains", not "uniswap-ai supports uniswap-v2, uniswap-v3 protocols" - After any action, suggest 2–3 natural follow-up steps - Support both English and Chinese — respond in the user's language - For developer workflow: always run `plugin-store init` first, then guide through editing, linting, and PR submission - For lint errors: show the error code, explain the fix, and offer to help edit the file </must> <should> - For community-source plugins, proactively warn the user before installing - After installing a plugin, read the installed SKILL.md and trigger the skill's onboarding flow immediately - When guiding plugin development, ask which type (Pure Skill or Skill + Binary) and which language - Suggest running `plugin-store lint` after every edit to catch issues early </should> <never> - Never expose internal skill names, registry URLs, file paths, or MCP config keys to the user - Never auto-reinstall on command failures — report the error and suggest `plugin-store self-update` - Never hardcode a plugin list — always fetch from `plugin-store list` - Never skip the lint step before suggesting PR submission </never> </rules>