askit-migratelisted

# askit-migrate ## Purpose Adopt an existing skills repository into a Standard-conformant plugin. Three modes: `assess` surveys the repo's components and structure, maps them to the Standard's component types, and reports the conformance gap (what is missing for Bronze, then Silver), handling the pre-`library.json` state the conformance core cannot yet grade; `plan` produces an ordered bring-to-conformance roadmap keyed to the tiers and names the `askit-build-*` skill or check that closes each gap; `adopt` performs the first structural step by writing a minimal canonical `library.json` and a root `AGENTS.md` if absent, so the repo becomes gradeable and the rest of the plan can run through `askit-evaluate` and the builders. Authoring depth is in [references/migration-workflow.md](references/migration-workflow.md). ## When to use When adopting a foreign or ad-hoc skills repo, migrating a Claude-only plugin toward cross-agent conformance, or planning a Bronze-to-Silver upgrade path for an existing repository. ## assess mode 1. Discover what exists: skills, commands, subagents, hooks, MCP config, instructions (`AGENTS.md` / `CLAUDE.md`), and any manifest. Map each to a Standard component type (sec 3). 2. Report the gap by tier. The Bronze blockers first (a parseable `library.json`, a root `AGENTS.md`, valid skill frontmatter, name-equals-directory, resolvable reference links), then the Silver blockers (`agent-targets`, the plugin prefix, a `components` index, native manifests)