AWS Kiro Clinical Interoperability skill

The clinical-interoperability skill from AWS's Kiro for Life Sciences bundle. Its content is real and concretely on-standard: FHIR resource types (Patient, Observation, Condition, DiagnosticReport, MolecularSequence) including a documented pattern for mapping VCF fields into FHIR Observation.component elements per the FHIR Genomics Implementation Guide, HL7 v2 ORU/ADT/ORM message structure with a worked example encoding a BRCA1 pathogenic-variant result, and OMOP CDM guidance -- verified by direct fetch of the skill file itself. This entry is marked marginal, not clean, for a specific, disclosed reason: unlike the other skill entries seeded in this pass (which wrap an executable tool, API, or script with a defined input/output contract), this is a Kiro steering document (inclusion: manual frontmatter) -- reference guidance injected into an agent's context, with no script, API call, or defined return schema of its own. The inputs/outputs recorded below are this registry's own reasonable characterisation of a guidance-lookup skill, not a contract declared by the source. Terms check: the repository's root LICENSE.txt is MIT-0 (MIT No Attribution), confirmed by direct fetch; MIT-0 is not on this registry's SPDX allow-list (schemas/vocab/licenses.json), so this entry records license: "other" with license_url pointing at that LICENSE.txt rather than an approximate SPDX match, per this registry's own convention for a real but un-listed licence. The candidate research note that led to this check described '10 named domain skills plus 16 steering workflows' including a 'gene-disease-associations' workflow chaining ClinVar to OMIM to HPO; direct inspection confirmed both the count and this specific skill/steering-file split (kiro-life-sciences/skills/ holds 10 domain-guidance files including this one, kiro-life-sciences/steering/ holds 16 workflow files including gene-disease-associations.md and fhir-clinical-integration.md), and separately confirmed the repository also ships genuine MCP servers (e.g. life-sciences-genomics, wrapping NCBI/Ensembl/ClinVar/GEO/SRA) as a distinct component from these skill/steering files. No slug collision with any existing entry in this registry.