CtrlK
BlogDocsLog inGet started
Tessl Logo

inkos-story-cover

根据作品、平台与用户视觉要求设计或生成封面。Use for story-cover direction and confirmed cover generation.

66

Quality

79%

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-story-cover/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

80%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-organized overview with strong domain-specific guidance and a properly signaled one-level reference. Its main weakness is workflow clarity: the process is conveyed as principles rather than an explicitly sequenced workflow with verification checkpoints.

Suggestions

Add a short numbered workflow (e.g. 1. gather work inputs, 2. build brief via references/cover-brief.md, 3. propose in chat, 4. generate only via generate_cover, 5. evaluate at final and thumbnail size) to make the sequence and verification explicit.

Include one worked example of a cover prompt or a filled-in brief excerpt so the actionable guidance has a concrete model to follow.

DimensionReasoningScore

Conciseness

The body is a tight set of bullets that each carry domain-specific guidance (no house-style imposition, cover-type taxonomy, generate_cover gating) with no padding or explanation of concepts Claude already knows, matching the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

Guidance is concrete and specific — a named input checklist, the `generate_cover` confirmation path, and the typography/background separation technique — but no worked example of a cover prompt or brief output is shown, a minor gap that keeps it at 4 rather than 5.

4 / 5

Workflow Clarity

The implied flow (gather work details → propose in chat → generate via generate_cover → evaluate at thumbnail size) is principle-based rather than an explicitly numbered sequence, and the confirmation gate is only an implicit checkpoint, fitting the 'sequence present but checkpoints missing or implicit' anchor.

3 / 5

Progressive Disclosure

The body is a concise overview that signals one clearly scoped one-level-deep reference ('Load references/cover-brief.md when converting a manuscript into a production-ready visual brief'), and that file exists and is well-organized, matching the top anchor.

5 / 5

Total

17

/

20

Passed

Description

78%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 cleanly answers both what the skill does and when to use it, with a specific story-cover niche and an explicit trigger clause. It is slightly limited in action breadth and natural-term coverage, which keeps specificity and trigger quality just below the top anchor.

Suggestions

Add one or two more concrete actions (e.g. 'iterate on a cover brief', 'regenerate a cover variant') to lift specificity toward the top anchor.

Include a couple of common natural synonyms users say (e.g. 'book cover', 'cover art', '封面设计') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the cover domain and two concrete actions ('设计或生成封面' = design or generate covers), matching the 'names domain and 1-2 concrete actions' anchor; it does not list several distinct actions, so it stays at 3 rather than 4.

3 / 5

Completeness

It states both the 'what' (design/generate covers from work, platform, and visual requirements) and an explicit 'when' ('Use for story-cover direction and confirmed cover generation'), satisfying the 'clearly and explicitly answers both what AND when' anchor.

5 / 5

Trigger Term Quality

Natural terms a user would say are present ('story cover', 'cover generation', '封面'), giving good keyword coverage; a few common synonyms (e.g. 'book cover', 'cover art') are missing, so it does not reach 5.

4 / 5

Distinctiveness Conflict Risk

The 'story-cover' niche and the generate_cover trigger are mostly distinct from generic image skills, but the bare word 'cover' carries minor overlap risk with other cover/image skills, so it sits at 4 rather than 5.

4 / 5

Total

16

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Narcooo/inkos
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.