Skip to content

Skill API Reference — Overview

Quick Reference

  • Total Skills: 11 (4 knowledge + 3 docs + 4 quality)
  • Total Workflows: 5
  • Input Format: Markdown + YAML frontmatter
  • Output Format: Markdown files in docs/

DocKit Master skills function as an API — each skill file defines inputs, processing rules, and outputs. This reference documents the interface of each skill.

SkillInputOutputCategory
analyze-codebaseProject filesanalysis.mdFoundation
persona-builderanalysis.md, source codepersonas/Knowledge
jtbd-analyzeranalysis.md, personas/jtbd/Knowledge
flow-mapperanalysis.md, personas/, jtbd/flows/Knowledge
tech-docsanalysis.mdarchitecture.md, database.md, etc.Documentation
sop-guideanalysis.md, knowledge layersop/Documentation
api-referenceanalysis.mdapi/Documentation
content-guidelinesN/A (rules only)N/AQuality
content-writingN/A (rules only)N/AQuality
llm-optimizationN/A (rules only)N/AQuality
seo-checklistGenerated docsAudit reportQuality
graph LR

    A["analyze-codebase"] --> B["persona-builder"]
    A --> C["jtbd-analyzer"]
    B --> C
    A --> D["flow-mapper"]
    B --> D
    C --> D
    A --> E["tech-docs"]
    D --> F["sop-guide"]
    A --> G["api-reference"]

Dependency summary: analyze-codebase is the root dependency. Knowledge skills chain: personas → JTBD → flows. Tech docs depend only on analysis. SOPs depend on the full knowledge layer.

All skills accept the global config object defined in Step 1:

DOC_TYPE = knowledge | tech | sop | api | all
FORMAT = markdown | astro
SCOPE = full | focused
LANGUAGE = en | vi | zh | ja
SEO = yes | no
LLM_OPTIMIZE = yes | no