Internal authoring and maintenance rules. Readers running the skills do not need
this file — see AGENTS.md and CLAUDE.md instead.
- Each
skills/<name>/SKILL.mdmust start with YAML frontmatter that includesname,description,license, andmetadata(author,version,homepage). - Keep standalone skill docs free of monorepo-only paths like
apps/cli/.... Route cross-skill handoffs via the publishedonekey-*skill names. - Fund-moving skills (
onekey-wallet,onekey-swap) route audit prerequisites toonekey-security. Wallet and swap docs route token research or pricing intents toonekey-market. - Shared operator, safety, response, and cross-domain routing rules live in
each skill's
references/common.md. Keep all four copies in sync when editing shared policy.
.github/workflows/validate.ymlstays dependency-light: shell checks for skill/frontmatter presence andpython -m json.toolfor plugin manifests.- Do not reintroduce Node/TypeScript scaffolding unless a CI requirement actually depends on it.
The repo ships manifests for five agent platforms. When adding or removing skills, update each one:
.claude-plugin/marketplace.json— Claude Code marketplace entry..claude-plugin/plugin.json— Claude Code plugin manifest..cursor-plugin/plugin.json— Cursor plugin manifest..opencode/opencode.json— OpenCodeinstructionsarray (lists eachSKILL.mdpath explicitly)..codex/INSTALL.md/.openclaw/INSTALL.md— user-facing install docs; update the skill table at the bottom.
- If
mainis rebuilt as an orphan root commit during first publication, mergemainback into the feature branch before opening a GitHub PR. GitHub rejects PR creation for unrelated histories.