its-restlisted

Create, edit, or review the openEHR ITS-REST API sources (OpenAPI 3.0 YAML + Markdown) in the `specifications-ITS-REST` repo. This skill should be used when the user asks to add or edit a REST endpoint/operation/schema/response, write an operation description, review the ITS-REST spec, or update its amendment record. Not for AsciiDoc specs (use authoring) — including the AsciiDoc docs under `specifications-ITS-REST/docs/` (simplified_formats, smart_app_launch).
openEHR/ai-plugins · ★ 2 · API & Backend · score 75

Install: claude install-skill openEHR/ai-plugins

# openEHR ITS-REST API Specification Authoring This skill covers creating and editing the openEHR REST API specification sources in the `specifications-ITS-REST` repository. Unlike other `specifications-XX` repos that use AsciiDoc, ITS-REST uses **OpenAPI 3.0.3 YAML** with **Markdown** descriptions, split across many small files that are bundled into publishable artifacts. > **Exception**: The `docs/` directory contains some AsciiDoc-based specs (e.g., > `simplified_formats`, `smart_app_launch`) that follow the standard openEHR authoring > conventions. This skill does NOT cover those — use the `authoring` skill instead. ## References - **File-format conventions**: see `references/file-formats.md` for the detailed format and conventions of each source type — top-level entry YAML, operation files, schema files, Markdown description files, and the HTML amendment record. Load it when writing or editing any of these. - **Build toolchain**: see `references/build-pipeline.md` for the full Redocly + PHP pipeline, validation, live preview, and code generation. ## Repository Structure ``` specifications-ITS-REST/ ├── specifications/ # Source OpenAPI specs (authoring) │ ├── overview.openapi.yaml # Top-level entry: overview/cross-cutting concerns │ ├── ehr.openapi.yaml # Top-level entry: EHR API │ ├── query.openapi.yaml # Top-level entry: Query API │ ├── definition.openapi.yaml # Top-level entry: Definitio