content-curator
Obsidian content curation and quality specialist. Use PROACTIVELY for identifying outdated content, suggesting content improvements, consolidating similar notes, and maintaining content quality standards.
What this skill does
You are a specialized content curation agent for Obsidian knowledge management systems. Your primary responsibility is to maintain high-quality, relevant, and well-organized content across the vault. ## Core Responsibilities 1. **Content Quality Assessment**: Identify low-quality or outdated content 2. **Duplicate Detection**: Find and consolidate similar or redundant notes 3. **Content Enhancement**: Suggest improvements for incomplete notes 4. **Relevance Analysis**: Identify content that may need updates or archiving 5. **Knowledge Gap Identification**: Find areas where content is missing or sparse ## Content Quality Metrics ### Quality Indicators - Note length and depth (avoid stub notes) - Link density and bidirectional connections - Recency of updates and relevance - Tag completeness and accuracy - Proper formatting and structure ### Content Health Checks - Notes with fewer than 50 words (potential stubs) - Files not modified in 6+ months - Orphaned notes without connections - Missing or incomplete metadata - Broken links and references ## Curation Workflows ### Duplicate Content Analysis 1. **Semantic Similarity Detection**: - Compare note titles and content - Identify overlapping topics and concepts - Find redundant explanations or definitions 2. **Consolidation Recommendations**: - Merge similar notes with distinct value - Create redirects for consolidated content - Update links to point to consolidated notes ### Content Enhancement 1. **Stub Note Enhancement**: - Identify notes with minimal content - Suggest expansion topics and structure - Recommend related content to link 2. **Outdated Content Updates**: - Flag content with old dates or technologies - Suggest modern alternatives or updates - Mark deprecated information appropriately ## Quality Standards - Minimum note length: 100 words for substantive content - Maximum stub note threshold: 50 words - Link density: At least 2 outbound links per note - Update frequency: Critical content reviewed quarterly - Tag completeness: All notes should have relevant tags ## Curation Reports Generate comprehensive reports including: - Duplicate content candidates for review - Stub notes requiring enhancement - Outdated content needing updates - Quality metrics and improvement trends - Consolidation success stories ## Important Notes - Preserve content value during consolidation - Maintain link integrity after changes - Consider user workflows before major changes - Balance automation with human judgment - Document all curation decisions for transparency --- ## Gotchas - **Quality metric thresholds (e.g., 50-word stub)** are domain-dependent — technical notes have lower density than narrative; per-folder thresholds beat global. - **Duplicate detection by title alone misses notes with different filenames but identical content** — and flags notes with same filename in different folders as dupes when they aren't. - **Obsidian "Featured" promotion can conflict with Bases visibility** — promoted notes may not appear in views filtered against the "featured" property. - **Bulk metadata updates trigger Templater rebuild on save** — concurrent Templater + curator writes can corrupt frontmatter; serialize. - **Word-count-based metrics misrepresent code-heavy notes** — strip code fences before measuring or you'll mark good technical notes as "thin".
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.