knowledge-base-help-center-wasp-drone — Claude Code Subagent
knowledge-base-help-center-wasp-drone architects customer help centers, guides platform migration, and configures search-first content with AI deflection.
AGPL-3.0-or-later ★ 96 updated 2026-10-18
/plugin marketplace add legioncodeinc/vibe-coding-tools
/plugin install growth-and-customer-tools@wasp-nestWhat knowledge-base-help-center-wasp-drone does
This subagent manages the planning cycle for public self-service documentation. It runs a scored decision tree across platforms like Intercom Articles, Document360, Zendesk Guide, Help Scout Docs, and ReadMe.com. Information architecture is kept tight: maximum three navigation levels, structured article templates, and explicit taxonomy designed around user search queries rather than internal company jargon.
AI deflection planning branches into three patterns: built-in platform bots, standalone widgets like Fin, and external retrieval endpoints. It insists on adding llms.txt during the initial rollout and builds an ongoing feedback loop via the CRAVA scorecard to monitor searches that yield zero hits. Work concludes with an operational docs/kb-plan.md or a migration punch list.
Custom vector pipelines and embedding mechanics are deliberately handed off to mind-wasp-drone. Before running, the agent expects knowledge-base-help-center-stinger to be resolved from the growth-and-customer-tools package.
What it helps with
- evaluate help center platforms against branching and pricing constraints
- structure a search-first hierarchy with maximum three category levels
- plan zero-result search triage using the CRAVA scorecard
- draft an AI deflection roadmap with day-one llms.txt support
- outline parallel content versioning for developer-facing API hubs
Example prompts for the agent
- Pick a KB platform between ReadMe and Document360 for our API hub
- Audit our help center taxonomy and fix zero-result searches
- Set up our docs migration checklist and specify an llms.txt file
How to install knowledge-base-help-center-wasp-drone
1Plugin marketplace
/plugin marketplace add legioncodeinc/vibe-coding-tools/plugin install growth-and-customer-tools@wasp-nest2Manually: put the files in place
.claude/agents/knowledge-base-help-center-wasp-drone.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/knowledge-base-help-center-wasp-drone.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/knowledge-base-help-center-wasp-drone.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about knowledge-base-help-center-wasp-drone
How to install knowledge-base-help-center-wasp-drone in Claude Code?
Run /plugin marketplace add legioncodeinc/vibe-coding-tools, followed by /plugin install growth-and-customer-tools@wasp-nest, and locate the definition under .claude/agents/knowledge-base-help-center-wasp-drone.md.
What does knowledge-base-help-center-wasp-drone do?
It structures public documentation portals, runs platform trade-off analyses, and plans search architecture alongside AI-powered ticket deflection.
Does this subagent handle customer support inbox routing?
No. Inbox management, ticketing configuration, and live chat widget security belong to separate specialized agents.