重要前提
安装AI Skills的关键前提是:必须科学上网,且开启TUN模式,这一点至关重要,直接决定安装能否顺利完成,在此郑重提醒三遍:科学上网,科学上网,科学上网。查看完整安装教程 →
npx skills add https://github.com/luongnv89/skills --skill note-taker此技能在一个专用的、基于 Git 的笔记仓库中维护一个私有的笔记系统。
设置: 必须配置笔记仓库路径。在项目的 CLAUDE.md 或 AGENTS.md 文件中查找 NOTES_REPO 变量,或在首次使用时向用户询问路径。
规则: 此技能有副作用(写入 + 提交 + 推送),因此必须由用户调用。
在现有仓库中创建/更新/删除文件之前,将当前分支与远程同步:
branch="$(git rev-parse --abbrev-ref HEAD)"
git fetch origin
git pull --rebase origin "$branch"
如果工作区不干净,先储藏,同步,然后恢复:
git stash push -u -m "pre-sync"
branch="$(git rev-parse --abbrev-ref HEAD)"
git fetch origin && git pull --rebase origin "$branch"
git stash pop
如果 origin 缺失、拉取不可用或发生变基/储藏冲突,请停止并在继续之前询问用户。
接受以下形式的输入:
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
如果用户提供多个项目,除非他们明确希望合并为一个笔记,否则将每个项目视为单独的笔记。
在以下位置创建处理后的笔记:
notes/YYYY/MM/YYYY-MM-DD--<slug>.md使用简短、稳定的 slug(短横线分隔)。如果不确定,请询问标题。
使用 assets/note-template.md 中的模板。至少包含以下部分:
始终将附件文件存储在与笔记文件相同的文件夹中。
示例:
notes/2026/02/2026-02-11--example.mdnotes/2026/02/2026-02-11--example--1.jpgnotes/2026/02/2026-02-11--example--2.mp4规则:
assets/images 或 assets/audio 下。--1、--2、...对于每个图像附件,包含一个内联 markdown 图像,以便在笔记中渲染:
对于非图像文件(视频/音频/文档),在"附件"部分下保持正常的 markdown 链接。
提交前,扫描笔记(以及任何粘贴的代码片段)中的:
如果发现:
[REDACTED_SECRET]更新 KANBAN.md:
更新笔记和 KANBAN.md 后,手动更新笔记仓库的 README.md:
提交消息约定:
note: add <简短标题>kanban: add tasks from <slug>note: update <slug>docs: update notes README(如果 README 已更改)当远程仓库存在时,始终推送,以便报告的 GitHub 链接对用户有效。一旦此技能被用户调用,不要询问额外的推送确认。
报告任何笔记操作完成时,请包含:
链接格式:
https://github.com/<owner>/<repo>/blob/main/<relative-path>从笔记仓库的 git remote get-url origin 检测远程 URL,以构建正确的链接。
完成每个主要步骤后,以此格式输出状态报告:
◆ [步骤名称] ([第 N 步,共 M 步] — [上下文])
··································································
[检查项 1]: √ 通过
[检查项 2]: √ 通过(如有相关则注明)
[检查项 3]: × 失败 — [原因]
[检查项 4]: √ 通过
[标准]: √ N/M 项满足
____________________________
结果: PASS | FAIL | PARTIAL
调整检查项名称以匹配步骤实际验证的内容。使用 √ 表示通过,× 表示失败,— 添加简要上下文。"标准"行总结了满足了多少验收标准。"结果"行给出总体结论。
◆ 信息录入(第 1 步,共 4 步 — 输入处理)
··································································
收到输入: √ 通过
类型检测: √ 通过(文本/语音/图像/文件)
内容解析: √ 通过
[标准]: √ 3/3 项满足
____________________________
结果: PASS
◆ 处理(第 2 步,共 4 步 — 笔记创建)
··································································
笔记已写入: √ 通过
附件已存储: √ 通过(与笔记同文件夹)
机密信息已编辑: √ 通过 — 未发现机密信息
[标准]: √ 3/3 项满足
____________________________
结果: PASS
◆ 组织(第 3 步,共 4 步 — 看板和索引)
··································································
任务已提取: √ 通过 — 添加了 2 个任务
看板已更新: √ 通过 — 任务在待办事项中
索引已维护: × 失败 — README 计数未更新
[标准]: √ 2/3 项满足
____________________________
结果: PARTIAL
◆ 发布(第 4 步,共 4 步 — git 推送和报告)
··································································
已提交: √ 通过
已推送: √ 通过
链接已报告: √ 通过 — 包含 GitHub 链接
[标准]: √ 3/3 项满足
____________________________
结果: PASS
AGENTS.mdPOLICY.md每周安装数
53
仓库
GitHub 星标数
44
首次出现
2026年2月8日
安全审计
安装于
codex51
gemini-cli50
github-copilot50
amp50
kimi-cli50
opencode50
This skill maintains a private notes system in a dedicated git-backed notes repository.
Setup: The notes repo path must be configured. Look for a NOTES_REPO variable in the project's CLAUDE.md or AGENTS.md, or ask the user for the path on first use.
Rule: This skill has side effects (writes + commits + pushes) so it must be user-invoked.
Before creating/updating/deleting files in an existing repository, sync the current branch with remote:
branch="$(git rev-parse --abbrev-ref HEAD)"
git fetch origin
git pull --rebase origin "$branch"
If the working tree is not clean, stash first, sync, then restore:
git stash push -u -m "pre-sync"
branch="$(git rev-parse --abbrev-ref HEAD)"
git fetch origin && git pull --rebase origin "$branch"
git stash pop
If origin is missing, pull is unavailable, or rebase/stash conflicts occur, stop and ask the user before continuing.
Accept input as:
If the user provides multiple items, treat each as a separate note unless they explicitly want a single combined note.
Create processed notes at:
notes/YYYY/MM/YYYY-MM-DD--<slug>.mdUse a short, stable slug (kebab-case). If unsure, ask for a title.
Use the template in assets/note-template.md. Minimum sections:
Always store attachment files in the same folder as the note file.
Example:
notes/2026/02/2026-02-11--example.mdnotes/2026/02/2026-02-11--example--1.jpgnotes/2026/02/2026-02-11--example--2.mp4Rules:
assets/images or assets/audio.--1, --2, ...For every image attachment, include an inline markdown image so it renders in the note:
For non-image files (video/audio/docs), keep normal markdown links under Attachments.
Before committing, scan the note (and any pasted snippets) for:
If found:
[REDACTED_SECRET]Update KANBAN.md:
After updating notes and KANBAN.md, update the notes repo README.md manually:
Commit message conventions:
note: add <short-title>kanban: add tasks from <slug>note: update <slug>docs: update notes README (if README changed)Always push when remote exists, so reported GitHub links are valid for user. Do not ask for extra push confirmation once this skill is invoked by the user.
When reporting completion of any note action, include:
Link format:
https://github.com/<owner>/<repo>/blob/main/<relative-path>Detect the remote URL from the notes repo's git remote get-url origin to build correct links.
After completing each major step, output a status report in this format:
◆ [Step Name] ([step N of M] — [context])
··································································
[Check 1]: √ pass
[Check 2]: √ pass (note if relevant)
[Check 3]: × fail — [reason]
[Check 4]: √ pass
[Criteria]: √ N/M met
____________________________
Result: PASS | FAIL | PARTIAL
Adapt the check names to match what the step actually validates. Use √ for pass, × for fail, and — to add brief context. The "Criteria" line summarizes how many acceptance criteria were met. The "Result" line gives the overall verdict.
◆ Intake (step 1 of 4 — input processing)
··································································
Input received: √ pass
Type detected: √ pass (text/voice/image/file)
Content parsed: √ pass
[Criteria]: √ 3/3 met
____________________________
Result: PASS
◆ Processing (step 2 of 4 — note creation)
··································································
Note written: √ pass
Attachments stored: √ pass (same folder as note)
Secrets redacted: √ pass — no secrets found
[Criteria]: √ 3/3 met
____________________________
Result: PASS
◆ Organization (step 3 of 4 — kanban and index)
··································································
Tasks extracted: √ pass — 2 tasks added
Kanban updated: √ pass — tasks in Backlog
Index maintained: × fail — README count not updated
[Criteria]: √ 2/3 met
____________________________
Result: PARTIAL
◆ Publish (step 4 of 4 — git push and reporting)
··································································
Committed: √ pass
Pushed: √ pass
Links reported: √ pass — GitHub links included
[Criteria]: √ 3/3 met
____________________________
Result: PASS
AGENTS.md in the notes repo rootPOLICY.md in the notes repo rootWeekly Installs
53
Repository
GitHub Stars
44
First Seen
Feb 8, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
codex51
gemini-cli50
github-copilot50
amp50
kimi-cli50
opencode50
Skills CLI 使用指南:AI Agent 技能包管理器安装与管理教程
52,700 周安装