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.

61

Quality

72%

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

77%

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 executable code and a well-sequenced, validated workflow, but it is somewhat verbose with repeated fidelity phrasing and keeps most material inline rather than progressively disclosing it to separate references.

Suggestions

Deduplicate the fidelity-lock instructions so the canonical phrasing lives in one place and the hard rules/checklist reference it rather than restating it.

Consider moving the full image-manifest.json example and the ecommerce-gallery.html spec into a reference file, keeping SKILL.md a leaner overview.

DimensionReasoningScore

Conciseness

Mostly efficient and free of Claude-known concept explanations, but the fidelity-lock phrasing and several hard rules repeat content already covered in Step 3 and the checklist, so it could be tightened.

2 / 3

Actionability

Provides fully executable POSIX bash for the media generate/wait loop, a concrete JSON manifest example, and a specific slot table — copy-paste ready with real env vars and flags.

3 / 3

Workflow Clarity

Steps 0-7 are clearly sequenced with explicit gates (Step 0 reference-mode check), exit-code feedback in the dispatch loop, and a pre-handoff checklist run, satisfying the batch-operation validation requirement.

3 / 3

Progressive Disclosure

A resource map and a clearly signaled one-level reference (references/checklist.md, verified to exist) are present, but the body is a fairly long monolithic block with the manifest and gallery specs inline rather than split out.

2 / 3

Total

10

/

12

Passed

Description

67%

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 is specific and distinct, clearly conveying what the skill produces, but it omits an explicit 'Use when...' trigger clause and has only moderate natural-keyword coverage, which limits completeness and trigger quality.

Suggestions

Add an explicit 'Use when...' clause naming the triggering situations (e.g., when the user wants ecommerce main/feature/lifestyle images from a real product photo).

Broaden natural trigger terms in the description itself to include common variations users say, such as 'packshot', 'product photos', or platform names.

DimensionReasoningScore

Specificity

Names multiple concrete actions: 'generating a compact set of product-faithful main, feature, and lifestyle images from real product reference photos' lists the specific image types it produces.

3 / 3

Completeness

The 'what' is clearly stated, but there is no explicit 'Use when...' trigger clause; the 'when' is only implied by 'V1 requires uploaded product imagery', which caps completeness at 2 per the rubric.

2 / 3

Trigger Term Quality

Includes relevant natural terms ('ecommerce image workflow', 'product reference photos', 'main, feature, and lifestyle images') but lacks common variations such as platform names or 'packshot'; coverage is moderate rather than broad.

2 / 3

Distinctiveness Conflict Risk

The narrow 'reference-product ecommerce image workflow' framing carves a clear niche tied to real reference photos, making it unlikely to trigger for unrelated skills.

3 / 3

Total

10

/

12

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.