CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

id-photo-tool

Replace an ID photo background color (blue/white/red) and/or add a configurable text watermark when you need compliant ID-photo variants from local JPG/PNG files.

Quality

75%

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 ./scientific-skills/Other/id-photo-tool/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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-structured, executable skill body with working CLI examples and an accurate, present bundle script. The main costs are cross-section repetition of the same constraints and missing example invocations for the configurable watermark options and claimed batch capability.

Suggestions

State each fact once: consolidate the supported colors, no-overwrite, and local-only guarantees into a single section instead of repeating them across Key Features, Implementation Details, and Security Notes.

Add example invocations showing the watermark flags (position, opacity, font size, font color), e.g., "python scripts/id_photo_tool.py add-watermark --input in.jpg --output out.jpg --text '...' --position bottom-right --opacity 0.5", since these are declared configurable but never demonstrated.

Either show how to batch-generate variants (the When to Use section claims it) or remove that claim so the documented workflow matches the skill's scope.

DimensionReasoningScore

Conciseness

Mostly efficient with no tutorials on concepts Claude already knows, but it repeats the same facts across sections: supported colors appear in both "Key Features" ("Supported target colors: `blue`, `white`, `red`") and "Implementation Details" ("Supported target colors: blue, white, red"), the no-overwrite guarantee appears three times ("Does not overwrite the original file", "without modifying the original input file", "does not overwrite the original file by default"), and local-only processing is stated three times ("Local processing only", "No network access is used; all processing is performed locally"). This matches the 'could be tightened' anchor rather than the 'several padded sections' one.

3 / 5

Actionability

Concrete, executable, copy-paste-ready CLI commands for both subcommands ("python scripts/id_photo_tool.py change-bg --input input.jpg --output output.jpg --color blue" and the add-watermark invocation) plus a dependency install command, and the referenced script exists. Minor gap: watermark options declared configurable ("Configurable opacity, font size, and font color", five positions) never appear in an example invocation, so their flag names are unknown.

4 / 5

Workflow Clarity

As a simple single-action CLI skill, the sequence (install pillow/numpy → run one command with explicit --input/--output) is unambiguous and non-destructive by design, so the batch/destruction validation cap does not apply. It falls short of 5 because "When to Use" claims batch generation of multiple variants ("batch-generate multiple variants") yet no batch workflow or example is given, and there is no output verification step.

4 / 5

Progressive Disclosure

Well-organized sections (When to Use, Key Features, Dependencies, Example Usage, Implementation Details) with the single bundle script (scripts/id_photo_tool.py) correctly referenced and present, and no nested references. Over 50 lines and the body inlines the full implementation details and option lists that could live in a reference file, so it is not the ideal 5 for a single-file skill.

4 / 5

Total

15

/

20

Passed

Description

73%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 specific, well-scoped description with concrete actions, explicit file formats, and an explicit trigger clause. Its main weaknesses are the second-person "when you need" phrasing (penalized per rubric voice rules) and limited synonym/trigger coverage.

Suggestions

Rewrite the trigger in third person to match the rubric's voice rule, e.g., "Use when the user needs compliant ID-photo background changes (blue/white/red) or watermarked variants from local JPG/PNG files."

Add natural synonyms and extensions users would say, such as "passport photo", "profile photo", ".jpg", and ".png", to broaden trigger coverage.

Mention the watermark positions and batch-variant capability referenced in the body so the description's action coverage matches the skill's actual scope.

DimensionReasoningScore

Specificity

The description names the domain ("ID photo") and two concrete actions with parameters ("Replace an ID photo background color (blue/white/red)", "add a configurable text watermark"), matching the '1-2 concrete actions, not comprehensive' anchor; it omits capabilities like watermark positioning and batch generation. Baseline was 4, but the second-person clause "when you need compliant ID-photo variants" triggers the rubric's voice penalty, reducing the score by 1.

3 / 5

Completeness

Both parts are present: a clear what ("Replace an ID photo background color... and/or add a configurable text watermark") and an explicit when clause ("when you need compliant ID-photo variants from local JPG/PNG files"). It falls short of the 5 anchor because the trigger is a single condition rather than varied concrete trigger phrases (e.g., "when the user mentions ID photos, background replacement, or watermarks").

4 / 5

Trigger Term Quality

Good natural keywords: "ID photo", "background color", "watermark", "JPG/PNG", "compliant ID-photo variants" — terms a user would plausibly say. A few common synonyms are missing (e.g., "passport photo", "profile photo", file extensions like .jpg/.png spelled out), which keeps it below the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

Clear niche (ID photo background replacement and watermarking for official submissions) with distinct triggers ("ID photo", "background color", "blue/white/red") and minimal overlap with general image-editing skills; the local-only, compliant-variants framing further separates it.

5 / 5

Total

16

/

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

aipoch/medical-research-skills

Path

scientific-skills/Other/id-photo-tool/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.