content-curator — Claude Code subagent: what it does, how to install
This subagent audits Obsidian notes, spots duplicates and stale material, and suggests cleanup work. Use it when a vault needs regular content review.
npx claude-code-templates@latest --agent obsidian-ops-team/content-curatorWhat content-curator does
content-curator reviews an Obsidian vault for weak or aging material. It checks short notes, disconnected files, broken references, incomplete metadata, tagging gaps, and structural issues. It also compares note titles and text to locate overlapping subjects and repeated explanations.
The subagent can propose ways to expand thin notes, suggest related links, recommend merges, and adjust references after consolidation. Its available tools are Read, Write, Edit, Grep, and Glob; it can produce reports covering duplicate candidates, notes needing expansion, outdated content, and quality trends.
Its checks use a 50-word threshold for possible stubs, a 100-word target for substantive notes, and an expectation of 2 outbound links per note. Critical material is reviewed quarterly in its quality rules. Because it can change notes with Write and Edit, review proposed edits before a large cleanup.
What it helps with
- flag outdated notes and technologies
- find overlapping or redundant notes
- plan note consolidation and link updates
- expand thin or incomplete material
- check tags, metadata, and broken links
Example prompts for the agent
- Review this Obsidian vault and find notes shorter than 50 words.
- Compare similar notes, propose a merge plan, and update their links.
- Create a report covering stale content, orphaned notes, and broken references.
How to install content-curator
1claude-code-templates
npx claude-code-templates@latest --agent obsidian-ops-team/content-curator2Manually: put the files in place
.claude/agents/content-curator.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/content-curator.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/content-curator.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about content-curator
How do I install content-curator in Claude Code?
Run npx claude-code-templates@latest --agent obsidian-ops-team/content-curator, then use .claude/agents/content-curator.md.
What does content-curator do?
It audits Obsidian content, identifies duplicates, stale notes, weak connections, and missing metadata, then suggests improvements or consolidation.
What thresholds does the subagent use?
A note under 50 words is treated as a possible stub, while substantive notes have a 100-word minimum in its quality standards. It also checks for 2 outbound links per note.
