CtrlK
BlogDocsLog inGet started
Tessl Logo

upload-screenshot

Upload an existing screenshot, chart, or generated image to the Open-Inspect session

64

Quality

76%

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 ./packages/sandbox-runtime/src/sandbox_runtime/skills/upload-screenshot/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is lean, executable, and well-structured for a simple single-purpose skill, with concrete command examples and clear success criteria. The only minor gap is the absence of an explicit validate/retry feedback loop, which keeps workflow clarity at 4 rather than 5.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: it states the key fact, a command signature, flag list, supported types, and success criteria with no padding or explanation of concepts Claude already knows, so every token earns its place.

5 / 5

Actionability

It provides a fully executable command signature with concrete flags, a copy-paste-ready generated-chart example, and explicit success criteria, covering the common cases with specific, runnable guidance.

5 / 5

Workflow Clarity

The Required Workflow lists a clear sequence (confirm file exists -> run upload-media -> report artifactId) with a guardrail to verify the artifactId was returned, but there is no explicit validate-and-retry feedback loop, so it sits just below the 5 anchor.

4 / 5

Progressive Disclosure

This is a simple single-purpose skill under 50 lines with no external bundle files; content is well-organized into clearly headed sections (Key Fact, When To Use, Command, Success Criteria, Guardrails), which per the rubric's simple-skill exception scores 5.

5 / 5

Total

19

/

20

Passed

Description

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

The description is specific and well-scoped to a clear niche, but it omits an explicit 'Use when...' trigger clause, which caps completeness at 3 per the rubric guidelines. Adding natural trigger phrases and synonyms (e.g. '.png', 'image file') would lift trigger-term quality and completeness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when you already have an image file on disk (.png, .jpg, .webp) and need to upload it for review.'

Include natural user phrasings like 'upload this image' or 'upload the screenshot' to improve trigger-term coverage.

Mention file extensions (.png, .jpg, .webp) in the description to strengthen distinctiveness and keyword match.

DimensionReasoningScore

Specificity

The description names the concrete action ('Upload') and enumerates specific inputs ('screenshot, chart, or generated image') plus the target ('Open-Inspect session'); it stops just short of listing multiple distinct operations, so it sits above the 3 anchor but below fully comprehensive.

4 / 5

Completeness

It clearly states what the skill does (upload an existing image to the Open-Inspect session) but provides no explicit 'Use when...' trigger clause, and the judging guideline caps completeness at 3 when trigger guidance is missing.

3 / 5

Trigger Term Quality

Natural terms like 'screenshot', 'chart', and 'generated image' are present and likely to be said by users, but common synonyms/file extensions (e.g. '.png', 'image file', 'diagram') and the literal phrasing 'upload this image' are absent, leaving a few natural terms missing.

4 / 5

Distinctiveness Conflict Risk

The skill is scoped to uploading pre-existing images to a specific session and is clearly distinct from a broader browser-capture workflow, with only minor overlap risk against related image skills.

4 / 5

Total

15

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
ColeMurray/background-agents
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.