CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

open-pull-request

Publish validated gh-aw changes as a draft pull request from a cloud agent.

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/open-pull-request/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 body is a well-structured, actionable instruction skill with concrete make targets and runtime tools, a clear sequenced publish flow, and explicit validation checkpoints. Minor gains are available from de-duplicating Policy vs Always/Never-do and adding a copy-paste command sequence.

Suggestions

Add a concise numbered or copy-paste command sequence for the publish flow so the ordering is executable at a glance.

Trim the redundancy between the Policy paragraph and the Always do / Never do lists (e.g. the "never use gh pr create" rule appears in both).

Convert the Assets and scripts entries into proper links or note explicitly that they are repo paths rather than skill bundle files.

DimensionReasoningScore

Conciseness

The body is lean and instruction-focused with only minor redundancy between the Policy section and the Always do / Never do lists, fitting the efficient-with-minor-trim anchor.

4 / 5

Actionability

Concrete commands and tool names (make fmt, make recompile, make agent-report-progress[-no-test], report_progress, create_pull_request) are given, though the sequence is prose rather than a copy-paste block.

4 / 5

Workflow Clarity

The Policy section sequences template inspection, per-change make targets, pre-push validation, report_progress push, and a single create_pull_request, with most checkpoints explicit; no validate-fix-retry loop but the operation is not destructive.

4 / 5

Progressive Disclosure

Sections are well-organized with no bundle files to split out; slightly over the 50-line simple-skill threshold and the listed repo references are not navigable links, so it sits at good-structure rather than a clear 5.

4 / 5

Total

16

/

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 states a clear, specific purpose but omits any "Use when..." trigger guidance and uses somewhat jargon-heavy terms, capping completeness and trigger-term quality at 3. It is reasonably distinct from sibling skills.

Suggestions

Add an explicit trigger clause, e.g. "Use when publishing a validated gh-aw branch as a draft PR from a cloud agent."

Include a couple of natural user-facing phrases or synonyms (e.g. "open a draft PR", "publish changes") alongside "gh-aw".

List one or two more concrete actions (e.g. "runs repo validation, pushes via report_progress, opens the PR") to lift specificity.

DimensionReasoningScore

Specificity

"Publish validated gh-aw changes as a draft pull request" names the domain and one concrete action but offers no broader list of capabilities, matching the 1-2 concrete actions anchor.

3 / 5

Completeness

The description gives a clear "what" but no explicit "when/Use when" trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Terms like "draft pull request", "gh-aw", and "cloud agent" are relevant but jargon-heavy and lack the natural synonyms/phrasings a user would say, fitting the some-relevant-keywords anchor.

3 / 5

Distinctiveness Conflict Risk

The niche (gh-aw cloud-agent draft PR publishing) is fairly distinct with only minor overlap risk against the related pr-finisher skill, matching the mostly-distinct anchor.

4 / 5

Total

13

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

github/gh-aw

Path

.github/skills/open-pull-request/SKILL.md

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.