How do I install the Airworthiness Liaison skill?

Run npx skillmds@latest add ashfordeou/airworthiness-liaison in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Airworthiness Liaison safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Airworthiness Liaison?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Airworthiness Liaison free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Airworthiness Liaison?

ashfordeOU (@ashfordeou) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Airworthiness Liaison by ashfordeou

Name: Airworthiness Liaison
Author: ashfordeOU

Airworthiness Liaison

Use when you must manage DO-178C airworthiness and certification liaison for an airborne software item: confirm the certification basis items with evidence, score stage-of-involvement audit readiness against the software level threshold, and track open liaison items to closure before authority audits. Produces the certification-basis coverage account, the SOI readiness verdict, and the open-item action flags that keep the certification plan on schedule. Trigger: airworthiness liaison, certification liaison, soi audit, certification basis, authority communication, audit readiness.

ashfordeOU Updated Sep 17, 2026

File contents

DO-178C Airworthiness Liaison (avionics/do178c/airworthiness-liaison)

Use when the task is DO-178C airworthiness and certification liaison: certification-basis coverage, SOI audit readiness, and open-item tracking with the certification authority.

Domain quick reference

Certification basis: the airworthiness requirements the software item must satisfy (airworthiness regulations plus the accepted means of compliance); each basis item needs evidence.
Stage-of-involvement (SOI) audits: the authority audits planning, development, verification, and configuration management artifacts; readiness is the fraction of required evidence that is present.
Readiness thresholds are project-defined and scale with the software level: levels A and B demand full evidence, lower levels tolerate small gaps.
Open liaison items (issue papers, audit findings) must close before the certification plan can complete.

Workflow

Collect the certification basis items and their evidence status.
Build the coverage account with cert_basis_coverage.
Map required evidence to the software level and score SOI readiness with soi_readiness.
Track open liaison items with liaison_action.
Gate the next audit on readiness and open-item closure.

Pitfalls

Counting basis items without evidence as covered.
Applying a level A readiness bar to level D work (and the reverse).
Letting open items ride through audits unclosed.

Behavior contract (gate 3)

The certification-basis, readiness, and action logic is exercised by the gate 3 contract test: scripts/test_airworthiness_liaison.py against scripts/airworthiness_liaison_logic.py (stdlib unittest, offline). Run: python3 scripts/test_airworthiness_liaison.py

Compliance

Standards referenced, not reproduced: DO-178C and ARP4754A text is proprietary (RTCA/SAE); summary-only per standards-map.yaml and brief 06. No objective tables or appendix text.
compliance: STANDARDS-REF, gated: false.

---name: airworthiness-liaisondescription: Use when you must manage DO-178C airworthiness and certification liaison for an airborne software item: confirm the certification basis items with evidence, score stage-of-involvement audit readiness against the software level threshold, and track open liaison items to closure before authority audits. Produces the certification-basis coverage account, the SOI readiness verdict, and the open-item action flags that keep the certification plan on schedule. Trigger: airworthiness liaison, certification liaison, soi audit, certification basis, authority communication, audit readiness.license: Apache-2.0---# DO-178C Airworthiness Liaison (avionics/do178c/airworthiness-liaison)Use when the task is DO-178C airworthiness and certification liaison:certification-basis coverage, SOI audit readiness, and open-itemtracking with the certification authority.## Domain quick reference- Certification basis: the airworthiness requirements the software item must satisfy (airworthiness regulations plus the accepted means of compliance); each basis item needs evidence.- Stage-of-involvement (SOI) audits: the authority audits planning, development, verification, and configuration management artifacts; readiness is the fraction of required evidence that is present.- Readiness thresholds are project-defined and scale with the software level: levels A and B demand full evidence, lower levels tolerate small gaps.- Open liaison items (issue papers, audit findings) must close before the certification plan can complete.## Workflow1. Collect the certification basis items and their evidence status.2. Build the coverage account with cert_basis_coverage.3. Map required evidence to the software level and score SOI readiness with soi_readiness.4. Track open liaison items with liaison_action.5. Gate the next audit on readiness and open-item closure.## Pitfalls- Counting basis items without evidence as covered.- Applying a level A readiness bar to level D work (and the reverse).- Letting open items ride through audits unclosed.## Behavior contract (gate 3)The certification-basis, readiness, and action logic is exercised bythe gate 3 contract test: scripts/test_airworthiness_liaison.pyagainst scripts/airworthiness_liaison_logic.py (stdlib unittest,offline). Run:python3 scripts/test_airworthiness_liaison.py## Compliance- Standards referenced, not reproduced: DO-178C and ARP4754A text is proprietary (RTCA/SAE); summary-only per standards-map.yaml and brief 06. No objective tables or appendix text.- compliance: STANDARDS-REF, gated: false.

Frequently asked questions