CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

inkos-imitation-writing

从参考文本提取可迁移的文体方法,为全新故事建立可执行风格指纹。

Quality

73%

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-imitation-writing/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.

An exemplary lean instruction-only body: concise, boundary-aware, and free of padding. Its main weakness is actionability — the workflow names what to extract and avoid but never shows or specifies the style-guide artifact Claude is meant to produce.

Suggestions

Add a brief skeleton or mini-example of the output style guide (e.g. 3-5 positive instructions plus one source-grounded observation) so the deliverable's format is unambiguous.

Number the steps explicitly (analyze reference → extract features → draft style guide → apply to the new work) to make the already-logical sequence explicit.

Optionally add one short worked illustration of a transferable feature vs. a non-transferable one to sharpen the extraction instruction.

DimensionReasoningScore

Conciseness

Five lean bullets with zero padding and no explanation of concepts Claude already knows — each line adds non-obvious guidance (authority boundaries, named extraction targets, reuse prohibitions, application posture). Matches the anchor 'every token earns its place'.

5 / 5

Actionability

Concrete in places — a named feature list ('narrative distance, sentence movement, paragraph rhythm, dialogue density, sensory selection…') and concrete prohibitions ('Do not reuse source names, distinctive phrases, scene order…') — but the deliverable is underspecified: no example or template of the output style guide, and 'a few source-grounded observations' is undefined. Matches 'some concrete guidance but incomplete; missing key details', not 4 because the shape of the artifact Claude must produce is left open.

3 / 5

Workflow Clarity

The bullets follow a logical sequence — authority boundary → extract features → avoid reuse → build style guide → apply flexibly — appropriate for a simple, non-destructive creative task where validation checkpoints are not needed. Not 5 because the sequence is implicit rather than framed as explicit steps; not 3 because the order is clearly discernible and nothing destructive/batch-related requires the validation cap.

4 / 5

Progressive Disclosure

The body is under 50 lines with no need for external references, and is appropriately organized as a flat bullet list with no inlined material that belongs in separate files. Per the simple-skill guideline, this earns the top score.

5 / 5

Total

17

/

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 states a clear and reasonably specific 'what' but omits any 'when' guidance, capping completeness. It relies on invented jargon ('可执行风格指纹', '可迁移') rather than natural trigger terms a user would say when asking for style imitation.

Suggestions

Add an explicit trigger clause, e.g. '当用户提供参考文本并希望以其中文风创作全新故事时使用' (use when the user supplies a reference text and wants new writing in that style).

Include natural user phrasings as trigger terms: 模仿文风、仿写、以…的写作风格创作、imitate an author's style.

Replace abstract coinages like '可执行风格指纹' with plainer wording (e.g. '提炼可操作的写作风格指南') so the capability reads concretely.

DimensionReasoningScore

Specificity

Names the domain (style transfer from a reference text) and two actions — '提取可迁移的文体方法' and '建立可执行风格指纹' — matching the anchor for 1-2 concrete actions without comprehensive coverage. It is not 4 because '可执行风格指纹' (executable style fingerprint) is abstract jargon rather than several concrete, distinct actions.

3 / 5

Completeness

The 'what' is clear (extract transferable stylistic methods, build a style fingerprint for a new story) but the 'when' is entirely missing — no 'Use when…' clause or equivalent trigger guidance, which caps completeness at 3. It is not 2 because the 'what' is specific rather than vague.

3 / 5

Trigger Term Quality

Relevant keywords are present ('参考文本', '文体', '风格') but common user phrasings are missing — no '模仿', '仿写', '文风', or '以…风格写作', and '可迁移'/'可执行风格指纹' are invented technical terms. Matches the anchor for some relevant keywords missing common variations, not 4 since natural synonyms users would actually say are absent.

3 / 5

Distinctiveness Conflict Risk

The niche — imitating a reference text's style for original fiction — is fairly distinct with only minor overlap risk against general writing/editing skills. Not 5 because the absence of explicit triggers means it could overlap with prose-editing or general writing skills.

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-imitation-writing/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.