CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

kv-design

Generate professional Key Visual (KV) design proposals and images; use when you have a slogan/copy and a marketing scenario but need a clear visual direction and a ready-to-generate image prompt.

Quality

80%

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 ./scientific-skills/Other/kv-design/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

A well-structured skill with an exemplary file layout — overview in SKILL.md, prompt templates one reference deep, and a working script. The main costs are redundant restatements across Key Features and Implementation Details, plus small gaps in install/error-handling guidance.

Suggestions

Merge the "Key Features" and "Implementation Details" sections into the workflow steps and drop the repeated parameters list (it restates the Step 1 collection checklist), cutting ~20 lines of duplication.

Add the dependency install command (pip install zhipuai requests) next to the API-key export in Step 4 so the runnable path is fully self-contained.

Add one line of error-recovery guidance for Step 4 (e.g. what to do if generation fails or the response contains no data) to close the workflow's validation gap.

DimensionReasoningScore

Conciseness

The body doesn't explain concepts Claude already knows, but three sections substantially restate each other: "Key Features" bullets ("negative space planning", "subject prominence") duplicate "Implementation Details", "Two-stage prompting workflow" restates Example Usage steps 2-3, and "Parameters to capture early" repeats the Step 1 collection list. This matches anchor 3: mostly efficient but could be tightened by consolidating redundant sections.

3 / 5

Actionability

The workflow is mostly executable: it names the exact reference file to open (references/design_prompts.md), the exact input blocks to fill ([KV Design Requirements], [Basic Requirements], [Design Proposal]), and copy-paste-ready commands (export ZHIPUAI_API_KEY, python scripts/generate_kv.py "<generated_prompt>"). Minor gaps keep it below anchor 5: no package-install command for the zhipuai/requests dependencies and no guidance for handling a failed generation.

4 / 5

Workflow Clarity

The four-step sequence (collect requirements → analyze design direction → generate image prompt → run script) is clearly ordered with explicit file paths at each stage. It matches anchor 4: clear sequence with most checkpoints present, but minor validation gaps — e.g. no step to sanity-check the generated design direction or recover if image generation fails (though the operation is non-destructive, so the batch/destructive cap doesn't apply).

4 / 5

Progressive Disclosure

The bundle structure is exemplary: SKILL.md is a lean overview, both prompt templates live in references/design_prompts.md (verified to exist, exactly one level deep, clearly signaled by path in the workflow), and the runnable code lives in scripts/generate_kv.py (verified to exist). This matches anchor 5: clear overview with well-signaled one-level-deep references and appropriate content split.

5 / 5

Total

16

/

20

Passed

Description

82%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.

A strong description with a clear what-and-when structure and a well-defined KV/marketing niche. Its main weakness is the second-person trigger phrasing, which both violates the third-person voice guideline and compresses the capability list.

Suggestions

Rewrite the trigger clause in third person, e.g. "Generate Key Visual (KV) design proposals, image prompts, and final marketing images. Use when a user provides a slogan/copy and marketing scenario (product launch, sale event, banner) and needs a visual direction."

Enumerate the concrete outputs more fully (design direction, optimized image-generation prompt, generated image) to lift capability coverage from 2-3 actions toward comprehensive.

DimensionReasoningScore

Specificity

The description names concrete deliverables — "Generate professional Key Visual (KV) design proposals and images" and "a ready-to-generate image prompt" — which initially matches anchor 4 (several specific actions, minor gaps). However, the trigger clause uses second person ("use when you have a slogan/copy and a marketing scenario but need a clear visual direction"), which the judging guidelines penalize by reducing specificity by 1, bringing it to anchor 3: concrete actions present but coverage not comprehensive.

3 / 5

Completeness

It explicitly answers both questions: the "what" ("Generate professional Key Visual (KV) design proposals and images") and a concrete "when" clause ("use when you have a slogan/copy and a marketing scenario but need a clear visual direction and a ready-to-generate image prompt"). The trigger conditions are specific rather than implied, matching anchor 5.

5 / 5

Trigger Term Quality

Good keyword coverage with natural phrasing: "Key Visual (KV)" pairs the term with its abbreviation, and "slogan/copy" gives a synonym pair alongside "marketing scenario" and "image prompt". It falls short of anchor 5 because common variations users would naturally say — "banner", "poster", "hero image", "ad creative" — are missing.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche — Key Visual design proposals and marketing image generation — with triggers (slogan/copy + marketing scenario) that would not plausibly route users to unrelated skills. This matches anchor 5: distinct triggers, minimal conflict risk.

5 / 5

Total

17

/

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

aipoch/medical-research-skills

Path

scientific-skills/Other/kv-design/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.