CtrlK
BlogDocsLog inGet started
Tessl Logo

skin-creator

Create and apply a two-asset LobsterAI visual skin from the user's style description. Use only when the AI Skin Designer kit supplies the structured skin_pack workflow marker; do not use for ordinary theme or image requests.

69

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

A well-structured, highly actionable skill body with a clear sequenced workflow, validation gates, and a properly signaled one-level reference. The only meaningful drag is redundancy between the Non-negotiable rules block and the workflow steps.

Suggestions

Collapse the Non-negotiable rules already enforced inline by the workflow (serial order, no parallel generation, no direct writes) into brief cross-references or a single sentence to reduce redundancy and lift conciseness.

If keeping the rules block, move the truly invariant constraints (single backend/model lock, never infer subscription from tool visibility) to the top and delete those restated lower in the workflow.

DimensionReasoningScore

Conciseness

The body is mostly lean and assumes competence (no concept explanations, concrete JSON blocks), but the "Non-negotiable rules" section restates material also covered in the workflow (serial order, no parallel generation, no direct file writes), so it could be tightened past the mostly-efficient anchor.

2 / 3

Actionability

Copy-paste-ready JSON payloads for create_draft, register_asset, and apply, plus concrete guidance (contrast ratios, #RRGGBB format, filename hints, focus coordinates) give fully executable direction matching the copy-paste-ready anchor.

3 / 3

Workflow Clarity

A clearly numbered six-step sequence with explicit checkpoints ("Proceed only after registration succeeds", "Apply only when both required slots are registered and ready") and a Failure handling section with recovery/stop guidance matches the explicit-validation anchor.

3 / 3

Progressive Disclosure

The body is an overview that signals one clearly-named one-level-deep reference ("Read [references/asset-contract.md] before the first image generation call"), and that file exists and holds the per-slot prompt-suffix templates, so detail is appropriately split out.

3 / 3

Total

11

/

12

Passed

Description

85%

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 tightly scoped, concrete description with an explicit use-when clause and a clear negative boundary that prevents mis-triggering. Its only weakness is trigger phrasing tied to system markers rather than natural user language.

Suggestions

Add natural-language trigger variants a user might actually say (e.g., "Use when the user asks to create or apply a LobsterAI skin or visual skin") alongside the system-marker condition to improve trigger_term_quality.

Keep the existing "do not use for ordinary theme or image requests" exclusion but consider one positive everyday synonym to broaden recognizable triggers without losing distinctiveness.

DimensionReasoningScore

Specificity

"Create and apply a two-asset LobsterAI visual skin from the user's style description" names concrete actions (create, apply) bound to a specific, bounded artifact (a two-asset skin), matching the multiple-concrete-actions anchor rather than the partial domain-only anchor at 2.

3 / 3

Completeness

It answers both what (create and apply a two-asset visual skin) and when via an explicit "Use only when the AI Skin Designer kit supplies the structured skin_pack workflow marker" clause, hitting the explicit-trigger anchor rather than the implied-only anchor at 2.

3 / 3

Trigger Term Quality

Relevant terms like "visual skin", "style description", and "theme or image requests" appear, but the actual trigger leans on technical jargon ("structured skin_pack workflow marker", "AI Skin Designer kit") that a user would not naturally say, so it stops at the "some relevant keywords, missing common variations" anchor.

2 / 3

Distinctiveness Conflict Risk

The gated trigger ("Use only when ... skin_pack workflow marker") plus the explicit exclusion ("do not use for ordinary theme or image requests") carve a clear niche unlikely to fire for unrelated skills, matching the distinct-triggers anchor.

3 / 3

Total

11

/

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
netease-youdao/LobsterAI
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.