generated: '2026-07-28'
method: generated
source: >-
  Generated by API Evangelist from live probes of the CASA surface on 2026-07-28
  and the repo artifacts (conventions/, vocabulary/, json-schema/, errors/,
  data-model/, authentication/, lifecycle/).
note: >-
  CASA publishes no OpenAPI and no AGENTS.md or skill files of its own - a search
  of casa.gov.au and its GitHub org candidates found none. These skills are
  therefore GENERATED, not searched, and every step in them is grounded in a real
  HTTP request, header, status code, field name or published CASA document
  verified on 2026-07-28. Where the underlying data cannot answer a question
  (AD-to-aircraft applicability, RPAS payload shapes) the skill says so instead of
  guessing.
skills:
  - file: casa-aviation-ingest-aircraft-register.md
    name: Ingest the Australian civil aircraft register
    api: casa-aviation:casa-aircraft-register-data
    summary: >-
      Conditional-poll, download, parse and validate the full register. Covers the
      403 User-Agent filter, ETag/Last-Modified 304 polling, the UTF-8 BOM,
      DD/MM/YYYY dates, the composite CoA category fields, the two dead columns
      and the personal-data handling obligation.
    operations:
      - GET https://services.casa.gov.au/CSV/acrftreg.csv
      - GET https://services.casa.gov.au/CSV/acrftreg.zip
      - HEAD https://services.casa.gov.au/CSV/acrftreg.csv
  - file: casa-aviation-lookup-airworthiness-directives.md
    name: Look up Australian Airworthiness Directives and fetch the AD document
    api: casa-aviation:casa-airworthiness-directives-data
    summary: >-
      Pull the AD listing, filter in-force directives correctly (Active OR
      Urgent), build the public AD citation, resolve any directive to its real PDF
      with the derived and verified ADfiles URL template, and understand why
      per-aircraft applicability is not answerable from the published data.
    operations:
      - GET https://services.casa.gov.au/JSON/combinedadweb.json
      - GET https://services.casa.gov.au/airworth/airwd/data/adweb.csv
      - GET https://services.casa.gov.au/airworth/airwd/data/folder.csv
      - GET https://services.casa.gov.au/airworth/airwd/ADfiles/{grouptitle}/{foldername}/{ADFILE}
  - file: casa-aviation-rpas-platform-access.md
    name: Qualify for CASA RPAS Digital Platform access
    api: casa-aviation:casa-rpas-digital-platform
    summary: >-
      Decide whether an application can obtain RPAS Platform credentials before
      writing integration code - the four approval gates, the paid Airservices
      prerequisite, the paused trial-aerodrome onboarding, the eight-weeks-notice
      withdrawal right, and why the uniform 403 makes probing useless.
    operations:
      - GET https://data.casa.rpasplatform.net/casa/data/advisories.geojson
      - GET https://data.casa.rpasplatform.net/casa/data/notifications.json
      - GET https://data.casa.rpasplatform.net/casa/gcd
      - GET https://data.casa.rpasplatform.net/asa/gcd