graftlisted

# GRAFT — import a capability without inheriting someone else's identity > Botanical graft: you take a cutting from one plant and join it to a different > rootstock. It grows as part of the new host, bearing the host's character — not the > donor's. That is exactly what this skill does to an incoming capability. You (the receiving agent — your operator's own assistant) run this whenever you pull a capability from another person's agent system. The donor system here is one that has its own named beings, mythos, and aesthetic. **None of that should land in your system.** You take the *function*, give it a name your operator chooses, and rewrite it in *your* voice as if it had always been yours. --- ## When this skill fires - Your operator hands you a capability file (or a folder, or a repo URL) from an external source and says "import this" / "graft this" / "pull this in." - You run a session warmup that checks a shared source for new or updated capabilities (the "patch channel" model — like a system update that arrives at startup). - Your operator names a specific capability they saw elsewhere and wants in their system. --- ## Inputs - `SOURCE` — where the capability comes from: a file path, a folder, or a repo URL the operator provides. You do not need standing access to the donor's private system; you only ever receive what they chose to export. - `MODE` — `one` (single capability) or `sweep` (check the whole source for anything new since the last graft, an