CtrlK
BlogDocsLog inGet started
Tessl Logo

ecommerce-image-workflow

Reference-product ecommerce image workflow for generating a compact set of product-faithful main, feature, and lifestyle images from real product reference photos. V1 requires uploaded product imagery and intentionally defers brief-only concept generation and platform-specific batch exports.

65

Quality

79%

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

Quality

Content

88%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 content is a well-sequenced, highly actionable workflow with executable dispatch code and explicit validation checkpoints; its main limitation is that most reference-grade detail lives inline in SKILL.md rather than being split into one-level-deep supporting files.

DimensionReasoningScore

Conciseness

The body is largely lean, avoids explaining concepts Claude already knows, and uses tight sections with executable blocks; a few prompt-template passages could be trimmed or consolidated, keeping it just below the leanest anchor.

4 / 5

Actionability

Provides fully executable, copy-paste-ready bash dispatch code with error handling, a concrete image-manifest.json schema, and specific slot prompt instructions covering the common three-slot case.

5 / 5

Workflow Clarity

Steps 0-7 are explicitly sequenced with validation checkpoints (Step 0 reference-mode guard that stops, dispatch loop with error/retry handling, checklist.md run before handoff), satisfying the feedback-loop expectation for this batch operation.

5 / 5

Progressive Disclosure

A resource map and a clearly signaled one-level-deep reference (references/checklist.md run before handoff) give good navigation, but the bulk of prompt/manifest content is inlined in SKILL.md rather than split out, leaving minor organization gaps.

4 / 5

Total

18

/

20

Passed

Description

70%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 clearly states what the skill produces and carves out a distinct niche, but it omits an explicit "Use when..." trigger clause, which caps completeness and slightly weakens trigger guidance within the description text itself.

Suggestions

Add an explicit trigger clause to the description, e.g. "Use when generating an ecommerce image set (main, feature, lifestyle) from uploaded product reference photos."

Surface a couple of natural marketplace terms (e.g. packshot, Amazon/Shopify product images) inside the description body rather than only in the triggers list.

Consider naming the concrete actions beyond "generating" (e.g. compose, dispatch, manifest) to lift specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the domain and several concrete deliverables ("main, feature, and lifestyle images" from "real product reference photos"), but the action vocabulary is essentially a single verb ("generating"), leaving minor coverage gaps versus a fully comprehensive action list.

4 / 5

Completeness

The "what" is clear (generate a compact product-faithful image set from reference photos), but there is no explicit "Use when..." clause or equivalent trigger guidance in the description; per the rubric this caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural terms users would say ("ecommerce image workflow", "product-faithful", "main, feature, and lifestyle images", "reference photos"); a few common marketplace synonyms (e.g. Amazon/Shopify packshot) appear only in the separate triggers field rather than the description itself.

4 / 5

Distinctiveness Conflict Risk

The "reference-product ecommerce image workflow" niche is specific and the V1 boundary (requires uploaded imagery, defers brief-only concepts) makes it clearly distinguishable from generic image-generation skills with minimal conflict risk.

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.

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
nexu-io/open-design
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.