meridian-archive-organizer

Classify deprecated Meridian code and documentation for archive or delete destinations.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/rodoHasArrived/Meridian-main --skill meridian-archive-organizer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meridian-archive-organizer
Source: https://github.com/rodoHasArrived/Meridian-main/tree/main/.agents/skills/meridian-archive-organizer
Command: npx skills add https://github.com/rodoHasArrived/Meridian-main --skill meridian-archive-organizer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Meridian repositories accumulate deprecated code and outdated documentation that are useful historically but harmful for navigation and decision-making.

Core Features & Use Cases

  • Evidence-based classification: Assigns each target a disposition like active, archived-doc, archived-code, delete, or already-archived.
  • Correct archive placement: Moves items into the right archive bucket (docs assessments/plans/summaries/migrations/assets, or retired code under archive/code).
  • Strong vs weak reference separation: Uses trace artifacts and bundled scripts to justify why something can be archived safely.
  • Documentation link & index repair: Updates READMEs, indexes, and nearby cross-links when paths change.
  • Validation and eval harness: Runs deterministic checks and reports rubric-style or scripted evaluation outcomes for non-trivial sweeps.

Quick Start

Use meridian-archive-organizer to determine where a deprecated file should go in Meridian and what evidence proves the move is safe.

Frequently Asked Questions about meridian-archive-organizer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I archive deprecated documentation and stale code in a repository without breaking references?

To archive deprecated documentation and stale code safely, classify strong versus weak references using trace artifacts, then move items into correct archive buckets while updating READMEs and cross-links to repair navigation paths.

What's the best way to determine if a misplaced file should be archived or deleted from a codebase?

The best way to determine if a misplaced file should be archived or deleted is to run deterministic evidence-based classification scripts that assign dispositions like active, archived-doc, archived-code, or delete based on traced reference strength.

How does evidence-based classification work for repository cleanup and archive placement?

Evidence-based classification for repository cleanup works by running trace scripts to separate strong active references from weak historical ones, justifying whether a target receives an archived-doc, archived-code, or delete disposition in the correct bucket.

Can I automate documentation link repair when moving outdated files into an archive directory?

Yes, you can automate documentation link repair when archiving outdated files by updating READMEs, indexes, and nearby cross-links during the archive placement process to ensure path consistency across the repository structure.

How do I validate that a repository cleanup sweep didn't miss any stale code or broken references?

You validate a repository cleanup sweep by running a deterministic eval harness that checks rubric-style outcomes and reports scripted evaluation results to confirm all stale code and broken references were resolved correctly.

Do I need any specific dependencies to run reference tracing for repository structure cleanup?

No specific external dependencies are required to run reference tracing for repository structure cleanup, as the Skill uses bundled scripts and trace artifacts to provide deterministic evidence for archive placement decisions.