CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gh-attach

Upload a frame the `visuals` skill rendered, or a video, to a GitHub pull request or issue with `gh --attach`, in the description or as a comment. Use for "attach this image to the PR", "put this file in the issue", "put the image under Evidence in the open PR". A raw screenshot goes through `visuals` first.

Quality

91%

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.

Excellent operational content: fully executable commands, explicit verification with feedback loops, and nuanced gh-specific gotchas. Minor room to trim duplicated routing guidance and shell explanations, and to split edge-case procedures into reference files.

DimensionReasoningScore

Conciseness

The body is dense and gh-specific throughout (acceptance table, pairing semantics, \r handling, publish-no-undo warnings), but the Evidence-placement routing is stated twice (intro and "Description, for PR evidence") and it over-explains shell behavior Claude knows ("the quotes are what keep the shell from reading that `#` as a comment"). Not 5 because of these minor trims; not 3 because nearly all content is non-obvious and earns its place.

4 / 5

Actionability

Every workflow ships copy-paste-ready commands: `gh pr edit <pr> --attach ...`, the awk placement pipeline, `printf ... | gh pr create --body-file -`, verification greps, and the `<img>` sizing snippet, covering comments, PR creation, existing descriptions, and multi-image cases. Not 4 because there are no gaps in executable detail for the common cases.

5 / 5

Workflow Clarity

Clear sequence with explicit validation checkpoints and feedback loops: confirm files and destination before publishing, upload in one command, then Verify counts `user-attachments` and leftover local paths, with recovery paths (short count → re-attach only the missing; above zero → rewrite the body rather than uploading a duplicate) and a result-to-action table. The destructive/batch cap does not apply since validation is thorough.

5 / 5

Progressive Disclosure

Sections are well-organized with clear cross-references ("**Verify** below", "**Place an image in an existing description**"), but this is a ~170-line self-contained document, above the under-50-line simple-skill exception, and the placement recipe and Sizing sections are peripheral procedures that could live in one-level-deep reference files. Not 5 because there is no content split at all; not 3 because what is inline is well-structured and nothing is buried.

4 / 5

Total

18

/

20

Passed

Description

92%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 description: concrete actions, explicit trigger phrases, and clear disambiguation from the visuals skill. The only gap is a few natural synonyms (upload, post, add) that users might say instead of attach/put.

DimensionReasoningScore

Specificity

"Upload a frame the `visuals` skill rendered, or a video, to a GitHub pull request or issue with `gh --attach`, in the description or as a comment" plus "A raw screenshot goes through `visuals` first" lists multiple concrete actions (upload frames or videos, to PRs or issues, as description embed or comment, route raw screenshots) with no gaps in coverage of the skill's scope. It is not 4 because there are no missing actions the skill performs.

5 / 5

Completeness

The "what" is explicit (upload a rendered frame or video to a GitHub PR or issue with `gh --attach`, in the description or as a comment) and the "when" is explicit via "Use for" followed by three concrete trigger phrases. This matches the anchor-5 pattern of both what and when with concrete triggers; not 4 because the when-clause is already maximally explicit.

5 / 5

Trigger Term Quality

Quoted natural phrases "attach this image to the PR", "put this file in the issue", "put the image under Evidence in the open PR", and "screenshot" are phrasings users would actually say, but common synonyms like "upload", "post", or "add this to the PR" are absent. It is not 5 because coverage of natural synonyms is incomplete; it is not 3 because several natural user phrasings are explicitly present.

4 / 5

Distinctiveness Conflict Risk

The niche is clear (attaching images/videos to GitHub PRs/issues) with distinct quoted triggers, and "A raw screenshot goes through `visuals` first" explicitly disambiguates from the adjacent `visuals` skill. Minimal conflict risk; not 4 because the boundary with the closest related skill is already stated.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

relative_links

Relative link issues: 1 missing, 3 suspicious

Warning

Total

14

/

16

Passed

Repository

aabuhijleh/abed-hub

Path

skills/gh-attach/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.