generated: '2026-07-31'
method: generated
source: >-
  openapi/anomalo-public-api-openapi.yml + conventions/anomalo-conventions.yml +
  errors/anomalo-problem-types.yml + mcp/anomalo-mcp.yml
note: >-
  Packaged Agent Skills for the Anomalo Public API. Every operationId referenced in these skills was
  verified against openapi/anomalo-public-api-openapi.yml. Anomalo publishes no AGENTS.md or skill files
  of its own; these were generated by API Evangelist. The first three mirror the flows Anomalo itself
  exposes through its official MCP server; the fourth covers lineage-based triage, which the REST API
  supports but the MCP surface does not.
skills:
  - file: anomalo-check-table-health.md
    name: Check the data quality health of an Anomalo table
    description: >-
      Find a monitored table by name or label, read its most recent check run, and explain which checks
      failed and why.
    api: openapi/anomalo-public-api-openapi.yml
    mutating: false
    mirrors_mcp_tools:
      - get_configured_tables
      - get_table_check_status
    operations:
      - get_active_organization_id
      - get_all_organizations
      - set_active_organization_id
      - list_labels_for_organization
      - configured_tables
      - get_table_information
      - tables
      - get_check_intervals
      - get_run_result
  - file: anomalo-run-checks-and-await-results.md
    name: Trigger an Anomalo check run and wait for the results
    description: >-
      Trigger the checks on a table or one specific check, poll to completion, and report the outcome.
      The only write flow Anomalo exposes to agents.
    api: openapi/anomalo-public-api-openapi.yml
    mutating: true
    guardrails:
      - 15-minute per-table throttle on full-table runs, matching Anomalo's own MCP server
      - no idempotency key exists, so never retry the POST on timeout
      - confirm with the human before running checks on a table not explicitly named
    mirrors_mcp_tools:
      - run_data_quality_checks_on_table
      - data_quality_check_run_status
    operations:
      - get_active_organization_id
      - get_table_information
      - get_checks_for_table
      - run_checks
      - get_run_result
      - get_task
  - file: anomalo-profile-table-data.md
    name: Summarize what is in an Anomalo-monitored table
    description: >-
      Retrieve Anomalo's statistical data profile for a monitored table and explain its contents,
      column types, null rates, uniqueness and distributions.
    api: openapi/anomalo-public-api-openapi.yml
    mutating: false
    mirrors_mcp_tools:
      - get_table_data_profile
    operations:
      - get_active_organization_id
      - configured_tables
      - get_table_information
      - get_table_profile
      - get_table_documentation
  - file: anomalo-triage-with-lineage.md
    name: Triage a failed Anomalo check using table lineage
    description: >-
      Walk the upstream lineage of a failing table to locate the root cause, then assess downstream
      blast radius.
    api: openapi/anomalo-public-api-openapi.yml
    mutating: false
    mirrors_mcp_tools: []
    note: >-
      No MCP equivalent. Anomalo's four lineage operations are REST-only and absent from its published
      agent surface, so this flow is unavailable to agents working through MCP alone.
    operations:
      - get_active_organization_id
      - get_table_information
      - get_check_intervals
      - get_run_result
      - get_run_result_triage_history
      - list_table_upstream_lineage
      - list_table_downstream_lineage
      - get_checks_for_table
shared_rules:
  authentication: 'X-Anomalo-Token: <api secret token>'
  base_url: https://{instance}/api/public/v1/
  tenancy: >-
    Always read GET /organization before trusting the scope of a result. The active organization is
    sticky server-side state on the API key, not a request parameter.
  idempotency: >-
    Not supported. No idempotency key, no deduplication, no conditional requests. Never blind-retry a
    write.
  retries: >-
    5xx: retry up to 5 attempts with exponential jitter backoff (1s initial, 10s cap). 4xx: never retry;
    the body is opaque text, not a structured error.
  csv_links: >-
    Bad-row and good-row CSV URLs require an authenticated browser session and cannot be fetched
    programmatically. Surface them to the human instead.
  check_outcomes: >-
    A 200 response does not mean healthy. Read check_passed / check_failed / check_errored /
    check_skipped from the payload, and never report an errored check as a data quality failure.