@gmickel/gno 1.0.3 → 1.0.5

package/README.md

@@ -964,3 +964,7 @@ Interpretation:
 <p align="center">
   made with ❤️ by <a href="https://twitter.com/gmickel">@gmickel</a>
 </p>
+
+## Download history
+
+[![ClawHub download history](https://skill-history.com/chart/gmickel/gno.svg)](https://skill-history.com/gmickel/gno)

package/assets/skill/README.md

@@ -0,0 +1,130 @@
+# GNO — Agent Skill
+
+Local-first semantic search for documents, notes, and knowledge bases,
+packaged as a Claude Code / Codex / OpenCode / OpenClaw skill.
+
+> **TL;DR** — this folder is a runnable agent skill. Drop it into any
+> Claude Code, Codex, OpenCode, or OpenClaw workspace and the agent can
+> index and search your local files through the `gno` CLI.
+
+## Prerequisites
+
+You need the `gno` CLI installed locally. The skill drives it; it does
+not ship the binary itself.
+
+```bash
+# macOS / Linux
+curl -fsSL https://gno.sh/install | bash
+
+# npm / Bun
+bun add -g @gmickel/gno        # or: npm install -g @gmickel/gno
+```
+
+Verify: `gno --version` should print `1.0.3` or later.
+
+## Install the skill
+
+There are two ways to install, and which one you pick depends on where
+you're starting from.
+
+### Option A — install from your local `gno` (recommended if you already have GNO)
+
+If you already installed GNO, it ships this skill in-tree. One command
+drops it into the right place for every supported agent, always in sync
+with your installed GNO version:
+
+```bash
+gno skill install --target claude       # Claude Code (default)
+gno skill install --target codex        # OpenAI Codex CLI
+gno skill install --target opencode     # OpenCode
+gno skill install --target openclaw     # OpenClaw
+gno skill install --target all          # All four
+```
+
+Scope is configurable:
+
+```bash
+gno skill install --scope project       # ./.claude/skills/gno (default)
+gno skill install --scope user          # ~/.claude/skills/gno
+```
+
+Inspect or uninstall:
+
+```bash
+gno skill show                          # preview what would be installed
+gno skill paths                         # resolved installation paths
+gno skill uninstall --target all        # remove from all agents
+```
+
+This path always gives you the skill that matches your GNO CLI — no
+version drift.
+
+### Option B — install from ClawHub (recommended if you use OpenClaw)
+
+ClawHub is the OpenClaw skill registry. Use this when you manage
+skills centrally across multiple workspaces or when you don't have GNO
+installed yet.
+
+```bash
+openclaw skills install gno             # installs @gmickel/gno
+openclaw skills update gno              # pull a newer version later
+openclaw skills info gno                # inspect what's installed
+```
+
+You can also browse the skill at
+<https://clawhub.ai/gmickel/gno> and download the folder manually.
+
+## What the skill teaches the agent
+
+Once installed, the agent gains a single callable capability: run `gno`
+commands from the workspace. The skill docs (see [SKILL.md](SKILL.md))
+walk the model through:
+
+- initialising a new index and adding collections
+- keyword (`search`), vector (`vsearch`), hybrid (`query`) and
+  AI-answer (`ask`) search modes
+- document retrieval (`get`, `multi-get`) including line ranges
+- link graph traversal (`links`, `backlinks`, `similar`, `graph`)
+- tagging, contexts, and per-collection embedding models
+- publishing notes as gno.sh reader snapshots (`publish export`)
+- MCP server setup for persistent agent access
+
+The reference docs in this folder are discoverable by the agent via
+progressive disclosure — the model only pulls them when it needs them:
+
+- [SKILL.md](SKILL.md) — core instructions + frontmatter
+- [cli-reference.md](cli-reference.md) — every CLI command, option and flag
+- [mcp-reference.md](mcp-reference.md) — MCP tool and resource contract
+- [examples.md](examples.md) — end-to-end usage patterns
+
+## Agent tooling contract
+
+The skill requests two tools:
+
+```yaml
+allowed-tools: Bash(gno:*) Read
+```
+
+- **`Bash(gno:*)`** — the agent can invoke `gno <anything>` on the
+  host. All writes are explicit CLI calls; nothing runs implicitly.
+- **`Read`** — the agent can open files the user has pointed at. No
+  filesystem writes come through the skill itself.
+
+## Versioning
+
+The skill version is tracked separately from the GNO CLI version. When
+the CLI ships a new feature worth teaching the model (new flag, new
+subcommand, new sanitizer behaviour), the skill gets a point bump. See
+the CHANGELOG entry on ClawHub or the `gno` repo's CHANGELOG for what
+landed in each bump.
+
+## License
+
+MIT-0 — use it freely, with or without attribution.
+
+## Links
+
+- Source: <https://github.com/gmickel/gno>
+- Hosted publishing: <https://gno.sh>
+- OpenClaw docs: <https://docs.openclaw.ai>
+- ClawHub listing: <https://clawhub.ai/gmickel/gno>

package/assets/skill/cli-reference.md

@@ -504,24 +504,51 @@ Export a note or collection as a gno.sh publish artifact JSON.
 gno publish export <target> [--out <path.json>] [options]
 ```
 
-| Option         | Default | Description                                                   |
-| -------------- | ------- | ------------------------------------------------------------- |
-| `--out`        | auto    | Output path, defaults to `~/Downloads/<slug>-<YYYYMMDD>.json` |
-| `--visibility` | public  | One of `public`, `secret-link`, `invite-only`, `encrypted`    |
-| `--slug`       | auto    | Override the published route slug                             |
-| `--title`      | auto    | Override the exported title                                   |
-| `--summary`    | auto    | Override the exported summary                                 |
-| `--json`       | false   | Structured result output                                      |
+| Option         | Default | Description                                                                |
+| -------------- | ------- | -------------------------------------------------------------------------- |
+| `--out`        | auto    | Output path, defaults to `~/Downloads/<slug>-<YYYYMMDD>.json`              |
+| `--visibility` | public  | One of `public`, `secret-link`, `invite-only`, `encrypted`                 |
+| `--slug`       | auto    | Override the published route slug                                          |
+| `--title`      | auto    | Override the exported title                                                |
+| `--summary`    | auto    | Override the exported summary                                              |
+| `--passphrase` | none    | Required for `--visibility encrypted`; encrypts locally before upload      |
+| `--preview`    | false   | Print sanitized markdown + preprocessor report instead of writing artifact |
+| `--json`       | false   | Structured result output                                                   |
 
 Examples:
 
 ```bash
 gno publish export work-docs --out ~/Downloads/work-docs.json
 gno publish export "gno://work-docs/runbooks/deploy.md" --out ~/Downloads/deploy.json
+
+# Encrypted share — ciphertext produced locally before upload
+gno publish export "gno://work-docs/offer-letter.md" \
+  --visibility encrypted --passphrase "correct horse battery staple"
+
+# Inspect what the sanitizer strips before writing anything
+gno publish export "gno://vault/my-note.md" --preview
 ```
 
 On success, upload the JSON file at `https://gno.sh/studio`.
 
+**Obsidian pre-processor (v1.0.2+)**: before the artifact is written, the
+export pipeline runs a sanitizer over each note's markdown. It:
+
+- drops the navigation-sidebar idiom (`[[Hub]] | [[Related]]` immediately
+  under the frontmatter)
+- strips any `[[_internal/...]]` references (privacy guard — the
+  `_internal/` convention is treated as never-publish)
+- converts `[[Target|Alias]]` to the alias text, and `[[Target]]` to the
+  tail segment of the target
+- drops `![[image.png]]` embeds (attachments are not bundled yet) with a
+  warning so the author can migrate to `![alt](url)` or wait for bundling
+- refuses to export a note whose frontmatter contains `publish: false`
+  (single-note export errors; collection export silently skips)
+
+Every sanitizer decision surfaces in the CLI output as a "Preprocessor
+notes" section, on the `--json` response under `warnings`, and on
+`--preview` as a structured report — so nothing is silently lost.
+
 ## Skill Management
 
 ### gno skill install

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@gmickel/gno",
-  "version": "1.0.3",
+  "version": "1.0.5",
   "description": "Local semantic search for your documents. Index Markdown, PDF, and Office files with hybrid BM25 + vector search.",
   "keywords": [
     "embeddings",
@@ -155,7 +155,7 @@
     "commander": "^14.0.2",
     "embla-carousel-react": "^8.6.0",
     "franc": "^6.2.0",
-    "lucide-react": "^0.563.0",
+    "lucide-react": "^1.8.0",
     "markitdown-ts": "^0.0.9",
     "minimatch": "^10.1.1",
     "nanoid": "^5.1.6",
@@ -168,7 +168,7 @@
     "react-markdown": "^10.1.0",
     "rehype-sanitize": "^6.0.0",
     "remark-gfm": "^4.0.1",
-    "shiki": "^3.20.0",
+    "shiki": "^4.0.2",
     "sqlite-vec": "^0.1.7-alpha.2",
     "streamdown": "^2.0.1",
     "tailwind-merge": "^3.4.0",