@neta-art/neta-search-cli 0.2.23 → 0.2.31

package/README.md

@@ -10,6 +10,7 @@ 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 submit <name>             # submit .agents/skills/<name>/ to the hub and wait for the result
 ```
 
 `<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/`.
@@ -18,10 +19,14 @@ npx -y @neta-art/neta-search-cli@latest skills init <name>               # scaff
 
 `use` prints the skill directory and the full SKILL.md, so an agent can follow it right away; relative paths in SKILL.md resolve against that directory. If the local entry is a pointer (frontmatter `metadata.neta-skill-id`), `use` fetches the full skill it points to.
 
+Every result has a trust level: `platform` (published by the Neta team), `verified` (passed Neta's review) or `community` (shared by a Cohub user, not reviewed). `find --json` items carry it as `trust`, plus `basic: true` for built-in Cohub abilities and `author` for community skills. `use` and `add` say so when a skill is a community one; read those before relying on them.
+
 Each `find --json` item carries a ready-to-run `use` command (`skills use <id> --via find`); prefix it with `npx -y @neta-art/neta-search-cli@latest` or `neta-search`. `--via` only labels where the use came from in usage stats.
 
 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.
+
 Inside a Cohub sandbox the CLI picks up the sandbox identity automatically; elsewhere it runs anonymously.
 
 Single file, no runtime dependencies. Node.js 20+.