kb-intake

Guide writers through structured KB article intake using Socratic questioning.

7|2|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/DomoApps/domo-documentation-hub --skill kb-intake
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kb-intake
Source: https://github.com/DomoApps/domo-documentation-hub/tree/main/.claude/skills/kb-intake
Command: npx skills add https://github.com/DomoApps/domo-documentation-hub --skill kb-intake

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guidance helps writers plan and structure a Knowledge Base article by conducting a focused, one-question-at-a-time intake using the Socratic Method, capturing context and requirements before drafting.

Core Features & Use Cases

  • Guided intake: Prompts focused questions to uncover audience, goals, scope, prerequisites, and content boundaries.
  • Structured summary: Produces a final artifact (Working title, target persona, goal, and scope) to guide the writing process.
  • Topic-to-article flow: Converts user-provided source material or topic into a clear article outline and plan.

Quick Start

Provide your source material or describe your topic so the intake process can begin.

Frequently Asked Questions about kb-intake

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure a knowledge base article from unstructured source material?

Plan knowledge base content by conducting a focused, one-question-at-a-time intake to capture audience persona, constraints, and prerequisites before drafting. This defines content boundaries and produces a structured summary to guide the writing process.

What is the Socratic method for content planning and documentation intake?

The Socratic method for documentation intake uses focused, one-question-at-a-time prompts to uncover audience, goals, scope, and prerequisites. It converts user-provided topics into a clear article outline and structured plan.

How do I create a knowledge base article outline that handles edge cases and prerequisites?

Create a knowledge base article outline by performing a structured intake to identify prerequisites, edge cases, and related content links. This captures content boundaries and constraints before drafting begins.

Can I use structured intake to define target audience and scope before writing technical documentation?

Yes, structured intake defines target audience and scope before writing technical documentation by prompting focused questions to elicit audience persona, goals, and constraints. This produces a working title and structured summary to guide writing.

What's the best way to convert a topic into a structured article outline for a knowledge base?

The best way to convert a topic into a structured article outline is through a guided intake process that asks focused questions about goals, scope, and audience. This yields a final artifact with a working title, target persona, and content boundaries for handoff.