CtrlK
BlogDocsLog inGet started
Tessl Logo

coral-review-source-spec

Review new or updated Coral source manifests and source PRs for content, style, product fit, query ergonomics, documentation quality, and consistency with existing Coral sources. Use when Codex is asked to review a sources/core/name or sources/community/name source directory, a manifest.yaml, or a GitHub PR that adds or changes a Coral source.

72

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 well-structured, concrete review spec that assumes competence and gives actionable criteria plus a clear workflow and output template. The main improvements are splitting the dense OAuth bullet and making workflow checkpoints more explicit.

Suggestions

Break the long OAuth bullet (line 44) into a short nested sub-list so each setup-path requirement is scannable.

Add an explicit validation/checkpoint note in the Workflow (e.g., confirm findings reference real file:line before writing the result) to reach the top workflow-clarity anchor.

Consider moving the long per-category checklist detail into a references/ file and keeping SKILL.md as an overview to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is information-dense and assumes Claude's competence with no concept padding, but the OAuth bullet (line 44) is a long run-on sentence that could be split for readability, keeping it just below lean.

4 / 5

Actionability

Criteria are highly concrete and executable for a review skill — exact input names requiring kind: secret, exact OAuth flows, snake_case naming rules, and a worked output template cover the common cases.

5 / 5

Workflow Clarity

A clear four-step Workflow is paired with a thorough Review Checklist, but validation/checkpoint guidance is implicit rather than explicit, fitting just below the top anchor.

4 / 5

Progressive Disclosure

No bundle files exist; the body is well-organized with clear section headers and one-level external URL references, though it is over 50 lines so the simple-skill exception does not push it to 5.

4 / 5

Total

17

/

20

Passed

Description

92%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 defines a niche review task and gives explicit trigger guidance with concrete path and file keywords. The only minor gap is trigger-term synonym coverage.

DimensionReasoningScore

Specificity

"Review ... for content, style, product fit, query ergonomics, documentation quality, and consistency with existing Coral sources" names the domain plus six concrete review facets, matching the comprehensive-coverage anchor.

5 / 5

Completeness

It states a clear "what" (review Coral source manifests/PRs across listed dimensions) and an explicit "Use when ..." trigger with concrete phrases, satisfying both halves.

5 / 5

Trigger Term Quality

"review a sources/core/name ... source directory, a manifest.yaml, or a GitHub PR that adds or changes a Coral source" gives good natural/domain keywords, but a few common synonyms are absent, fitting just below the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

The Coral source-manifest/PR niche with path and manifest.yaml triggers is highly specific with minimal overlap risk against other skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
withcoral/coral
Reviewed

Table of Contents

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.