Skip to content
Skills Library
AI & agents · Writing

pace-knowledge

/pace-knowledge

Use for PACEflow knowledge/thoughts notes, finding-to-knowledge extraction, correction knowledge links, and Obsidian frontmatter/L0-L2 note structure.

Repository
paceflow ↗
Licence
MIT
Last repository change
17.08.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
4
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 17.08.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • SKILL.md zawiera komentarze HTML (4). Nie widać ich w podglądzie Markdown, a model je czyta.

What it does and when to use it

Use for PACEflow knowledge/thoughts notes, finding-to-knowledge extraction, correction knowledge links, and Obsidian frontmatter/L0-L2 note structure.

Original author description

Use for PACEflow knowledge/thoughts notes, finding-to-knowledge extraction, correction knowledge links, and Obsidian frontmatter/L0-L2 note structure.

How it works

  1. thoughts/ 笔记
  2. knowledge/ 笔记
  3. 创建时机
  4. Findings → Knowledge 提取 SOP
  5. Corrections 双写流程
  6. L0/L1/L2 信息分层
  7. Obsidian 操作指引
Original SKILL.md headings · 185 lines, 577 words
SKILL.md preview
---
name: pace-knowledge
effort: medium
description: >
  Use for PACEflow knowledge/thoughts notes, finding-to-knowledge extraction,
  correction knowledge links, and Obsidian frontmatter/L0-L2 note structure.
---

# Obsidian 知识库笔记管理规则

管理 Obsidian Vault 中 `thoughts/` 和 `knowledge/` 目录的笔记创建与维护。

**Vault 路径**:由 `PACE_VAULT_PATH` 环境变量指定的 Vault 路径

`spec.md` 的 `project-summary` 是项目元描述,不是 knowledge/thoughts 笔记的 L0 `summary` 字段。

> **SessionStart 自动注入**:SessionStart hook 会自动扫描 `thoughts/` 和 `knowledge/` 目录中与当前项目相关的笔记(通过 frontmatter `projects` 字段匹配),将 L0 摘要注入到会话上下文中。注入按 kind 分配独立名额:相关知识段 wiki 最多 3 条、knowledge 最多 2 条,未成熟想法段 thoughts 最多 3 条;startup 与 compact 恢复使用同一套名额。

> **状态体系说明**:knowledge/thoughts 笔记使用 `discussing`/`concluded`/`archived` 状态标记(frontmatter `status` 字段),与 task.md 的 checkbox 状态标记(`[ ]`/`[/]`/`[x]`)是**两套独立的含义系统**,各自在自身文件类型内使用。

---

## thoughts/ 笔记

**用途**:酝酿中的想法、方案讨论、可行性验证——尚未成熟到进入 PACE 执行阶段。

仓库内 `plugin/hooks/templates/knowledge-note.md` 是 knowledge/thoughts 笔记的参考模板;实际创建仍按本 skill 的字段要求写入 Obsidian vault。

### 模板

```markdown
---
status: discussing
projects: [项目名]
tags: [标签1, 标签2]
summary: "一句话摘要,Home.md 仪表盘显示用"
created: YYYY-MM-DDTHH:mm:ss+08:00
updated: YYYY-MM-DDTHH:mm:ss+08:00
---

# 标题

## 摘要

<!-- L1:关键结论/想法,300-500 tokens -->

- 结论 1
- 结论 2

## 详情

<!-- L2:完整分析过程、对比、推理链 -->
```

### 状态流转

| 状态 | 含义 | 流转条件 |
|------|------|---------|
| `discussing` | 酝酿中,尚无定论 | 创建时默认 |
| `concluded` | 已有结论,可执行或归档 | 讨论收敛、方案确定 |
| `archived` | 已过时或已被执行吸收 | 关联 CHG 完成 / 内容过时 |

### 规则

- `summary` 必填,不超过 80 字
- `projects` 至少关联一个项目名(对应 `projects/` 下的目录名)
- 更新内容时同步更新 `updated` 时间戳
- Home.md 仪表盘查询 `status = "discussing"` 的笔记

---

## knowledge/ 笔记

**用途**:跨项目可复用的经验、模式、最佳实践——从项目 findings 中提炼的知识沉淀。

### 模板

```markdown
---
status: concluded
projects: [来源项目1, 来源项目2]
tags: [标签1, 标签2]
summary: "一句话摘要,Home.md 仪表盘显示用"
created: YYYY-MM-DDTHH:mm:ss+08:00
updated: YYYY-MM-DDTHH:mm:ss+08:00
sources:
  - 来源项目/findings
---

# 标题

## 摘要

<!-- L1:关键结论,300-500 tokens -->

- 结论 1
- 结论 2

## 详情

<!-- L2:完整内容、代码示例、对比表格 -->
```

### 规则

- `summary` 必填,不超过 80 字
- `sources` 标注知识来源(哪个项目的 findings)
- `status` 通常为 `concluded`(已验证的知识)
- 知识过时时更新内容或改 status 为 `archived`
- Home.md 仪表盘显示所有非 README 的 knowledge/ 笔记

---

## 创建时机

### thoughts/ 创建条件

- 讨论中出现值得持久化但未成熟的想法
- 方案对比需要跨会话保持
- 用户主动要求"记下来"或"先想想"

### knowledge/ 创建条件

- 项目 findings 中发现跨项目通用经验
- 同一踩坑经验在 2+ 个项目出现
- 用户要求提取知识

### 留在别处的情况

- 项目特有的实现细节 → 留在 `changes/findings/<id>.md`
- 一次性调试信息 → 用完即弃,留在当前会话上下文
- 已有同主题笔记 → 更新现有笔记承载新内容

---

## Findings → Knowledge 提取 SOP

