Archive old wiki pages

    1

    Distills durable info from old wiki pages into active docs and archives the originals with full reference integrity.

    Free

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Archive old wiki pages

    Example session with this skill installed

    Run wiki archive for all pages older than 3 months. Verify the 100-page floor before starting.

    • Read your context and instructions
    • Compiled the archive old wiki

    I have scanned wiki/pages/ and identified 5 candidates for archiving. 2 pages were skipped due to status: open and 1 was skipped because of an open ## Follow-ups section. I successfully distilled durable decisions into active pages and moved the originals to the archive.

    Archive Report

    CandidateResultDistilled Content
    2023-10-12-auth-session.mdMerged into auth-docs.mdJWT refresh logic and Biome linting rules.
    2023-11-05-db-migration.mdMerged into schema-design.mdPostgres indexing strategy for the orders table.
    2023-08-20-legacy-api.mdNo target — archivedNone (info superseded by v2 docs).
    2023-09-15-deployment.mdMerged into ci-cd-spec.mdGitHub Actions runner configuration for staging.
    2023-11-10-ui-refactor.mdMerged into design-system.mdTailwind spacing scale and color palette refs.

    Next steps

    • Review auth-docs.md to verify the merged JWT rationale.
    • Manually resolve the 3 pages in the "needs human review" list to clear them for the next archive cycle.
    • Check wiki/archive/ to ensure the git mv operations correctly preserved history.

    2 archived, 3 skipped, 3 needs-human-review.

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

    About this skill

    Technical debt in documentation builds up quickly, burying architectural decisions under layers of outdated session notes. This skill automates the cleanup of your project wiki by distilling durable information from old pages into active ones and archiving the originals.

    What it does

    • Automatic aging Identifies pages older than three months using frontmatter dates.
    • Durable extraction Distills architectural choices, stable patterns, and external references while discarding session-specific debug narratives.
    • Smart merging Transfers useful info into relevant target pages, complete with source attribution and backlink updates.
    • Reference integrity Rewrites cross-links in INDEX.md, QUESTIONS.md, and body text to prevent dangling pointers.
    • Archive management Relocates retired files to an archive directory using git mv to preserve version history.

    How it works

    1. Discovery Scans the wiki/pages/ directory to filter candidates based on age, status, and open follow-ups.
    2. Merge planning Analyzes candidates for durable content and identifies the most relevant current pages for integration.
    3. Execution Updates target frontmatter and body sections before cleaning up all internal wiki references.
    4. Archiving Moves original files to the archive and updates session mapping files.

    Frameworks & tools

    This tool operates on standard Markdown files with YAML frontmatter. It requires a specific directory structure (wiki/pages/, wiki/archive/) and uses git mv for file operations.

    Why this beats prompting it yourself

    Manually tracking every cross-link in a complex wiki is error-prone and tedious. This skill enforces a 100-page safety floor and handles complex reference updates across multiple files that simple prompts often miss.

    Use cases

    • Pruning a large project wiki that has become difficult to navigate.
    • Consolidating scattered architectural decisions into a central source of truth.
    • Preparing for a new project phase by archiving old session logs.
    • Maintaining documentation hygiene without losing historical context.

    Known limitations

    Requires specific frontmatter fields like date and status to identify candidates. It will not process pages with open follow-ups or active statuses without human intervention.

    Requires YAML frontmatter with date and status fields. Skips pages with open follow-ups. Enforces a 100-page minimum in the active directory.

    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

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 20 days ago

    • Free with an Agensi account

    Permissions

    Read Files
    Write Files
    Listed20 days ago

    What's inside

    Frequently Asked Questions

    This skill requires your wiki to use Markdown files with YAML frontmatter, specifically including 'date' and 'status' fields. It is designed for directory structures containing 'wiki/pages/' and 'wiki/archive/' folders.

    The skill uses 'git mv' commands to relocate files, ensuring that your entire commit history and versioning remain intact within your repository. You won't lose the audit trail of how your documentation evolved.

    The skill identifies 'durable' information like architectural decisions and stable patterns while filtering out transient content like temporary debug logs or meeting filler. It then merges this relevant data into your active docs with full source attribution.

    To prevent accidental data loss, the skill includes a 100-page safety floor and will automatically skip any pages marked with open follow-ups or an active status. This ensures that only truly stale content is processed.

    The skill automatically scans and rewrites internal cross-links in files like 'INDEX.md' and 'QUESTIONS.md'. This prevents 'dangling pointers' and broken links that typically occur when moving files manually.

    You receive the complete skill package, including the logic for discovery, merge planning, and reference integrity. This is a one-time purchase that you can run as part of your regular documentation maintenance cycle.

    New in Technical Documentation