CtrlK
BlogDocsLog inGet started
Tessl Logo

gh-attach

Attach an image or video to a GitHub pull request or issue with `gh --attach`, as a comment or in the description. Use for "add a screenshot to the PR", "put this image in the issue", "show before/after in the description".

76

Quality

97%

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

100%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.

An exemplary single-purpose skill body: executable commands, an acceptance table, result handling, and a verification section with feedback loops for an irreversible publish operation. It is concise, well-structured, and needs no external references.

DimensionReasoningScore

Conciseness

Lean throughout: assumes Claude knows what gh/PRs are and spends tokens only on non-obvious gh-specific behavior (alt-text `#` quoting, path-pairing rules, untrusted-body handling). The `gh 2.99` version note is a genuine requirement rather than padding.

5 / 5

Actionability

Every section gives copy-paste-ready `gh` commands covering the common cases (comment, description edit, create, in-body placement, verify), with exact flags and absolute-path conventions.

5 / 5

Workflow Clarity

Sequences a publish-and-no-undo operation with an upfront acceptance table, a result-decision table, and an explicit Verify section with count checks and feedback loops (re-attach missing files, rewrite a misplaced reference rather than re-uploading).

5 / 5

Progressive Disclosure

No bundle files are needed; the body is self-contained and organized under clear section headers (What it accepts, Attaching, Read the result, Verify, Sizing), giving easy navigation with no nested references.

5 / 5

Total

20

/

20

Passed

Description

95%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 tight, well-targeted description that states concrete capabilities and gives natural-language trigger phrases a user would actually say. It clearly answers both what the skill does and when to invoke it, with low conflict risk.

DimensionReasoningScore

Specificity

Names concrete actions ('Attach an image or video', 'as a comment or in the description', 'with `gh --attach`') across PR/issue targets, but stops short of enumerating create-vs-edit or multi-file behavior, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what (attach image/video to a PR or issue via gh --attach, as comment or description) and when (a 'Use for' clause with concrete trigger phrases).

5 / 5

Trigger Term Quality

Quotes three natural user phrases ('add a screenshot to the PR', 'put this image in the issue', 'show before/after in the description') covering synonyms and the realistic ways users ask for this.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (GitHub PR/issue media attachment via `gh --attach`) with distinct triggers and minimal overlap with other 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.

Validation14 / 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, 1 suspicious

Warning

Total

14

/

16

Passed

Repository
aabuhijleh/abed-hub
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.