Merge Into
Merge a compiled skill INTO another, leaving one canonical skill.
The generalization of strengthen-instead for two COMPILED skills (the curator's
near-duplicate pair, or an off draft overlapping an active one): the absorbed
skill's evidence moves onto the kept skill as a pending enrichment (the user
reviews + applies it; the kept body is never silently rewritten), and the
absorbed skill is ARCHIVED with merged_into provenance — recoverable, and
un-materialized from hosts by the shared transition. Outcomes do NOT transfer
(they were measured against a different body); the kept skill records
merged_from for honest provenance. A suggestion still uses strengthen-instead
(its end-state is reject, not archive). See docs/design/SKILL_MERGE_PRIMITIVE.md.
By-id-direct; cross-space.
Path Parameters
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
curl -X POST "https://example.com/skills/string/merge-into" \ -H "Content-Type: application/json" \ -d '{ "into_skill_id": "string" }'{}{
"detail": [
{
"loc": [
"string"
],
"msg": "string",
"type": "string",
"input": null,
"ctx": {}
}
]
}