agentleFS
c-ibarrac-ibarra/ObsidianKnowledgeCurator/.agents/skills/note-review/SKILL.md

note-review

Skill0 starsChanged 43 days agoMITView on GitHub

Use this skill when the user wants to review, improve, audit, or clean up notes in their vault. Triggers include "review this note", "improve my note on", "audit my vault", "find stale notes", "vault health check".

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run diagnostics (excluding dswok):

    line 84
  2. Distinctive:

    Never auto-apply bulk edits — always get confirmation

    line 112
  3. Very specific:

    Never use obsidian delete — use obsidian move folder="_archive" instead

    line 113

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Note Review Skill

Goal

Audit one or more notes (or the full vault) for quality issues and propose targeted improvements — using obsidian CLI for all operations.

Prerequisites

pgrep -x Obsidian > /dev/null && echo "open" || echo "CLOSED"
# Read obsidian-cli skill before operating

⚠️ Always exclude from any audit: dataScienceKnowledgeBase/dswok

Mode A — Review a single note

  1. Gather all info:
obsidian read file="<note name>"
obsidian links file="<note name>"
obsidian backlinks file="<note name>" counts
obsidian wordcount file="<note name>"
  1. Evaluate against vault quality checklist:
  • Clear and specific H1 title (not "Untitled")
  • Header blockquote present with all fields
  • Tags: #no-read-yet in blockquote (or updated tag)
  • No YAML frontmatter
  • ## 📌 Key Takeaways section present
  • At least one outgoing [[wikilink]]
  • ## Related section present
  • No emojis outside of ## 📌 Key Takeaways
  • File name follows naming convention
  • Substantial content (>3 real sentences)
  1. Present review report:
📋 Review: [[Note Name]]

✅ Good:
- Correct structure and clear title

⚠️ Issues:
- Missing header blockquote
- No outgoing wikilinks — isolated note
- File name doesn't follow naming convention

✏️ Suggested changes:
1. Add header blockquote with Tags: #no-read-yet
2. Add to Related: [[Note X]], [[Note Y]]
3. Rename to: "Channel — Video Title.md"

Apply? [All / Select / Skip]
  1. If approved, apply:
obsidian prepend file="<name>" content="> **Author — Title**\n> Source: ...\n> Type: video\n> Tags: #no-read-yet\n"
obsidian append file="<name>" content="\n## Related\n- [[Note X]]"
obsidian rename file="<old name>" name="<new name>"  # preserves backlinks

Mode B — Find stale notes

obsidian search query="#no-read-yet" limit=30
obsidian recents limit=20

Cross-reference: notes with #no-read-yet that haven't appeared in recents = likely stale.

Present sorted by estimated age. For each, offer:

  • "Expand this note?" → open and expand
  • "Archive?" → obsidian move file="<name>" folder="_archive"
  • "Skip"

Mode C — Vault health check

Run diagnostics (excluding dswok):

obsidian orphans total        # notes without any links
obsidian unresolved           # broken wikilinks
obsidian deadends             # notes without backlinks
obsidian tags total           # tag taxonomy
obsidian files folder="<RootFolder>" total

Report format:

🏥 Vault Health Report

📁 Notes in RootFolder: X
🔗 Orphan notes: X (no incoming or outgoing links)
🔴 Broken wikilinks: X
⬛ Notes without backlinks: X
🏷️ Unique tags: X

Recommendations:
1. Review X orphan notes — link or archive
2. Fix X broken wikilinks
3. [if many tags] Consolidate taxonomy

Offer to address each category one at a time.

Constraints

  • Never auto-apply bulk edits — always get confirmation
  • Never use obsidian delete — use obsidian move folder="_archive" instead
  • Never touch dataScienceKnowledgeBase/dswok
  • Skip _archive/ folder in all audits
  • Rename with obsidian rename (not file system mv) — preserves backlinks

Examples

"Review Claude Code CLI note"

obsidian read file="Claude Code CLI"
obsidian links file="Claude Code CLI"
obsidian backlinks file="Claude Code CLI" counts
obsidian wordcount file="Claude Code CLI"
# → report → user approves → apply fixes

"Vault health check"

obsidian orphans total
obsidian unresolved
obsidian deadends
obsidian tags total
# → present report → offer to fix per category

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.