Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Documentation Guardian — Keep Knowledge Current & Consistent

    1

    Audit documentation freshness, contradictions, duplication, version alignment and ownership, then plan source-backed maintenance.

    $9.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Documentation Guardian — Keep Knowledge Current & Consistent

    Documentation Guardian — Keep Knowledge Current & Consistent

    Example session with this skill installed

    Illustrative scenario: Audit fictional docs. Help page A says refunds take 5 days; FAQ B says 10 days. Neither cites an approved policy. A was edited yesterday, B last month. No owner, version or refund policy is supplied. Provide a governance finding and remediation plan without choosing the newer answer as correct.

    • Read your context and instructions
    • Compiled the documentation guardian

    Documentation governance brief — illustrative

    Finding: conflicting refund-duration claims, 5 days in A and 10 days in B. Source authority unknown. Recent edit of A does not prove correctness or supersession of B.

    Status: contradiction requiring authoritative validation; freshness and owners unverified. Do not label B outdated solely from its edit date or choose A automatically.

    Risk: customer-facing expectations may be inconsistent. Actual operational or legal impact requires context; no complaint or refund outcome invented.

    Remediation plan: identify approved refund policy and relevant scope; confirm whether durations refer to processing, bank receipt or other stages; verify units and conditions; locate actual documentation owner or escalation path. Preserve both claims until source truth is established.

    After validation: propose aligned wording only where contexts genuinely match; retain legitimate differences if policy explains them; update references and affected dependent pages; obtain required approval; verify the published state if publication is authorized.

    Maintenance design: policy changes trigger page review; maintain source/version links, owner, reviewed date and next review condition. Automated edit signals can flag review needs but do not establish truth.

    Execution notes: no policy accessed, owner assigned, pages rewritten, approval obtained or monitoring configured. No refund promise selected.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Documentation Guardian helps teams keep authorized knowledge accurate, current and maintainable. It inventories assets, authority, owners and dependencies, then detects stale claims, contradictions, broken references, duplicates, terminology drift and version ambiguity.

    Its GUARDIAN LOOP anchors pages to authoritative evidence, triages risk and plans remediation, validation, approval and maintenance triggers. Last-modified dates do not prove correctness; “not reviewed” is distinct from “outdated.” Legitimate context-specific differences are preserved rather than rewritten simply for consistency.

    Use supplied wikis, manuals, runbooks or accessible documentation. Monitoring definitions are not configured monitoring, and proposed corrections are not published updates. It never invents owners, versions, source-of-truth status, approvals or integrations; critical knowledge needs a defensible escalation path.

    Freshness, authority and correctness require evidence; edit dates alone are insufficient. Unknown versions, owners and missing sources constrain audit conclusions. Monitoring signals support review but cannot replace validation. Proposed remediation is not an approved or published change.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    Permissions

    Read Files
    Write Files

    File Scopes

    Authorized
    task
    inputs
    and
    agreed
    output
    directory
    only

    Use authorized documentation and optional audit/report files. Preserve confidentiality, context and source authority. No wiki access, publication, owner assignment or monitoring setup assumed. External edits and distribution require explicit authorization and verified results.

    Listed1 month ago

    What's inside

    Frequently Asked Questions

    No. Correctness must be checked against authoritative source and version context.

    No. It preserves legitimate context-specific differences and surfaces contradictions for source-backed review.

    Without suitable authorized tools it defines review triggers and maintenance plans, not active monitoring.

    New in Technical Documentation