⚠️

重要前提

安装AI Skills的关键前提是：必须科学上网，且开启TUN模式，这一点至关重要，直接决定安装能否顺利完成，在此郑重提醒三遍：科学上网，科学上网，科学上网。查看完整安装教程 →

Git笔记记录器：私有、自动化的Git仓库笔记管理系统，支持多格式附件与看板同步

note-taker by luongnv89/skills

53 周安装量

44 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/luongnv89/skills --skill note-taker

自动化知识管理版本控制

🇨🇳中文介绍

笔记记录器（Git 管理）

此技能在一个专用的、基于 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 缺失、拉取不可用或发生变基/储藏冲突，请停止并在继续之前询问用户。

工作流程

1) 信息录入

接受以下形式的输入：

文本：消息内容
：总结（除非用户要求，否则不存储完整转录）

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

2) 确定文件名 + 文件夹

在以下位置创建处理后的笔记：

notes/YYYY/MM/YYYY-MM-DD--<slug>.md

使用简短、稳定的 slug（短横线分隔）。如果不确定，请询问标题。

使用 assets/note-template.md 中的模板。至少包含以下部分：

摘要（简短）
详情（仅重要内容）
任务（复选框）
附件（路径 + 链接）

4) 存储附件（强制）

始终将附件文件存储在与笔记文件相同的文件夹中。

笔记：notes/2026/02/2026-02-11--example.md
附件：
- notes/2026/02/2026-02-11--example--1.jpg
- notes/2026/02/2026-02-11--example--2.mp4

切勿将此工作流的笔记附件存储在 assets/images 或 assets/audio 下。
保持确定的后续编号：--1、--2、...
在笔记 markdown 中使用相对路径。

5) 在笔记 markdown 中嵌入图像（强制）

对于每个图像附件，包含一个内联 markdown 图像，以便在笔记中渲染：

![<简短替代文本>](./<附件文件名>)

对于非图像文件（视频/音频/文档），在"附件"部分下保持正常的 markdown 链接。

6) 编辑机密信息（强制）

提交前，扫描笔记（以及任何粘贴的代码片段）中的：

API 密钥 / 令牌 / 密码 / 私钥

替换为 [REDACTED_SECRET]
如果仍有歧义，在提交前询问

7) 提取任务 → 看板

更新 KANBAN.md：

将新任务添加到待办事项
每个任务应包含指向笔记路径的链接

8) 维护 README 索引（强制）

更新笔记和 KANBAN.md 后，手动更新笔记仓库的 README.md：

更新概览计数（总笔记数、总任务数）
更新笔记索引表，包含指向最新笔记的链接

9) 提交和推送（强制，用于报告链接）

提交消息约定：

note: add <简短标题>
kanban: add tasks from <slug>
note: update <slug>
docs: update notes README（如果 README 已更改）

当远程仓库存在时，始终推送，以便报告的 GitHub 链接对用户有效。一旦此技能被用户调用，不要询问额外的推送确认。

10) 使用 GitHub 链接报告（强制）

报告任何笔记操作完成时，请包含：

每个新建/更新的笔记 markdown 文件的 GitHub 链接
每个附加媒体文件的 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 步）

◆ 信息录入（第 1 步，共 4 步 — 输入处理）
··································································
  收到输入:             √ 通过
  类型检测:             √ 通过（文本/语音/图像/文件）
  内容解析:             √ 通过
  [标准]:               √ 3/3 项满足
  ____________________________
  结果:                 PASS

处理（第 2 步，共 4 步）

◆ 处理（第 2 步，共 4 步 — 笔记创建）
··································································
  笔记已写入:           √ 通过
  附件已存储:           √ 通过（与笔记同文件夹）
  机密信息已编辑:       √ 通过 — 未发现机密信息
  [标准]:               √ 3/3 项满足
  ____________________________
  结果:                 PASS

组织（第 3 步，共 4 步）

