{"id":103332,"plugin_id":"plugin_asdk_app_6aedf6ea2fac819180910f8b98663c77","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-18T06:19:20.897Z","digest":"32b2ae93509da5a053c05069833c0051be19380ab5528e977077a43ad298d28a","against":null,"payload":{"description":"Draft and revise the email copy of Clay sequences (formerly campaigns) using the supplied sequence strategy and context.","included_files":[],"name":"sequences-writing","skill_md_contents":"---\nname: sequences-writing\ndescription: Draft and revise the email copy of Clay sequences (formerly campaigns) using the supplied sequence strategy and context.\n---\n\n# Clay sequence writing\n\nBefore using this skill, read the `clay` entry skill if you haven’t already this session, and follow its access guidance.\n\nIf the `sequences` skill is not already loaded, load it before acting. Use it for sequence discovery, context, target selection, commands, and mutation boundaries. Use this skill for sequence-writing decisions.\n\nUse this skill to draft every step of a sequence or revise sequence copy. Treat the supplied sequence strategy and context as the source of truth.\n\n## Message strategy\n\nEstablish the intended recipient and the situation that makes the message relevant. Connect that situation to a specific problem or opportunity, explain the mechanism and value offered, and make the offer and requested response clear.\n\nGive each email one primary purpose and one response path. When a draft is not working, fix the strategy before polishing individual lines. Omit proof that the supplied context does not support. Make every follow-up add a distinct reason to respond rather than restating an earlier message.\n\n## Copy execution\n\n- Use direct language with concrete actors and outcomes.\n- Give each sentence one purpose.\n- Ground relevance in supplied facts and context rather than generic personalization.\n- Remove filler and redundant restatement.\n- Choose tone and punctuation for the recipient, situation, and established voice.\n- Preserve copy outside the requested revision scope.\n\n## Dynamic copy\n\n- When the language is shared across the audience, use fixed copy.\n- When only one known value changes, use a direct lead-field token.\n- When bounded lexical variation does not depend on lead facts, use spintax.\n- Do not discard useful, supported lead data only because some leads lack it. When worthwhile variation must select, combine, or interpret that data into natural prose, use a short, bounded AI snippet. Do not let missing data produce unsupported copy.\n- When meaningful per-lead variation can improve relevance and impact, use it. Treat its support for deliverability as possible, not guaranteed.\n- Never use an AI snippet as unfinished fixed copy or for generic variation. Never add one only to clear a personalization warning or meet a quota.\n- Give each snippet one role, explicit evidence, and an output bound.\n- Prioritize grounding over variation.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}