Content Curator Pro

Automated quality analysis and curation engine for Obsidian vaults, detecting stale notes, duplicates, and knowledge gaps.

When to Use This Agent

Choose this agent when you need to:

• Audit an entire Obsidian vault for content quality, staleness, and completeness
• Identify and consolidate duplicate or near-duplicate notes before they proliferate
• Generate actionable curation reports with prioritized remediation tasks
• Detect knowledge gaps where topics are referenced but lack dedicated notes

Consider alternatives when:

• You need to restructure your tag taxonomy (use Tag Agent Partner instead)
• Your primary concern is vault performance and file sizes rather than content quality

Quick Start

Configuration

Copy
name: content-curator-pro
type: agent
category: obsidian-ops-team

Example Invocation

Copy
claude agent:invoke content-curator-pro "Audit my vault for stubs, duplicates, and orphaned notes"

Example Output

=== Content Curation Report ===
Vault: ~/ObsidianVault (1,247 notes scanned)

STUB NOTES (< 80 words): 43 found
  - daily/2025-11-03.md (12 words) → Recommend: expand or archive
  - projects/api-redesign.md (34 words) → Recommend: expand with specs

DUPLICATE CLUSTERS: 7 detected
  Cluster #1 (similarity: 0.91):
    - concepts/event-sourcing.md
    - architecture/event-driven-patterns.md
    → Recommend: merge into concepts/event-sourcing.md

ORPHANED NOTES: 19 found (zero inbound links)
KNOWLEDGE GAPS: 5 referenced topics without dedicated notes

Core Concepts

Content Quality Scoring Overview

Aspect	Details
Word Count Threshold	Notes under 80 words flagged as stubs requiring expansion
Link Density Minimum	At least 2 outbound wikilinks per substantive note
Staleness Window	Notes unmodified for 180+ days marked for review
Metadata Completeness	Frontmatter must include tags, created date, and status

Curation Pipeline Architecture

┌─────────────┐     ┌─────────────┐
│  Vault Scan  │────▶│  Quality    │
│  & Indexing  │     │  Scoring    │
└─────────────┘     └─────────────┘
        │                   │
        ▼                   ▼
┌─────────────┐     ┌─────────────┐
│  Duplicate   │────▶│  Report     │
│  Detection   │     │  Generator  │
└─────────────┘     └─────────────┘

Configuration

Parameter	Type	Default	Description
stub_threshold	integer	80	Word count below which a note is flagged as a stub
staleness_days	integer	180	Days without modification before flagging for review
similarity_cutoff	float	0.85	Cosine similarity threshold for duplicate detection
min_link_density	integer	2	Minimum outbound wikilinks expected per note
exclude_folders	list	["templates","daily"]	Directories to skip during curation scans

Best Practices

1. Run Curation Scans on a Schedule Content quality degrades gradually. Running weekly or biweekly curation scans prevents the accumulation of stubs, broken links, and orphaned notes that make a vault progressively harder to navigate.

2. Triage Before Bulk Operations Review the curation report manually before executing automated consolidations. Some apparent duplicates may represent intentionally distinct perspectives, and merging them blindly destroys valuable nuance.

3. Preserve Backlinks During Consolidation When merging duplicate notes, always update every inbound link to point to the surviving note. Broken backlinks silently erode the vault's knowledge graph and undermine future discoverability.

4. Exclude Ephemeral Content from Quality Checks Daily notes, scratchpads, and template files should be added to the exclusion list. Flagging these as low-quality stubs generates noise and obscures genuinely problematic content.

5. Track Curation Metrics Over Time Store each curation report so you can compare vault health across periods. Trending metrics like orphan count, average link density, and stub percentage reveal whether your knowledge practices are improving or regressing.

Common Issues

1. False duplicate detection on related but distinct topics Lower the similarity_cutoff from 0.85 to 0.75 if the agent misses true duplicates, or raise it to 0.92 if unrelated notes on adjacent topics are being incorrectly clustered. Always review clusters before merging.

2. Daily notes flooding the stub report Add your daily notes folder to exclude_folders in the configuration. Daily notes are naturally short and ephemeral, so they should not be held to the same quality standards as reference notes.

3. Orphaned notes appearing for intentionally standalone content Add a frontmatter field standalone: true to notes that are deliberately unlinked, such as inbox captures or imported bookmarks. The agent respects this flag and omits them from orphan reports.