CtrlK
BlogDocsLog inGet started
Tessl Logo

pr-submission

PR title format, commit conventions, and pre-PR checklist for SkillHub. Use when preparing or reviewing pull requests.

70

Quality

85%

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

85%

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

An actionable, well-structured conventions skill with concrete commands, a validation checklist, and clean section organization. The main weakness is a redundant re-listing of commit types that slightly undercuts conciseness.

Suggestions

Remove the duplicated Types list under 'Commit Message Format' and replace it with a reference to the PR-title types table, since it already states 'Same convention as PR titles'.

Add a brief feedback loop for checklist failures (e.g., 'If a check fails, fix the issue and re-run the failing command before opening the PR') to strengthen workflow clarity.

DimensionReasoningScore

Conciseness

The body is mostly lean with no concept tutorials, but 'Commit Message Format' redundantly re-lists the same Types already shown in the PR-title table, which could be tightened to a single reference.

2 / 3

Actionability

Concrete, copy-paste-ready commands (`make test-backend-app`, `make typecheck-web`, `make generate-api`, `make staging`) plus specific PR-title/commit examples and a structured PR body template.

3 / 3

Workflow Clarity

A clear 4-step workflow sequence paired with an explicit validation checklist (tests pass, typecheck passes, smoke test passes) provides the checkpoints the score-3 anchor requires.

3 / 3

Progressive Disclosure

A single self-contained conventions skill with no external references needed, organized into six clearly-headed sections; per the simple-skills note, well-organized sections suffice.

3 / 3

Total

11

/

12

Passed

Description

85%

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 clear, specific description that covers both what the skill does and when to use it, with a distinct project-scoped niche. Trigger-term coverage is somewhat narrow and could add common phrasings users actually say.

Suggestions

Broaden trigger terms to include common phrasings users naturally say, e.g. 'Use when opening, creating, or reviewing a PR, or writing commit messages.'

Mention commit messages explicitly in the trigger clause so users asking about 'commit message' phrasing are captured.

DimensionReasoningScore

Specificity

Lists three concrete deliverables — 'PR title format, commit conventions, and pre-PR checklist' — matching the score-3 anchor for multiple specific concrete actions.

3 / 3

Completeness

Explicitly answers both what (title format, commit conventions, pre-PR checklist) and when via the 'Use when preparing or reviewing pull requests' trigger clause.

3 / 3

Trigger Term Quality

'Use when preparing or reviewing pull requests' gives natural keywords but limited variations, missing common phrasings like 'open a PR' or 'commit message'; fits score-2's 'some relevant keywords but missing common variations'.

2 / 3

Distinctiveness Conflict Risk

Project-scoped to 'SkillHub' with a pre-PR checklist niche, giving a distinct trigger unlikely to conflict with generic git skills.

3 / 3

Total

11

/

12

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
iflytek/skillhub
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.