# Adapt the selected templates

Use the host's actual authoring procedure; this guide supplies template-specific adaptation inputs, not a replacement Skill manager or writing method.

Inspect the recipient's current instructions, configured resources and offered tools before asking factual capability questions. Ask only for choices that change the resulting Skill. For a user-facing role, establish the desired behavioral archetype and translate it into concrete judgment, initiative, disagreement and communication behaviors. Do not insert a preselected personality, biography or claimed identity.

No settled delegation choice → ask whether and which integration the user wants; visible tools/profiles or template names cannot choose for them. Carry an unchanged confirmed choice through adaptation and handoffs; no repeated question. No integration wanted → work inline. Selected integration's actual source/docs and exposed contract define tools, profiles, resource inheritance, isolation, context and completion; retain exact source pointers. Verify desired execution forms against actual selected delegation, coordination and worktree support. Missing chosen capability → name the concrete gap and offer suitable research; no automatic installation or invented runtime. An accepted task carries necessary authorized steps; separately regulated installation/activation still needs its actual grant. Tool names supply neither capabilities nor authorization. No mandatory questionnaire.

Read the chosen example and its `CUSTOMIZE.md` when present. Keep only dependencies included in the recipient's selection or resolve them to an actual existing source. Unselected responsibilities such as Git, credentials and shell policy stay with the recipient's real project/harness owners.

Create the recipient's responsible original at an authorized native destination. Replace generic adaptation choices with confirmed behavior and remove example-only statements such as “not an installed resource” from the resulting active original. Retain such labels in the template source itself. Preserve Writing for Agents' original body and applicable license notices; keep host-specific mechanics in its separate reference.

Check the delivered original and its pointers. Report actual source changes, native discovery/loading and observed behavior separately. Copying, static checks and text simulations do not prove model compliance or live operation.