一键导入
reviewing-notes
Audit notes for quality issues. Use when asked to "review notes", "check content quality", "audit my knowledge base", or "find broken links".
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Audit notes for quality issues. Use when asked to "review notes", "check content quality", "audit my knowledge base", or "find broken links".
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Must read guide on creating/editing mermaid charts with validation tools and syntax reference for all diagram types
Generate interactive HTML walkthroughs with clickable Mermaid diagrams (flowcharts and ER diagrams) that explain codebase features, flows, architecture, and database schemas. Use when asked to "walkthrough", "explain this flow", "how does X work", "trace the code path", "annotated diagram", "code walkthrough", "explain the architecture of", "walk me through", "database schema", "explain the tables", "data model".
Create a note from any resource: URL, book, podcast, article, video, GitHub repo, Reddit thread, PDF, quote, or raw idea. Trigger on "add", "save", "capture", "note this", "take notes on", or any request to record content in the knowledge base.
Add tweets to the Second Brain. Use when the user provides a Twitter/X URL and pasted tweet content, asking to "add a tweet", "save this tweet", or "capture this tweet".
Query your Second Brain with keyword search. Use when asked to "ask my notes", "what do I know about", "query my knowledge", "/ask", or when the user has a question that their notes might answer.
Create Obsidian templates for the Second Brain vault. Use when asked to "create a template", "make a template for", "add an Obsidian template", or "template for X".
| name | reviewing-notes |
| description | Audit notes for quality issues. Use when asked to "review notes", "check content quality", "audit my knowledge base", or "find broken links". |
| allowed-tools | Read, Glob, Grep |
This skill audits the knowledge base for quality issues and produces an actionable report.
# List all content files
ls content/*.md
Read each file and check for:
summary: field in frontmatterParse all [[slug]] patterns and verify each target exists:
# Extract wiki-links from a file
grep -o '\[\[[^]]*\]\]' content/note-name.md
# Check if target file exists
ls content/target-slug.md
title fieldtype fielddate fieldOrganize findings by severity:
## Quality Audit Report
### Critical Issues
- **Broken Links**
- `note-a.md`: links to [[non-existent]] (file not found)
### High Priority
- **Missing Summaries**
- `note-b.md`: no summary field
- `note-c.md`: summary is empty
- **Orphan Notes** (no connections)
- `isolated-note.md`: 0 incoming, 0 outgoing links
### Medium Priority
- **Insufficient Tags** (<2 tags)
- `note-d.md`: only 1 tag
- **Short Content** (<100 words)
- `stub-note.md`: 45 words
### Low Priority
- **Missing Optional Fields**
- `note-e.md`: no date field
| Issue | Severity | Impact |
|---|---|---|
| Broken wiki-link | Critical | Navigation fails |
| Missing summary | High | Poor discoverability |
| Orphan note | High | Lost in graph |
| <2 tags | Medium | Harder to find |
| Short content | Medium | May be incomplete |
| Missing date | Low | Timeline unclear |
When reviewing: