[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718E1AEANRF6MP2ZA5H0TN3":3,"skill-same:01M718E1AEANRF6MP2ZA5H0TN3":80},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":31,"publishedAt":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":6,"ownerHtmlUrl":63,"ownerBlogUrl":64,"ownerDescription":6,"updatedAt":65,"install":66,"resources":79},"01M718E1AEANRF6MP2ZA5H0TN3","brand-review",null,"Review content against your brand voice, style guide, and messaging pillars, flagging deviations by severity with specific before\u002Fafter fixes. Use when checking a draft before it ships, when auditing copy for voice consistency and terminology, or when screening for unsubstantiated claims, missing disclaimers, and other legal flags.","anthropics\u002Fknowledge-work-plugins","anthropics","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F76263028?v=4","01M697XGDPXJAVQ8391V2BCYTE","Anthropic","01M7188MPC48111TN566QNQE3X",35660,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fmarketing\u002Fskills\u002Fbrand-review\u002FSKILL.md",[18,23,28],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",{"categoryNo":29,"categoryName":30,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000037","律师与法务",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"brand","brand review","review","style","terminology","with","draft","style guide","use","missing","for","fixes","severity","consistency","guide","screening","flags","claims","when","messaging","2026-11-10 10:12:30",false,"---\nname: brand-review\ndescription: Review content against your brand voice, style guide, and messaging pillars, flagging deviations by severity with specific before\u002Fafter fixes. Use when checking a draft before it ships, when auditing copy for voice consistency and terminology, or when screening for unsubstantiated claims, missing disclaimers, and other legal flags.\nargument-hint: \"\u003Ccontent to review>\"\n---\n\n# Brand Review\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md).\n\nReview marketing content against brand voice, style guidelines, and messaging standards. Flag deviations and provide specific improvement suggestions.\n\n## Trigger\n\nUser runs `\u002Fbrand-review` or asks to review, check, or audit content against brand guidelines.\n\n## Inputs\n\n1. **Content to review** — accept content in any of these forms:\n   - Pasted directly into the conversation\n   - A file path or ~~knowledge base reference (e.g. Notion page, shared doc)\n   - A URL to a published page\n   - Multiple pieces for batch review\n\n2. **Brand guidelines source** (determined automatically):\n   - If a brand style guide is configured in local settings, use it automatically\n   - If not configured, ask: \"Do you have a brand style guide or voice guidelines I should review against? You can paste them, share a file, or describe your brand voice. Otherwise, I'll do a general review for clarity, consistency, and professionalism.\"\n\n## Review Process\n\n### With Brand Guidelines Configured\n\nEvaluate the content against each of these dimensions:\n\n#### Voice and Tone\n- Does the content match the defined brand voice attributes?\n- Is the tone appropriate for the content type and audience?\n- Are there shifts in voice that feel inconsistent?\n- Flag specific sentences or phrases that deviate with an explanation of why\n\n#### Terminology and Language\n- Are preferred brand terms used correctly?\n- Are any \"avoid\" terms or phrases present?\n- Is jargon level appropriate for the target audience?\n- Are product names, feature names, and branded terms used correctly (capitalization, formatting)?\n\n#### Messaging Pillars\n- Does the content align with defined messaging pillars or value propositions?\n- Are claims consistent with approved messaging?\n- Is the content reinforcing or contradicting brand positioning?\n\n#### Style Guide Compliance\n- Grammar and punctuation per style guide (e.g., Oxford comma, title case vs. sentence case)\n- Formatting conventions (headers, lists, emphasis)\n- Number formatting, date formatting\n- Acronym usage (defined on first use?)\n\n### Without Brand Guidelines (Generic Review)\n\nEvaluate the content for:\n\n#### Clarity\n- Is the main message clear within the first paragraph?\n- Are sentences concise and easy to understand?\n- Is the structure logical and easy to follow?\n- Are there ambiguous statements or unclear references?\n\n#### Consistency\n- Is the tone consistent throughout?\n- Are terms used consistently (no switching between synonyms for the same concept)?\n- Is formatting consistent (headers, lists, capitalization)?\n\n#### Professionalism\n- Is the content free of typos, grammatical errors, and awkward phrasing?\n- Is the tone appropriate for the intended audience?\n- Are claims supported or substantiated?\n\n### Legal and Compliance Flags (Always Checked)\n\nRegardless of whether brand guidelines are configured, flag:\n- **Unsubstantiated claims** — superlatives (\"best\", \"fastest\", \"only\") without evidence or qualification\n- **Missing disclaimers** — financial claims, health claims, or guarantees that may need legal disclaimers\n- **Comparative claims** — comparisons to competitors that could be challenged\n- **Regulatory language** — content that may need compliance review (financial services, healthcare, etc.)\n- **Testimonial issues** — quotes or endorsements without attribution or disclosure\n- **Copyright concerns** — content that appears to be closely paraphrased from other sources\n\n## Brand Voice Reference\n\nUse these frameworks to evaluate content against brand standards or to help the user document their brand voice.\n\n### Brand Voice Documentation Framework\n\nA complete brand voice document should cover these areas:\n\n1. **Brand Personality** — Define the brand as if it were a person. Example: \"If our brand were a person, they would be a knowledgeable colleague who explains complex things simply, celebrates your wins genuinely, and never talks down to you.\"\n2. **Voice Attributes** — 3-5 attributes that define how the brand communicates, each defined with what it means in practice, what it does NOT mean (to prevent misinterpretation), and an example.\n3. **Audience Awareness** — Who the brand is speaking to (primary and secondary), what they care about, their level of expertise, and how they expect to be addressed.\n4. **Core Messaging Pillars** — 3-5 key themes the brand consistently communicates, the hierarchy of these messages, and how each pillar connects to audience needs.\n5. **Tone Spectrum** — How the voice adapts across contexts while remaining recognizably the same brand.\n6. **Style Rules** — Specific grammar, formatting, and language rules.\n7. **Terminology** — Preferred and avoided terms.\n\n### Voice Attribute Spectrums\n\nWhen defining or evaluating brand voice, position attributes on a spectrum:\n\n| Spectrum | One End | Other End |\n|----------|---------|-----------|\n| Formality | Formal, institutional | Casual, conversational |\n| Authority | Expert, authoritative | Peer-level, collaborative |\n| Emotion | Warm, empathetic | Direct, matter-of-fact |\n| Complexity | Technical, precise | Simple, accessible |\n| Energy | Bold, energetic | Calm, measured |\n| Humor | Playful, witty | Serious, earnest |\n| Innovation | Cutting-edge, forward-looking | Established, proven |\n\nFor each chosen attribute, document it in this format:\n\n**[Attribute name]**\n- **We are**: [what this means in practice]\n- **We are not**: [common misinterpretation to avoid]\n- **This sounds like**: [example sentence demonstrating the attribute]\n- **This does NOT sound like**: [example sentence violating the attribute]\n\nExample:\n\n**Approachable**\n- **We are**: friendly, clear, jargon-free, welcoming to beginners and experts alike\n- **We are not**: dumbed-down, overly casual, or lacking substance\n- **This sounds like**: \"Here's how to get started — it takes about five minutes.\"\n- **This does NOT sound like**: \"Yo! This is super easy, even a noob can do it lol.\"\n\n### Tone Adaptation Across Channels and Contexts\n\nThe brand voice stays consistent, but tone adapts to context. Tone is the emotional inflection applied to the voice.\n\n#### Tone by Channel\n\n| Channel | Tone Adaptation | Example |\n|---------|----------------|---------|\n| Blog | Informative, conversational, educational | \"Let's walk through how this works and why it matters for your team.\" |\n| Social media (LinkedIn) | Professional, thought-provoking, concise | \"Three things we learned from running 50 campaigns this quarter.\" |\n| Social media (Twitter\u002FX) | Punchy, direct, sometimes witty | \"Your landing page has 3 seconds. Make them count.\" |\n| Email marketing | Personal, helpful, action-oriented | \"We put together something we think you'll find useful.\" |\n| Sales collateral | Confident, benefit-driven, specific | \"Teams using our platform reduce reporting time by 40%.\" |\n| Support\u002FHelp docs | Clear, patient, step-by-step | \"If you see this error, here's how to fix it.\" |\n| Press release | Formal, factual, newsworthy | \"The company today announced the launch of...\" |\n| Error messages | Empathetic, helpful, blame-free | \"Something went wrong on our end. We're looking into it.\" |\n\n#### Tone by Situation\n\n| Situation | Tone Adaptation |\n|-----------|----------------|\n| Product launch | Excited, confident, forward-looking |\n| Incident or outage | Transparent, empathetic, accountable |\n| Customer success story | Celebratory, specific, crediting the customer |\n| Thought leadership | Authoritative, nuanced, evidence-based |\n| Onboarding | Welcoming, encouraging, clear |\n| Bad news (price increase, deprecation) | Honest, respectful, solution-oriented |\n| Competitive comparison | Confident but fair, fact-based, not disparaging |\n\n#### Tone Adaptation Rule\nThe voice attributes remain fixed. Tone dials them up or down based on context. For example, if a brand is \"bold and warm\":\n- In a product launch, dial up boldness\n- In an incident response, dial up warmth\n- Neither attribute disappears; the balance shifts\n\n### Style Guide Enforcement\n\n#### Grammar and Mechanics\nDocument and enforce these choices consistently:\n\n| Rule | Options | Example |\n|------|---------|---------|\n| Oxford comma | Yes \u002F No | \"fast, reliable, and secure\" vs. \"fast, reliable and secure\" |\n| Sentence case vs. title case (headings) | Sentence \u002F Title | \"How to get started\" vs. \"How to Get Started\" |\n| Contractions | Use \u002F Avoid | \"we're\" vs. \"we are\" |\n| Em dash spacing | No spaces \u002F Spaces | \"this—and more\" vs. \"this — and more\" |\n| Numbers | Spell out 1-9, numerals 10+ \u002F Always numerals | \"five features\" vs. \"5 features\" |\n| Percent | % \u002F percent | \"50%\" vs. \"50 percent\" |\n| Date format | Month DD, YYYY \u002F DD\u002FMM\u002FYYYY \u002F etc. | \"January 15, 2025\" |\n| Time format | 12-hour \u002F 24-hour | \"3:00 PM\" vs. \"15:00\" |\n| Lists | Periods \u002F No periods on fragments | \"Set up your account.\" vs. \"Set up your account\" |\n\n#### Formatting Conventions\n- Heading hierarchy (when to use H1, H2, H3)\n- Bold and italic usage (bold for emphasis, italic for titles\u002Fterms)\n- Link text (descriptive vs. \"click here\" — always descriptive)\n- Image alt text requirements\n- Code formatting (for technical brands)\n- Callout or highlight box usage\n\n#### Punctuation and Emphasis\n- Exclamation mark policy (limited use, never more than one)\n- Ellipsis usage (avoid in most professional contexts)\n- ALL CAPS policy (avoid; use bold for emphasis instead)\n- Emoji usage by channel (professional channels: minimal or none; social: where appropriate)\n\n### Terminology Management\n\n#### Preferred Terms\n\nMaintain a list of preferred terms and their incorrect alternatives:\n\n| Use This | Not This | Notes |\n|----------|----------|-------|\n| sign up (verb) | signup (verb) | \"signup\" is the noun form |\n| log in (verb) | login (verb) | \"login\" is the noun\u002Fadjective form |\n| set up (verb) | setup (verb) | \"setup\" is the noun\u002Fadjective form |\n| email | e-mail | No hyphen |\n| website | web site | One word |\n| data is (singular) | data are | Unless the publication requires plural |\n\n#### Product and Feature Names\n- Official capitalization for product names\n- When to use the full product name vs. shorthand\n- Whether to use \"the\" before product names\n- How to handle versioning in copy\n- Trademark and registration symbols (when required and when to omit)\n\n#### Inclusive Language\n- Use gender-neutral language (they\u002Fthem for unknown individuals)\n- Avoid ableist language (\"crazy\", \"blind spot\", \"lame\")\n- Use person-first language where appropriate\n- Avoid culturally specific idioms that may not translate\n- Use \"simple\" or \"straightforward\" instead of \"easy\" (what is easy varies by person)\n\n#### Industry Jargon Management\n- Define which technical terms the audience understands without explanation\n- List jargon that should always be defined or replaced with plain language\n- Specify which acronyms need to be spelled out on first use\n- Audience-specific glossary for terms that mean different things to different readers\n\n#### Competitor and Category Terms\n- How to refer to your product category (use your preferred framing)\n- How to refer to competitors (by name or generically)\n- Terms competitors have coined that you should avoid (to prevent reinforcing their positioning)\n- Your preferred differentiation language\n\n## Output Format\n\nPresent the review as:\n\n### Summary\n- Overall assessment: how well the content aligns with brand standards (or general quality)\n- 1-2 sentence summary of the biggest strengths\n- 1-2 sentence summary of the most important improvements\n\n### Detailed Findings\n\nFor each issue found, provide:\n\n| Issue | Location | Severity | Suggestion |\n|-------|----------|----------|------------|\n\nWhere severity is:\n- **High** — contradicts brand voice, contains compliance risk, or significantly undermines messaging\n- **Medium** — inconsistent with guidelines but not damaging\n- **Low** — minor style or preference issue\n\n### Revised Sections\n\nFor the top 3-5 highest-severity issues, provide a before\u002Fafter showing the original text and a suggested revision.\n\n### Legal\u002FCompliance Flags\n\nList any legal or compliance concerns separately with recommended actions.\n\n## After Review\n\nAsk: \"Would you like me to:\n- Revise the full content with these suggestions applied?\n- Focus on fixing just the high-severity issues?\n- Review additional content against the same guidelines?\n- Help you document your brand voice for future reviews?\"\n","# Brand Review\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md).\n\nReview marketing content against brand voice, style guidelines, and messaging standards. Flag deviations and provide specific improvement suggestions.\n\n## Trigger\n\nUser runs `\u002Fbrand-review` or asks to review, check, or audit content against brand guidelines.\n\n## Inputs\n\n1. **Content to review** — accept content in any of these forms:\n   - Pasted directly into the conversation\n   - A file path or ~~knowledge base reference (e.g. Notion page, shared doc)\n   - A URL to a published page\n   - Multiple pieces for batch review\n\n2. **Brand guidelines source** (determined automatically):\n   - If a brand style guide is configured in local settings, use it automatically\n   - If not configured, ask: \"Do you have a brand style guide or voice guidelines I should review against? You can paste them, share a file, or describe your brand voice. Otherwise, I'll do a general review for clarity, consistency, and professionalism.\"\n\n## Review Process\n\n### With Brand Guidelines Configured\n\nEvaluate the content against each of these dimensions:\n\n#### Voice and Tone\n- Does the content match the defined brand voice attributes?\n- Is the tone appropriate for the content type and audience?\n- Are there shifts in voice that feel inconsistent?\n- Flag specific sentences or phrases that deviate with an explanation of why\n\n#### Terminology and Language\n- Are preferred brand terms used correctly?\n- Are any \"avoid\" terms or phrases present?\n- Is jargon level appropriate for the target audience?\n- Are product names, feature names, and branded terms used correctly (capitalization, formatting)?\n\n#### Messaging Pillars\n- Does the content align with defined messaging pillars or value propositions?\n- Are claims consistent with approved messaging?\n- Is the content reinforcing or contradicting brand positioning?\n\n#### Style Guide Compliance\n- Grammar and punctuation per style guide (e.g., Oxford comma, title case vs. sentence case)\n- Formatting conventions (headers, lists, emphasis)\n- Number formatting, date formatting\n- Acronym usage (defined on first use?)\n\n### Without Brand Guidelines (Generic Review)\n\nEvaluate the content for:\n\n#### Clarity\n- Is the main message clear within the first paragraph?\n- Are sentences concise and easy to understand?\n- Is the structure logical and easy to follow?\n- Are there ambiguous statements or unclear references?\n\n#### Consistency\n- Is the tone consistent throughout?\n- Are terms used consistently (no switching between synonyms for the same concept)?\n- Is formatting consistent (headers, lists, capitalization)?\n\n#### Professionalism\n- Is the content free of typos, grammatical errors, and awkward phrasing?\n- Is the tone appropriate for the intended audience?\n- Are claims supported or substantiated?\n\n### Legal and Compliance Flags (Always Checked)\n\nRegardless of whether brand guidelines are configured, flag:\n- **Unsubstantiated claims** — superlatives (\"best\", \"fastest\", \"only\") without evidence or qualification\n- **Missing disclaimers** — financial claims, health claims, or guarantees that may need legal disclaimers\n- **Comparative claims** — comparisons to competitors that could be challenged\n- **Regulatory language** — content that may need compliance review (financial services, healthcare, etc.)\n- **Testimonial issues** — quotes or endorsements without attribution or disclosure\n- **Copyright concerns** — content that appears to be closely paraphrased from other sources\n\n## Brand Voice Reference\n\nUse these frameworks to evaluate content against brand standards or to help the user document their brand voice.\n\n### Brand Voice Documentation Framework\n\nA complete brand voice document should cover these areas:\n\n1. **Brand Personality** — Define the brand as if it were a person. Example: \"If our brand were a person, they would be a knowledgeable colleague who explains complex things simply, celebrates your wins genuinely, and never talks down to you.\"\n2. **Voice Attributes** — 3-5 attributes that define how the brand communicates, each defined with what it means in practice, what it does NOT mean (to prevent misinterpretation), and an example.\n3. **Audience Awareness** — Who the brand is speaking to (primary and secondary), what they care about, their level of expertise, and how they expect to be addressed.\n4. **Core Messaging Pillars** — 3-5 key themes the brand consistently communicates, the hierarchy of these messages, and how each pillar connects to audience needs.\n5. **Tone Spectrum** — How the voice adapts across contexts while remaining recognizably the same brand.\n6. **Style Rules** — Specific grammar, formatting, and language rules.\n7. **Terminology** — Preferred and avoided terms.\n\n### Voice Attribute Spectrums\n\nWhen defining or evaluating brand voice, position attributes on a spectrum:\n\n| Spectrum | One End | Other End |\n|----------|---------|-----------|\n| Formality | Formal, institutional | Casual, conversational |\n| Authority | Expert, authoritative | Peer-level, collaborative |\n| Emotion | Warm, empathetic | Direct, matter-of-fact |\n| Complexity | Technical, precise | Simple, accessible |\n| Energy | Bold, energetic | Calm, measured |\n| Humor | Playful, witty | Serious, earnest |\n| Innovation | Cutting-edge, forward-looking | Established, proven |\n\nFor each chosen attribute, document it in this format:\n\n**[Attribute name]**\n- **We are**: [what this means in practice]\n- **We are not**: [common misinterpretation to avoid]\n- **This sounds like**: [example sentence demonstrating the attribute]\n- **This does NOT sound like**: [example sentence violating the attribute]\n\nExample:\n\n**Approachable**\n- **We are**: friendly, clear, jargon-free, welcoming to beginners and experts alike\n- **We are not**: dumbed-down, overly casual, or lacking substance\n- **This sounds like**: \"Here's how to get started — it takes about five minutes.\"\n- **This does NOT sound like**: \"Yo! This is super easy, even a noob can do it lol.\"\n\n### Tone Adaptation Across Channels and Contexts\n\nThe brand voice stays consistent, but tone adapts to context. Tone is the emotional inflection applied to the voice.\n\n#### Tone by Channel\n\n| Channel | Tone Adaptation | Example |\n|---------|----------------|---------|\n| Blog | Informative, conversational, educational | \"Let's walk through how this works and why it matters for your team.\" |\n| Social media (LinkedIn) | Professional, thought-provoking, concise | \"Three things we learned from running 50 campaigns this quarter.\" |\n| Social media (Twitter\u002FX) | Punchy, direct, sometimes witty | \"Your landing page has 3 seconds. Make them count.\" |\n| Email marketing | Personal, helpful, action-oriented | \"We put together something we think you'll find useful.\" |\n| Sales collateral | Confident, benefit-driven, specific | \"Teams using our platform reduce reporting time by 40%.\" |\n| Support\u002FHelp docs | Clear, patient, step-by-step | \"If you see this error, here's how to fix it.\" |\n| Press release | Formal, factual, newsworthy | \"The company today announced the launch of...\" |\n| Error messages | Empathetic, helpful, blame-free | \"Something went wrong on our end. We're looking into it.\" |\n\n#### Tone by Situation\n\n| Situation | Tone Adaptation |\n|-----------|----------------|\n| Product launch | Excited, confident, forward-looking |\n| Incident or outage | Transparent, empathetic, accountable |\n| Customer success story | Celebratory, specific, crediting the customer |\n| Thought leadership | Authoritative, nuanced, evidence-based |\n| Onboarding | Welcoming, encouraging, clear |\n| Bad news (price increase, deprecation) | Honest, respectful, solution-oriented |\n| Competitive comparison | Confident but fair, fact-based, not disparaging |\n\n#### Tone Adaptation Rule\nThe voice attributes remain fixed. Tone dials them up or down based on context. For example, if a brand is \"bold and warm\":\n- In a product launch, dial up boldness\n- In an incident response, dial up warmth\n- Neither attribute disappears; the balance shifts\n\n### Style Guide Enforcement\n\n#### Grammar and Mechanics\nDocument and enforce these choices consistently:\n\n| Rule | Options | Example |\n|------|---------|---------|\n| Oxford comma | Yes \u002F No | \"fast, reliable, and secure\" vs. \"fast, reliable and secure\" |\n| Sentence case vs. title case (headings) | Sentence \u002F Title | \"How to get started\" vs. \"How to Get Started\" |\n| Contractions | Use \u002F Avoid | \"we're\" vs. \"we are\" |\n| Em dash spacing | No spaces \u002F Spaces | \"this—and more\" vs. \"this — and more\" |\n| Numbers | Spell out 1-9, numerals 10+ \u002F Always numerals | \"five features\" vs. \"5 features\" |\n| Percent | % \u002F percent | \"50%\" vs. \"50 percent\" |\n| Date format | Month DD, YYYY \u002F DD\u002FMM\u002FYYYY \u002F etc. | \"January 15, 2025\" |\n| Time format | 12-hour \u002F 24-hour | \"3:00 PM\" vs. \"15:00\" |\n| Lists | Periods \u002F No periods on fragments | \"Set up your account.\" vs. \"Set up your account\" |\n\n#### Formatting Conventions\n- Heading hierarchy (when to use H1, H2, H3)\n- Bold and italic usage (bold for emphasis, italic for titles\u002Fterms)\n- Link text (descriptive vs. \"click here\" — always descriptive)\n- Image alt text requirements\n- Code formatting (for technical brands)\n- Callout or highlight box usage\n\n#### Punctuation and Emphasis\n- Exclamation mark policy (limited use, never more than one)\n- Ellipsis usage (avoid in most professional contexts)\n- ALL CAPS policy (avoid; use bold for emphasis instead)\n- Emoji usage by channel (professional channels: minimal or none; social: where appropriate)\n\n### Terminology Management\n\n#### Preferred Terms\n\nMaintain a list of preferred terms and their incorrect alternatives:\n\n| Use This | Not This | Notes |\n|----------|----------|-------|\n| sign up (verb) | signup (verb) | \"signup\" is the noun form |\n| log in (verb) | login (verb) | \"login\" is the noun\u002Fadjective form |\n| set up (verb) | setup (verb) | \"setup\" is the noun\u002Fadjective form |\n| email | e-mail | No hyphen |\n| website | web site | One word |\n| data is (singular) | data are | Unless the publication requires plural |\n\n#### Product and Feature Names\n- Official capitalization for product names\n- When to use the full product name vs. shorthand\n- Whether to use \"the\" before product names\n- How to handle versioning in copy\n- Trademark and registration symbols (when required and when to omit)\n\n#### Inclusive Language\n- Use gender-neutral language (they\u002Fthem for unknown individuals)\n- Avoid ableist language (\"crazy\", \"blind spot\", \"lame\")\n- Use person-first language where appropriate\n- Avoid culturally specific idioms that may not translate\n- Use \"simple\" or \"straightforward\" instead of \"easy\" (what is easy varies by person)\n\n#### Industry Jargon Management\n- Define which technical terms the audience understands without explanation\n- List jargon that should always be defined or replaced with plain language\n- Specify which acronyms need to be spelled out on first use\n- Audience-specific glossary for terms that mean different things to different readers\n\n#### Competitor and Category Terms\n- How to refer to your product category (use your preferred framing)\n- How to refer to competitors (by name or generically)\n- Terms competitors have coined that you should avoid (to prevent reinforcing their positioning)\n- Your preferred differentiation language\n\n## Output Format\n\nPresent the review as:\n\n### Summary\n- Overall assessment: how well the content aligns with brand standards (or general quality)\n- 1-2 sentence summary of the biggest strengths\n- 1-2 sentence summary of the most important improvements\n\n### Detailed Findings\n\nFor each issue found, provide:\n\n| Issue | Location | Severity | Suggestion |\n|-------|----------|----------|------------|\n\nWhere severity is:\n- **High** — contradicts brand voice, contains compliance risk, or significantly undermines messaging\n- **Medium** — inconsistent with guidelines but not damaging\n- **Low** — minor style or preference issue\n\n### Revised Sections\n\nFor the top 3-5 highest-severity issues, provide a before\u002Fafter showing the original text and a suggested revision.\n\n### Legal\u002FCompliance Flags\n\nList any legal or compliance concerns separately with recommended actions.\n\n## After Review\n\nAsk: \"Would you like me to:\n- Revise the full content with these suggestions applied?\n- Focus on fixing just the high-severity issues?\n- Review additional content against the same guidelines?\n- Help you document your brand voice for future reviews?\"\n",{"name":5,"description":7,"argument-hint":57},"\u003Ccontent to review>","main","e605d8ddbfb688da57dfaaceebd93f12a64ef1d3","marketing\u002Fskills\u002Fbrand-review",3944,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins","https:\u002F\u002Fgithub.com\u002Fanthropics","https:\u002F\u002Fanthropic.com","2026-11-14 06:21:52",{"source":8,"skillName":5,"commands":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add anthropics\u002Fknowledge-work-plugins --skill brand-review",{"tool":72,"command":73},"bunx","bunx skills add anthropics\u002Fknowledge-work-plugins --skill brand-review",{"tool":75,"command":76},"pnpm","pnpm dlx skills add anthropics\u002Fknowledge-work-plugins --skill brand-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fmarketing\u002Fskills\u002Fbrand-review\u002FSKILL.md",true,[],[81,107,131,153,180,206],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":52},"01M718Y97HCGW12Q53PSJDY03W","ticket-deflector","Reads a forwarded customer email or ticket, pulls order and refund status from a payments connector (PayPal, Square, or Stripe) or Shopify, account history from the CRM, and open tickets from a support desk (Zoho Desk), drafts a tone-matched reply in the owner's writing voice, and can issue a refund through the payments connector with explicit owner approval. With Shopify connected it also runs a proactive order-triage mode that surfaces orders needing attention — unfulfilled past the promised window, payment problems, pending refunds, stuck shipments — and drafts the next action for each before the customer has to ask. Use when the user says \"draft a response,\" \"answer this customer,\" \"where's my order,\" \"I want a refund,\" \"check my orders,\" or \"anything about to blow up.\"","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Fticket-deflector\u002FSKILL.md",[],[88,89,90,91,92,93,94,50,95,96,97,98,99,100,101,102,103,104,105,106],"ticket","ticket deflector","mode","up","payments","open","writing","workflow","ask","Connector","text","mail","window","next","customer","support","crm","past","read",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":52},"01M718Y55HFAN5705ME5VEDZ9K","tax-season-organizer","Prepares tax-season materials for the owner's accountant, not tax advice. US federal tax; a non-US business gets its closed-books packet instead. Two modes: (1) quarterly estimated tax from YTD net income in the ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books); (2) year-end 1099 prep, scanning the ledger, PayPal, and Stripe for contractors paid over USD 600 into a 1099-NEC list with missing W-9 flags.\nAny tax request routes first to \u002Ftax-prep, which confirms the books are closed and reconciled before running this skill. Use this skill directly only when the owner says the period's books are already closed: \"books are closed, now do the 1099s,\" \"run the quarterly estimate off the closed numbers,\" or \"just the contractor W-9 list.\"","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Ftax-season-organizer\u002FSKILL.md",[],[114,115,116,117,118,119,120,121,122,123,50,124,125,126,127,128,106,48,129,130],"tax season organizer","tax","us federal","which","netsuite","paid","end","usd","only","now","books","xero","scanning","run","request","list","stripe",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":52},"01M718Y13VVPHDD9NTDBVFJ2AZ","tax-prep","Prepares tax materials as a two-link chain — month-end-prep confirms the books are closed and reconciled first, then tax-season-organizer calculates the quarterly estimated payment or builds the year-end 1099-NEC list and accountant packet from those closed numbers. Requires a ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books); uses Gusto, PayPal, and Stripe when connected, else CSV upload. US federal tax math; a non-US business gets the closed-books packet. Prep material for a CPA, never tax advice, nothing filed. Trigger on \"quarterly taxes,\" \"estimated tax payment,\" \"how much should I set aside,\" \"1099s,\" \"1099-NEC,\" \"W-9s,\" \"year-end tax prep,\" \"get my books ready for my accountant,\" any phrasing that suggests a tax deadline is coming, or a question about net profit or YTD income that sounds like worry about a tax bill. An owner who says the period's books are already closed routes to tax-season-organizer directly.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Ftax-prep\u002FSKILL.md",[],[138,115,139,140,116,141,142,118,143,144,145,146,147,42,148,120,149,150,151,152],"tax prep","prep","SET","as","ready","never","zoho books","get","chain","profit","trigger","material","question","paypal","business",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":162,"publishedAt":52},"01M718XWTWQZ01GYSG9T8RW8TW","speed-to-lead","Makes sure no inbound lead goes unanswered. Watches web forms, the shared inbox, and the CRM for new inquiries, qualifies each one against the owner's criteria, drafts a reply in the owner's voice with real meeting times for the owner to approve and send, routes anything hot to a human right away, and logs the whole thing to the CRM. Never sends on its own. Built to run on a schedule so overnight inquiries are drafted and sorted by morning, and works from forwarded or pasted inquiries when no connector is available. Use this whenever the owner is worried about inbound leads or response time — including phrasings like \"leads are going cold,\" \"did anyone answer that inquiry,\" \"I keep missing form submissions,\" \"nothing falls through the cracks,\" \"handle my inbound,\" \"respond to this lead,\" or \"we lose people because nobody gets back fast enough.\" Reach for it for a single unanswered inquiry as readily as for a standing setup.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Fspeed-to-lead\u002FSKILL.md",[159],{"categoryNo":160,"categoryName":161,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000034","行政与办公人员",[163,164,165,166,167,168,143,169,170,171,172,173,174,175,50,176,177,97,178,179],"speed to lead","lead","speed","shared","back","cold","time","inbox","send","respond","new","web forms","people","schedule","logs","sure","human",{"skillNo":181,"name":182,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":184,"categories":185,"keywords":189,"publishedAt":52},"01M718XQYMN1KY3TPS33967FK0","social-content-engine","Runs the owner's content operation as a standing thing rather than a one-off: keeps a rolling posting calendar, learns the owner's voice, generates on-brand Canva graphics, writes captions that sound like them, repurposes one asset into every channel format, and stages posts for approval instead of publishing on its own. Pulls product photos and prices from Shopify when connected; with no connectors, drafts the calendar and asset briefs for manual posting. Use this whenever the owner talks about posting, content, or social — including \"I need to post more,\" \"we've gone quiet on Instagram,\" \"what should we post this month,\" \"make the content,\" \"give me a month of posts,\" \"write this in my voice,\" \"repurpose this,\" or \"set up our content calendar.\" Reach for it for a single post as readily as for a full quarter. One handoff: a finished, approved campaign brief goes to canva-creator; this skill owns the standing operation.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Fsocial-content-engine\u002FSKILL.md",[186],{"categoryNo":187,"categoryName":188,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者",[190,191,192,193,194,195,140,196,197,198,199,91,200,50,201,202,203,106,204,205],"social","social content engine","engine","content engine","social content","content","brief","posts","Captions","prices","campaign","me","product","calendar","write","drafts",{"skillNo":207,"name":208,"nameZh":6,"description":209,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":210,"categories":211,"keywords":212,"publishedAt":52},"01M718XMPJVH0EVRVP998BVZPC","smb-router","The front door to the Small Business plugin. Listens to what the owner needs right now — vague or specific — and routes them to the best skill or slash command for the moment. Also serves as a guide: explains what's available, suggests what to try next, and adapts recommendations based on stored business context. Trigger whenever the owner asks \"what can you do,\" \"help me with my business,\" \"what should I focus on,\" \"I don't know where to start,\" or any open-ended business request that doesn't clearly match a single skill.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Fsmb-router\u002FSKILL.md",[],[213,214,215,141,216,42,148,217,93,218,123,152,219,220,221,37,222,201,223,101],"router","smb","smb router","do","front","single","you","vague","can","plugin","focus"]