CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gh-attach

Attach an image or video that already exists 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". To take or annotate the image first, use `visuals`.

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.

A tightly written, highly actionable body whose commands are executable as written and whose verification/feedback loop for the destructive upload operation is exemplary. The main weaknesses are the entirely-inline structure with a dangling reference to a script the bundle does not actually ship.

Suggestions

Either ship the referenced `gh-attach shot` script in the bundle (e.g., scripts/) or remove/correct the claim that this package ships it.

Consider moving the Sizing and Verify edge-case detail into a references/ file to shorten SKILL.md toward a lean overview.

Fold the version requirement ("gh 2.99 or later") into a prerequisites line or compatibility note rather than a bare sentence, so it ages more gracefully.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence throughout (no explanations of gh, GitHub, or markdown basics) and every section covers genuinely non-obvious gotchas, but a bare version requirement ("Needs `gh` 2.99 or later") and a few tightly-packed passages could be trimmed or restructured, keeping it just below the leanest anchor.

4 / 5

Actionability

Fully executable, copy-paste-ready commands cover the common cases end to end: attaching in one command, commenting, placing an image under an existing `## Evidence` heading via a working awk recipe, verifying embed counts, and resizing with an `<img>` tag.

5 / 5

Workflow Clarity

The workflow has explicit validation checkpoints (the Verify section, with count-based checks for both embeds and leftover local paths) and clear feedback loops (short count → re-attach only the missing; misplaced reference → hand-rewrite rather than re-upload), plus a result table mapping exit-code/URL combinations to next actions.

5 / 5

Progressive Disclosure

Sections are clear and well cross-referenced (Verify, Sizing, Place an image in an existing description), but all ~167 lines live inline in SKILL.md with no splitting, and the body references a shipped script `gh-attach shot` that is not present in the bundle (no scripts/ directory), leaving minor organization gaps.

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 precise, well-scoped description with concrete capabilities, explicit trigger phrases, and clean boundary handling against the related `visuals` skill. The only gap is a few natural synonyms (e.g., "screenshot") that would round out trigger coverage.

Suggestions

Add one or two common synonyms to the trigger list, e.g. "screenshot" or "add this image to the PR", to broaden natural-language matching.

Optionally mention supported media (png/jpg/gif/svg video) briefly so media-type requests surface the skill.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — attaching an existing image or video to a GitHub PR or issue via `gh --attach`, in the description or as a comment — with comprehensive coverage of targets and placements, matching the top anchor.

5 / 5

Completeness

It explicitly answers both what (attach an existing image/video to a PR or issue with `gh --attach`, in the description or as a comment) and when (a "Use for" clause with concrete user phrasings), plus boundary guidance routing image creation to the `visuals` skill.

5 / 5

Trigger Term Quality

Natural quoted triggers like "attach this image to the PR" and "put this file in the issue" are strong, but common synonyms such as "screenshot", "add an image", or file extensions (png, jpg) are missing, landing on 'good coverage; a few natural terms missing' rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

A clear niche (GitHub PR/issue attachment via `gh --attach`) with distinct trigger phrasings, and explicit delegation of image-taking/annotation to `visuals` minimizes overlap with related skills.

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.