agentleFS
LedgerHQLedgerHQ/ledger-live/.agents/skills/docs-migrate/SKILL.md

docs-migrate

Skill627 starsChanged 8 days agoMITView on GitHub

Migrate docs into our target structure. Use when asked to migrate or clean up existing docs – agentic and otherwise.

The file

Files
SKILL.md

Migrate Docs

The idea is to take content from the scattered sources, decide what to keep, discard or refine and then, create or update docs without duplication, in line with our target structure.

Process

  1. Identify the source, one or a small set of files or pages
  2. Identify the target: the new home(s) for the content
  3. Identify duplication between the source and target
  4. Decide what to discard/keep and what to refine
  5. (Write a plan to) update or create the target, and delete the source

Guidelines

  • The content is what we care about
  • The format should follow our target structure
  • Use /docs-update-or-create

Output

Either the plan or (if instructed to) do the migration from step 5.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.