◆ 组织（第 3 步，共 4 步 — 看板和索引）
··································································
  任务已提取:           √ 通过 — 添加了 2 个任务
  看板已更新:           √ 通过 — 任务在待办事项中
  索引已维护:           × 失败 — README 计数未更新
  [标准]:               √ 2/3 项满足
  ____________________________
  结果:                 PARTIAL

发布（第 4 步，共 4 步）

◆ 发布（第 4 步，共 4 步 — git 推送和报告）
··································································
  已提交:               √ 通过
  已推送:               √ 通过
  链接已报告:           √ 通过 — 包含 GitHub 链接
  [标准]:               √ 3/3 项满足
  ____________________________
  结果:                 PASS

每日结束：列出今日笔记 + 建议重新组织（标签 / 合并 / 拆分）
每日 10–15 分钟：回顾待办事项 → 选择 → 移至进行中 → 完成

仓库流程规则：笔记仓库根目录下的 AGENTS.md
编辑和工作流策略：笔记仓库根目录下的 POLICY.md

🇺🇸English

Note Taker (Git-managed)

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.

Repo Sync Before Edits (mandatory)

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.

Workflow

1) Intake

Accept input as:

Text : the message content
Voice : summarize (do not store full transcript unless user asks)
Image / video / file : copy attachment file and reference it from the note

If the user provides multiple items, treat each as a separate note unless they explicitly want a single combined note.

2) Decide filename + folder

Create processed notes at:

notes/YYYY/MM/YYYY-MM-DD--<slug>.md

Use a short, stable slug (kebab-case). If unsure, ask for a title.

3) Write the note

Use the template in assets/note-template.md. Minimum sections:

Summary (short)
Details (only what matters)
Tasks (checkboxes)
Attachments (paths + links)

4) Store attachments (mandatory)

Always store attachment files in the same folder as the note file.

Example:

Note: notes/2026/02/2026-02-11--example.md
Attachments:
- notes/2026/02/2026-02-11--example--1.jpg
- notes/2026/02/2026-02-11--example--2.mp4

Rules:

Never store note attachments for this workflow under assets/images or assets/audio.
Keep deterministic suffixes: --1, --2, ...
Use relative paths in note markdown.

5) Embed images in note markdown (mandatory)

For every image attachment, include an inline markdown image so it renders in the note:

![<short-alt-text>](./<attachment-filename>)

For non-image files (video/audio/docs), keep normal markdown links under Attachments.

6) Redact secrets (mandatory)

Before committing, scan the note (and any pasted snippets) for:

API keys / tokens / passwords / private keys

If found:

replace with [REDACTED_SECRET]
if ambiguity remains, ask before commit

7) Extract tasks → Kanban

Update KANBAN.md:

Add new tasks to Backlog
Each task should include a link to the note path

8) Maintain README index (mandatory)

After updating notes and KANBAN.md, update the notes repo README.md manually:

Update overview counts (total notes, total tasks)
Update notes index table with links to latest notes

9) Commit and push (mandatory for reporting links)

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.

10) Report back with GitHub links (mandatory)

When reporting completion of any note action, include:

GitHub link to each new/updated note markdown file
GitHub link to each attached media file (if added)
Commit hash

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.

Step Completion Reports

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)

◆ 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)

◆ 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)

◆ 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)

◆ 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

Daily routines

End-of-day: list today’s notes + propose re-organization (tags / merges / splits)
Daily 10–15min: review Backlog → pick → move to In Progress → Done

References

Repo process rules: AGENTS.md in the notes repo root
Redaction + workflow policy: POLICY.md in the notes repo root

Weekly Installs

Repository

luongnv89/skills

GitHub Stars

First Seen

Feb 8, 2026

Security Audits

Gen Agent Trust HubPass SocketPass SnykPass

Installed on

codex51

gemini-cli50

github-copilot50

amp50

kimi-cli50

opencode50

Skills CLI 使用指南：AI Agent 技能包管理器安装与管理教程

52,700 周安装