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 highly actionable, well-sequenced skill body with concrete commands, executable YAML examples, and an explicit validation loop. Its main weakness is density: long inlined OAuth/metadata rule paragraphs that strain token efficiency and could be externalized as references.

Suggestions

Split the dense OAuth authoring rules (lines 89-96) and the Metadata UX Rules section into a dedicated reference file (e.g. `references/oauth-and-metadata.md`), keeping only a concise summary and a clearly signaled pointer in SKILL.md to improve both conciseness and progressive disclosure.

Break the multi-clause OAuth paragraphs into a short bulleted checklist so each rule is scannable instead of a run-on sentence.

Add a one-line pointer near the top of the Authoring Rules section to the source manifest schema URL so the long authoring checklist can lean on it rather than restating every constraint inline.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and assumes competence (no generic concept explanations), but the dense OAuth authoring paragraphs (lines 89-96) are long run-on guidance that could be split or trimmed for token efficiency.	4 / 5
Actionability	Provides copy-paste-ready shell commands (`coral source lint`, `coral source add --file`, `coral sql "..."`) and complete executable YAML examples (Bearer auth, OAuth authorization_code, `from: one_of`) covering the common cases.	5 / 5
Workflow Clarity	The numbered Workflow (read → define → lint → validate → inspect → query → refine) plus the explicit Validation Loop and Deliverable give a clear sequence with validation checkpoints and a fix-and-repeat feedback loop.	5 / 5
Progressive Disclosure	Clear section structure with one well-signaled one-level-deep reference ("Read `references/http-source-checklist.md`"), but the lengthy Authoring Rules and Metadata UX Rules blocks are inlined in SKILL.md and could be split into reference files.	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 strong, third-person description that clearly states both the capability and the usage triggers with Coral-specific terms. Minor room to expand the action list and add synonyms, but it is comprehensive and low-conflict.

Dimension	Reasoning	Score
Specificity	"Create or update a Coral source spec YAML for a custom HTTP API or local dataset" plus "authoring a standalone source" and "adapting that spec into a Coral repo source" lists several specific actions across two concrete target types, with only minor coverage gaps (e.g. repair/migration not enumerated).	4 / 5
Completeness	Explicitly answers both what ("Create or update a Coral source spec YAML...") and when ("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`") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural working terms a user would say ("Coral source spec YAML", "coral source add --file", "sources/core", "sources/community", "custom HTTP API", "local dataset") with good coverage, though a few natural synonyms/extensions are absent.	4 / 5
Distinctiveness Conflict Risk	The Coral-specific niche and distinct triggers (`coral source add --file`, `sources/core`, `sources/community`) make conflict with other skills minimal.	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: 334387d

Reviewed: 3 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.