migrate-nanoclaw Skill
Extracts user customizations from a fork, generates a replayable migration guide, and upgrades to upstream by reapplying customizations on a clean base. Replaces merge-based upgrades with intent-based migration. Published by microsoft in amplifier-app-nanoclaw.
Decision snapshot
Is this a fit?
Documentation, Data analysis, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is migrate-nanoclaw Skill?
Extracts user customizations from a fork, generates a replayable migration guide, and upgrades to upstream by reapplying customizations on a clean base. Replaces merge-based upgrades with intent-based migration. Published by microsoft in amplifier-app-nanoclaw. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Documentation
- Data analysis
- Documentation use cases
- Data analysis use cases
Declared skill metadata
- Source file: .claude/skills/migrate-nanoclaw/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use migrate-nanoclaw Skill
- Use it for documentation.
- Use it for data analysis.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/amplifier-app-nanoclaw
- Skill file: .claude/skills/migrate-nanoclaw/SKILL.md
What it does
Extracts user customizations from a fork, generates a replayable migration guide, and upgrades to upstream by reapplying customizations on a clean base. Replaces merge-based upgrades with intent-based migration.
Skill instructions
Context NanoClaw users fork the repo and customize it — changing config values, editing source files, modifying personas, adding skills. When upstream ships updates or refactors, git merge produces painful conflicts because the same core files were changed on both sides. This skill extracts the user's customizations into a migration guide — capturing both the intent (what they want) and the implementation details (how they did it, with code snippets, API calls, and specific configurations). On upgrade, it checks out clean upstream in a worktree, then reapplies customizations using the guide. No merge conflicts because there's nothing to merge. The migration guide is markdown, not structured data. It needs to capture the full range of what a user might customize, with enough implementation detail that a fresh Claude session can reapply it without having seen the original code. Standard changes (config values, simple logic) can be described briefly. Non-standard changes (specific APIs, c
Verified compatibility and discovery
Frequently asked questions
What is migrate-nanoclaw?
migrate-nanoclaw is a open-source AI agent skill with Copy skill directory. Extracts user customizations from a fork, generates a replayable migration guide, and upgrades to upstream by reapplying customizations on a clean base.
Who is migrate-nanoclaw best for?
migrate-nanoclaw is best for reusing agent instructions, scripts, and references, documentation workflows, data analysis workflows.
How do I install migrate-nanoclaw?
Install or run migrate-nanoclaw using Copy skill directory. Check migrate-nanoclaw for the latest setup command.
Is migrate-nanoclaw actively maintained?
migrate-nanoclaw may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
