publish-to-nextclaw-marketplace
Skill263 starsChanged 39 days agoMITView on GitHub
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.
- Deletes or force-pushes
In this repository37 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/code-citation-clickable.mdcCursor rule
- .cursor/rules/commit-message-english.mdcCursor rule
- autonomous-maintainability-campaignSkill
- autonomous-requirement-discoverySkill
- delivering-delegated-linear-issuesSkill
- development-deliverySkill
- development-designSkill
- development-implementationSkill
- development-lifecycleSkill
- development-retrospectiveSkill
- development-reviewSkill
- development-task-understandingSkill
- development-validationSkill
- idea-search-funnelSkill
- nextclaw-agent-instructions-governanceSkill
- nextclaw-product-blog-storytellingSkill
- nextclaw-product-visual-assetsSkill
- x-twitter-birdSkill
- aigen-image-generationSkill
- bb-browserSkill
- browser-controlSkill
- claude-code-narp-runtimeSkill
- clawhub-nextclawSkill
- codex-narp-runtimeSkill
- find-skillsSkill
- gemigo-cliSkill
- impeccableSkill
- lark-cliSkill
- linear-cliSkill
- mmx-cliSkill
- nextclaw-skin-studioSkill
- opencliSkill
- proxy-local-ai-subscriptionsSkill
- skillhub-guideSkill
- superpowersSkill
- ui-ux-pro-maxSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
20 rules. About 0 are common, 12 are distinctive, and 8 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈12
Distinctive · estimate
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Use this skill when the user wants to publish a local skill to the NextClaw marketplace or update an existing listing.
- Very specific: line 14
check that the local nextclaw version is new enough,
- Distinctive: line 15
verify platform identity and username readiness,
- Very specific: line 17
run publish or update,
- Distinctive: line 20
Do not pretend the account is ready when it is not.
- Distinctive: line 21
If the user is logged in but still has no platform username, stop and ask them to set it first.
- Very specific: line 39
If the version is lower than 0.17.6, do not continue with a fallback flow.
- Distinctive: line 44
Treat these fields differently:
- Distinctive: line 61
Do not blur official and personal publishing together.
- Distinctive: line 65
Before publishing, check these in order.
- Very specific: line 73
Must be 0.17.6 or later.
- Distinctive: line 91
If the user wants personal publishing, make sure the platform account already has a username.
- Distinctive: line 99
if it is missing, direct the user to one of those two concrete paths before publishing
- Distinctive: line 122
Do not publish with half-complete bilingual metadata.
- Distinctive: line 126
Use the official marketplace API domain:
- Very specific: line 132
Do not use a workers.dev endpoint as the default public publishing target.
- Distinctive: line 161
Only do this when admin permission is actually present.
- Very specific: line 174
if the marketplace item does not exist yet, use publish
- Very specific: line 175
if it already exists, use update
- Distinctive: line 179
After publishing, verify the remote item directly.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
nextclawversion is new enough, - verify platform identity and username readiness,
- choose the correct package scope,
- run
publishorupdate, - 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-skilland@alice/my-skill.- It also supports the clearer
--scopeand--package-namepublish parameters. - Personal publishing now depends on the platform
usernamemodel added in the same release line.
Always verify first:
nextclaw --versionIf 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 segmentpackage 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 orNEXTCLAW_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
nextclaw --versionMust be 0.17.6 or later.
2. Platform login
For normal user publishing, log in first:
nextclaw login --api-base https://ai-gateway-api.nextclaw.io/v1For official @nextclaw/* publishing, an admin token may also be used through:
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.mdmarketplace.json
The marketplace metadata should be complete and explicit. At minimum, verify:
slugnamesummarysummaryI18n.ensummaryI18n.zhdescriptiondescriptionI18n.endescriptionI18n.zhauthortags
Do not publish with half-complete bilingual metadata.
Publish Flow
Use the official marketplace API domain:
https://marketplace-api.nextclaw.ioDo not use a workers.dev endpoint as the default public publishing target.
Publish a new personal skill
nextclaw skills publish ./my-skill \
--meta ./my-skill/marketplace.json \
--scope alice \
--api-base https://marketplace-api.nextclaw.ioEquivalent explicit package name form:
nextclaw skills publish ./my-skill \
--meta ./my-skill/marketplace.json \
--package-name @alice/my-skill \
--api-base https://marketplace-api.nextclaw.ioPublish an official NextClaw skill
nextclaw skills publish ./my-skill \
--meta ./my-skill/marketplace.json \
--scope nextclaw \
--api-base https://marketplace-api.nextclaw.ioOnly do this when admin permission is actually present.
Update an existing skill
nextclaw skills update ./my-skill \
--meta ./my-skill/marketplace.json \
--package-name @alice/my-skill \
--api-base https://marketplace-api.nextclaw.ioDefault 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:
curl -sS https://marketplace-api.nextclaw.io/api/v1/skills/items/%40alice%2Fmy-skillCheck 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:
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.6or 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/accountor runnextclaw account set-username <username>, then retry
Scope mismatch
- Symptom: publish rejects
@scope/namebecause 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
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

