CtrlK
BlogDocsLog inGet started
Tessl Logo

upload-photo

Attach a screenshot/image/video to a PR or issue, or embed an image in a GitHub comment.

61

Quality

73%

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 ./.opencode/skills/upload-photo/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

80%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 tight, highly actionable body of executable gh CLI commands that covers attach, embed, and URL retrieval. Its only real gap is the lack of an explicit validation checkpoint for the batch attach operation, which caps workflow clarity.

Suggestions

Add an explicit verify step after batch attaches, e.g. re-fetch the comment and confirm all expected assets were posted before proceeding.

Note that `brew upgrade gh` is macOS-only and offer a cross-platform alternative (e.g. the gh CLI installer or package manager) for non-mac users.

Consider folding the version requirement into a brief "Requirements" note so the time-sensitive detail is clearly separated from the action steps.

DimensionReasoningScore

Conciseness

Lean and free of concept padding, with every line actionable or a useful note; the time-sensitive "GitHub CLI 2.99 or newer" version line is a minor conciseness cost that keeps it just below 5.

4 / 5

Actionability

Provides fully executable, copy-paste-ready commands for attaching, embedding, and retrieving the asset URL, covering the common cases with concrete flags and placeholders.

5 / 5

Workflow Clarity

A rough sequence exists (check/upgrade gh, attach or embed, read back the URL), but this is a batch operation (up to 50 files) with no explicit validation checkpoint, so workflow clarity is capped at 3 per the guidelines.

3 / 5

Progressive Disclosure

Under 50 lines with no need for external references, yet well organized into short labeled sections, so it earns 5 under the simple-skill exception.

5 / 5

Total

17

/

20

Passed

Description

66%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 concise, concrete description that names specific actions and natural trigger terms within a distinctive GitHub niche. Its main weakness is the absence of an explicit "Use when..." trigger clause, which caps completeness at 3.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to attach a screenshot or image to a GitHub PR/issue or embed one in a comment."

Broaden trigger terms with synonyms and extensions users actually say (photo, picture, .png, .jpg, attachment, upload).

Mention additional concrete actions if applicable (e.g. retrieving the uploaded asset URL) to lift specificity toward 5.

DimensionReasoningScore

Specificity

Names concrete actions ("Attach a screenshot/image/video", "embed an image in a GitHub comment") with specific targets and media types, but coverage stops at two actions rather than being comprehensive.

4 / 5

Completeness

The "what" is clear, but there is no "Use when..." clause or equivalent explicit trigger guidance, so per the judging guidelines completeness is capped at 3.

3 / 5

Trigger Term Quality

Includes natural terms a user would say (screenshot, image, video, PR, issue, GitHub comment), but misses synonyms (picture, photo, attachment) and file extensions (.png, .jpg) needed for a 5.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (GitHub PR/issue image attachment via gh CLI) with distinct triggers; minor overlap risk with general image-handling skills, and the missing trigger clause keeps it just below 5.

4 / 5

Total

15

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
different-ai/openwork
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.