CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

inkos-play-illustration

互动世界场景和实体的插画方法,保持画面与当前事实一致,避免把游戏规则画成虚构界面。

Quality

78%

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 ./packages/core/skills/inkos-play-illustration/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 an exemplary short, instruction-only skill: lean, concrete, and unambiguous, with well-scoped do and don't lists that directly constrain illustration output. The only improvement space is a small amount of concrete visual guidance (viewpoint defaults, style consistency examples) that would sharpen actionability further.

DimensionReasoningScore

Conciseness

Six lean bullets with zero concept over-explanation; every token instructs behavior Claude does not already know (e.g., 'Rules about turns, choices, state tracking, or controls do not become objects or interface elements'), matching the lean-and-efficient anchor.

5 / 5

Actionability

Concrete, checkable guidance: an explicit preservation list ('location, lighting, time of day, characters, clothing, and important objects') and an explicit exclusion list ('captions, narration blocks, dialogue boxes, buttons, menus, inventory panels, resource counters, clocks, HUD overlays, and watermarks'). Minor gaps — no viewpoint default, style guidance, or good/bad examples — keep it below fully executable coverage.

4 / 5

Workflow Clarity

This is a simple, single-purpose skill where the single action (produce a fact-consistent illustration of the described subject) is unambiguous; per the simple-skill exception no multi-step sequence or validation loop is required, and none applies since the operation is neither destructive nor batch.

5 / 5

Progressive Disclosure

The body is under 50 lines, self-contained, and references no bundle files (none exist), so per the simple-skill guideline well-organized inline content suffices; the flat bullet structure is appropriate for this length.

5 / 5

Total

19

/

20

Passed

Description

53%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 communicates a reasonably specific and distinctive purpose, but it reads more like a design principle than a trigger: it lacks any 'when to use this' guidance and omits natural synonyms and concrete output types (scenes, portraits, objects). Adding an explicit trigger clause and a couple of concrete deliverables would move it from mediocre to strong.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to draw, illustrate, or depict an interactive-world scene, character, or object, or requests a visual rendering of game state.'

List the concrete output types in the description (scene illustrations, character portraits, object images) so the 'what' is actionable rather than a method statement.

Include common user phrasings/synonyms such as 画, 绘图, 立绘, image, or screenshot to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain ("互动世界场景和实体的插画方法") and two directive goals ("保持画面与当前事实一致", "避免把游戏规则画成虚构界面"), but unlike the level-4 anchor it never lists concrete actions such as producing scene illustrations, character portraits, or object images.

3 / 5

Completeness

The 'what' is clear (illustration method for interactive-world scenes and entities with fact consistency), but there is no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant keywords are present (插画, 场景, 实体, 游戏规则), matching the 'some relevant keywords' anchor, but common variations users would naturally say (画/绘图, 立绘, image, character portrait, game interface) are missing.

3 / 5

Distinctiveness Conflict Risk

The interactive-world/fact-consistency framing carves a fairly distinct niche with low conflict risk against unrelated skills, but the generic '插画方法' wording leaves minor overlap with general illustration or image-generation skills, fitting between the 3 and 5 anchors.

4 / 5

Total

13

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Narcooo/inkos

Path

packages/core/skills/inkos-play-illustration/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.