当 `changes/findings/<id>.md` 中的调研结论被判定为跨项目通用经验时,执行以下步骤:

1. **判定通用性**:该经验是否在其他项目中也可能遇到?(如 Hook I/O 协议、AI 验证纪律、路径处理)
2. **检查 knowledge/ 是否已有同主题笔记**:正确做法是先使用当前环境可用的只读搜索工具检索 `knowledge/` 目录中的标题和标签;专用搜索工具不可用时,用只读 Bash `rg` / `grep` / `find` fallback。搜索失败只影响检索方式,不代表知识库流程失败。
3. **已有** → Edit 追加新内容到 `## 详情` section,更新 `updated` 日期和 `sources`
4. **未有** → Write 创建新笔记,使用 knowledge/ 模板,`status: concluded`
5. **关联 finding**:`record-finding` 不维护 knowledge frontmatter 字段(knowledge 反向链接优先写在 knowledge 笔记正文引用原 finding)。finding 详情可经 `update-finding` 维护——`append` 向正文**末尾追加**、`status` 迁移状态、`change-link` / `merged-into` 补关联(既有正文只可追加、不可改写;详见 `agent-references/instructions/update-finding.md`)。需要补充「与 knowledge 笔记的关系」等正文增量时,派 `artifact-writer update-finding append=<增量>` 追加到原 finding,无需另建补充 finding。

> 提取的知识必须自包含——不依赖原 finding 的上下文就能理解。摘要是结论,详情是完整推理。

### 联动触发

此 SOP **不仅**由用户手动触发。以下场景应**主动评估**是否需要提取:

- **记录新 finding 时**(由 `artifact-writer record-finding` 触发):recording finding → 评估通用性 → 通用则执行本 SOP
- **Corrections 双写时**:`record-correction` → 评估通用性 → 通用则提取到 knowledge/
- **审计/复盘发现时**:P0/P1 或可复用的问题模式 → 评估是否为通用模式

> artifact-management 的 `references/change-lifecycle.md` 中 "Finding / Correction 联动" 会指引 AI 在 agent 写入详情后主动评估并触发本 SOP。

---

## Corrections 双写流程

被用户纠正时("不对"、"别这样"、"错了"等),先评估 knowledge 双写,再通过 artifact writer 记录 correction:

1. **评估通用性**:该纠正是否跨项目通用?
   - **通用**(如 AI 验证习惯、决策偏差模式)→ 步骤 2
   - **仅限本项目**(如特定 API 用法)→ 步骤 3,agent 输入 `project-scope: project-only`
2. **写入或选定 knowledge/**:追加到已有笔记或新建,标注来源项目,拿到 `[[note]]` wikilink
3. **记录 correction**:派 `artifact-writer record-correction`,写入 `changes/corrections/<id>.md` 和 `corrections.md` 索引,必填 `trigger-quote`、`wrong-behavior`、`correct-behavior`、`trigger-scenario`、`root-cause`,并二选一提供 `knowledge-link: [[note]]` 或 `project-scope: project-only`

> PostToolUse hook 检测 correction 详情/索引写入后会 HINT 提醒同步 knowledge/。

---

## L0/L1/L2 信息分层

| 层级 | 内容 | Token 量 | 用途 |
|------|------|---------|------|
| **L0** | frontmatter `summary` | ~50 | SessionStart 匹配注入 |
| **L1** | `## 摘要` section | ~300-500 | 快速了解核心结论 |
| **L2** | `## 详情` 及以下 | 不限 | 按需 Read 全文 |

---

## Obsidian 操作指引

操作 Obsidian 笔记时,优先调用当前可用的 `obsidian:*` plugin skill;未安装 Obsidian plugin skill 时回退到 fs 操作:

- **CLI 操作**(搜索/创建/追加/属性编辑)→ 调用 `obsidian:obsidian-cli`
- **Markdown 语法**(wikilinks/callouts/embeds/properties)→ 调用 `obsidian:obsidian-markdown`
- **Obsidian 未运行**时 → 回退 fs 直接操作(Read/Write/Edit 工具)
- **Hook 层**始终使用 fs(延迟 <5ms),仅 post-tool-use H12 用 fire-and-forget spawn 调用 CLI

Versions

The database has no other skills named pace-knowledge.

Database snapshot: 13.11.2026 · package version 4b170b55cffc (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100pace-bridge
    Use to bridge a confirmed Superpowers/native plan into PACEflow CHG/HOTFIX artifacts, create artifact-writer prompts, and mark the specific plan as synced.
  • 100pace-workflow
    Use for PACEflow-managed coding work: create, approve, resume, verify, close, or archive CHG/HOTFIX before project file edits.
  • 100okf-ops
    Assess, validate, and adopt the Open Knowledge Format (OKF) across markdown+frontmatter knowledge bases. Triggers on: OKF, open knowledge format, knowledge bundle, frontmatter conformance, validate frontmatter, markdown knowledge base, adopt OKF, is this repo OKF-ready, index.md log.md.
  • 100knowledge-graph
    Knowledge graph and smart memory management using graphify + Obsidian-inspired patterns. Use when: setting up a knowledge graph, managing memory health, cross-linking notes, compiling wiki pages from scattered notes, adding structured frontmatter, or running memory health…
  • 90note
    Use when working with files in ~/Notes (the user's Obsidian vault). Covers vault structure (PARA), file naming, frontmatter, icons, templates, kanban boards, and the obsidian CLI.
  • 100obsidian-vault
    Vault structure, file naming, frontmatter, tags, tasks, and linking conventions. Use when: "vault structure", "file naming", "frontmatter", "wiki links", "obsidian", "tags", "tasks", "create note", "organize notes".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.