Publish your skills

Skills are reusable abilities for AI agents: a folder with a SKILL.md that tells an agent what to do. Anyone on Cohub can publish the skills they write here. Published skills show up on this site and in skills find as community skills, under your name, so other people's agents can find and use them.

The short version

Have a skill in your space that you'd like to share? Paste this to your agent in a chat in that space, in Neta Studio or Cohub (replace <name> with the skill's name, or leave it and the agent will ask):

Share my skill <name> on the Neta skills directory. Run `npx -y @neta-art/neta-search-cli@latest skills submit <name>` in this space and tell me the result word for word. If you're not sure which skill I mean, list the folders in .agents/skills/ and ask me. If it fails, fix what it says (frontmatter, size, a missing Cohub username) and run it again. Lint warnings are only suggestions; they don't block publishing.

It is listed within a few minutes as @<your-username>/<name>. No trial run is needed to share it.

Don't have one yet? Ask your agent to turn what you just did into a skill in .agents/skills/, use it once in your world, and when you're happy with it, share it with the line above.

Want help making it better? Use skill-creator (neta-search/skill-creator, by the Neta team). It checks your skill against the review rules, tries it once in your space (this uses your credits), offers to share the Work it made, and publishes when you say so. Later it also helps with review feedback, suggestions from other creators, and updates.

Want to change someone else's skill, get your skill into Neta Studio, or read the Neta team's review of your skill? See the Q&A at the end of this page.

Two things have to be true: you own the space, and the chat was started by you (the server checks both). You also need a Cohub username.

1. Write a skill

A skill is a directory with a SKILL.md. The easiest way is to ask your agent to write it (see The short version), or let skill-creator write and check it for you. To write it yourself, start from a template:

npx -y @neta-art/neta-search-cli@latest skills init <name>

This creates .agents/skills-drafts/<name>/SKILL.md. Drafts are not loaded into your agent's skill list while you work on them. <name> is kebab-case (comic-panels, brawl-creator), at most 60 characters.

SKILL.md starts with a frontmatter block:

---
name: comic-panels
description: Turn a scene into a 4-panel comic page with consistent characters. Use when the user wants a comic, manga page or storyboard.
---

Below the frontmatter, write the instructions for the agent: the steps, what to produce, what to check. You can put scripts, templates and reference files next to SKILL.md and refer to them with relative paths.

2. Try it

npx -y @neta-art/neta-search-cli@latest skills use <name>

use prints the skill for your agent to follow. It works on drafts, and nothing is shared. When the skill is ready, move it out of the drafts folder:

npx -y @neta-art/neta-search-cli@latest skills add <name>

Now it is in .agents/skills/<name>/, part of your space's skills.

3. Share a Work made with it

If you try your skill in a Neta Studio world, it usually makes a Work: a page, a game, an image, a video. If you are happy with it, share it so people can see what your skill makes. This step is optional, but we recommend it.

Share only Works you are happy for everyone to see. If you make a Work Unlisted again later, it stops appearing in the Community and on your skill's page.

4. Publish

npx -y @neta-art/neta-search-cli@latest skills submit <name>

Before sending anything, submit runs skills lint on the folder: errors stop the submit, warnings are only shown. You can run skills lint <name> yourself at any time; it runs locally and sends nothing.

Run it from a chat in your space (or ask your agent to). It checks the folder, sends this version, waits for the result and prints one of:

Nothing is shared until you submit. Using a skill in your own space does not publish it.

Requirements

WhatLimit
WhoThe space owner, from a chat they started in that space
Cohub usernameRequired: you publish as @username/<name>. Set it with cohub profile update --username <name>
Namekebab-case folder name, at most 60 characters
SKILL.mdMust have frontmatter with a description
SizeAt most 1000 files, 20 MB per file, 100 MB in total
FilesNo symbolic links
SecretsFiles that look like secrets are left out (.env, *.pem, *.key, id_rsa…). If any file contains something that looks like a key or token (API keys, private keys, connection strings with passwords), the whole skill is not published; remove it and submit again

Hidden files and folders (starting with .), node_modules and __pycache__ are not included.

If your skill has exactly the same content as one that is already listed, the lists show them as one entry. Yours still works under its own name.

5. Update, withdraw

What "Community" means

Every skill here has a trust level:

LevelMeaning
PlatformBuilt in, published by the Neta team
OfficialMade by the Neta team
VerifiedShared by a Cohub user and reviewed by the Neta team
CommunityShared by a Cohub user and not reviewed

When someone's agent uses a community skill, the CLI tells it the skill is unreviewed and sets limits: it won't follow instructions that try to read or send out credentials or the user's data, or delete things the user didn't ask about. Write your skill so that it does not need any of that.

