Help Center

What This Skill Does

The Help Center skill is an integrated framework designed for building, migrating, and optimizing technical support ecosystems. It moves beyond simple documentation by treating the help center as operational infrastructure. It manages the entire lifecycle of a support knowledge base, from initial provider selection—comparing SaaS vendors against custom builds—to complex content migrations and the implementation of support deflection metrics. The skill relies on a structured memory system in ~/help-center/ to ensure that architecture, taxonomy decisions, and rollout logs are persisted across sessions.

Installation

To integrate this skill into your environment, run the following command in your terminal: clawhub install openclaw/skills/skills/ivangdavila/help-center Ensure that your workspace allows for local file creation within the ~/help-center/ directory, as the skill requires this path to maintain its memory, provider matrices, and migration playbooks.

Use Cases

• Provider Selection: Comparing vendors like Zendesk or Intercom against a custom-built, headless CMS solution to minimize long-term costs and lock-in.
• Content Migration: Systematically porting legacy articles into a new taxonomy, ensuring proper URL redirection and metadata mapping to prevent SEO degradation.
• Support Workflow Alignment: Designing a knowledge base structure that directly informs ticket triage, auto-response triggers, and agent escalation paths.
• Optimization: Regularly auditing search query logs to identify knowledge gaps and tracking deflection rates to measure the ROI of your support content.

Example Prompts

1. "I need to choose a new help center provider for our startup. Can you help me set up the provider-matrix.md and compare three options based on our 5-person team size and limited budget?"
2. "We are migrating our existing help center from Notion to a custom Next.js site. Please help me create a migration-playbook.md with a plan for URL redirects and a content audit."
3. "Our ticket volume is too high. Analyze our current support workflow and suggest a content taxonomy that maps better to our Jira ticket tags."

Tips & Limitations

• Always start with strategy: Do not jump into choosing tools until you have defined your team size, ticket volume, and language requirements. The skill enforces this via its core rules.
• Memory persistence: Keep your ~/help-center/ folder clean. Always update memory.md after a significant decision to ensure the AI remembers the 'why' behind your current configuration.
• Taxonomy first: Avoid the common trap of mass-importing content. Define your categories and article templates first, or you will end up with unsearchable clutter. Note that this skill requires careful orchestration of file-system operations and expects you to provide the input data regarding your specific business constraints.