Skills smart-base-skills

Derived: every skill markdown file, with the description it declares in its own front matter. Sub-graph smart-base/skills.

This is an index, not the documentation. It says what exists and what each artefact declares about itself. What a process is for, when you would be in it, and what it is not, is authored beside it and reuses these entries rather than restating them — see the auto-docs skill.
ArtefactWhat it declares about itself
dak-l1-library
smart-base/skills/content/authoring-who-smart-guidelines/dak-l1-library.md		Build a DAK's library from the L1 sources its Component 1 cites, and the L1 knowledge graph that records them.
dak-postprocessing
smart-base/skills/content/authoring-who-smart-guidelines/dak-postprocessing.md		What the DAK post-processing phase accomplishes after the IG Publisher runs — the JSON/JSON-LD surface, the DAK API hub, and the metadata-to-Liquid bridge that is the seam the just-the-docs transition cuts at.
dak-preprocessing
smart-base/skills/content/authoring-who-smart-guidelines/dak-preprocessing.md		What the DAK pre-processing phase actually accomplishes, step by step, before the IG Publisher runs — and which of its steps exist only to satisfy the Publisher's own page index — and how it runs as the overlay on fhir-…
grade
smart-base/skills/content/authoring-who-smart-guidelines/grade.md		GRADE — the grading system a WHO guideline folio declares for certainty of evidence, and the Evidence-to-Decision judgement a recommendation rests on.
guideline-use-case
smart-base/skills/content/authoring-who-smart-guidelines/guideline-use-case.md		Stage 0 of smart-guideline-end-to-end: turn a request for a SMART Guideline into a use case — population, setting, jurisdiction and interventions in scope, new or an adaptation — in the requester's own words.
ig-artifact-ingestion
smart-base/skills/content/authoring-who-smart-guidelines/ig-artifact-ingestion.md		no description in the artefact
l2-component-edit-review
smart-base/skills/content/authoring-who-smart-guidelines/l2-component-edit-review.md		How one L2 DAK component is edited by the agent and reviewed by a person: personas and user scenarios, BPMN business processes, DMN decision and scheduling logic, core data elements and glossary with their terminology b…
l2-dak-authoring
smart-base/skills/content/authoring-who-smart-guidelines/l2-dak-authoring.md		Author the L2 layer of a WHO SMART Guideline — the Digital Adaptation Kit between the narrative L1 guideline and the L3 FHIR artefacts — one DAK component per pass (personas, user scenarios, business processes, data dic…
l2-dependency-choice
smart-base/skills/content/authoring-who-smart-guidelines/l2-dependency-choice.md		Stage 3 of smart-guideline-end-to-end: choose which existing DAKs (WHO's, or a jurisdiction's adaptation) the guideline builds on.
l3-dependency-choice
smart-base/skills/content/authoring-who-smart-guidelines/l3-dependency-choice.md		Stage 5 of smart-guideline-end-to-end: choose which existing FHIR IGs (WHO's, or a jurisdiction's) the guideline's L3 builds on.
l3-readiness
smart-base/skills/content/authoring-who-smart-guidelines/l3-readiness.md		The check between stages 5 and 6 of smart-guideline-end-to-end (Gateway_L3Ready): may the agent write L3 assets yet? Yes only when every source of the use case has its L1 extraction, every L2 asset names the L1 node it…
l4-application-brief
smart-base/skills/content/authoring-who-smart-guidelines/l4-application-brief.md		Stage 7 of smart-guideline-end-to-end: get from the requester a description of the consuming application — who uses it, on what device, which L2 processes and L3 resources it covers, connectivity, the systems it talks t…
l4-application-build
smart-base/skills/content/authoring-who-smart-guidelines/l4-application-build.md		Stage 8b of smart-guideline-end-to-end: build the consuming application against the stage-6 IG build (a clean build, not a publication), from the brief and the chosen stage-8a wireframes, with conformance tests from the…
recommendation-candidates
smart-base/skills/content/authoring-who-smart-guidelines/recommendation-candidates.md		Turn one ingested L1 source into L1 3.0 recommendation nodes: list every normative sentence as a candidate, let the agent decide each in a curation file, then refuse a non-verbatim statement or unknown location and writ…
recommendation-extraction
smart-base/skills/content/authoring-who-smart-guidelines/recommendation-extraction.md		Extract the recommendations of an L1 source as L1 3.0 recommendation and remark nodes, then describe each one's scenario: the persona (role) who acts on it, the business process they act in, and the user story, as smart…
recommendation-scenarios
smart-base/skills/content/authoring-who-smart-guidelines/recommendation-scenarios.md		Join each L1 recommendation to who acts on it and during which business process: one smart-kg L2 user-scenario candidate per recommendation, from the agent's mapping, reusing the target guide's personas and processes fi…
smart-base-tools
smart-base/skills/content/authoring-who-smart-guidelines/smart-base-tools.md		no description in the artefact
smart-guideline-create
smart-base/skills/content/authoring-who-smart-guidelines/smart-guideline-create.md		Somebody asked for a new WHO SMART Guideline (an IG built on smart-base, or a DAK that will feed one).
smart-guideline-end-to-end
smart-base/skills/content/authoring-who-smart-guidelines/smart-guideline-end-to-end.md		The whole road from a use case to a running application on WHO SMART Guidelines, for a new guideline or a jurisdiction's adaptation, as an orchestrator of ten named stage skills, each with its own input and output contr…
smart-stack-layering
smart-base/skills/content/authoring-who-smart-guidelines/smart-stack-layering.md		Which layer a WHO SMART asset, rule, script or page belongs to — fhir-harness, smart-base (with its L1 and DAK document kinds) or smart-ig — and the one question that settles it.
toolchain-ownership
smart-base/skills/content/authoring-who-smart-guidelines/toolchain-ownership.md		Taking ownership of the WHO smart-base scripts in a litlfred fork, rewriting them to the Skill I/O contract, and the one gate that governs when a script may actually move.
transcription-verbatim
smart-base/skills/content/authoring-who-smart-guidelines/transcription-verbatim.md		Check L1 authored from pictures (a schedule poster, a slide deck: a source with no usable text layer) against the image narratives and transcriptions it names: every statement verbatim in one of them, every transcriptio…

folio-assistant — code under the Apache License 2.0, documentation under CC BY 3.0. Generated schema and API references are rebuilt from source on every push to main.

deployed dev