Coral Review Source Spec

Review Goal

Review the source as product surface. Do not spend the review mainly restating CI, schema validation, or YAML lint results unless those failures are visible and relevant. Focus on whether the source will be understandable, useful, safe, and consistent for Coral users and agents.

Workflow

1. Identify the target source directory or PR changes.
   • For a path request, inspect manifest.yaml, any README, and related source docs or tests.
   • For a PR request, find changed files under sources/core/ or sources/community/. If the PR does not add or update a source, say the skill is not applicable and review normally.
2. Read guidance in the Coral repo before judging style:
   • CONTRIBUTING.md, especially "Source contributions".
   • The repo AGENTS.md and any nearer AGENTS.md.
   • Similar existing sources in sources/core/ and the community example in sources/community/hn/.
3. Compare against existing source patterns, not a generic API-wrapper ideal. Look at nearby sources with similar shape: public no-auth APIs, token APIs, OAuth-backed APIs, GraphQL APIs, search-heavy APIs, log/time-series APIs, or generated large API sources.
4. Produce a code-review style result: findings first, ordered by severity, with file and line references. Include open questions only after findings. If there are no substantive issues, say so and mention residual risks or review gaps.

Review Checklist