CtrlK
BlogDocsLog inGet started
Tessl Logo

pr-ready

Resolve CI failures, merge conflicts, or local branch changes to get a PR ready

64

Quality

76%

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 ./.agents/skills/pr-ready/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 lean, well-structured workflow: a diagnostic checklist followed by clearly sequenced remediation steps per condition, with validation steps and a confirmation checkpoint. The only improvements are specifying the exact gh commands and an explicit post-push CI verification step.

DimensionReasoningScore

Conciseness

Roughly 30 lines with zero padding; every line is a useful instruction and no concepts Claude already knows are re-explained.

5 / 5

Actionability

Concrete ordered steps with explicit commands (`git status`, the `gh` CLI), but the exact gh invocations (e.g. `gh pr checks`, `gh pr view`) are not given, leaving minor gaps from copy-paste readiness.

4 / 5

Workflow Clarity

Clear diagnostic sequence leading into two condition branches with validation steps (run formatting/tests/builds, run relevant local checks) and a user-confirmation checkpoint before pushing; the only gap is an explicit re-verify-CI-green loop after pushing.

4 / 5

Progressive Disclosure

Under 50 lines with no need for external references, and the content is cleanly organized into a trigger list, a diagnostic checklist, and two per-condition step lists.

5 / 5

Total

18

/

20

Passed

Description

66%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 names a clear, distinctive niche with three concrete conditions, but omits any explicit 'when to use this' trigger clause, which caps completeness. Keyword coverage is good though missing common phrasings users would naturally say.

Suggestions

Add an explicit trigger clause, e.g. "Use when a pull request has failing checks, a merge conflict, or unpushed changes and needs to be made ready to merge."

Include natural trigger variations such as "failing checks", "red CI", "ready to merge", and spell out "pull request" at least once for keyword matching.

Name one or two concrete resolution actions (e.g. "rebase onto the base branch and fix failing checks") to strengthen the 'what' without adding length.

DimensionReasoningScore

Specificity

Lists three parallel concrete items in the PR domain ("Resolve CI failures, merge conflicts, or local branch changes") matching the 'several specific actions; minor gaps' anchor, though the actual resolution actions (rebase, inspect logs) are left to the body.

4 / 5

Completeness

Has a clear 'what' (resolve CI failures, merge conflicts, or local branch changes to get a PR ready) but no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Natural terms users would say — "CI failures", "merge conflicts", "PR", "branch changes" — but common variations like "failing checks", "red CI", "ready to merge", or "pull request" spelled out are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche (PR readiness workflow) with distinct triggers, but "resolve CI failures" carries minor overlap risk with general debugging/CI-fixing skills.

4 / 5

Total

15

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
remotion-dev/remotion
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.