CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

attach-media

Uploads local screenshots and recordings to GitHub and embeds them in a PR or issue body or comment as inline-rendering user-attachments URLs, via `gh --attach` with a curl fallback; never writes placeholders. Triggers on "attach screenshots to the PR", "upload this recording to the PR", "/attach-media".

Quality

86%

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

77%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 well-engineered operational skill: tight, command-dense, with an explicit preflight checklist, fallback ladder, and a verify-and-report feedback loop. Its main defect is bundle integrity — the two rules/ files carrying the full upload and body-region procedures are referenced but missing, which also leaves key paths not fully executable from the shipped skill.

Suggestions

Add the missing ./rules/upload-ladder.md and ./rules/body-region.md files to the bundle (or inline their essential procedures), since three of the four referenced paths in the body do not resolve.

Spell out one complete rung-1 invocation in the body (e.g., gh pr edit <n> --body-file <f> --attach <file>) so the primary upload path is copy-paste ready even without the ladder file.

Tighten the check-4 table cell by moving the light/dark-pair and contact-sheet edge cases into a short list or the upload-ladder reference, reducing the dense nested parenthetical.

DimensionReasoningScore

Conciseness

The body is dense and operational — preflight table, exact ffmpeg commands, rung table, region template, report format — with no explanation of concepts Claude already knows. It is not a 5 because a few rationale asides could be trimmed ('It is ~20× smaller...', 'An absent region is honest; a placeholder claims work that never happened') and the check-4 cell packs light/dark-pair and contact-sheet edge cases into one long nested parenthetical that could be tightened.

4 / 5

Actionability

Commands are concrete and mostly copy-paste ready (three full ffmpeg invocations, the rung-1 gh flags, the curl endpoint, the region template with exact delimiters). It is not a 5 because full rung-1/rung-2 command syntax and the --to urls output procedure are delegated to rules/upload-ladder.md and rules/body-region.md, which are absent from the bundle, so the primary paths are not fully executable from what is shipped.

4 / 5

Workflow Clarity

A clear four-step sequence (preflight → upload ladder → write region → verify/report) with a per-file failure checklist, explicit on-failure actions at every stage, a dry-run mode, and a post-write verification loop (re-read region, confirm one URL per file and no local path, remove and downgrade failures). It is not a 4 because validation checkpoints are explicit and complete, including the mandatory look-at-every-file check for a batch (1–50 file) operation.

5 / 5

Progressive Disclosure

The design is right — lean overview delegating detail to well-labeled one-level-deep files ('Full procedure:', 'Full contract:', 'Rationale:') — but scored against the actual bundle, three of the four referenced paths (rules/upload-ladder.md, rules/body-region.md, and its § --to urls anchor) do not exist; only references/rationale.md resolves. It is not a 4 because majority-dangling references are more than minor organization gaps, leaving the delegated detail unavailable anywhere.

3 / 5

Total

16

/

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: third-person, dense with concrete actions, mechanisms (gh --attach, curl fallback), an explicit no-placeholders constraint, and verbatim natural-language trigger phrases. The only weakness is slightly narrow trigger coverage — synonyms, issue-phrased variants, and file extensions are missing.

DimensionReasoningScore

Specificity

"Uploads local screenshots and recordings to GitHub and embeds them in a PR or issue body or comment as inline-rendering user-attachments URLs, via `gh --attach` with a curl fallback; never writes placeholders" lists multiple concrete actions (upload, embed in body or comment) with the exact mechanism, fallback, and an explicit negative constraint — zero vague language, matching the comprehensive-coverage anchor. It is not a 4 because no capability gap remains for this skill's niche, and it uses third person throughout.

5 / 5

Completeness

The 'what' is explicit and detailed (upload + embed as inline-rendering user-attachments URLs via gh --attach with curl fallback) and the 'when' is given as three verbatim trigger phrases ('Triggers on "attach screenshots to the PR"...'), which is the equivalent-explicit-trigger guidance the rubric requires. It is not a 4 because the when-clause is already maximally concrete, not merely 'could be more explicit'.

5 / 5

Trigger Term Quality

The explicit triggers 'attach screenshots to the PR', 'upload this recording to the PR', and '/attach-media' are phrases a user would naturally say, giving good keyword coverage. It falls short of the 5 anchor because synonyms (add/put/embed images), issue-oriented phrasings, and file extensions (png, mp4, gif) are absent.

4 / 5

Distinctiveness Conflict Risk

"Uploads local screenshots and recordings to GitHub... embeds them in a PR or issue body or comment" carves a clear niche (GitHub PR/issue media attachment via user-attachments URLs) with distinct, context-anchored triggers, so minimal conflict risk with other skills. It is not a 4 because the trigger phrases are specific to this exact task rather than overlapping a broader category.

5 / 5

Total

19

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 3 missing

Warning

Total

13

/

16

Passed

Repository

mthines/agent-skills

Path

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