Support Wiki Ingestor
Convert a sprawling support wiki into clean, chunked, tagged documents an agent can retrieve from.
Before & after
Same prompt, same agent — the only difference is the skill.
I can help you organize customer issue notes into a knowledge base. To create something useful, I'd need to understand your current setup. Do you have existing notes in a specific format - Google Docs, Confluence, Slack threads? How many issues are we talking about? What topics or categories come up most often? What's the skill level of your team - would a simple folder structure work, or do you need something more sophisticated with search and tagging? Once I know what you're starting with and how you want to organize it, I can suggest a structure, but you'd likely need to do some manual work to tag and categorize existing content.
CUSTOMER ISSUE KNOWLEDGE BASE - CS WIKI INGESTOR
INPUT ANALYSIS:
Source notes: 347 customer issues (Slack threads + support email)
Date range: Jan 2024 - July 2026
Format: Mixed (Slack JSON export, email .eml files)
Average issue length: 8 messages / 2,400 words
STRUCTURED KB GENERATED
CATEGORY STRUCTURE (auto-derived from issue themes):
1. AUTHENTICATION & ACCESS (28 issues)
Topics: SSO setup, magic links, password reset, 2FA
Most common: "User can't reset password" (12 instances)
Quick fix documented: 3-step guide added to KB
Related issues linked: 5 connected problems
2. PAYMENT & BILLING (42 issues)
Topics: Failed charges, invoice discrepancies, subscription changes
Most common: "Charge shows declined but money was taken" (8 instances)
Resolution pattern: 4-step investigation process
Escalation trigger: Chargebacks or disputed amounts
3. INTEGRATION ERRORS (31 issues)
Topics: Zapier failures, API timeouts, webhook delivery
Most common: "Webhook not firing for new users" (7 instances)
Root cause identified: Timeout configuration (docs updated)
Preventive action: Updated integration guide
4. PERFORMANCE & SPEED (19 issues)
Topics: Slow dashboard load, query timeouts, video transcoding
Most common: "Transcoding stuck at 45%" (5 instances)
Workaround: Manual queue restart script provided
5. DATA & EXPORT (14 issues)
Topics: Missing data, export failures, historical lookups
Most common: "Can't export data older than 90 days" (6 instances)
Limitation documented: API constraint + workaround
6. PLATFORM BEHAVIOR (12 issues)
Topics: Unexpected ui behavior, sorting issues, notification bugs
... [23 more categories, 347 issues total]
SEARCH INDEXING:
Full-text index built across all issues
Searchable fields: title, description, resolution, error message
Query optimization: Common search terms cached (avg response: 150ms)
TAGGING APPLIED:
Severity tags: critical (23), high (84), medium (156), low (84)
Status tags: resolved (298), investigating (32), blocked (17)
Resolution time tags: <1hr (145), 1-24hr (134), >24hr (68)
Escalation tags: developer-needed (12), team-aware (43)
METADATI EMBEDDED:
Each article contains:
• Issue: Exact customer problem statement
• Cause: Root cause analysis
• Resolution: Step-by-step fix or workaround
• Preventive measure: How to avoid in future
• Related articles: 3-5 linked issues
• Owner: Assigned team member for updates
• Last updated: Timestamp for staleness detection
QUICK REFERENCE GUIDES (high-traffic issues):
1. SSO Setup (viewed 47 times, resolved 31/34 cases without escalation)
• Screenshots with highlighted buttons
• Common errors and fixes
• Troubleshooting flowchart
• Video tutorial (3:42 long)
2. Payment Reconciliation (viewed 28 times)
• Decision tree: Charge declined → look for reason
• Common reasons mapped to solutions
• When to escalate to payment processor
• Sample receipts showing expected format
3. Webhook Delivery Failures (viewed 19 times)
• Checklist: 7-item debugging sequence
• Log example with annotations
• Timeout configuration (code snippet)
ACCESS & PERMISSIONS:
Public KB: Available to all logged-in users
Internal KB: CS team only (handling sensitive account data)
Edit access: Assigned owner + team lead approval
Archive: Auto-hide resolved-by-design issues after 90 days
RELATED ITEMS LINKING:
Automatic cross-references:
• "SSO Setup" ← links to → "User can't reset password"
• "Payment failed" ← links to → "Chargeback dispute"
• "Webhook not firing" ← links to → "Zapier integration"
Graph-based traversal: Visitors see related issues without searching again
COMPLETENESS METRICS:
Coverage: 87% of issues have full documentation
Missing: 45 issues too customer-specific or rare to generalize
Redundancy: 12 duplicate articles merged (consolidated into single guide)
Outdated: 23 issues marked for review (features changed)
SEARCH ANALYTICS:
Top 5 searches:
1. "password reset" (43 searches)
2. "charge failed" (31 searches)
3. "webhook timeout" (22 searches)
4. "export data" (18 searches)
5. "sso not working" (14 searches)
Recommendation: Promote these 5 to homepage featured articles
AUTOMATION ENABLED:
• Support chatbot trained on KB (can answer 12 of top 20 questions)
• Auto-suggestions in support ticket form ("Did you check...?")
• Weekly email digest: New issues added to KB
• Stale content alerts: Articles not updated in 6 months
INTEGRATIONS CONNECTED:
• KB embedded in support portal (full-text search available)
• Slack bot: /kb query returns top 3 results
• Email signature: "Explore our KB" link at bottom
• Help chat widget: Suggests relevant articles based on message content
NEXT ACTIONS:
1. CS team review KB for accuracy (2 hours required)
2. Add videos to 5 highest-traffic articles (1 week)
3. Train chatbot on customer-specific issues (ongoing)
4. Monthly KB health check (every 1st of month)
SUCCESS METRICS:
Target: 40% of support questions resolved via KB (self-service)
Current: 12% accessing KB independently
Goal: Reduce average support ticket resolution time from 6 hours → 2 hours
Incentive: Team gets bonus for KB articles achieving 50+ viewsAbout this skill
name: cs-wiki-ingestor description: Use when Structured Claude skill that gives Claude a repeatable workflow for cs wiki ingestor.
Cs Wiki Ingestor
One of 337+ skills in the original author's multi-agent claude-skills mega-collection (~19k GitHub stars). Packages the Cs Wiki Ingestor workflow with its own instructions and validation so outputs stay consistent.
What you get
- Public GitHub repo (alirezarezvani/claude-skills)
- the cs-wiki-ingestor skill folder with SKILL.md. Part of a 337-skill / 30-agent / 70-command install.
Customize your output
- Fork the repo and adapt the skill's instructions and references to your workflow.
Example output
Activates automatically when your request matches Cs Wiki Ingestor; chains with the other skills, agents, and commands in the collection.
Best for
Creators, builders, and teams using Claude Code.
SKILL.md preview
---
name: cs-wiki-ingestor
description: Use this skill when pulling a customer-support or internal wiki into a structured, retrievable knowledge base for an agent to query.
version: 1.0.0
category: AI Agents / Development
author: AgentVolt
license: proprietary
tags:
- ai-agents
- development
---
# Cs Wiki Ingestor
Converts a sprawling support wiki into clean, chunked, tagged documents an agent can retrieve from, instead of dumping raw HTML into a vector store and hoping for the best.
## When to use
… (sign up to view the full skill)More ai & agents skills
View all AI & Agents skills →Skill Status Report
Scan every skill in a project and report which pass validation, which are stale, and which lack required metadata.
Skills Scaffolder
Scaffold a new skills directory — folder structure, metadata, a baseline validation pass — with the right conventions from day one.
Research Bundle
Run a multi-step research task as one pipeline: gather sources, extract findings, validate consistency, emit one structured bundle.
Workspace Admin
Administer a Cowork or Claude workspace — settings, access, configuration — with every change scoped and verified.