Agent skill

Publish To Nextclaw Marketplace

A skill your agent uses when the user wants to publish or update a local skill in the NextClaw marketplace, especially when they need clear guidance for version readiness, platform login, username…

MITAuto-check passed

Install Publish To Nextclaw Marketplace

skills CLI

$ npx skills add Peiiii/nextclaw --skill publish-to-nextclaw-marketplace -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install Peiiii/nextclaw publish-to-nextclaw-marketplace --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/Peiiii/nextclaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/publish-to-nextclaw-marketplace .claude/skills/publish-to-nextclaw-marketplace && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "publish-to-nextclaw-marketplace" agent skill from https://github.com/Peiiii/nextclaw/tree/master/skills/publish-to-nextclaw-marketplace into .claude/skills/publish-to-nextclaw-marketplace/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-to-nextclaw-marketplace", 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

$skill-installer install https://github.com/Peiiii/nextclaw/tree/master/skills/publish-to-nextclaw-marketplace

Type 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.

skills CLI

$ npx skills add Peiiii/nextclaw --skill publish-to-nextclaw-marketplace -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Peiiii/nextclaw publish-to-nextclaw-marketplace --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Peiiii/nextclaw.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/publish-to-nextclaw-marketplace .agents/skills/publish-to-nextclaw-marketplace && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "publish-to-nextclaw-marketplace" agent skill from https://github.com/Peiiii/nextclaw/tree/master/skills/publish-to-nextclaw-marketplace into .agents/skills/publish-to-nextclaw-marketplace/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-to-nextclaw-marketplace", 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.

skills CLI

$ npx skills add Peiiii/nextclaw --skill publish-to-nextclaw-marketplace -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Peiiii/nextclaw publish-to-nextclaw-marketplace --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Peiiii/nextclaw.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/publish-to-nextclaw-marketplace .cursor/skills/publish-to-nextclaw-marketplace && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "publish-to-nextclaw-marketplace" agent skill from https://github.com/Peiiii/nextclaw/tree/master/skills/publish-to-nextclaw-marketplace into .cursor/skills/publish-to-nextclaw-marketplace/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-to-nextclaw-marketplace", 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

$ gemini skills install https://github.com/Peiiii/nextclaw.git --path skills/publish-to-nextclaw-marketplace

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Peiiii/nextclaw --skill publish-to-nextclaw-marketplace -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Peiiii/nextclaw publish-to-nextclaw-marketplace --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Peiiii/nextclaw.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/publish-to-nextclaw-marketplace .gemini/skills/publish-to-nextclaw-marketplace && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "publish-to-nextclaw-marketplace" agent skill from https://github.com/Peiiii/nextclaw/tree/master/skills/publish-to-nextclaw-marketplace into .gemini/skills/publish-to-nextclaw-marketplace/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-to-nextclaw-marketplace", 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.

GitHub CLI

$ gh skill install Peiiii/nextclaw publish-to-nextclaw-marketplace

Installs 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).

skills CLI

$ npx skills add Peiiii/nextclaw --skill publish-to-nextclaw-marketplace -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Peiiii/nextclaw.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/publish-to-nextclaw-marketplace .github/skills/publish-to-nextclaw-marketplace && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "publish-to-nextclaw-marketplace" agent skill from https://github.com/Peiiii/nextclaw/tree/master/skills/publish-to-nextclaw-marketplace into .github/skills/publish-to-nextclaw-marketplace/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-to-nextclaw-marketplace", 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.

skills CLI

$ npx skills add Peiiii/nextclaw --skill publish-to-nextclaw-marketplace -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Peiiii/nextclaw publish-to-nextclaw-marketplace --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Peiiii/nextclaw.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/publish-to-nextclaw-marketplace .opencode/skills/publish-to-nextclaw-marketplace && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "publish-to-nextclaw-marketplace" agent skill from https://github.com/Peiiii/nextclaw/tree/master/skills/publish-to-nextclaw-marketplace into .opencode/skills/publish-to-nextclaw-marketplace/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-to-nextclaw-marketplace", 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: publish-to-nextclaw-marketplace
GitHub stars: 260
Token cost: ~1.6k tokens
SKILL.md length: 664 words
Files: 2
Skills in repo: 70
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

