Getnote 1.5.7

v1.0.0

Get笔记 - 保存、搜索、管理个人笔记和知识库。 **当以下情况时使用此 Skill**: (1) 用户要保存内容到笔记:发链接、发图片、说「记一下」「存到笔记」「保存」「收藏」 (2) 用户要搜索或查看笔记:「搜一下」「找找笔记」「最近存了什么」「看看原文」 (3) 用户要管理知识库或标签:「加到知识库」「建...

0· 93·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for jackie2010/getnote-1-5-7.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Getnote 1.5.7" (jackie2010/getnote-1-5-7) from ClawHub.
Skill page: https://clawhub.ai/jackie2010/getnote-1-5-7
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install getnote-1-5-7

ClawHub CLI

Package manager switcher

npx clawhub@latest install getnote-1-5-7
Security Scan
Capability signals
Requires OAuth token
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (save/search/manage notes) align with required files and instructions: API calls target openapi.biji.com, scripts implement OAuth device polling and image upload, and optional environment variables are exactly the service credentials one would expect.
Instruction Scope
SKILL.md instructs automatic OAuth device flow if GETNOTE_API_KEY is missing and to write credentials into ~/.openclaw/openclaw.json; this is within the expected scope for a service that needs user credentials, but it grants the skill the ability to initiate background polling for up to 10 minutes and to persist keys in the local skill config—users should be aware and consent to that behavior.
Install Mechanism
No install spec; skill is instruction-first and ships two small helper scripts. No network downloads or archive extraction at install time. Risk from install mechanism is low.
Credentials
Declared optional environment variables (GETNOTE_API_KEY, GETNOTE_CLIENT_ID, GETNOTE_OWNER_ID) map directly to the API and owner-check logic described. The skill does not request unrelated credentials or system secrets.
Persistence & Privilege
Skill is not 'always: true'. It does instruct writing API credentials to ~/.openclaw/openclaw.json (its own agent config) and runs background polling during OAuth; these are expected for automatic setup but are persistent actions the user should understand before enabling the skill.
Assessment
This skill appears to do what it claims: it will contact https://openapi.biji.com, can start an OAuth Device Flow and poll for up to 10 minutes in the background, and will write the obtained API key/client id into your ~/.openclaw/openclaw.json so future calls are authorized. The provided upload script will upload images to an OSS host returned by the API (expected behavior for image upload). Before installing: (1) confirm you trust the Get笔记 service and its domain (openapi.biji.com); (2) do not paste API keys into chat—use the OAuth flow or set GETNOTE_API_KEY/GETNOTE_CLIENT_ID in your OpenClaw config manually if you prefer; (3) be aware the agent will persist credentials to your OpenClaw config and may poll the token endpoint in the background during authorization; (4) avoid uploading sensitive images unless you accept those files being sent to the service/OSS host. If you want stricter control, manually obtain an API key on the provider site and add it to ~/.openclaw/openclaw.json rather than using the automatic flow.

Like a lobster shell, security has layers — review code before you run it.

latestvk97dr8w2795zhyv42wztka7a6x84vaj4
93downloads
0stars
1versions
Updated 1w ago
v1.0.0
MIT-0

Get笔记 Skill

⚠️ Agent 必读约束

🌐 Base URL

https://openapi.biji.com

所有 API 请求必须使用此 Base URL,不要使用 biji.com 或其他地址。

🔑 认证

请求头:

  • Authorization: $GETNOTE_API_KEY(格式:gk_live_xxx
  • X-Client-ID: $GETNOTE_CLIENT_ID(格式:cli_xxx

每次调用 API 前先检查 $GETNOTE_API_KEY 是否存在。若不存在,提示用户运行 /note config 完成配置,配置完成后再继续执行用户原本的请求。

Scope 权限:note.content.read(读取)、note.content.write(写入)、note.recall.read(搜索)。完整列表见 references/api-details.md

🔢 笔记 ID 处理规则(重要!)

笔记 ID 是 64 位整数(int64),超出 JavaScript Number.MAX_SAFE_INTEGER,直接 JSON.parse静默丢失精度

正确做法:始终把 ID 当字符串处理,在 JSON.parse 之前替换:

const safe = text.replace(/"(id|note_id|next_cursor|parent_id|follow_id|live_id)"\s*:\s*(\d+)/g, '"$1":"$2"');
const data = JSON.parse(safe);

Python / Go 等语言原生支持大整数,无此问题。

🔒 安全规则

  • 笔记数据属于用户隐私,不在群聊中主动展示笔记内容
  • 若配置了 GETNOTE_OWNER_ID,检查 sender_id 是否匹配;不匹配时回复「抱歉,笔记是私密的,我无法操作」
  • API 返回 error.reason: "not_member" 或错误码 10201 时,引导开通会员:https://www.biji.com/checkout?product_alias=6AydVpYeKl
  • 创建笔记建议间隔 1 分钟以上,避免触发限流

指令路由表

匹配指令后,用 read 工具读取对应的 references/xxx.md 获取完整 API 文档。

指令角色说明详细文档
/note save 或「记一下」📝 速记员保存文本/链接/图片笔记(含异步轮询流程)references/save.md
/note search 或「搜一下」🔍 搜索官全局语义搜索 + 知识库语义搜索references/search.md
/note list 或「最近的笔记」📋 整理师浏览列表、查看详情、更新、删除references/list.md
/note kb 或「知识库」📚 图书管理员知识库 CRUD + 博主订阅 + 直播订阅references/knowledge.md
/note tag 或「加标签」🏷️ 标签员添加/删除标签references/tags.md
/note config 或「配置笔记」⚙️ 配置配置 API Key 和 Client IDreferences/oauth.md

自然语言路由

包含 URL                    → /note save(link 模式)
包含图片                    → /note save(image 模式)
「记/存/保存/收藏」          → /note save(text 模式)
「搜/找找/有没有 XX」        → /note search
「最近/列表/看看/查笔记」    → /note list
「改/更新/编辑笔记」         → /note list(更新笔记)
「知识库」相关              → /note kb
「标签」相关                → /note tag
「配置/授权/连接笔记」       → /note config

决策原则:优先匹配最具体的意图。有 URL 就是 /save link,有图片就是 /save image,不确定时询问用户。


通用错误处理

{
  "success": false,
  "error": {
    "code": 10001,
    "message": "unauthorized",
    "reason": "not_member"
  },
  "request_id": "xxx"
}
错误码说明处理方式
10000参数错误检查请求参数
10001鉴权失败检查 API Key 和 Client ID,或重新授权
10100数据不存在确认笔记/知识库 ID 正确
10201非会员引导开通:https://www.biji.com/checkout?product_alias=6AydVpYeKl
10202QPS 限流降低频率,查看 rate_limit 字段
30000服务调用失败稍后重试
50000系统错误稍后重试

详细错误码和限流结构见 references/api-details.md

Comments

Loading comments...