@neta-art/neta-search-cli 0.2.53 → 0.2.58

package/README.md

@@ -12,6 +12,7 @@ npx -y @neta-art/neta-search-cli@latest skills update                    # updat
 npx -y @neta-art/neta-search-cli@latest skills init <name>               # scaffold your own skill
 npx -y @neta-art/neta-search-cli@latest skills lint <name>               # static check before submitting (local; nothing is sent)
 npx -y @neta-art/neta-search-cli@latest skills submit <name>             # submit .agents/skills/<name>/ to the hub and wait for the result
+npx -y @neta-art/neta-search-cli@latest skills listing submit <name>     # send its showcase (.agents/skills/<name>/.listing/) to be shown once reviewed
 npx -y @neta-art/neta-search-cli@latest skills feedback [name]           # read Neta's review feedback on your own skills
 npx -y @neta-art/neta-search-cli@latest skills propose <name> --note "…"  # send your changes to an installed skill's author as a suggestion
 npx -y @neta-art/neta-search-cli@latest skills proposals [name] [id]      # suggestions others sent for your skills (--mine: the ones you sent)
@@ -39,7 +40,9 @@ Suggestions for your own skills: `proposals` lists the skills that have them, `p
 
 `submit` publishes one of your skills and works inside a Cohub sandbox only, from a chat started by the space owner: it runs the static check first (see `lint`), sends this version, and waits for the result: published (with its digest) or why not. Nothing is shared until you submit: `use` only runs a skill. `submit --withdraw <name>` takes it down again; deleting the directory does not.
 
-`lint [name-or-dir]` checks a skill folder locally and sends nothing. **Errors** are what the skills site would reject (a missing frontmatter or description, a SKILL.md saved with Windows line endings or a byte-order mark, size limits, a SKILL.md or skill folder that is a symbolic link, anything that looks like a secret, a folder installed from someone else); `submit` stops on them. **Warnings** are suggestions and never block: other symbolic links (skipped when publishing), paths the skill mentions that are not in it, hard-coded `/workspace/...` paths (use paths relative to the skill folder or the current folder), missing or incomplete test declarations (`evals/matrix.json`), common writing problems (no rule that replies follow the user's language, no hand-off card, no `--work-title`, no out-of-scope section, non-English text hard-coded in the deliverable), ready-made non-English words for the agent to say to users, instructions not written in English (recommended, not required), and the optional `listing.json` (your skill's name and description in `en` / `zh` and up to 6 showcase Works for Studio; only Works made in Studio and shared publicly are shown, not links to other sites; refer to a Work by its id or its `https://neta.art/w/<id>` link). After `submit`, the result says which languages of the name and description were read and which showcase Works can be shown, and why not. It is a static check, not a review: passing it says nothing about how well the skill works. `--json` for agents.
+`listing submit <name>` sends the skill's showcase, kept in `.agents/skills/<name>/.listing/`: `listing.json` with the name and description per language (`en`, `zh`, `ja`, `ko`, `es`, `de`) and a `media` list of up to 6 items in order of preference: `{"video": "demo.mp4", "poster": "cover.jpg"}` (mp4, 5 to 30 seconds, at most 30 MB; the poster is optional), `{"image": "shot.png"}` (jpg, png or webp, at most 10 MB), or `{"work": "https://neta.art/w/<id>"}` (a Work made in Studio and shared publicly). The files sit next to `listing.json`. Once reviewed, the showcase can be shown publicly in Studio, the Neta community, the skill's page and the public skills site. It is not part of the skill: changing it never makes a new version, people who install the skill do not get it, and publishing the skill with `submit` does not send it (the result of `submit` reminds you when it has not been sent or changed since). The server reads the folder from your space; nothing is uploaded by the CLI, and nothing is shown before review. The result says which items are usable and why not. `listing submit --withdraw <name>` takes your consent back: it stops being shown within a minute, including copies the Neta team adopted, but the addresses of copies already adopted cannot be deleted. Same rules as `submit`: inside a Cohub sandbox, from a chat started by the space owner. A `listing.json` at the skill's top level is the old place (it is part of every version); `lint` says to move it.
+
+`lint [name-or-dir]` checks a skill folder locally and sends nothing. **Errors** are what the skills site would reject (a missing frontmatter or description, a SKILL.md saved with Windows line endings or a byte-order mark, size limits, a SKILL.md or skill folder that is a symbolic link, anything that looks like a secret, a folder installed from someone else); `submit` stops on them. **Warnings** are suggestions and never block: other symbolic links (skipped when publishing), paths the skill mentions that are not in it, hard-coded `/workspace/...` paths (use paths relative to the skill folder or the current folder), missing or incomplete test declarations (`evals/matrix.json`), common writing problems (no rule that replies follow the user's language, no hand-off card, no `--work-title`, no out-of-scope section, non-English text hard-coded in the deliverable), ready-made non-English words for the agent to say to users, instructions not written in English (recommended, not required), and the optional showcase in `.listing/` (format, missing files, file types, sizes and video length; see `listing submit`). It is a static check, not a review: passing it says nothing about how well the skill works. `--json` for agents.
 
 `feedback [name]` reads Neta's review feedback on your own skills (Neta reviews skills it nominates; when one needs changes, the feedback says what, where in the files, and how to fix it). Like `submit`, it works only inside a Cohub sandbox, in a chat the space owner started in that space: the server checks that you are the author before showing anything. `skills list` also marks your own skills that have feedback (it does the same check while it looks for updates; if it cannot check, it just shows the list). Without a name, `feedback` lists your skills that have feedback; with a name it saves the latest feedback to `.neta-search/skill-feedback/<name>/<version>/` (`fix-pack.json` for agents, `feedback.md` for people) and prints it. `--digest` picks a version.