CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

unsplash-integration

Integration skill for searching and fetching high-quality, free-to-use professional photography from Unsplash.

Quality

60%

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 ./skills/unsplash-integration/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 skill is well-sectioned and appropriately sized, but its core instruction stops at the level of vague direction: no API endpoint, code sample, or auth detail is ever given, and a large fraction of the text is marketing prose. An agent reading it would know the intent but not how to execute the download step.

Suggestions

Replace 'Use the Unsplash API or direct URL' with a concrete, executable example: the actual search endpoint (e.g., https://api.unsplash.com/search/photos?query=...&client_id=...) or a source.unsplash.com URL pattern, including the required access key.

Cut the marketing padding — the intro paragraph, the Context section, and the 'ABSOLUTE MANDATE' rule — to roughly halve the body while keeping the When to Use triggers, the workflow, and the performance rule.

Add a verification step to the workflow (e.g., confirm the downloaded image dimensions match the requested parameters) to give the sequence a checkpoint.

DimensionReasoningScore

Conciseness

Multiple sections are marketing padding rather than instruction: the intro ('essential for elevating the visual tone of any project'), the entire Context section ('breathtaking imagery... premium, modern visual aesthetic'), and adjective-heavy rules ('ABSOLUTE MANDATE', 'stunning visual impact'). This is 'noticeably verbose; several unnecessary explanations or padded sections' — it is not a 3 because the padding spans whole sections, not minor trimmable instances.

2 / 5

Actionability

There is some concrete guidance — the URL parameter example '?w=1600&q=85&fit=crop' and example search keywords like 'neon cyberpunk street aesthetics' — but the core instruction 'Use the Unsplash API or direct URL to source the imagery' provides no endpoint, no code, no command, and no mention of the required API access key. This matches 'some concrete guidance but incomplete; missing key details' rather than 4, which requires mostly executable guidance.

3 / 5

Workflow Clarity

A coherent 4-step sequence exists (Search Intentionally, Filter, Download via API, Dynamic Resizing), but there are no validation or verification checkpoints (e.g., confirming the download succeeded or the image fits), and each step is described abstractly. This fits anchor 3 ('steps listed but validation gaps; sequence present but checkpoints missing or implicit'), not 4, since the steps also lack executable specifics.

3 / 5

Progressive Disclosure

The body is under 50 lines, needs no external references, and is organized into clear, well-labeled sections (Context, When to Use, Execution Workflow, Strict Rules) with no content that belongs in separate files. Per the rubric guideline for simple skills under 50 lines with no external-reference needs, well-organized sections alone merit a 5.

5 / 5

Total

13

/

20

Passed

Description

53%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 gives a clear, third-person statement of what the skill does with a distinctive brand anchor, but it omits any explicit 'when to use' guidance and lacks common natural trigger terms like 'photos', 'images', or 'stock photos'. These gaps leave it serviceable but under-specified for reliable triggering.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks for photos, images, stock photography, hero images, or visual assets, or mentions Unsplash.'

Add natural synonyms and variations users would say (photos, images, pictures, stock photos, hero images) to broaden trigger term coverage.

Optionally enumerate one or two more concrete capabilities (e.g., dynamic resizing via URL parameters) to raise specificity.

DimensionReasoningScore

Specificity

The description names the domain ('professional photography from Unsplash') and exactly two concrete actions ('searching and fetching'), matching the anchor for 1-2 concrete actions without comprehensive coverage. It is not a 4 because no additional capabilities (e.g., resizing, API details) are listed, and not a 2 because the actions stated are concrete rather than generic.

3 / 5

Completeness

It clearly answers 'what' ('searching and fetching high-quality, free-to-use professional photography from Unsplash') but contains no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 2 because the 'what' is clear, not vague.

3 / 5

Trigger Term Quality

It includes some relevant keywords ('Unsplash', 'photography', 'searching', 'fetching') but misses the natural phrases users would say such as 'photos', 'images', 'stock photos', 'pictures', or 'hero image'. This matches the anchor 'some relevant keywords but missing common variations or synonyms' rather than level 4, which requires broad natural-term coverage.

3 / 5

Distinctiveness Conflict Risk

The brand name 'Unsplash' establishes a clear niche with mostly distinct triggers and minimal conflict risk, but 'high-quality... professional photography' leaves minor overlap risk with generic image/stock-photo skills. This fits anchor 4 ('mostly distinct; minor overlap risk') better than 5, whose examples have fully distinct trigger phrases.

4 / 5

Total

13

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

skills/unsplash-integration/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.