pixelbin-media

Generate and edit images and videos with an 85+ API portfolio and build visually appealing website pages via Pixelbin.

Quality

47%

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/pixelbin-media/SKILL.md

Quality

Content

35%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a thin catalogue stub that advertises an upstream skill rather than providing usable instructions: it is organized and brief but offers no executable guidance and pushes the real workflow to an external README. Strengthening the local install/invocation steps would address the lowest dimensions.

Suggestions

Replace the vague "install the upstream bundle" instruction with concrete, copy-paste-ready commands (e.g., the exact clone path and destination in the skills directory) to raise actionability.

Provide an explicit, validated workflow sequence with checkpoints instead of deferring to "inspect the upstream README for exact paths."

Remove the verbatim duplicate of the frontmatter description in the "What it does" section, or replace it with genuinely new detail, to improve conciseness.

Dimension	Reasoning	Score
Conciseness	The body is short and does not explain concepts Claude already knows, but the "What it does" section repeats the frontmatter description verbatim and the "How to use" prose could be tightened. It is not 3 because of the duplicated description and mild filler, and not 1 because it is not padded or verbose.	2 / 3
Actionability	The only command is `open https://github.com/pixelbin-dev/skills`, which merely opens a URL, and the real instruction is the vague "install the upstream bundle into your active agent's skills directory" with no concrete steps. It describes rather than instructs and offers no copy-paste-ready guidance, matching the score-1 anchor.	1 / 3
Workflow Clarity	A recognizable two-step sequence exists (install the upstream bundle, then invoke by name or trigger), but it is high-level and defers actual steps to "inspect the upstream README for exact paths" with no validation or checkpoints. It is not 3 because the sequence is fuzzy and unvalidated, and not 1 because some ordered steps are present.	2 / 3
Progressive Disclosure	The content is organized into clear sections (What it does, Source, How to use) for a short skill, but the sole reference is an external GitHub URL that itself requires further indirection ("inspect the upstream README for exact paths"). It is not 3 because the reference is external with nested indirection rather than a well-signaled one-level-deep local file, and not 1 because sections are organized and there is only a single pointer.	2 / 3
	Total	7 / 12 Passed

Description

60%

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 names concrete capabilities and anchors them to the Pixelbin brand, but it omits any explicit "Use when..." trigger guidance, which caps completeness and leaves distinctiveness only moderate. Adding a usage-trigger clause would lift the two weakest dimensions.

Suggestions

Append a "Use when..." clause naming natural triggers (e.g., image/video generation or editing, CDN media transforms, building visual web pages) to raise completeness and trigger_term_quality.

Include common user phrasings ("resize image", "optimize media", "image CDN") so the description surfaces terms users actually say.

Tie distinctiveness to a concrete capability unique to Pixelbin (e.g., real-time URL-based media transforms) rather than the generic "generate and edit" framing.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — "Generate and edit images and videos" and "build visually appealing website pages" — rather than vague language. It is not below 3 because it enumerates several distinct, specific capabilities rather than naming only a domain.	3 / 3
Completeness	It clearly answers "what" (generate/edit images, videos, website pages) but provides no explicit "when should Claude use it" guidance. Per the judging guidelines, a missing "Use when..." clause caps completeness at 2, so it cannot reach 3.	2 / 3
Trigger Term Quality	It includes some natural terms users would say ("images and videos", "website pages") plus the brand "Pixelbin", but lacks common variations and a "Use when..." trigger clause. It is not 3 because coverage of natural trigger phrasings is incomplete, and not 1 because the keywords present are user-facing rather than jargon.	2 / 3
Distinctiveness Conflict Risk	The "via Pixelbin" brand anchor and "85+ API portfolio" give it a niche, but "generate and edit images and videos" is broad enough to overlap with other media skills. It is not 3 because the description alone does not surface distinct triggers that reliably disambiguate it from generic image-generation skills.	2 / 3
	Total	9 / 12 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: nexu-io/open-design
Path: skills/pixelbin-media/SKILL.md
Commit: a2ba3ee

Reviewed: about 13 hours 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.