Community skills are on this site and in find. They do not appear in Neta Studio's skill picker or board menu; that needs a review by the Neta team (see Q&A).

The Neta team can take a skill down if its content is a problem. You will see that when you submit next.

For agents

Everything above as commands:

npx -y @neta-art/neta-search-cli@latest skills init <name>              # template in .agents/skills-drafts/<name>/
npx -y @neta-art/neta-search-cli@latest skills use <name>               # try it (nothing is shared)
npx -y @neta-art/neta-search-cli@latest skills add <name>               # drafts → .agents/skills/<name>/
npx -y @neta-art/neta-search-cli@latest skills submit <name>            # publish as @<username>/<name>; prints the result
npx -y @neta-art/neta-search-cli@latest skills submit --withdraw <name> # take it down
npx -y @neta-art/neta-search-cli@latest skills find "<keyword>"         # search everything that is listed

Q&A

I changed someone else's skill. Can I publish my version?

It depends on whose skill it is:

To publish your version, install the skill (<handle> is what the site shows, e.g. neta-search/<name>), change it, and submit it as your own:

npx -y @neta-art/neta-search-cli@latest skills add <handle>
npx -y @neta-art/neta-search-cli@latest skills submit <name>

How do I send an improvement to a skill's author?

npx -y @neta-art/neta-search-cli@latest skills propose <name> --note "what you changed and why"

Run it in the space where you changed the skill. Only the author and you can see the suggestion. If they use it, their next version credits you ("With improvements from @you"); you need a Cohub username for that. skills proposals --mine shows what happened to yours. Skills by the Neta team do not take suggestions yet: publish your own fork instead.

Someone sent me a suggestion. What do I do?

skills list and skills submit tell you when there are suggestions for your skills. Then:

npx -y @neta-art/neta-search-cli@latest skills proposals <name>
npx -y @neta-art/neta-search-cli@latest skills proposals <name> <id>
npx -y @neta-art/neta-search-cli@latest skills submit <name> --adopts <id>

The first lists them. The second saves one to .neta-search/skill-proposals/<name>/<id>/, with a comparison to your files. The third publishes your new version and credits the sender.

You decide what to take; change it as much as you like before you submit. To say no: skills proposals <name> <id> --decline --reason "...". Forgot --adopts? Run skills proposals <name> <id> --adopted-in <digest>.

Can others publish changed versions of my skill?

Not by default: their changes come to you as suggestions. To let anyone publish a fork (with credit to you), add this to the frontmatter of your SKILL.md:

metadata:
  neta-adaptations: open

It takes effect when you submit a version with this setting: the site reads it from your latest published version. suggest (the default) switches it back the same way. Forks already published stay.

How does my skill get into Neta Studio?

Neta Studio's skill picker and board menu only show skills that the Neta team has reviewed. The team looks through community skills, including how much people use them, and picks some for review. You don't need to apply. If the review passes, your skill is marked Verified, and the team may add it to Neta Studio.

After that, each new version you submit is reviewed again. Neta Studio keeps using the version that passed until the new one passes. Meanwhile this site and find show your newest version, marked Community until its review passes.

My skill was reviewed but not marked Verified. Why?

skills list marks skills that have review feedback. Read it with:

npx -y @neta-art/neta-search-cli@latest skills feedback <name>

It saves the feedback to .neta-search/skill-feedback/<name>/: what to change, in which file. Ask your agent to fix it, then submit again; the new version is reviewed again. Only you can read it, and nothing about it is shown on this site.

Can I choose the text and video shown for my skill in Neta Studio?

You can submit a draft. Put a listing.json next to SKILL.md:

{
  "en": { "name": "...", "description": "..." },
  "zh": { "name": "...", "description": "..." },
  "media": { "works": ["<Work id or https://neta.art/w/<id> link>"] }
}

Names up to 80 characters, descriptions up to 300, up to 6 Works. Works must be ones you made in Neta Studio and shared as Public (shown in Community); Unlisted Works don't count. submit tells you which ones can be shown. The Neta team uses your draft when the skill goes into Neta Studio, and may edit it.

Which language should my skill be in?

English is recommended for the instructions, because agents read them and users speak many languages. It is not required. Whatever you write in, tell the agent to reply in the user's language.

Can my skill use other skills?

Put everything it needs in its own folder (scripts, templates, references), or call Neta's and Cohub's commands directly. Don't point to other skills' folders or to mods other than /mods/neta and /mods/cohub_base: people who download your skill won't have them. skills lint warns about these.

Who can see my skill?

Nothing is shared until you submit. After that, anyone can find it and download every file in it, so never put keys or passwords in it.

I deleted or renamed the folder. Is my skill gone?

No. The published version stays. Use skills submit --withdraw <name> to take it down. A renamed folder is a new skill.

Raw markdown for agents: docs.md