Skill Builder Import

Import a hand-written skill as a managed draft (body verbatim, no compile).

The third way a skill is born (beside suggested + authored-from-scratch): it flows through the same review -> activate -> materialize -> evolve loop, gaining verification, self-improvement, cross-tool sync, and versioning. A folder import keeps the whole tree (nested folders + binary assets) verbatim. Returns the created draft, or — when it looks like an existing active skill and force is false — the duplicate it matched, so the user can strengthen that one instead. Looks up by content; space-agnostic (skills list cross-space).

Response Body