Scaffold vertical

Skill smithdak/dossier/.claude/skills/scaffold-vertical

Scaffold a vertical-specific knowledge-base template from Dossier's knowledge model. Use to stand up a reusable starting taxonomy for an industry/vertical (e.g., Digital Experience Agency) — seed concept stubs, vertical-specific types, and an index — so a new client in that vertical is a fast instantiation, not a from-scratch build.From its SKILL.md

Install

npx -y skills add smithdak/dossier --skill scaffold-vertical

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.1 KB, as published. Nobody here has run it

Scaffold a Vertical Template

Create a reusable, vertical-specific KB template that conforms to knowledge/model/index.md. Verticals are the economics — they turn each new client into a fast instantiation. Time-to-Live-Wiki is the metric.

Procedure

Name the vertical (e.g., digital-experience-agency) and read the knowledge model.
Map the vertical's canonical knowledge — the processes, workflows, roles, systems, policies, and decisions that most companies in this vertical share. This is the template's value: the 70% that's common.
Choose vertical types — reuse core types; propose vertical-specific types only where they earn their place (e.g., a DXA might add engagement, client, capability). Clear with the knowledge-architect.
Generate the template under verticals/<vertical>/:
- index.md (type index) describing the vertical and how to instantiate it.
- Seed concept stubs — well-formed frontmatter + a description + TODO markers for client-specific detail, marked status: draft, confidence: asserted, source: vertical-template.
- A manifest listing what a client engagement must fill in.
Keep it atomic and linked — stubs reference each other with [[id]] so the graph shape ships with the template.

Rules

Templates are starting points, not truth — every stub is draft until a client engagement grounds it with real source/verified content.
Don't invent client specifics. The template encodes structure and common patterns, not made-up facts.
Reuse the core model; resist taxonomy sprawl.

Output

A verticals/<vertical>/ directory of conformant stubs + an index + an instantiation manifest, plus a summary of the concepts/types created and what each new client must supply.