A skill your agent uses when the user wants to publish or update a local skill in the NextClaw marketplace, especially when they need clear guidance for version readiness, platform login, username…

Works in 4 steps: CLI version → Platform login → Platform username → …
The user wants to publish
SKILL.md covers Overview, Hard Requirement, Marketplace Identity Model and Readiness Checklist, plus 4 more sections
Calls curl; reaches marketplace-api.nextclaw.io and platform.nextclaw.io; needs NEXTCLAW_MARKETPLACE_ADMIN_TOKEN

What it does

Publish To Nextclaw Marketplace is an agent skill from Peiiii/nextclaw. Use when the user wants to publish or update a local skill in the NextClaw marketplace, especially when they need clear guidance for version readiness, platform login, username setup, scoped package naming, and post-publish verification.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `marketplace.json`).

The repository describes itself as: A human-centered long-term AI partner—not a task-centered assistant. The licence is MIT.

When your agent uses it

The user wants to publish
Update a local skill in the NextClaw marketplace
Especially when they need clear guidance for version readiness
Scoped package naming

Example prompts

“/publish-to-nextclaw-marketplace”

Requirements

A credential in NEXTCLAW_MARKETPLACE_ADMIN_TOKEN

Workflow steps

4 steps, taken from the step headings in SKILL.md.

CLI version
Platform login
Platform username
Local skill files

What it can do on your machine

Read from SKILL.md and the folder at commit 4d9d500. 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
Shell commands in SKILL.md call:
- curl
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- marketplace-api.nextclaw.io
- platform.nextclaw.io
- ai-gateway-api.nextclaw.io
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
- NEXTCLAW_MARKETPLACE_ADMIN_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Publish To Nextclaw Marketplace loads about 1.6k tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 664 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~67
When it runs · the whole SKILL.md, loaded when a task matches: ~1.6k

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

The full file from Peiiii/nextclaw at commit 4d9d500, republished under its MIT licence (© Peiiii). 664 words, ~1,635 tokens.

Download SKILL.mdSave it as .claude/skills/publish-to-nextclaw-marketplace/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: publish-to-nextclaw-marketplace
description: Use when the user wants to publish or update a local skill in the NextClaw marketplace, especially when they need clear guidance for version readiness, platform login, username setup, scoped package naming, and post-publish verification.

Publish To NextClaw Marketplace

Overview

Use this skill when the user wants to publish a local skill to the NextClaw marketplace or update an existing listing.

This skill owns the full publishing loop:

check that the local nextclaw version is new enough,
verify platform identity and username readiness,
choose the correct package scope,
run publish or update,
then verify the listing and install path.

Do not pretend the account is ready when it is not. If the user is logged in but still has no platform username, stop and ask them to set it first.

Hard Requirement

This workflow requires NextClaw v0.17.6 or later.

Why:

v0.17.6+ is the baseline that supports scoped marketplace package names such as @nextclaw/my-skill and @alice/my-skill.
It also supports the clearer --scope and --package-name publish parameters.
Personal publishing now depends on the platform username model added in the same release line.

Always verify first:

bash

nextclaw --version

If the version is lower than 0.17.6, do not continue with a fallback flow. Tell the user to upgrade NextClaw first.

Marketplace Identity Model

Treat these fields differently:

slug: the local skill directory name and the skill name segment
package name: the canonical marketplace identifier, shaped like @scope/skill-name

Publishing scopes:

official scope: @nextclaw/<skill-name>
personal scope: @<username>/<skill-name>

Rules:

