CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

inkos-spinoff-writing

从既有 Work 正典派生番外,保持母本事实同时建立独立的侧篇弧线。

Quality

67%

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-spinoff-writing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 admirably lean instruction-only skill: no filler, well-targeted constraints, and appropriately self-contained for its size. Its weakness is operational concreteness — no worked examples and no explicit sequence or verification step for the core risk (contradicting the parent canon).

Suggestions

Add one or two worked examples of a side-story dramatic question (e.g. an unseen interval during a timeskip) to make the selection guidance executable rather than abstract.

Specify how inventions are to be marked (e.g. a short annotation in the draft or a tracked list) so "Mark new side-story inventions as additions" has a concrete mechanism.

Turn the bullets into an explicit ordered checklist with a final verification step (re-read parent canon facts touched by the draft and confirm none are advanced, erased, or rewritten).

DimensionReasoningScore

Conciseness

Six single-sentence directives with zero padding, no explanation of concepts Claude already knows, and full assumption of the model's fiction-writing competence — every token earns its place.

5 / 5

Actionability

Some guidance is concrete ("Choose a real side-story dramatic question: an unseen interval, another character's consequential viewpoint, a prehistory, aftermath, or bounded what-if"), but "Mark new side-story inventions as additions" specifies no format or procedure, and there are no worked examples, so key execution details are missing.

3 / 5

Workflow Clarity

The bullets imply a rough sequence (treat parent as authority → pick the question → shape the arc → reuse canon → mark inventions) but the ordering is implicit and there are no validation checkpoints, e.g. how to verify the parent mainline state was not contradicted.

3 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references, and the flat list is navigable; it falls short of the 5 standard only because there are no organizing sections to help scanning.

4 / 5

Total

15

/

20

Passed

Description

50%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 its purpose compactly and concretely but reads as a definition rather than a trigger: it answers 'what' clearly while omitting 'when' entirely and covering few natural trigger synonyms. Adding an explicit use-when clause would move it up a full band.

Suggestions

Add an explicit 'Use when...' clause, e.g. "当用户要求为既有作品写番外、外传或衍生短篇时使用" — this is the single largest gap and currently caps completeness at 3.

Include natural trigger synonyms users would actually say (番外、外传、衍生作、side story、spinoff) so the skill is discoverable across phrasings.

List the concrete spinoff forms the skill handles (unseen interval, alternate viewpoint, prehistory, aftermath, bounded what-if) to sharpen specificity and distinctiveness against sequel/continuation skills.

DimensionReasoningScore

Specificity

The description names the domain and a few concrete actions — "派生番外" (derive spinoffs), "保持母本事实" (preserve parent facts), "建立独立的侧篇弧线" (build an independent side arc) — but coverage is not comprehensive, matching the '1-2 concrete actions' anchor rather than the 'several specific actions' level.

3 / 5

Completeness

The 'what' is clear (derive canon-preserving spinoffs with an independent arc), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

"番外", "正典", "母本", and "侧篇" are relevant domain keywords and "番外" is a natural user term, but common variations like "外传", "衍生", "spinoff", or "side story" are missing, placing it at 'some relevant keywords but missing variations'.

3 / 5

Distinctiveness Conflict Risk

The spinoff/canon niche is somewhat specific, but the description could still overlap with sibling writing skills (sequels, continuation, canon expansion) and offers no distinct trigger phrases to disambiguate.

3 / 5

Total

12

/

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-spinoff-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.