# verify-catalog-entry

> Verify an Alastor catalog entry against its airbyte-connectors source/destination specs. Use when reviewing PRs that add or modify catalog entries, or when adding a new connector to the UI catalog.

- Author: matiascoulougian
- Repository: faros-ai/verify-catalog-entry-skill
- Version: 20260209110005
- Stars: 0
- Forks: 0
- Last Updated: 2026-02-09
- Source: https://github.com/faros-ai/verify-catalog-entry-skill
- Web: https://mule.run/skillshub/@@faros-ai/verify-catalog-entry-skill~verify-catalog-entry:20260209110005

---

---
name: verify-catalog-entry
description: Verify an Alastor catalog entry against its airbyte-connectors source/destination specs. Use when reviewing PRs that add or modify catalog entries, or when adding a new connector to the UI catalog.
allowed-tools: Bash(python3:*)
---

Verify that an Alastor catalog entry correctly matches the underlying airbyte-connectors source and destination specs.

Arguments: $ARGUMENTS
- First argument: Path to the catalog JSON file relative to Alastor (e.g., `catalog/resources/sources/qa/zephyr.json`)
- Second argument: Path to the airbyte-connectors repo (e.g., `../airbyte-connectors` or absolute path)

Steps:

1. Run the verification script:
   ```bash
   python3 .agents/skills/verify-catalog-entry/scripts/verify_catalog.py $ARGUMENTS
   ```

2. Parse the JSON output and present a report covering:

   **Critical Issues** (must fix):
   - Missing required fields from source spec
   - Incorrectly named fields (typos, wrong property paths)
   - Unsupported catalog types (e.g., `jsonArray` doesn't exist)
   - Authentication type mismatches
   - `sourceType` mismatch with connector's `type` getter

   **Warnings** (should review):
   - Source spec fields not exposed in catalog (might be intentional)
   - Type mismatches between catalog and spec (e.g., `textarea` vs `array`)
   - Fields in catalog that don't exist in source spec
   - Nested object arrays that need special handling

   **Info** (for awareness):
   - Entities field vs actual destination models produced
   - Default values comparison
   - Required field differences

3. End with actionable recommendations for fixing any issues found.