[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ACQ7K73WCS1CF75E7FRYA2":3,"skill-same:01M6ACQ7K73WCS1CF75E7FRYA2":95},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":32,"publishedAt":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":56,"repositoryHtmlUrl":57,"repositoryHomepageUrl":6,"ownerHtmlUrl":58,"ownerBlogUrl":59,"ownerDescription":6,"updatedAt":60,"install":61,"resources":74},"01M6ACQ7K73WCS1CF75E7FRYA2","knowledge-base-article-writing",null,"Draft a knowledge base article from a resolved issue or common question. Use when a ticket resolution is worth documenting for self-service, the same question keeps coming up, a workaround needs to be published, or a known issue should be communicated to customers.","Significant-Gravitas\u002Fskills-catalog","Significant-Gravitas","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F130738209?v=4","01M6AC83EPDGBFN19MWYRREJD0","AutoGPT","01M6ACEY98TKHDWJH0B93PHNMG",2,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fknowledge-base-article-writing\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fknowledge-base-article-writing\u002FSKILL.md",[19,24,27],{"categoryNo":20,"categoryName":21,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":25,"categoryName":26,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":28,"categoryName":29,"taxonomyType":30,"taxonomyTypeDesc":31},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[33,34,35,36,37,38,39],"writing","knowledge base article writing","github","customer","support","https","plugins","2026-11-10 10:12:30",false,"---\nname: knowledge-base-article-writing\ndescription: Draft a knowledge base article from a resolved issue or common question. Use when a ticket resolution is worth documenting for self-service, the same question keeps coming up, a workaround needs to be published, or a known issue should be communicated to customers.\nargument-hint: \u003Cresolved issue or ticket>\nlicense: Apache-2.0\nmetadata:\n  author: Anthropic\n  source: anthropics\u002Fknowledge-work-plugins\u002Fcustomer-support\u002Fskills\u002Fkb-article\n  source_url: https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002F1c7187c4fc17feefa6cde39517f12dae1249e6c4\u002Fcustomer-support\u002Fskills\u002Fkb-article\u002FSKILL.md\n  upstream-commit: 1c7187c4fc17feefa6cde39517f12dae1249e6c4\n  original-name: kb-article\n  packaged-by: AutoGPT\n  packaged-on: '2026-09-25'\n---\n\n> Packaging adaptation by AutoGPT, 2026-09-25. Original authorship and licence are retained. Changes are limited to the recorded name, metadata and local references; see ATTRIBUTION.md in this package.\n\n\n# \u002Fkb-article\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](references\u002FCONNECTORS.md).\n\nDraft a publish-ready knowledge base article from a resolved support issue, common question, or documented workaround. Structures the content for searchability and self-service.\n\n## Usage\n\n```\n\u002Fkb-article \u003Cresolved issue, ticket reference, or topic description>\n```\n\nExamples:\n- `\u002Fkb-article How to configure SSO with Okta — resolved this for 3 customers last month`\n- `\u002Fkb-article Ticket #4521 — customer couldn't export data over 10k rows`\n- `\u002Fkb-article Common question: how to set up webhook notifications`\n- `\u002Fkb-article Known issue: dashboard charts not loading on Safari 16`\n\n## Workflow\n\n### 1. Understand the Source Material\n\nParse the input to identify:\n\n- **What was the problem?** The original issue, question, or error\n- **What was the solution?** The resolution, workaround, or answer\n- **Who does this affect?** User type, plan level, or configuration\n- **How common is this?** One-off or recurring issue\n- **What article type fits best?** How-to, troubleshooting, FAQ, known issue, or reference (see article types below)\n\nIf a ticket reference is provided, look up the full context:\n\n- **~~support platform**: Pull the ticket thread, resolution, and any internal notes\n- **~~knowledge base**: Check if a similar article already exists (update vs. create new)\n- **~~project tracker**: Check if there's a related bug or feature request\n\n### 2. Draft the Article\n\nUsing the article structure, formatting standards, and searchability best practices below:\n\n- Follow the template for the chosen article type (how-to, troubleshooting, FAQ, known issue, or reference)\n- Apply the searchability best practices: customer-language title, plain-language opening sentence, exact error messages, common synonyms\n- Keep it scannable: headers, numbered steps, short paragraphs\n\n### 3. Generate the Article\n\nPresent the draft with metadata:\n\n```\n## KB Article Draft\n\n**Title:** [Article title]\n**Type:** [How-to \u002F Troubleshooting \u002F FAQ \u002F Known Issue \u002F Reference]\n**Category:** [Product area or topic]\n**Tags:** [Searchable tags]\n**Audience:** [All users \u002F Admins \u002F Developers \u002F Specific plan]\n\n---\n\n[Full article content — using the appropriate template below]\n\n---\n\n### Publishing Notes\n- **Source:** [Ticket #, customer conversation, or internal discussion]\n- **Existing articles to update:** [If this overlaps with existing content]\n- **Review needed from:** [SME or team if technical accuracy needs verification]\n- **Suggested review date:** [When to revisit for accuracy]\n```\n\n### 4. Offer Next Steps\n\nAfter generating the article:\n- \"Want me to check if a similar article already exists in your ~~knowledge base?\"\n- \"Should I adjust the technical depth for a different audience?\"\n- \"Want me to draft a companion article (e.g., a how-to to go with this troubleshooting guide)?\"\n- \"Should I create an internal-only version with additional technical detail?\"\n\n---\n\n## Article Structure and Formatting Standards\n\n### Universal Article Elements\n\nEvery KB article should include:\n\n1. **Title**: Clear, searchable, describes the outcome or problem (not internal jargon)\n2. **Overview**: 1-2 sentences explaining what this article covers and who it's for\n3. **Body**: Structured content appropriate to the article type\n4. **Related articles**: Links to relevant companion content\n5. **Metadata**: Category, tags, audience, last updated date\n\n### Formatting Rules\n\n- **Use headers (H2, H3)** to break content into scannable sections\n- **Use numbered lists** for sequential steps\n- **Use bullet lists** for non-sequential items\n- **Use bold** for UI element names, key terms, and emphasis\n- **Use code blocks** for commands, API calls, error messages, and configuration values\n- **Use tables** for comparisons, options, or reference data\n- **Use callouts\u002Fnotes** for warnings, tips, and important caveats\n- **Keep paragraphs short** — 2-4 sentences max\n- **One idea per section** — if a section covers two topics, split it\n\n## Writing for Searchability\n\nArticles are useless if customers can't find them. Optimize every article for search:\n\n### Title Best Practices\n\n| Good Title | Bad Title | Why |\n|------------|-----------|-----|\n| \"How to configure SSO with Okta\" | \"SSO Setup\" | Specific, includes the tool name customers search for |\n| \"Fix: Dashboard shows blank page\" | \"Dashboard Issue\" | Includes the symptom customers experience |\n| \"API rate limits and quotas\" | \"API Information\" | Includes the specific terms customers search for |\n| \"Error: 'Connection refused' when importing data\" | \"Import Problems\" | Includes the exact error message |\n\n### Keyword Optimization\n\n- **Include exact error messages** — customers copy-paste error text into search\n- **Use customer language**, not internal terminology — \"can't log in\" not \"authentication failure\"\n- **Include common synonyms** — \"delete\u002Fremove\", \"dashboard\u002Fhome page\", \"export\u002Fdownload\"\n- **Add alternate phrasings** — address the same issue from different angles in the overview\n- **Tag with product areas** — make sure category and tags match how customers think about the product\n\n### Opening Sentence Formula\n\nStart every article with a sentence that restates the problem or task in plain language:\n\n- **How-to**: \"This guide shows you how to [accomplish X].\"\n- **Troubleshooting**: \"If you're seeing [symptom], this article explains how to fix it.\"\n- **FAQ**: \"[Question in the customer's words]? Here's the answer.\"\n- **Known issue**: \"Some users are experiencing [symptom]. Here's what we know and how to work around it.\"\n\n## Article Type Templates\n\n### How-to Articles\n\n**Purpose**: Step-by-step instructions for accomplishing a task.\n\n**Structure**:\n```\n# How to [accomplish task]\n\n[Overview — what this guide covers and when you'd use it]\n\n## Prerequisites\n- [What's needed before starting]\n\n## Steps\n### 1. [Action]\n[Instruction with specific details]\n\n### 2. [Action]\n[Instruction]\n\n## Verify It Worked\n[How to confirm success]\n\n## Common Issues\n- [Issue]: [Fix]\n\n## Related Articles\n- [Links]\n```\n\n**Best practices**:\n- Start each step with a verb\n- Include the specific path: \"Go to Settings > Integrations > API Keys\"\n- Mention what the user should see after each step (\"You should see a green confirmation banner\")\n- Test the steps yourself or verify with a recent ticket resolution\n\n### Troubleshooting Articles\n\n**Purpose**: Diagnose and resolve a specific problem.\n\n**Structure**:\n```\n# [Problem description — what the user sees]\n\n## Symptoms\n- [What the user observes]\n\n## Cause\n[Why this happens — brief, non-jargon explanation]\n\n## Solution\n### Option 1: [Primary fix]\n[Steps]\n\n### Option 2: [Alternative if Option 1 doesn't work]\n[Steps]\n\n## Prevention\n[How to avoid this in the future]\n\n## Still Having Issues?\n[How to get help]\n```\n\n**Best practices**:\n- Lead with symptoms, not causes — customers search for what they see\n- Provide multiple solutions when possible (most likely fix first)\n- Include a \"Still having issues?\" section that points to support\n- If the root cause is complex, keep the customer-facing explanation simple\n\n### FAQ Articles\n\n**Purpose**: Quick answer to a common question.\n\n**Structure**:\n```\n# [Question — in the customer's words]\n\n[Direct answer — 1-3 sentences]\n\n## Details\n[Additional context, nuance, or explanation if needed]\n\n## Related Questions\n- [Link to related FAQ]\n- [Link to related FAQ]\n```\n\n**Best practices**:\n- Answer the question in the first sentence\n- Keep it concise — if the answer needs a walkthrough, it's a how-to, not an FAQ\n- Group related FAQs and link between them\n\n### Known Issue Articles\n\n**Purpose**: Document a known bug or limitation with a workaround.\n\n**Structure**:\n```\n# [Known Issue]: [Brief description]\n\n**Status:** [Investigating \u002F Workaround Available \u002F Fix In Progress \u002F Resolved]\n**Affected:** [Who\u002Fwhat is affected]\n**Last updated:** [Date]\n\n## Symptoms\n[What users experience]\n\n## Workaround\n[Steps to work around the issue, or \"No workaround available\"]\n\n## Fix Timeline\n[Expected fix date or current status]\n\n## Updates\n- [Date]: [Update]\n```\n\n**Best practices**:\n- Keep the status current — nothing erodes trust faster than a stale known issue article\n- Update the article when the fix ships and mark as resolved\n- If resolved, keep the article live for 30 days for customers still searching the old symptoms\n\n## Review and Maintenance Cadence\n\nKnowledge bases decay without maintenance. Follow this schedule:\n\n| Activity | Frequency | Who |\n|----------|-----------|-----|\n| **New article review** | Before publishing | Peer review + SME for technical content |\n| **Accuracy audit** | Quarterly | Support team reviews top-traffic articles |\n| **Stale content check** | Monthly | Flag articles not updated in 6+ months |\n| **Known issue updates** | Weekly | Update status on all open known issues |\n| **Analytics review** | Monthly | Check which articles have low helpfulness ratings or high bounce rates |\n| **Gap analysis** | Quarterly | Identify top ticket topics without KB articles |\n\n### Article Lifecycle\n\n1. **Draft**: Written, needs review\n2. **Published**: Live and available to customers\n3. **Needs update**: Flagged for revision (product change, feedback, or age)\n4. **Archived**: No longer relevant but preserved for reference\n5. **Retired**: Removed from the knowledge base\n\n### When to Update vs. Create New\n\n**Update existing** when:\n- The product changed and steps need refreshing\n- The article is mostly right but missing a detail\n- Feedback indicates customers are confused by a specific section\n- A better workaround or solution was found\n\n**Create new** when:\n- A new feature or product area needs documentation\n- A resolved ticket reveals a gap — no article exists for this topic\n- The existing article covers too many topics and should be split\n- A different audience needs the same information explained differently\n\n## Linking and Categorization Taxonomy\n\n### Category Structure\n\nOrganize articles into a hierarchy that matches how customers think:\n\n```\nGetting Started\n├── Account setup\n├── First-time configuration\n└── Quick start guides\n\nFeatures & How-tos\n├── [Feature area 1]\n├── [Feature area 2]\n└── [Feature area 3]\n\nIntegrations\n├── [Integration 1]\n├── [Integration 2]\n└── API reference\n\nTroubleshooting\n├── Common errors\n├── Performance issues\n└── Known issues\n\nBilling & Account\n├── Plans and pricing\n├── Billing questions\n└── Account management\n```\n\n### Linking Best Practices\n\n- **Link from troubleshooting to how-to**: \"For setup instructions, see [How to configure X]\"\n- **Link from how-to to troubleshooting**: \"If you encounter errors, see [Troubleshooting X]\"\n- **Link from FAQ to detailed articles**: \"For a full walkthrough, see [Guide to X]\"\n- **Link from known issues to workarounds**: Keep the chain from problem to solution short\n- **Use relative links** within the KB — they survive restructuring better than absolute URLs\n- **Avoid circular links** — if A links to B, B shouldn't link back to A unless both are genuinely useful entry points\n\n## KB Writing Best Practices\n\n1. Write for the customer who is frustrated and searching for an answer — be clear, direct, and helpful\n2. Every article should be findable through search using the words a customer would type\n3. Test your articles — follow the steps yourself or have someone unfamiliar with the topic follow them\n4. Keep articles focused — one problem, one solution. Split if an article is growing too long\n5. Maintain aggressively — a wrong article is worse than no article\n6. Track what's missing — every ticket that could have been a KB article is a content gap\n7. Measure impact — articles that don't get traffic or don't reduce tickets need to be improved or retired\n","> Packaging adaptation by AutoGPT, 2026-09-25. Original authorship and licence are retained. Changes are limited to the recorded name, metadata and local references; see ATTRIBUTION.md in this package.\n\n\n# \u002Fkb-article\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](references\u002FCONNECTORS.md).\n\nDraft a publish-ready knowledge base article from a resolved support issue, common question, or documented workaround. Structures the content for searchability and self-service.\n\n## Usage\n\n```\n\u002Fkb-article \u003Cresolved issue, ticket reference, or topic description>\n```\n\nExamples:\n- `\u002Fkb-article How to configure SSO with Okta — resolved this for 3 customers last month`\n- `\u002Fkb-article Ticket #4521 — customer couldn't export data over 10k rows`\n- `\u002Fkb-article Common question: how to set up webhook notifications`\n- `\u002Fkb-article Known issue: dashboard charts not loading on Safari 16`\n\n## Workflow\n\n### 1. Understand the Source Material\n\nParse the input to identify:\n\n- **What was the problem?** The original issue, question, or error\n- **What was the solution?** The resolution, workaround, or answer\n- **Who does this affect?** User type, plan level, or configuration\n- **How common is this?** One-off or recurring issue\n- **What article type fits best?** How-to, troubleshooting, FAQ, known issue, or reference (see article types below)\n\nIf a ticket reference is provided, look up the full context:\n\n- **~~support platform**: Pull the ticket thread, resolution, and any internal notes\n- **~~knowledge base**: Check if a similar article already exists (update vs. create new)\n- **~~project tracker**: Check if there's a related bug or feature request\n\n### 2. Draft the Article\n\nUsing the article structure, formatting standards, and searchability best practices below:\n\n- Follow the template for the chosen article type (how-to, troubleshooting, FAQ, known issue, or reference)\n- Apply the searchability best practices: customer-language title, plain-language opening sentence, exact error messages, common synonyms\n- Keep it scannable: headers, numbered steps, short paragraphs\n\n### 3. Generate the Article\n\nPresent the draft with metadata:\n\n```\n## KB Article Draft\n\n**Title:** [Article title]\n**Type:** [How-to \u002F Troubleshooting \u002F FAQ \u002F Known Issue \u002F Reference]\n**Category:** [Product area or topic]\n**Tags:** [Searchable tags]\n**Audience:** [All users \u002F Admins \u002F Developers \u002F Specific plan]\n\n---\n\n[Full article content — using the appropriate template below]\n\n---\n\n### Publishing Notes\n- **Source:** [Ticket #, customer conversation, or internal discussion]\n- **Existing articles to update:** [If this overlaps with existing content]\n- **Review needed from:** [SME or team if technical accuracy needs verification]\n- **Suggested review date:** [When to revisit for accuracy]\n```\n\n### 4. Offer Next Steps\n\nAfter generating the article:\n- \"Want me to check if a similar article already exists in your ~~knowledge base?\"\n- \"Should I adjust the technical depth for a different audience?\"\n- \"Want me to draft a companion article (e.g., a how-to to go with this troubleshooting guide)?\"\n- \"Should I create an internal-only version with additional technical detail?\"\n\n---\n\n## Article Structure and Formatting Standards\n\n### Universal Article Elements\n\nEvery KB article should include:\n\n1. **Title**: Clear, searchable, describes the outcome or problem (not internal jargon)\n2. **Overview**: 1-2 sentences explaining what this article covers and who it's for\n3. **Body**: Structured content appropriate to the article type\n4. **Related articles**: Links to relevant companion content\n5. **Metadata**: Category, tags, audience, last updated date\n\n### Formatting Rules\n\n- **Use headers (H2, H3)** to break content into scannable sections\n- **Use numbered lists** for sequential steps\n- **Use bullet lists** for non-sequential items\n- **Use bold** for UI element names, key terms, and emphasis\n- **Use code blocks** for commands, API calls, error messages, and configuration values\n- **Use tables** for comparisons, options, or reference data\n- **Use callouts\u002Fnotes** for warnings, tips, and important caveats\n- **Keep paragraphs short** — 2-4 sentences max\n- **One idea per section** — if a section covers two topics, split it\n\n## Writing for Searchability\n\nArticles are useless if customers can't find them. Optimize every article for search:\n\n### Title Best Practices\n\n| Good Title | Bad Title | Why |\n|------------|-----------|-----|\n| \"How to configure SSO with Okta\" | \"SSO Setup\" | Specific, includes the tool name customers search for |\n| \"Fix: Dashboard shows blank page\" | \"Dashboard Issue\" | Includes the symptom customers experience |\n| \"API rate limits and quotas\" | \"API Information\" | Includes the specific terms customers search for |\n| \"Error: 'Connection refused' when importing data\" | \"Import Problems\" | Includes the exact error message |\n\n### Keyword Optimization\n\n- **Include exact error messages** — customers copy-paste error text into search\n- **Use customer language**, not internal terminology — \"can't log in\" not \"authentication failure\"\n- **Include common synonyms** — \"delete\u002Fremove\", \"dashboard\u002Fhome page\", \"export\u002Fdownload\"\n- **Add alternate phrasings** — address the same issue from different angles in the overview\n- **Tag with product areas** — make sure category and tags match how customers think about the product\n\n### Opening Sentence Formula\n\nStart every article with a sentence that restates the problem or task in plain language:\n\n- **How-to**: \"This guide shows you how to [accomplish X].\"\n- **Troubleshooting**: \"If you're seeing [symptom], this article explains how to fix it.\"\n- **FAQ**: \"[Question in the customer's words]? Here's the answer.\"\n- **Known issue**: \"Some users are experiencing [symptom]. Here's what we know and how to work around it.\"\n\n## Article Type Templates\n\n### How-to Articles\n\n**Purpose**: Step-by-step instructions for accomplishing a task.\n\n**Structure**:\n```\n# How to [accomplish task]\n\n[Overview — what this guide covers and when you'd use it]\n\n## Prerequisites\n- [What's needed before starting]\n\n## Steps\n### 1. [Action]\n[Instruction with specific details]\n\n### 2. [Action]\n[Instruction]\n\n## Verify It Worked\n[How to confirm success]\n\n## Common Issues\n- [Issue]: [Fix]\n\n## Related Articles\n- [Links]\n```\n\n**Best practices**:\n- Start each step with a verb\n- Include the specific path: \"Go to Settings > Integrations > API Keys\"\n- Mention what the user should see after each step (\"You should see a green confirmation banner\")\n- Test the steps yourself or verify with a recent ticket resolution\n\n### Troubleshooting Articles\n\n**Purpose**: Diagnose and resolve a specific problem.\n\n**Structure**:\n```\n# [Problem description — what the user sees]\n\n## Symptoms\n- [What the user observes]\n\n## Cause\n[Why this happens — brief, non-jargon explanation]\n\n## Solution\n### Option 1: [Primary fix]\n[Steps]\n\n### Option 2: [Alternative if Option 1 doesn't work]\n[Steps]\n\n## Prevention\n[How to avoid this in the future]\n\n## Still Having Issues?\n[How to get help]\n```\n\n**Best practices**:\n- Lead with symptoms, not causes — customers search for what they see\n- Provide multiple solutions when possible (most likely fix first)\n- Include a \"Still having issues?\" section that points to support\n- If the root cause is complex, keep the customer-facing explanation simple\n\n### FAQ Articles\n\n**Purpose**: Quick answer to a common question.\n\n**Structure**:\n```\n# [Question — in the customer's words]\n\n[Direct answer — 1-3 sentences]\n\n## Details\n[Additional context, nuance, or explanation if needed]\n\n## Related Questions\n- [Link to related FAQ]\n- [Link to related FAQ]\n```\n\n**Best practices**:\n- Answer the question in the first sentence\n- Keep it concise — if the answer needs a walkthrough, it's a how-to, not an FAQ\n- Group related FAQs and link between them\n\n### Known Issue Articles\n\n**Purpose**: Document a known bug or limitation with a workaround.\n\n**Structure**:\n```\n# [Known Issue]: [Brief description]\n\n**Status:** [Investigating \u002F Workaround Available \u002F Fix In Progress \u002F Resolved]\n**Affected:** [Who\u002Fwhat is affected]\n**Last updated:** [Date]\n\n## Symptoms\n[What users experience]\n\n## Workaround\n[Steps to work around the issue, or \"No workaround available\"]\n\n## Fix Timeline\n[Expected fix date or current status]\n\n## Updates\n- [Date]: [Update]\n```\n\n**Best practices**:\n- Keep the status current — nothing erodes trust faster than a stale known issue article\n- Update the article when the fix ships and mark as resolved\n- If resolved, keep the article live for 30 days for customers still searching the old symptoms\n\n## Review and Maintenance Cadence\n\nKnowledge bases decay without maintenance. Follow this schedule:\n\n| Activity | Frequency | Who |\n|----------|-----------|-----|\n| **New article review** | Before publishing | Peer review + SME for technical content |\n| **Accuracy audit** | Quarterly | Support team reviews top-traffic articles |\n| **Stale content check** | Monthly | Flag articles not updated in 6+ months |\n| **Known issue updates** | Weekly | Update status on all open known issues |\n| **Analytics review** | Monthly | Check which articles have low helpfulness ratings or high bounce rates |\n| **Gap analysis** | Quarterly | Identify top ticket topics without KB articles |\n\n### Article Lifecycle\n\n1. **Draft**: Written, needs review\n2. **Published**: Live and available to customers\n3. **Needs update**: Flagged for revision (product change, feedback, or age)\n4. **Archived**: No longer relevant but preserved for reference\n5. **Retired**: Removed from the knowledge base\n\n### When to Update vs. Create New\n\n**Update existing** when:\n- The product changed and steps need refreshing\n- The article is mostly right but missing a detail\n- Feedback indicates customers are confused by a specific section\n- A better workaround or solution was found\n\n**Create new** when:\n- A new feature or product area needs documentation\n- A resolved ticket reveals a gap — no article exists for this topic\n- The existing article covers too many topics and should be split\n- A different audience needs the same information explained differently\n\n## Linking and Categorization Taxonomy\n\n### Category Structure\n\nOrganize articles into a hierarchy that matches how customers think:\n\n```\nGetting Started\n├── Account setup\n├── First-time configuration\n└── Quick start guides\n\nFeatures & How-tos\n├── [Feature area 1]\n├── [Feature area 2]\n└── [Feature area 3]\n\nIntegrations\n├── [Integration 1]\n├── [Integration 2]\n└── API reference\n\nTroubleshooting\n├── Common errors\n├── Performance issues\n└── Known issues\n\nBilling & Account\n├── Plans and pricing\n├── Billing questions\n└── Account management\n```\n\n### Linking Best Practices\n\n- **Link from troubleshooting to how-to**: \"For setup instructions, see [How to configure X]\"\n- **Link from how-to to troubleshooting**: \"If you encounter errors, see [Troubleshooting X]\"\n- **Link from FAQ to detailed articles**: \"For a full walkthrough, see [Guide to X]\"\n- **Link from known issues to workarounds**: Keep the chain from problem to solution short\n- **Use relative links** within the KB — they survive restructuring better than absolute URLs\n- **Avoid circular links** — if A links to B, B shouldn't link back to A unless both are genuinely useful entry points\n\n## KB Writing Best Practices\n\n1. Write for the customer who is frustrated and searching for an answer — be clear, direct, and helpful\n2. Every article should be findable through search using the words a customer would type\n3. Test your articles — follow the steps yourself or have someone unfamiliar with the topic follow them\n4. Keep articles focused — one problem, one solution. Split if an article is growing too long\n5. Maintain aggressively — a wrong article is worse than no article\n6. Track what's missing — every ticket that could have been a KB article is a content gap\n7. Measure impact — articles that don't get traffic or don't reduce tickets need to be improved or retired\n",{"name":5,"license":15,"metadata":45,"description":7,"argument-hint":52},{"author":46,"source":47,"source_url":48,"packaged-by":12,"packaged-on":49,"original-name":50,"upstream-commit":51},"Anthropic","anthropics\u002Fknowledge-work-plugins\u002Fcustomer-support\u002Fskills\u002Fkb-article","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002F1c7187c4fc17feefa6cde39517f12dae1249e6c4\u002Fcustomer-support\u002Fskills\u002Fkb-article\u002FSKILL.md","2026-09-25","kb-article","1c7187c4fc17feefa6cde39517f12dae1249e6c4","\u003Cresolved issue or ticket>","main","7ed3b73314d5186120e8d4006febfd7e1c92cf08","skills\u002Fknowledge-base-article-writing",0,"https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas","agpt.co","2026-11-10 22:38:50",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add Significant-Gravitas\u002Fskills-catalog --skill knowledge-base-article-writing",{"tool":67,"command":68},"bunx","bunx skills add Significant-Gravitas\u002Fskills-catalog --skill knowledge-base-article-writing",{"tool":70,"command":71},"pnpm","pnpm dlx skills add Significant-Gravitas\u002Fskills-catalog --skill knowledge-base-article-writing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fknowledge-base-article-writing\u002FSKILL.md",true,[75,81,85,89],{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"ATTRIBUTION.md","REFERENCE","参考文档",1796,"https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fknowledge-base-article-writing\u002FATTRIBUTION.md",{"path":82,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":16},"LICENSE","许可证",11358,{"path":86,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002FCONNECTORS.md",1468,"https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fknowledge-base-article-writing\u002Freferences\u002FCONNECTORS.md",{"path":90,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":93,"sourceHtmlUrl":94},"scripts\u002Fmd_to_pdf.py","SCRIPT","脚本",13258,"https:\u002F\u002Fgithub.com\u002Fdrn\u002Fdots\u002Fblob\u002Fmaster\u002Fagents\u002Fskills\u002Fpdf\u002Fscripts\u002Fmd_to_pdf.py",[96,107,131,141,155,173],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":40},"01M6AD3S89TGF74S7MK4K5CGC7","workplace-memory-management","Two-tier memory system that makes Claude a true workplace collaborator. Decodes shorthand, acronyms, nicknames, and internal language so Claude understands requests like a colleague would. CLAUDE.md for working memory, memory\u002F directory for the full knowledge base.","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fworkplace-memory-management\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fworkplace-memory-management\u002FSKILL.md",[],[104,105,39,38,35,106],"workplace memory management","memory","directory",{"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":111,"licenseFileUrl":112,"sourceHtmlUrl":113,"categories":114,"keywords":124,"publishedAt":40},"01M6AD3F5X5DYW1BABD49BQKP8","website-seo-audit","Audit a website, investigate its real search opportunities, and deliver a short data-backed report on the few changes most likely to grow organic traffic that converts.","MIT","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-seo-audit\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-seo-audit\u002FSKILL.md",[115,118,121],{"categoryNo":116,"categoryName":117,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000019","营销推广",{"categoryNo":119,"categoryName":120,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":122,"categoryName":123,"taxonomyType":30,"taxonomyTypeDesc":31},"01JBSEEDCAT000000000000035","市场营销",[125,126,127,35,39,38,128,129,130],"website seo audit","audit","website","search","report","plugin",{"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":111,"licenseFileUrl":135,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":40},"01M6AD32RYMK03P50DM0T184NJ","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fverification-before-completion\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fverification-before-completion\u002FSKILL.md",[],[139,140,38,35],"verification before completion","verification",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":145,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":40},"01M6AD2WSQG7BGPXA7XP4DFZX8","vendor-evaluation","Evaluate a vendor — cost analysis, risk assessment, and recommendation. Use when reviewing a new vendor proposal, deciding whether to renew or replace a contract, comparing two vendors side-by-side, or building a TCO breakdown and negotiation points before procurement sign-off.","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fvendor-evaluation\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fvendor-evaluation\u002FSKILL.md",[],[149,150,39,38,151,152,153,35,154],"vendor evaluation","negotiation","assessment","risk assessment","cost analysis","review",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":159,"sourceHtmlUrl":160,"categories":161,"keywords":168,"publishedAt":40},"01M6AD2RBT6004C07RZRDSTA52","vendor-contract-status","Check the status of existing agreements with a vendor across all connected systems — CLM, CRM, email, and document storage — with gap analysis and upcoming deadlines. Use when onboarding or renewing a vendor, when you need a consolidated view of what's signed and what's missing (MSA, DPA, SOW), or when checking for approaching expirations and surviving obligations.","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fvendor-contract-status\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fvendor-contract-status\u002FSKILL.md",[162,165],{"categoryNo":163,"categoryName":164,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000005","邮件与沟通",{"categoryNo":166,"categoryName":167,"taxonomyType":30,"taxonomyTypeDesc":31},"01JBSEEDCAT000000000000037","律师与法务",[169,170,35,171,39,172,38],"vendor contract status","status","storage","onboarding",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":111,"licenseFileUrl":177,"sourceHtmlUrl":178,"categories":179,"keywords":183,"publishedAt":40},"01M6AD2KPNXN5CNS3CA4FRWT97","user-cohort-analysis","Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fuser-cohort-analysis\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSignificant-Gravitas\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fuser-cohort-analysis\u002FSKILL.md",[180],{"categoryNo":181,"categoryName":182,"taxonomyType":30,"taxonomyTypeDesc":31},"01JBSEEDCAT000000000000033","数据分析师",[184,185,38,35],"user cohort analysis","analytics"]