Skills fhir-ig-skills

Derived: every skill markdown file, with the description it declares in its own front matter. Sub-graph fhir-harness/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
fhir-questionnaire-wireframe
fhir-harness/skills/content/fhir-ig-authoring/fhir-questionnaire-wireframe.md
no description in the artefact
fhir-validation
fhir-harness/skills/content/fhir-ig-authoring/fhir-validation.md
no description in the artefact
ig-publication
fhir-harness/skills/content/fhir-ig-authoring/ig-publication.md
no description in the artefact
l3-fhir-authoring
fhir-harness/skills/content/fhir-ig-authoring/l3-fhir-authoring.md
no description in the artefact
terminology-management
fhir-harness/skills/content/fhir-ig-authoring/terminology-management.md
no description in the artefact
fhir-client-operations
fhir-harness/skills/fhir-client/fhir-client-operations.md
Reading, searching and writing FHIR R4 resources through the SMARTerFHIR client (BaseClient and its vendor subclasses): the launch-context reads, requestResource, create with its automatic subject/encounter/contex…
smart-launch
fhir-harness/skills/fhir-client/smart-launch.md
How a browser app performs a SMART on FHIR launch — EHR launch and standalone launch — with the SMARTerFHIR library: SmartLaunchHandler, the LAUNCH and EMR enums, the scopes it requests per EHR vendor, how the red…
fhir-ig-create
fhir-harness/skills/fhir-ig-base/fhir-ig-create.md
Somebody asked for a new FHIR Implementation Guide.
ig-ast-delta
fhir-harness/skills/fhir-ig-base/ig-ast-delta.md
List and view what changed between two IG ASTs, check whether an AST is still valid for the IG's current inputs, and render the delta as just-the-docs pages that carry the provisional mark.
ig-binary-artefacts
fhir-harness/skills/fhir-ig-base/ig-binary-artefacts.md
Where the IG Publisher's binary outputs go — full-ig.zip, package.tgz and its R4/R4B variants, package.db, validator packs, and the definitions, examples and expansions zips — and why a pages branch is the wrong place f…
ig-build-pipeline
fhir-harness/skills/fhir-ig-base/ig-build-pipeline.md
The bare FHIR IG pipeline — FSH to SUSHI to the IG Publisher to a pages branch, with no pre-processing and no post-processing.
ig-publisher-fork
fhir-harness/skills/fhir-ig-base/ig-publisher-fork.md
Requirements for an agent working a local experimental fork of the IG Publisher — which repositories, what the AST must carry, what must not change, and the acceptance criteria.
ig-publisher-reduction
fhir-harness/skills/fhir-ig-base/ig-publisher-reduction.md
The phased transition that reduces the IG Publisher to AST + QA — five phases, each with an exit criterion that is measured rather than asserted, and the staleness contract that makes an AST-backed staging build honest.
ig-render-jekyll
fhir-harness/skills/fhir-ig-base/ig-render-jekyll.md
Rendering a FHIR IG's content through the just-the-docs pipeline instead of mounting the IG Publisher's finished HTML — the JSON-only representation contract, navigation derived from sushi-config.yaml, and the LHS rail.
ig-site-links
fhir-harness/skills/fhir-ig-base/ig-site-links.md
What happens to an IG's links when its pages are rendered on our site rather than by the IG Publisher: which are rewritten (artefact pages, a case-only mismatch, the Publisher's downloads and pages, files of the IG's re…
ig-site-theme
fhir-harness/skills/fhir-ig-base/ig-site-theme.md
How an IG rendered through just-the-docs wears the theme its instance ALREADY declares: the one webpage theme becomes the IG site's colour scheme.

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 b08c961 · 2026-10-23T23:11:09Z