CtrlK
BlogDocsLog inGet started
Tessl Logo

htmlcss-to-image

HTML/CSS to Image integration. Manage Images. Use when the user wants to interact with HTML/CSS to Image data.

55

Quality

63%

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/htmlcss-to-image/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 highly actionable with concrete commands and a useful action catalog, and is reasonably well structured, but it is mildly verbose in spots and lacks validation checkpoints for its destructive and batch image operations.

Suggestions

Add an explicit validation/confirmation step before destructive and batch actions (e.g. 'List images and confirm IDs with the user before running delete-image or delete-batch-images').

Trim low-value prose such as 'Use action names and parameters as needed.' and the 'Developers and designers use it…' sentence to improve token efficiency.

Fix the step labeling inconsistency (the implicit 'Step 1' versus the referenced 'Step 2' and orphan '1b' header) so the connection sequence is unambiguous.

DimensionReasoningScore

Conciseness

The body is mostly efficient with copy-paste command blocks, but includes light padding such as the intro ('Developers and designers use it to generate previews or thumbnails of web content.') and the filler line 'Use action names and parameters as needed.' that could be trimmed.

3 / 5

Actionability

It provides fully executable, copy-paste-ready commands for the full lifecycle (install, login, connection ensure, action list/run, request proxy) plus a concrete popular-actions table with specific action keys covering the common cases.

5 / 5

Workflow Clarity

The connection workflow is sequenced with polling and state checkpoints (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but the skill surfaces destructive and batch actions (delete-image, delete-batch-images, create-batch-images) with no validation or verification step before running them, capping workflow clarity at 3 per the batch/destruction rule.

3 / 5

Progressive Disclosure

No bundle files exist, so all content lives in one well-organized file with clear section headers and no nested references; structure is good, but at ~160 lines with an inline actions table there are minor organization gaps rather than the lean overview-plus-references ideal.

4 / 5

Total

15

/

20

Passed

Description

57%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 correctly answers both what the skill does and when to use it and is tied to a distinct named service, but its action language is generic ('Manage Images') and its trigger coverage lacks natural synonyms a user would actually say.

Suggestions

Replace the generic 'Manage Images' with concrete actions, e.g. 'Create, list, and delete images from HTML/CSS or URLs'.

Add natural trigger synonyms such as 'render HTML to an image', 'screenshot a webpage', or 'convert HTML/CSS to PNG'.

Make the 'when' clause more specific than 'interact with HTML/CSS to Image data' — e.g. 'Use when the user wants to convert HTML/CSS or a URL into a static image.'

DimensionReasoningScore

Specificity

The description names the domain ('HTML/CSS to Image integration') but its only action phrase is the generic 'Manage Images', which is minimal and non-concrete rather than listing specific actions like create/list/delete images.

2 / 5

Completeness

Both halves are present — a 'what' ('HTML/CSS to Image integration. Manage Images.') and a 'when' ('Use when the user wants to interact with HTML/CSS to Image data.'), but the 'when' clause is generic and lacks concrete trigger phrases, so it falls short of a 5.

4 / 5

Trigger Term Quality

It surfaces the product name 'HTML/CSS to Image' and 'Images' as triggers, but misses natural synonyms and variations users would say such as 'render HTML to image', 'screenshot a webpage', or 'HTML to PNG'.

3 / 5

Distinctiveness Conflict Risk

Tying triggers to the specific named service 'HTML/CSS to Image' gives it a clear niche with minimal conflict risk, though the generic 'Manage Images' phrasing leaves minor overlap with general image-management skills.

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.

Validation15 / 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
membranedev/application-skills
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.