Migrate

Scan and chunk markdown/txt content for classification into PAI taxonomy destinations.

1|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/davdunc/pai-framework --skill migrate-davdunc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Migrate
Source: https://github.com/davdunc/pai-framework/tree/main/skills/Migrate
Command: npx skills add https://github.com/davdunc/pai-framework --skill migrate-davdunc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrates existing content into the correct PAI destination taxonomy so your TELOS, preferences, and knowledge become usable inside your Claude Code–based assistant.

Core Features & Use Cases

  • Chunked intake + classification: Scans markdown/txt content (or other PAI installs and rules exports), splits it into chunks, and proposes where each chunk belongs in PAI.
  • Provenance-preserving commits: Commits only approved chunks and stamps each commit with source provenance.
  • Confidence-based approval workflow: Uses confidence thresholds to auto-approve high-confidence chunks, route medium items for confirmation, and force careful review for low/UNCLEAR chunks.
  • Destination coverage: Routes content into TELOS (mission/goals/etc.), IDEAL_STATE (private curated dimensions), preferences, identity, and typed Knowledge notes, plus feedback/memory rule patterns.

Quick Start

Run the migrate flow on a directory of notes by asking: migrate my notes from the path /path/to/content.

Frequently Asked Questions about Migrate

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

FAQPage Schema
How do I migrate existing markdown notes into a structured personal AI system?▼

Migrating existing notes into a personal AI system involves scanning and chunking markdown files, then classifying each chunk for routing into structured TELOS, preferences, and knowledge categories. A confidence-scored approval loop ensures correct placement before committing.

What is the best way to import CLAUDE.md and .cursorrules files into a personal AI memory system?▼

Importing CLAUDE.md and .cursorrules files into a personal AI memory system involves scanning the exported instruction and rules content, chunking it, and routing it to the correct destination taxonomy. Provenance tags are stamped on each commit to preserve the source origin.

Can I migrate content from prior PAI USER and MEMORY folders without losing provenance?▼

Migrating content from prior PAI USER, TELOS, and MEMORY folders preserves provenance by stamping each approved commit with source origin data. The migration process scans existing folder structures and routes chunks into the correct destination categories with confidence-scored approvals.

How does chunk classification handle low-confidence or unclear content during migration?▼

Chunk classification handles low-confidence or UNCLEAR content by forcing careful review during the migration approval loop. High-confidence chunks are auto-approved, medium-confidence items are routed for confirmation, and UNCLEAR chunks require manual verification before committing to the destination taxonomy.

Does the personal AI migration workflow require manual approval for every imported chunk?▼

The migration workflow does not require manual approval for every chunk. Confidence thresholds auto-approve high-confidence chunks, route medium-confidence items for confirmation, and force careful review only for low-confidence or UNCLEAR content.

What limitations exist when migrating plain text and markdown files to a PAI taxonomy?▼

Migrating plain text and markdown files to a PAI taxonomy is limited by the confidence-scoring accuracy of chunk classification. UNCLEAR or low-confidence chunks require manual review, and all commits must pass through the provenance-tagged approval loop before routing to TELOS or knowledge outputs.