Name: html-to-image
Rating: 52 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

html-to-image

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

Quality

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/html-to-image/SKILL.md

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.

The body delivers strong, executable Membrane CLI guidance with a clear connection-state workflow and feedback loop. It is let down mainly by minor padding (intro paragraph, empty overview) and a slight image-vs-PDF inconsistency in the popular-actions table.

Suggestions

Remove the empty 'HTML to Image Overview' placeholder bullets and trim the introductory paragraph to assume Claude's familiarity.

Reconcile the popular-actions table with the skill's image purpose — it currently leads with PDF-generation actions for an 'HTML to Image' skill.

Fix the step numbering so the referenced 'Step 2' and the '1b' sub-step are explicitly labeled in the connection workflow.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient executable commands, but the introductory paragraph explains the service at a level Claude could infer and the 'HTML to Image Overview' section is filler placeholder bullets ('Conversion Task / Result Image'), matching 'Mostly efficient but includes some unnecessary explanation or could be tightened'; not 4 because the padding is noticeable.	3 / 5
Actionability	It provides concrete, copy-pasteable CLI commands for install, auth, connect, search, run, and proxy with flag tables, matching 'Mostly executable guidance; concrete code or commands with minor gaps'; not 5 because CONNECTION_ID/<actionId> placeholders require substitution and the popular-actions table lists PDF actions for an image skill.	4 / 5
Workflow Clarity	The install→auth→connect→search→run sequence is clear and includes an explicit polling feedback loop over connection states (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), matching 'Clear sequence with most checkpoints present'; not 5 because step numbering is inconsistent (a referenced 'Step 2' and a '1b' are not cleanly labeled).	4 / 5
Progressive Disclosure	No bundle files exist, so this is a single well-organized file with clear section headers and no nested references, matching 'Good structure; most content is appropriately placed; references mostly clear'; not 5 because it exceeds ~50 lines and the proxy-options/action tables could arguably live in a reference file.	4 / 5
	Total	15 / 20 Passed

Description

48%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 includes an explicit 'Use when…' trigger and names a distinct service, but the capability statement ('Manage Images') is too generic to convey what the skill concretely does. Trigger-term coverage lacks the natural verbs and synonyms users would actually say.

Suggestions

Replace 'Manage Images' with concrete capabilities, e.g. 'Convert HTML/CSS to PNG or JPEG images and capture webpage screenshots.'

Add natural trigger phrases and synonyms, e.g. 'Use when the user wants to convert HTML to an image, generate a screenshot of a webpage, or render HTML/CSS to PNG/JPEG.'

Tighten the 'what' so it clearly answers what the skill does, not just the integration domain.

Dimension	Reasoning	Score
Specificity	The description names the domain ('HTML to Image integration') but the only action stated is the generic 'Manage Images', matching the anchor 'Names the domain but actions are minimal or generic'; it does not reach 3 because no concrete capability (e.g. convert, screenshot) is enumerated.	2 / 5
Completeness	An explicit 'Use when the user wants to interact with HTML to Image data' trigger is present, but the 'what' is vague ('Manage Images'), so it sits between anchor 2 (vague what, no when) and anchor 4 (clear what + when); the unclear 'what' keeps it at 3 rather than 4.	3 / 5
Trigger Term Quality	It surfaces the service name 'HTML to Image' and 'Images' but omits natural variations a user would say ('convert HTML to image', 'screenshot', 'generate image'), matching 'Some relevant keywords but missing common variations or synonyms'; not 2 because the service-specific term is more than one generic keyword.	3 / 5
Distinctiveness Conflict Risk	The named service 'HTML to Image' gives it a clear niche with minimal conflict risk, matching 'Mostly distinct; minor overlap risk'; not 5 because 'Manage Images' is generic and could weakly overlap with general image-handling skills.	4 / 5
	Total	12 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/html-to-image/SKILL.md
Commit: f484c82

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.