Migrate

Classifies external content chunks against the DevOS taxonomy and commits them with provenance.

Updated Sep 3, 2026
One-click install
npx skills add https://github.com/ruban-s/DevOS --skill migrate-ruban-s
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Migrate
Source: https://github.com/ruban-s/DevOS/tree/main/skills/Migrate
Command: npx skills add https://github.com/ruban-s/DevOS --skill migrate-ruban-s

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Adopting a structured personal knowledge system means inheriting years of accumulated notes, rule files, and vault exports that were never shaped to its taxonomy. Manually sorting hundreds of chunks into the right destinations is tedious enough that the old material usually sits unused. ## Core Features & Use Cases - Multi-source intake: Accepts .md/.txt files, directories, stdin, other DevOS installs, CLAUDE.md, Cursor rules, OpenAI Custom Instructions, and Obsidian/Notion/Apple Notes exports. - Confidence-based routing: MigrateScan classifies each chunk into TELOS, IDEAL_STATE, preference, identity, or knowledge targets; confidence ≥70% auto-approves, 40-70% asks for confirmation, and <40% requires a walk-through. - Provenance-stamped commits: MigrateApprove commits approved chunks with source file, section, and timestamp metadata, with fast-path, per-category, and per-chunk review modes. - Use Case: Point it at an old CLAUDE.md or Obsidian vault and get a routing table showing how many chunks land in each destination, then bulk-approve the confident ones and walk through the unclear remainder. ## Quick Start Ask the agent to run /migrate on a file or directory such as an old CLAUDE.md or notes export and approve the proposed routing table.

Frequently Asked Questions about Migrate

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

FAQPage Schema
How do I import my old notes into DevOS?▼

Run /migrate with a file path, directory, or pasted content. MigrateScan classifies every chunk against the DevOS taxonomy and presents a routing table, then MigrateApprove commits approved chunks with provenance metadata attached.

What file formats and sources does content migration support?▼

Supported sources include .md, .markdown, and .txt files, directory recursion, stdin, other DevOS TELOS or KNOWLEDGE directories, CLAUDE.md, .cursorrules, OpenAI Custom Instructions, and Obsidian, Notion, or Apple Notes exports.

How does confidence-based approval work during migration?▼

Chunks scoring 70% or higher are auto-approve eligible, 40-70% are shown for confirmation, and below 40% require a line-by-line walk-through. UNCLEAR chunks can never be bulk-approved and always need explicit routing.

Can I migrate Cursor rules or CLAUDE.md into DevOS?▼

Yes, but AI collaboration rules are always walked through one by one and routed to a constitutional surface such as CLAUDE.md operational rules, a hook, settings.json, or a skill's Gotchas section, never to harness memory feedback files.

Why does everything classify as UNCLEAR during migration?▼

The source likely lacks recognizable DevOS-taxonomy patterns, such as code comments, logs, or raw data. Pre-filter non-prose chunks before scanning, or add the content manually via /Telos or as general Knowledge notes.

Does migration overwrite or duplicate existing content?▼

No. If the same content already exists in the target via substring match, it is flagged and you are asked before appending. Running with --dry-run first previews all commits before anything is written.