Cadasto
OrganizationopenEHR assistant AI plugin suite with Skills, commands, and MCP server configuration for clinical workflow integration
Categories
Indexed Skills (8)
aql-authoring
This skill should be used when the user asks to "write an AQL query", "optimize an AQL query", "review AQL", or "query openEHR data" — the multi-step authoring/optimization workflow for AQL (Archetype Query Language) over openEHR clinical data. For a one-off explanation of an existing query or a single AQL keyword/operator (no authoring), the `/openehr-explain` command suffices.
archetype-authoring
This skill should be used when the user asks to "create", "edit", "specialize", "review / remediate", "write the rationale for", "translate / localise", or "fix the ADL syntax of" an openEHR archetype (including "this archetype won't parse / won't validate"), or to import a CKM archetype into the workspace for reuse. It covers the full author → review (lint → fix → re-lint) → rationale → translate lifecycle. To merely explain an existing archetype with no edits, use `/openehr-explain` instead.
archetype-lint
This skill should be used when the user asks to "lint an archetype", "validate an archetype", "check archetype compliance", "check archetype rules compliance", or "run archetype rules". Applies 24 normative lint rules with ERROR/WARNING/INFO severity. Supports STRICT and PERMISSIVE modes. Reports violations only — it does not modify files; to lint *and* remediate, use the `archetype-authoring` skill. Auto-invoked on lint/validate intent, and also directly invocable as `/archetype-lint <file or id> [strict]`.
composition-builder
This skill should be used when the user asks to "build a composition", "create a composition", "validate a composition", "convert a composition", or "generate FLAT/STRUCTURED/CANONICAL format". Covers building openEHR compositions in all simplified formats and guiding their validation and format conversion (against a target template; there is no automated validator/converter tool). Also handles quick format explanations and single-payload sketches directly. For designing the template itself (OET/OPT), use `template-authoring`; this skill produces runtime data instances against an existing template.
demographic-modeling
This skill should be used when the user asks to "design a demographic model", "model a person/organisation/role", "design party relationships", "plan identity structures", or "work with demographic archetypes". Covers designing openEHR demographic models using the PARTY hierarchy, roles, capabilities, relationships, and identity patterns. For clinical EHR archetypes (OBSERVATION/EVALUATION/etc.) use `archetype-authoring`; for a one-off lookup of a demographic RM type with no design work, `/openehr-explain` suffices. This skill owns the demographic PARTY model.
openehr-assistant
This skill should be used when a conversation touches openEHR outside a task owned by a dedicated skill — e.g. "what is an archetype?", "how do openEHR templates work?", "which composition category fits this data?", "find me a guide on X", "where do I start with openEHR modeling?" — or names openEHR concepts (ADL, CKM, RM types, OPT, terminology bindings, CGEM). Provides general openEHR awareness, guide browsing (`guide_search` / `guide_get`), clinical modeling guidance, and tool/skill routing. Not for focused tasks owned by a dedicated skill — archetype authoring/linting, template authoring, composition building, AQL authoring, artefact diffing, or demographic modeling — route those to the matching skill; this skill is the awareness and routing layer.
semantic-diff
This skill should be used when the user asks to "diff two archetypes", "compare two templates", "what changed between these two versions", "is this a patch, minor or major bump?", "how compatible are these two artefacts?", or invokes `/semantic-diff`. Auto-detects archetype vs template (any serialisation) and version vs sibling comparison, then reports a version-bump verdict (rule G1) or a compatibility report with a path-compatibility table. Not a textual/git diff; to review or fix a single artefact, use the `archetype-authoring` or `template-authoring` skill.
template-authoring
This skill should be used when the user asks to "create a template", "design a template", "constrain archetypes into a template", "review a template", "categorise a dataset with CGEM", "should this be persistent, episodic or event?", "split this form across compositions", "sketch a template from this form / which archetypes does this form need", or "work with OET / .t.json / OPT / web-template files" — OET authoring, constraint review, the form → template-sketch inverse workflow, and reading the tool-generated serialisations. Use `/ckm-search` to find existing CKM templates and `/openehr-explain` to explain one; this skill is for authoring and constraining new OET designs.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.