CtrlK
BlogDocsLog inGet started
Tessl Logo

pr

Open or update a pull request in this monorepo. Covers the pre-push checks, the changeset decision, Conventional Commit titles, how to fill the PR template, and what to do once CI runs. Use when asked to open a PR, push a branch for review, fix a red PR, or judge whether a branch is ready to merge.

74

Quality

92%

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

SKILL.md
Quality
Evals
Security

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 well-structured, highly actionable PR workflow with concrete commands, explicit validation checkpoints, and a CI feedback loop. It is efficient and clearly navigable, with only minor conciseness and organization room for improvement.

DimensionReasoningScore

Conciseness

Largely lean and action-first with no conceptual padding, but a handful of explanatory 'because…' justifications and prose guardrails could be trimmed slightly without losing clarity.

4 / 5

Actionability

Fully executable, copy-paste-ready commands throughout (`git switch -c`, `pnpm format && pnpm lint:fix`, `gh pr create … --body-file`), plus a concrete worked title example (`feat(core): add a plugin resolver cache`) covering the common cases.

5 / 5

Workflow Clarity

Eight numbered steps in clear order with explicit validation ('Everything has to pass before you push', 'Check git diff --cached before every commit'), a CI feedback loop (read failing job → reproduce → fix → push), and checklists/guardrails for a destructive-ish operation.

5 / 5

Progressive Disclosure

Well-organized into eight labeled sections plus a clear one-level-deep Related-skills table; the workflow is appropriately self-contained, with only minor organization gaps keeping it below the top anchor.

4 / 5

Total

18

/

20

Passed

Description

96%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, concrete description that names six specific actions and pairs them with explicit, natural 'Use when…' triggers. It is highly specific and complete, with only minor overlap risk against a possible commit-message skill.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Open or update a pull request', 'pre-push checks', 'the changeset decision', 'Conventional Commit titles', 'how to fill the PR template', 'what to do once CI runs' — giving comprehensive coverage rather than vague abstraction.

5 / 5

Completeness

Explicitly answers both what ('Open or update a pull request… Covers…') and when ('Use when asked to open a PR, push a branch for review, fix a red PR, or judge whether a branch is ready to merge') with concrete trigger phrases.

5 / 5

Trigger Term Quality

'Use when asked to open a PR, push a branch for review, fix a red PR, or judge whether a branch is ready to merge' uses the exact natural phrases a developer would say, with synonyms (PR / pull request) included.

5 / 5

Distinctiveness Conflict Risk

A clear PR-workflow niche with distinct triggers, but 'Conventional Commit titles' creates minor overlap risk with a dedicated commit-message skill, keeping it just below the top anchor.

4 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 4 suspicious

Warning

Total

15

/

16

Passed

Repository
kubb-labs/kubb
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.