
Getnote Note
Capture URLs, screenshots, and quick text into Get笔记 from your agent session without leaving the terminal.
Overview
getnote-note is an agent skill most often used in Idea (also Build docs, Grow content) that saves, lists, views, updates, and deletes Get笔记 notes via the getnote CLI.
Install
npx skills add https://github.com/iswalle/getnote-cli --skill getnote-noteWhat is this skill?
- Save link, text, or local image notes via `getnote save` with optional `--title` and repeatable `--tag` flags
- Share and internal biji.com link behaviors: sync on share URLs, internal `biji.com/note/{id}` for cross-note references
- Async auto-poll for generic URLs and images; sync text saves; JSON output mode returns final note payload
- Full note lifecycle: list, view, update, and delete through the authenticated getnote CLI
- Requires `getnote` installed with `getnote auth status` showing Authenticated
- 5 core save/list/view/update/delete operations documented
- 3 input modes: URL, local image path, and text
Adoption & trust: 670 installs on skills.sh; 127 GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You find useful links and snippets during agent sessions but they never land in a searchable note library tied to your workflow.
Who is it for?
Solo builders who already use Get笔记 and want their agent to file research, bookmarks, and screenshots from the terminal.
Skip if: Teams without Get笔记 or builders who need a self-hosted markdown vault with no third-party note service.
When should I use this skill?
Manage notes in Get笔记 via the getnote CLI after authentication is confirmed.
What do I get? / Deliverables
Authenticated CLI commands persist tagged notes with correct async/sync handling so your research and references stay in Get笔记 for later specs and shipping.
- Saved Get笔记 notes with titles and tags
- JSON note payloads when using `-o json`
- Updated or deleted note records via CLI
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Research and discovery is the canonical shelf because builders most often save articles, competitor links, and field notes while investigating an idea. The research subphase matches link clipping, tagged text saves, and reference gathering that feed later specs and builds.
Where it fits
Save competitor landing pages and articles with `--tag competitor` while mapping the market.
Store customer interview quotes as text notes tagged for later prioritization.
Attach design screenshots via `getnote save ./screenshot.png` and reference other notes with internal biji.com links.
Archive launch checklist URLs and release notes sources in one searchable notebook.
Clip distribution and SEO articles to reuse when drafting changelog or blog posts.
How it compares
Use instead of pasting URLs into chat history when you need durable, tagged notes in Get笔记 rather than generic filesystem snippets.
Common Questions / FAQ
Who is getnote-note for?
Indie developers and agent users who run the getnote CLI against Get笔记 and want procedural save/list/update/delete commands in SKILL.md form.
When should I use getnote-note?
During idea research to archive competitor articles, while validating to store interview notes, and during build or grow when linking internal notes or sharing public note URLs.
Is getnote-note safe to install?
Review the Security Audits panel on this Prism page and treat the skill as documentation for a CLI that uses your Get笔记 credentials and network access.
SKILL.md
READMESKILL.md - Getnote Note
# getnote-note Skill Save, list, view, update, and delete notes in Get笔记. ## Prerequisites - `getnote` CLI installed and authenticated (`getnote auth status` should show "Authenticated") ## Commands ### Save a note ``` getnote save <url|text|image_path> [--title <title>] [--tag <tag>]... ``` | Flag | Description | |------|-------------| | `--title` | Optional title | | `--tag` | Tag to apply; may be repeated | - URL (`http://` or `https://`) → link note: - **Share link** (`biji.com/note/share_note/*` or `d.biji.com/*` short link) → **sync**, returns `note_id` directly, no polling needed - **Internal note link** (`biji.com/note/{note_id}`) → this is the format for linking to another note inside note content; use it in `content` field when referencing other notes. If the current note will be shared publicly, prefer using the referenced note's share link (`getnote note share <id>`) instead of the internal link format - **Other URLs** → async, auto-polls until done - Local image path → image note (async, auto-polls until done) - Otherwise → text note (sync) ```bash getnote save https://example.com --title "Great article" getnote save "Remember to review the docs" --tag work --tag important getnote save ./screenshot.png --title "Design mockup" ``` In `-o json` mode, silently polls and returns the final note JSON (including `title`, `content`/summary, `note_type`, `tags`, `created_at`). --- ### Track save task ``` getnote task <task_id> ``` Manually check progress of an async save task. ```bash getnote task task_xyz789 -o json ``` Returns `status` (`pending` / `processing` / `success` / `failed`) and `note_id` when done. --- ### List recent notes ``` getnote notes [--since-id <id>] [--all] ``` Returns 20 notes per page (fixed). No `--limit` flag. | Flag | Description | |------|-------------| | `--since-id` | Pagination cursor (last note ID seen) | | `--all` | Fetch all notes (auto-paginate, streams output) | ```bash getnote notes getnote notes --all getnote notes --since-id 1234567890 getnote notes -o json ``` **Note types**: `plain_text` / `img_text` / `link` / `audio` / `meeting` / `local_audio` / `internal_record` / `class_audio` / `recorder_audio` / `recorder_flash_audio` --- ### Get note details ``` getnote note <id> [--field <field>] ``` Returns full note including content, tags, attachments. Use `--field` to extract a single value. | `--field` values | Description | |------|-------------| | `id` | Note ID | | `title` | Title | | `content` | Content / AI summary | | `type` | Note type | | `created_at` | Creation time | | `updated_at` | Last updated time | | `url` | Source URL (link notes) | | `excerpt` | Excerpt | | `web_content` | Full web page content (link notes only) | | `source` | Note source (e.g. `openapi`, `manual`) | | `tags` | Comma-separated tag names | ```bash getnote note 1234567890 getnote note 1234567890 --field content getnote note 1234567890 --field url getnote note 1234567890 -o json ``` --- ### Update a note ``` getnote note update <id> [--title <title>] [--content <content>] [--tag <tags>] ``` | Flag | Description | |------|-------------| | `--title` | New title | | `--content` | New content (plain_text notes only) | | `--tag` | Comma-separated tags — **replaces all existing tags** | ```bash getnote note update 1234567890 --title "Updated title" getnote note update 1234567890 --tag "work,important" ``` > ⚠️ `--tag` replaces all tags. For partial tag changes use `getnote tag add/remove`. > ⚠️ Content update only works on `plain_text` notes. --- ### Delete a note ``` getnote note delete <id> [-y] ``` Moves note to trash. ```bash getnote note delete 1234567890 -y ``` --- ### Share a note ``` getnote note share <id> [--exclude-audio] ``` Generates a public share link for a note. Idempotent — calling multiple times returns the same URL. ```bash getnote note share 12