migration-context

Classify flat markdown docs and propose migrations to .claude/context/.

2|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/erclx/aitk --skill migration-context
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migration-context
Source: https://github.com/erclx/aitk/tree/main/claude/skills/migration-context
Command: npx skills add https://github.com/erclx/aitk --skill migration-context

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves the fragmentation of project documentation by identifying and relocating agent-flavored content from standard docs folders into a structured .claude/context/ directory.

Core Features & Use Cases

  • Automated Classification: Scans markdown files to distinguish between agent-specific rules, seed-derived configurations, and human-facing tutorials.
  • Conflict Detection: Prevents accidental overwrites by checking for existing files and reporting potential naming collisions.
  • Use Case: Use this when you want to standardize a project's documentation to align with the three-tier context model, ensuring your AI agents have consistent access to rules and conventions.

Quick Start

Run the migration-context skill to analyze your current docs directory and generate a proposal for moving agent-flavored files to the context folder.

Frequently Asked Questions about migration-context

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

FAQPage Schema
How do I migrate project documentation to an agent-ready context directory?

Classify and migrate project documentation by scanning flat markdown files to identify agent rules, conventions, and seed-derived configurations, generating a proposal to relocate them into a structured context directory without modifying files directly.

What is the three-tier context model for organizing agent-flavored documentation?

The three-tier context model organizes agent-flavored content by distinguishing agent-specific rules, seed-derived configurations, and human-facing tutorials, ensuring AI agents access consistent conventions within a dedicated context directory.

How do I prevent accidental overwrites when moving markdown files to a new context folder?

Prevent accidental overwrites during documentation migration by using built-in conflict detection, which checks for existing files and reports potential naming collisions before proposing any file relocation.

Do I need git and the aitk CLI to classify and propose documentation migrations?

Yes, you need git and the aitk CLI installed to perform automated file discovery and conflict checking, enabling the skill to scan your docs directory and propose moving agent-flavored files without modifying them directly.

Can I automate the separation of agent rules from human-facing tutorials in my docs directory?

Yes, you can automate this separation by scanning markdown files to distinguish between agent-specific rules, seed-derived configurations, and human-facing tutorials, generating a structured migration proposal for the context directory.

What's the best way to standardize project docs for AI agents without losing existing file structure?

Standardize project docs by analyzing your current directory and generating a relocation proposal that identifies agent-flavored content, checking for naming collisions to ensure existing file structures remain intact without direct modifications.