@nextclaw/* publishing requires admin permission or NEXTCLAW_MARKETPLACE_ADMIN_TOKEN
personal publishing requires an active platform login
personal publishing also requires a platform username
the personal scope must exactly match the current username

Do not blur official and personal publishing together.

Readiness Checklist

Before publishing, check these in order.

1. CLI version

bash

nextclaw --version

Must be 0.17.6 or later.

For normal user publishing, log in first:

bash

nextclaw login --api-base https://ai-gateway-api.nextclaw.io/v1

For official @nextclaw/* publishing, an admin token may also be used through:

bash

NEXTCLAW_MARKETPLACE_ADMIN_TOKEN=...

3. Platform username

If the user wants personal publishing, make sure the platform account already has a username.

Important:

login alone is not enough
the username must already exist on the NextClaw platform account
the canonical web page is https://platform.nextclaw.io/account
the CLI fallback is nextclaw account set-username <username>
if it is missing, direct the user to one of those two concrete paths before publishing

4. Local skill files

The local skill directory should contain at least:

SKILL.md
marketplace.json

The marketplace metadata should be complete and explicit. At minimum, verify:

slug
name
summary
summaryI18n.en
summaryI18n.zh
description
descriptionI18n.en
descriptionI18n.zh
author
tags

Do not publish with half-complete bilingual metadata.

Publish Flow

Use the official marketplace API domain:

text

https://marketplace-api.nextclaw.io

Do not use a workers.dev endpoint as the default public publishing target.

Show full SKILL.md (257 more words)Show less

Publish a new personal skill

bash

nextclaw skills publish ./my-skill \
  --meta ./my-skill/marketplace.json \
  --scope alice \
  --api-base https://marketplace-api.nextclaw.io

Equivalent explicit package name form:

bash

nextclaw skills publish ./my-skill \
  --meta ./my-skill/marketplace.json \
  --package-name @alice/my-skill \
  --api-base https://marketplace-api.nextclaw.io

Publish an official NextClaw skill

bash

nextclaw skills publish ./my-skill \
  --meta ./my-skill/marketplace.json \
  --scope nextclaw \
  --api-base https://marketplace-api.nextclaw.io

Only do this when admin permission is actually present.

Update an existing skill

bash

nextclaw skills update ./my-skill \
  --meta ./my-skill/marketplace.json \
  --package-name @alice/my-skill \
  --api-base https://marketplace-api.nextclaw.io

Default decision rule:

if the marketplace item does not exist yet, use publish
if it already exists, use update

Post-Publish Verification

After publishing, verify the remote item directly.

Example:

bash

curl -sS https://marketplace-api.nextclaw.io/api/v1/skills/items/%40alice%2Fmy-skill

Check for:

HTTP 200
correct canonical packageName
expected slug
complete bilingual summary and description
install kind is marketplace

Then do an install smoke in a temporary directory outside the repo or target workspace:

bash

tmp_dir="$(mktemp -d)"
nextclaw skills install @alice/my-skill --api-base https://marketplace-api.nextclaw.io --workdir "$tmp_dir"
find "$tmp_dir" -maxdepth 3 -type f | sort
rm -rf "$tmp_dir"

The point is to verify real installability without polluting the current repo.

Failure Modes

Version too old

Symptom: scoped publish flags or username-aware flow are missing
Action: upgrade to NextClaw v0.17.6 or later

Not logged in

Symptom: publish rejects because there is no active platform identity
Action: run nextclaw login --api-base https://ai-gateway-api.nextclaw.io/v1

Username missing

Symptom: personal publish fails because the platform account has no username
Action: open https://platform.nextclaw.io/account or run nextclaw account set-username <username>, then retry

Scope mismatch

Symptom: publish rejects @scope/name because the scope does not match the current username
Action: publish under @<your-username>/<skill-name> instead

Insufficient permission for `@nextclaw/*`

Symptom: official scope publishing is rejected
Action: use an admin account or NEXTCLAW_MARKETPLACE_ADMIN_TOKEN, otherwise switch to personal scope

Success Criteria

This skill is working correctly when:

it refuses to continue on nextclaw < 0.17.6
it distinguishes official and personal scope correctly
it does not treat login as a substitute for username readiness
it publishes or updates through marketplace-api.nextclaw.io
it verifies the remote item and install path after upload

Files

SKILL.md and 1 other file in skills/publish-to-nextclaw-marketplace of Peiiii/nextclaw.

SKILL.md
marketplace.json

Open the folder on GitHubat commit 4d9d500

Compare with similar skills

Publish To Nextclaw Marketplace 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.

Publish To Nextclaw Marketplace compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Publish To Nextclaw Marketplace this skillPeiiii/nextclaw	260	—	~1.6k	Automated safety check: Pass	MIT	yesterday
Publishcode-yeongyu/oh-my-openagent	70k	—	~5.5k	Automated safety check: Warn	Custom licence	today
Social Publisheraffaan-m/ECC	277k	1 repos	~1.1k	Automated safety check: Pass	MIT	today
Publishyc-software/qm	15k	—	~2.2k	Automated safety check: Warn	MIT	yesterday
Social Publishingwshobson/agents	40k	—	~914	Automated safety check: Pass	MIT	6 days ago
PublishQ00/ouroboros	6.2k	—	~2.7k	Automated safety check: Pass	MIT	3 days ago

Similar skills

Publish
code-yeongyu/oh-my-openagent
Publish oh-my-opencode to npm by triggering the GitHub Actions publish workflow and verifying its artifacts.
70k GitHub stars~5.5k tokensUpdated today
DevOps & CloudAuto-check: warnings
Social Publisher
affaan-m/ECC
Agent-driven scheduling and publishing of social media posts across 13 platforms via SocialClaw.
277k GitHub starsUsed in 1 repo~1.1k tokens
Writing & ContentAuto-check passed
Publish
yc-software/qm
Publish a long-lived internal web app, site, or dashboard from the agent computer.
15k GitHub stars~2.2k tokensUpdated yesterday
DevOps & CloudAuto-check: warnings
Social Publishing
wshobson/agents
Schedule and publish social media posts across 13 platforms (X, LinkedIn, Instagram, Facebook Pages, TikTok, Discord, Telegram, YouTube, Reddit, WordPress, Pinterest) via the SocialClaw API.
40k GitHub stars~914 tokensUpdated 6 days ago
Writing & ContentAuto-check passed
Publish
Q00/ouroboros
Publish Seed specification as GitHub Issues for team-based project management
6.2k GitHub stars~2.7k tokensUpdated 3 days ago
Product & Project ManagementAuto-check passed
Shipvela Publish
sickn33/agentic-awesome-skills
Publish an explicitly selected website through the user's connected Shipvela MCP account, track the exact deployment, and return its live HTTPS URL after success.
47k GitHub stars~1.9k tokensUpdated 2 days ago
DevOps & CloudAuto-check: notes

More from Peiiii/nextclaw

All 70 skills in this repo

Nextclaw Skin Studio
Peiiii/nextclaw
A skill your agent uses when a user wants to browse, apply, inspect, create, refine, switch, or remove a NextClaw skin; wants a personal skin with arbitrary CSS, JavaScript, images, SVG, DOM…
260 GitHub stars~1.8k tokensUpdated yesterday
Auto-check passed
Development Task Telemetry
Peiiii/nextclaw
A skill your agent uses when a development task needs visible phase tracing, task-level or phase-level Token measurement, model/effort comparison, or a deterministic usage report or local dashboard…
260 GitHub stars~802 tokensUpdated yesterday
Auto-check passed
Nextclaw Product Visual Assets
Peiiii/nextclaw
当 NextClaw 产品更新后需要生成、替换、挑毛病或检查官网、GitHub README、用户文档或社交传播中的真实截图、AI 宣传视觉、整页 HTML 宣传预览、社区二维码等对外视觉资产时使用；也用于“更新截图”“重新截一批图”“做宣传页”“生成 campaign 页面”“视觉审稿”“五星挑刺法”或发布前检查视觉资产。普通站点布局开发或只写文章不触发。
260 GitHub stars~801 tokensUpdated yesterday
Auto-check passed
UI UX Pro Max
Peiiii/nextclaw
A skill your agent uses when the user wants professional UI/UX design guidance, design-system generation, UX review, or stack-specific frontend guidance through a bundled local UI/UX Pro Max dataset…
260 GitHub stars~2k tokensUpdated yesterday
Auto-check passed
Impeccable
Peiiii/nextclaw
A skill your agent uses when the user wants distinctive, production-grade frontend design, anti-generic AI aesthetics, UX critique, technical UI audits, or final polish through bundled Impeccable…
260 GitHub stars~2.5k tokensUpdated yesterday
Auto-check passed
Nextclaw Skill Resource Hub
Peiiii/nextclaw
Curate NextClaw skill resources, including OpenClaw and community sources.
260 GitHub stars~479 tokensUpdated yesterday
Auto-check passed

Questions about Publish To Nextclaw Marketplace

What does Publish To Nextclaw Marketplace do?

A skill your agent uses when the user wants to publish or update a local skill in the NextClaw marketplace, especially when they need clear guidance for version readiness, platform login, username…. Publish To Nextclaw Marketplace is an agent skill from Peiiii/nextclaw. Use when the user wants to publish or update a local skill in the NextClaw marketplace, especially when they need clear guidance for version readiness, platform login, username setup, scoped package naming, and post-publish verification.

When should I use Publish To Nextclaw Marketplace?

Publish To Nextclaw Marketplace fits situations like: the user wants to publish; update a local skill in the NextClaw marketplace; especially when they need clear guidance for version readiness; scoped package naming.

How do I install Publish To Nextclaw Marketplace in Claude Code?

Run `npx skills add Peiiii/nextclaw --skill publish-to-nextclaw-marketplace -a claude-code`. Or copy the skill folder (skills/publish-to-nextclaw-marketplace in Peiiii/nextclaw) into .claude/skills/publish-to-nextclaw-marketplace in your project. Claude Code loads it when a task matches its description.

How do I install Publish To Nextclaw Marketplace in Codex?

Run `npx skills add Peiiii/nextclaw --skill publish-to-nextclaw-marketplace -a codex`. Or copy the skill folder (skills/publish-to-nextclaw-marketplace in Peiiii/nextclaw) into .agents/skills/publish-to-nextclaw-marketplace in your project. Codex loads it when a task matches its description.

Can I use Publish To Nextclaw Marketplace 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 Peiiii/nextclaw --skill publish-to-nextclaw-marketplace -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/publish-to-nextclaw-marketplace, .gemini/skills/publish-to-nextclaw-marketplace, .github/skills/publish-to-nextclaw-marketplace and .opencode/skills/publish-to-nextclaw-marketplace in your project.

What does Publish To Nextclaw Marketplace need to run?

Going by SKILL.md and its folder, Publish To Nextclaw Marketplace needs the command-line tools its instructions call (curl) and credentials named NEXTCLAW_MARKETPLACE_ADMIN_TOKEN. Our summary lists: A credential in NEXTCLAW_MARKETPLACE_ADMIN_TOKEN.

Does Publish To Nextclaw Marketplace access the network?

SKILL.md names 3 domains. In commands or code: marketplace-api.nextclaw.io, platform.nextclaw.io and ai-gateway-api.nextclaw.io; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Publish To Nextclaw Marketplace 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 Publish To Nextclaw Marketplace use?

Publish To Nextclaw Marketplace is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Publish To Nextclaw Marketplace use?

About 1.6k tokens (SKILL.md is roughly 6.5k 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 Publish To Nextclaw Marketplace?

Skills that share tags, products or a category with Publish To Nextclaw Marketplace: Publish (code-yeongyu/oh-my-openagent, 70k stars), Social Publisher (affaan-m/ECC, 277k stars), Publish (yc-software/qm, 15k stars) and Social Publishing (wshobson/agents, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Publish To Nextclaw Marketplace?

Peiiii (a GitHub user) maintains it in Peiiii/nextclaw, which has 260 GitHub stars. The repository holds 70 skills in this directory. The repository was last updated on October 9, 2026.

Source: Peiiii/nextclaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Publish To Nextclaw Marketplace

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Publish To NextClaw Marketplace

Overview

Hard Requirement

Marketplace Identity Model

Readiness Checklist

1. CLI version

2. Platform login

3. Platform username

4. Local skill files

Publish Flow

Publish a new personal skill

Publish an official NextClaw skill

Update an existing skill

Post-Publish Verification

Failure Modes

Version too old

Not logged in

Username missing

Scope mismatch

Insufficient permission for @nextclaw/*

Success Criteria

Files

Compare with similar skills

Similar skills

More from Peiiii/nextclaw

Questions about Publish To Nextclaw Marketplace

Insufficient permission for `@nextclaw/*`