菜单
Design knowledge bases — information architecture, article templates, categorization, search optimization, maintenance, and analytics. TRIGGER when: user says /knowledge-base-design, needs to build a help center, or wants to structure internal/external documentation.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/ashutoshsrivastava17/skill-library --skill knowledge-base-design命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Model financial scenarios — base, upside, and downside cases with revenue, cost, and cash flow projections. Produce scenario comparison tables with sensitivity analysis. Finance-specific scenario planning distinct from strategy-level scenario planning. TRIGGER when: user says /financial-scenario-planning, "financial scenario", "financial modeling", "scenario model", "stress test financials", or asks to model financial outcomes under different assumptions.
Develop scenario plans with multiple futures, key uncertainties, signposts, and strategic responses for each scenario. Structure scenario analysis for strategic decision-making. TRIGGER when: user says /strategic-scenario-planning, "scenario planning", "scenario analysis", "what-if analysis", "strategic scenarios", "contingency planning".
Package a support escalation for engineering or management with full context, timeline, business impact, and recommended actions. TRIGGER when: user says "escalate", "escalation", "needs engineering", "needs management", "critical issue", "P0", "P1", "sev1", "sev2", "customer at risk", "churn risk", "executive escalation", or "get engineering involved".
基于 SOC 职业分类
正在显示 SKILL.md
| name | knowledge-base-design |
| description | Design knowledge bases — information architecture, article templates, categorization, search optimization, maintenance, and analytics. TRIGGER when: user says /knowledge-base-design, needs to build a help center, or wants to structure internal/external documentation. |
| argument-hint | [knowledge base scope and audience] |
| user-invocable | true |
You are a knowledge management specialist. Design a knowledge base that is easy to find, read, and maintain.
| Element | Options |
|---|---|
| Type | External (customer-facing) / Internal (employee) / Both |
| Audience | End users, developers, admins, agents |
| Content types | How-tos, troubleshooting, FAQs, reference, concepts |
| Volume | Estimated number of articles |
| Tools | Zendesk, Confluence, Notion, GitBook, custom |
Top-level categories (5-9 max):
| Category | Content Type | Example Articles |
|---|---|---|
| Getting Started | Onboarding, setup | Quick start guide, account setup |
| Features | How-to guides | Using dashboards, configuring alerts |
| Troubleshooting | Problem-solution | Error codes, common issues |
| API/Developer | Technical reference | API docs, webhooks, SDKs |
| Account & Billing | Administrative | Plan changes, invoices, cancellation |
How-to template:
# How to [Task]
## Overview
[1-2 sentence description of what this achieves]
## Prerequisites
- [Requirement 1]
## Steps
1. [Step with screenshot]
2. [Step with screenshot]
## Result
[What the user should see when done]
## Related Articles
- [Link 1]
Troubleshooting template:
# [Error/Problem]
## Symptoms
[What the user sees]
## Cause
[Why this happens]
## Solution
1. [Fix step 1]
2. [Fix step 2]
## If This Doesn't Help
[Escalation path]
| Technique | Details |
|---|---|
| Titles | Use the question/task the user would search |
| Keywords | Include synonyms and common misspellings |
| Metadata | Tags, categories, product area, version |
| Structure | Headers that match sub-queries |
| Cross-links | Link related articles to improve discovery |
| Activity | Cadence | Owner |
|---|---|---|
| Content review | Quarterly per category | Content owners |
| Accuracy audit | Every release | Product + docs team |
| Analytics review | Monthly | KB manager |
| Feedback triage | Weekly | Support + docs team |
| Archival | Quarterly | KB manager |
| Metric | Target |
|---|---|
| Self-service rate | > 70% of help center visitors don't create a ticket |
| Search success | > 70% of searches result in article views |
| Article helpfulness | > 80% positive ratings |
| Coverage | < 5% of tickets have no matching KB article |
| Freshness | < 10% of articles older than 6 months without review |
## Knowledge Base Design: [Name]
### Architecture: [Category structure]
### Templates: [Article types with templates]
### Search: [Optimization plan]
### Maintenance: [Review cadence]
### Metrics: [Success criteria]