{"id":87821,"plugin_id":"plugin_asdk_app_6aed0ba07b0881919d817a94fbe4ff2a","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-09T18:09:09.143Z","digest":"2a4dd3e91c621d0dde9d7be53c146dbbd94143d3827dff77d71257d1c7adc95d","against":null,"payload":{"description":"Write or review copy so it matches an organization's brand voice and guidelines - website copy, articles, headlines, calls to action, meta descriptions, emails and social posts. Use when the user asks to write on-brand content, check whether copy sounds like them, or edit copy against a style guide, and whenever another Agility skill writes customer-facing text.","included_files":[],"name":"brand-voice","skill_md_contents":"---\nname: brand-voice\ndescription: Write or review copy so it matches an organization's brand voice and guidelines - website copy, articles, headlines, calls to action, meta descriptions, emails and social posts. Use when the user asks to write on-brand content, check whether copy sounds like them, or edit copy against a style guide, and whenever another Agility skill writes customer-facing text.\n---\n\n# Brand voice\n\n## Find the guidelines\n\nUse the organization's own guidelines. Look, in this order, for:\n\n1. a guidelines document the user attached or pointed to in this conversation\n2. a brand or style guide stored in their Agility instance (search for \"brand\",\n   \"style guide\" or \"voice\" with `search_instance`)\n3. their existing published copy: read three or four strong pages or articles\n   and describe the voice you see (sentence length, person, formality, words\n   they use and avoid)\n\nIf none of these exist, say so, describe the voice you will use, and ask the\nuser to confirm it before writing much.\n\nRead the guidelines fresh each time. Do not rely on a version from earlier in\nthe conversation if the user may have changed it.\n\n## Write\n\n- Decide the one point the piece must make before drafting.\n- Follow the guidelines' rules on person, tone, vocabulary, capitalization,\n  punctuation and calls to action.\n- Be specific. A line that could appear unchanged on a competitor's site is too\n  generic; rewrite it with something only this organization can say.\n- Do not state facts, numbers, rankings, prices, customer names or quotes that\n  you cannot verify from the user's material. Flag them instead.\n- Do not disparage competitors.\n\n## Check before handing it over\n\nRun the guidelines' own checklist if they have one. Otherwise check:\n\n- Does it follow every explicit rule in the guidelines?\n- Does it lead with what the reader gets?\n- Is every claim supported by the user's material?\n- Are headlines and calls to action consistent with the rest of the site?\n\n## Report like an editor\n\nWhen reviewing someone's copy, start with what works, then what to change and\nwhy, quoting the guideline that applies. Criticize the copy, not the writer.\nGive a revised version, and list anything you flagged for the user to verify.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}