@neta-art/neta-search-cli 0.2.43 → 0.2.47

package/README.md

@@ -10,7 +10,9 @@ npx -y @neta-art/neta-search-cli@latest skills add  <id>                 # insta
 npx -y @neta-art/neta-search-cli@latest skills list                      # what's in .agents/skills/, and which installed ones have updates
 npx -y @neta-art/neta-search-cli@latest skills update                    # update installed skills to their current release (or name some: handle, id or directory)
 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 feedback [name]           # read Neta's review feedback on your own skills
 ```
 
 `<id>` is what `find` prints: a handle such as `neta-skills/holo-pack-opening` or `cohub/agent-browser`. Skills without a handle are listed as `cohub:<spaceId>/<name>`, which works everywhere a handle does. `update` and `remove` also accept the directory name under `.agents/skills/`.
@@ -25,7 +27,11 @@ Each `find --json` item carries a ready-to-run `use` command (`skills use <id> -
 
 Use `@latest` (or an exact version): with a range such as `@0.2`, npx keeps running whatever matching version it cached earlier and never checks for a newer one.
 
-`submit` publishes one of your skills and works inside a Cohub sandbox only, from a chat started by the space owner: it checks the directory locally (frontmatter, size, symlinks), 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.
+`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.
+
+`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.
 
 Inside a Cohub sandbox the CLI picks up the sandbox identity automatically; elsewhere it runs anonymously.