CtrlK
BlogDocsLog inGet started
Tessl Logo

conventions-check

Review a pull request's title, description, and scope against the repository's PR conventions.

62

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.flue/.agents/skills/conventions-check/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

93%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.

The content is exemplary: concise, highly actionable, with explicit rules and a precise output schema. The only slight gap is workflow validation, which is largely inapplicable to this single-pass analysis skill.

DimensionReasoningScore

Conciseness

The body is lean and task-focused with no padding explaining what a PR or convention is, and consistently assumes Claude's competence ('Do not narrate your work', 'Default to no finding').

5 / 5

Actionability

Provides concrete, executable guidance: named input fields, explicit flag/non-flag conditions with examples, and a copy-paste-ready result shape with a worked JSON example.

5 / 5

Workflow Clarity

A clear sequence (Inputs -> Security -> Rules -> Severities -> Result) with explicit decision checkpoints ('When in doubt, pass', 'Do not flag...'); it is not a destructive/batch operation, so a validate->retry loop is not applicable, leaving only minor validation gaps.

4 / 5

Progressive Disclosure

No bundle files exist and the skill is self-contained; content is well-organized into clearly headed sections with no nested references and nothing that should be split into a separate file.

5 / 5

Total

19

/

20

Passed

Description

53%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.

The description clearly states what the skill does but lacks an explicit 'when to use it' trigger clause, which limits its completeness. It is reasonably specific and distinct, though trigger-term coverage could be broader.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases, e.g. 'Use when reviewing a pull request against the repo's contribution conventions, PR template, or title format rules.'

Include common synonyms users might say such as 'contribution guidelines', 'PR template', or 'PR review' to broaden trigger-term coverage.

Consider listing the concrete checks (title format, description presence, scope accuracy) in the description itself to lift specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the PR-review domain and concrete review targets ('title, description, and scope') but does not comprehensively enumerate the review actions, matching the anchor for domain + 1-2 concrete actions.

3 / 5

Completeness

Provides a clear 'what' but no 'Use when...' clause; per the rubric guideline, a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Includes relevant natural terms ('pull request', 'PR conventions', 'title', 'description', 'scope') but misses common synonyms a user would say such as 'contribution guidelines' or 'convention check'.

3 / 5

Distinctiveness Conflict Risk

Targets a specific niche (PR convention adherence) with mostly distinct triggers, with only minor overlap risk against a generic PR-review skill.

4 / 5

Total

13

/

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
cloudflare/cloudflare-docs
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.