CtrlK
BlogDocsLog inGet started
Tessl Logo

open-pr

Take a cloudflare/agents GitHub issue plus any repro findings and one-shot a fix PR — branch, change, test, push, and open the PR linked to the issue.

63

Quality

74%

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 ./agent-think/skills/open-pr/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 a well-structured, highly actionable multi-step workflow with strong validation and feedback loops; its main weaknesses are minor over-explanation and parameterized placeholders that need substitution.

DimensionReasoningScore

Conciseness

The body is mostly lean operational prose with executable commands and assumes Claude's competence; a few explanatory passages (e.g. the @agent-think instruction preamble) could be trimmed.

4 / 5

Actionability

Concrete, copy-paste-ready bash commands appear throughout (git clone, gh issue view, pnpm install, build, deploy, gh pr create), with only minor gaps from placeholders like <package> and <demoUrl> that require substitution.

4 / 5

Workflow Clarity

Eight clearly sequenced numbered steps include explicit validation checkpoints (test pass/fail with a fix loop, demo observability via curl, a one-shot-able skip decision) and a structured return block acting as a checklist.

5 / 5

Progressive Disclosure

Content is well-organized into clearly headed sections with the only external reference (the reproduce skill's recipe) clearly signaled; no bundle files exist, though some inline material like the PR-body template could optionally live in a reference file.

4 / 5

Total

17

/

20

Passed

Description

67%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 is specific and clearly niche-scoped with concrete workflow actions, but it lacks an explicit 'Use when' trigger clause and has limited keyword synonym coverage, which cap completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when an @agent-think run targets a cloudflare/agents GitHub issue for a one-shot fix PR.'

Broaden trigger-term coverage with synonyms like 'pull request', 'patch', and 'bug report' so users' natural phrasings match.

Keep the third-person imperative voice (it currently uses 'Take ...') which suits the rubric; avoid drifting into first/second person.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'branch, change, test, push, and open the PR linked to the issue' — giving comprehensive coverage of the fix-PR workflow rather than vague abstraction.

5 / 5

Completeness

The 'what' is clear (one-shot a fix PR with explicit sub-steps), but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Relevant keywords like 'GitHub issue', 'fix PR', and 'repro findings' are present and natural, but coverage is narrow and misses common synonyms such as 'pull request', 'patch', or 'bug report'.

3 / 5

Distinctiveness Conflict Risk

The narrow 'cloudflare/agents GitHub issue ... fix PR' niche has distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

16

/

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/agents
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.