coral-create-source-spec

Create or update a Coral source spec YAML for a custom HTTP API or local dataset. Use when authoring a standalone source for `coral source add --file`, or when adapting that spec into a Coral repo source under `sources/core` or `sources/community`.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, highly actionable skill body with executable YAML/SQL/CLI examples and a strong lint-validate-inspect-refine feedback loop. Its main weaknesses are moderate cross-section redundancy and a large amount of detailed OAuth guidance inlined in the main file rather than externalized to references.

Suggestions

Reduce redundancy between the Workflow, Validation Loop, and HTTP Sources sections — e.g., consolidate the coral.source add non-interactive/OAuth-interactive guidance so it lives in one place and is referenced.

Break the long single-paragraph OAuth authoring rules into a short inline summary plus a dedicated references/oauth-credential-methods.md, keeping SKILL.md lighter and improving progressive disclosure.

Tighten or bullet the dense OAuth flow paragraphs (authorization-code, device-code, client-credentials) so each rule is scannable rather than buried in prose.

Dimension	Reasoning	Score
Conciseness	The body is information-dense and Coral-specific with no padding of concepts Claude already knows, but there is redundancy across the Workflow, Validation Loop, and HTTP Sources sections and several very long single-paragraph OAuth rule blocks that could be tightened — efficient with minor trim opportunities, so above a 3 but not a 5.	4 / 5
Actionability	Provides copy-paste-ready YAML snippets (HeaderAuth, OAuth authorization_code, one_of fallback), concrete CLI commands (coral source lint/add/test/sql), and complete executable SQL validation queries covering the common inspection cases, matching anchor 5.	5 / 5
Workflow Clarity	The 9-step Workflow is clearly sequenced with explicit validation checkpoints (lint at step 4, validate in the right mode at step 5, inspect shape at step 6) and a refine-and-repeat feedback loop, with the Validation Loop section giving concrete error-recovery queries until the source behaves correctly.	5 / 5
Progressive Disclosure	Sections are well-organized and the single reference references/http-source-checklist.md is clearly signaled one level deep ('Read references/http-source-checklist.md when you need table-shape and pagination guidance'), but the bulk of detailed OAuth authoring rules remain inlined in SKILL.md rather than split out, leaving minor organization gaps versus anchor 5.	4 / 5
	Total	18 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, well-targeted description that states concrete actions and an explicit 'Use when' trigger with multiple concrete modes. It is slightly jargon-heavy on trigger terms and modest in verb diversity, but clearly answers what and when for a distinct niche.

Dimension	Reasoning	Score
Specificity	Quotes 'Create or update a Coral source spec YAML for a custom HTTP API or local dataset' and 'authoring a standalone source' / 'adapting that spec into a Coral repo source' — several concrete actions (create, update, author, adapt) with comprehensive coverage of HTTP/local and standalone/repo modes, just short of anchor 5's broader verb diversity.	4 / 5
Completeness	Explicitly answers both what ('Create or update a Coral source spec YAML...') and when with a concrete 'Use when authoring a standalone source... or when adapting that spec...' trigger clause, matching anchor 5.	5 / 5
Trigger Term Quality	Includes natural Coral-domain terms a user would say — 'source spec YAML', 'coral source add --file', 'sources/core', 'sources/community', 'HTTP API', 'local dataset' — good coverage though leaning on technical/path jargon with few synonyms, so not a 5.	4 / 5
Distinctiveness Conflict Risk	The Coral-specific triggers ('coral source add --file', 'sources/core', 'sources/community', 'Coral source spec YAML') carve a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: withcoral/coral
Path: plugins/coral/skills/coral-create-source-spec/SKILL.md
Commit: 2c58881

Reviewed: 12 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.