audit-content
$
npx mdskill add dandye/ai-runbooks/audit-contentAudit documentation quality, relevance, and maintenance needs.
- Identifies outdated content, broken links, and clarity issues.
- Depends on file system access to scan directories and metadata.
- Prioritizes findings by severity level and category selection.
- Delivers actionable recommendations with optional automated fixes.
SKILL.md
.github/skills/audit-contentView on GitHub ↗
--- name: audit-content description: Comprehensive content quality and maintenance assessment. Evaluates documentation quality, relevance, maintenance needs, and provides actionable recommendations. required_roles: scribe: roles/scribe.editor personas: [information-architect, content-strategist, editor] --- # Content Audit Skill Perform a comprehensive quality and maintenance assessment of documentation or content. This skill evaluates content against quality standards, checks for freshness, identifies maintenance needs, and provides actionable recommendations. ## Inputs - `PATH` - The directory or file path to audit (e.g., "/docs") - `SEVERITY` - (Optional) Minimum severity level to report: "low", "medium", "high" (default: "medium") - `CATEGORY` - (Optional) Categories to audit: "all", "quality", "relevance", "links", "metadata" (default: "all") - `FIX_MODE` - (Optional) Boolean, whether to suggest or apply automated fixes where possible (default: false) ## Workflow ### Step 1: Inventory & Freshness Check Scan the target `PATH` to list all content assets. - Check "Last Modified" dates. - Identify outdated content (e.g., > 6 months old). - Verify author/owner metadata. ### Step 2: Quality Assessment Evaluate content against quality metrics: - **Clarity & Readability**: Is the content easy to understand? (e.g., plain language). - **Completeness**: Does it cover the topic sufficiently? - **Accuracy**: Are there broken links, deprecated terms, or incorrect instructions? - **Structure**: Does it follow standard templates and formatting? ### Step 3: Issues & Recommendations Generate a report of identified issues, categorized by severity: - **High**: Broken paths, critical misinformation, missing required sections. - **Medium**: Outdated styling, poor readability, minor inaccuracies. - **Low**: Typos, inconsistent formatting. If `FIX_MODE` is enabled, generate or apply suggestions for fixes. ## Required Outputs A `CONTENT_AUDIT_REPORT` in markdown format containing: - **Summary**: Total files, overall quality score, critical issues count. - **Detailed Findings**: Table of issues per file with severity. - **Action Items**: Prioritized list of recommended changes. - **Freshness Report**: List of stale or outdated documents. ## Quick Reference - **Purpose**: Support content maintenance planning and quality improvement. - **Key Metrics**: Quality Score (0-100), Freshness (Age in days), Link Health (% valid).
More from dandye/ai-runbooks
- analyze-content-gapsIdentify content gaps and organizational opportunities. Analyzes missing content areas, redundancies, and consolidation opportunities.
- check-duplicates"Check for duplicate or similar cases. Use before deep analysis to avoid investigating the same incident twice. Takes a CASE_ID and returns list of similar cases."
- close-case-artifact"Close a case or alert with proper reason and documentation. Use when triage determines an alert is FP/BTP or investigation is complete. Requires artifact ID, type, closure reason, and root cause."
- cluster-documentsAutomated content similarity and grouping analysis. Groups related documents by topic, purpose, or content similarity.
- confirm-action"Ask the user to confirm before taking a significant action. Use before containment, remediation, or other impactful operations to ensure analyst approval. Presents options and waits for response."
- correlate-ioc"Check for existing SIEM alerts and case management entries related to IOCs. Use to understand if an indicator has triggered previous alerts or is part of ongoing investigations. Takes IOC list and returns related alerts and cases."
- deep-dive-ioc"Perform exhaustive analysis of a critical IOC. Use when an IOC needs Tier 2+ investigation beyond basic enrichment - includes GTI pivoting, deep SIEM searches, correlation with related entities, and threat attribution. For escalated IOCs requiring comprehensive investigation."
- design-metadata-schemaDesign comprehensive metadata frameworks. Develops structured metadata templates and tagging systems.
- document-in-case"Add a comment to a case to document findings, actions, or recommendations. Use to maintain audit trail during investigations. Requires CASE_ID and comment text."
- enrich-ioc"Enrich an IOC (IP, domain, hash, URL) with threat intelligence. Use when you need to look up reputation and context for an indicator using GTI and SIEM. Returns threat intel findings, SIEM entity summary, and IOC match status."