CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

muapi-couple-grid-creator

Create a stylized 6-box grid featuring a couple in various romantic poses and outfits, with each pose framed inside a unique cardboard box packaging.

Quality

74%

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 ./library/visual/couple-grid-creator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 a lean, well-structured, single-purpose recipe with genuinely executable guidance: an input gate, the exact model and prompt, auth and fallback handling, and clear sections. Remaining gaps are minor — a literal copy-paste command example, an aspect-ratio decision rule, and failure-handling guidance.

DimensionReasoningScore

Conciseness

The ~48-line body is lean — an inputs table, one generation step with the full prompt, and brief agent notes. Minor over-explanation exists: the description is restated verbatim in bold under the title, and the generic 'Notes for the Executing Agent' boilerplate (curl fallback, placeholder substitution) is standard recipe scaffolding. Not 5 because of that small padding; not 3 because nothing explains concepts Claude already knows.

4 / 5

Actionability

Concrete guidance is present: the exact CLI ('muapi image edit' with model='qwen-image-edit-plus'), the complete image-edit prompt, aspect ratio, an auth check ('muapi auth configure' if MUAPI_API_KEY is unset), and a curl fallback with polling. Not 5 because no literal copy-paste invocation with the prompt inline is shown — the command is described structurally ('model=...') rather than given as an executable line, leaving a minor gap.

4 / 5

Workflow Clarity

The sequence is clear and gated: check for 'couple_image', ask the user to upload a photo if missing, generate the grid, present it. Not 5 because there are minor validation gaps — no guidance if generation fails or the output doesn't match the 6-box layout, and the '1:1 or 4:5' aspect ratio choice is left ambiguous. Not 3 because this is a non-destructive single-action skill with an explicit input checkpoint, so the sequence is unambiguous.

4 / 5

Progressive Disclosure

There are no bundle files (references/, scripts/, assets/ all absent), the skill is under 50 lines, and the body is organized into clearly labeled sections (Inputs, Steps, Trigger Keywords, Notes) with all content appropriately inline for a single-task skill — matching the simple-skill exception for a top score.

5 / 5

Total

17

/

20

Passed

Description

58%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 and concretely communicates what the skill produces, with a distinctive niche that minimizes conflict risk. Its main weakness is the absence of any 'when to use' guidance and natural trigger terms in the description itself, leaving completeness and trigger-term quality at middling levels.

Suggestions

Append a 'Use when...' clause, e.g. 'Use when the user wants a couple photo grid, packaging-style romantic portraits, or a box-framed couple collage' — this directly lifts completeness from 3 to 4-5.

Fold 2-3 natural trigger synonyms into the description (e.g. 'couple photo grid', 'box collage', 'packaging portrait') instead of keeping them only in the body's Trigger Keywords section.

Mention the required input (a clear photo of the couple) in the description so users can immediately tell whether they can use the skill.

DimensionReasoningScore

Specificity

The description gives a concrete, detailed rendering of the output ('Create a stylized 6-box grid featuring a couple in various romantic poses and outfits, with each pose framed inside a unique cardboard box packaging'), but describes a single action with attributes rather than several distinct actions, so it sits between the '1-2 concrete actions' and 'several specific actions' anchors — noticeably above the midpoint.

4 / 5

Completeness

It has a clear 'what' (create a stylized 6-box couple grid with cardboard box packaging) but no 'when' — no 'Use when...' clause or equivalent trigger guidance, capping completeness at 3 per the judging guidelines. Not 4 because 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Relevant keywords appear ('couple', 'grid', 'romantic poses', 'cardboard box packaging') but common variations and synonyms users would naturally say (e.g. 'couple photo grid', 'box collage', 'packaging portrait') are missing from the description; natural trigger phrases exist only in the body's Trigger Keywords section. Not below 3 since the terms present are natural rather than jargon; not 4 because key variations are absent.

3 / 5

Distinctiveness Conflict Risk

The cardboard-box-packaging couple grid is a clear, distinctive niche unlikely to trigger for unrelated skills, but the description itself carries no explicit trigger phrases to separate it from closely related couple-portrait/image-generation skills, so minor overlap risk remains. Not 5 because distinct triggers are absent; not 3 because the niche is far more specific than generic overlap examples.

4 / 5

Total

14

/

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.

Validation — 15 / 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

SamurAIGPT/Generative-Media-Skills

Path

library/visual/couple-grid-creator/SKILL.md

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.