CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

inkos-fanfic-writing

基于外部正典创作同人作品,管理正典边界、角色声音与允许偏离。

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

Quality

Content

86%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 skill: every bullet is a specific, testable constraint, mode semantics (canon/AU/OOC/CP) are defined once, and the scale needs no external files. The only soft spot is a few abstract directives without illustrative examples of desired voice or output.

DimensionReasoningScore

Conciseness

Every bullet earns its place ('Preserve recognizable voice through motive, knowledge, rhythm, and behavioral choices, not copied phrases'); no padding and no explanation of concepts Claude already knows — the AU/OOC/CP mode definitions are domain knowledge worth stating.

5 / 5

Actionability

Concrete, testable decision rules ('keep the gap open or ask; do not turn a guess into canon'; new characters 'must serve the new line and remain distinguishable from source canon'), but some lines are abstract ('Build a new dramatic line rather than replaying source scenes') and no illustrative examples are given — minor gaps, not missing key details.

4 / 5

Workflow Clarity

A flat, single-purpose constraint list with no destructive or batch operations needing validation; the single action is largely unambiguous, but minor process gaps remain (e.g., what to do when the user does not name a mode, how to verify voice fidelity).

4 / 5

Progressive Disclosure

Six lines total with no references/, scripts/, or assets/ bundle; nothing here warrants splitting into separate files, and the inline bullet list is appropriately organized at this scale, so the simple-skill exception applies.

5 / 5

Total

18

/

20

Passed

Description

58%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 clearly states what the skill does with several concrete facets and occupies a distinct niche, but it omits any 'when to use' trigger guidance and misses common synonyms (同人文, fanfic, AU, OOC, CP) that users would naturally say. It sits above the midpoint but well short of the strong examples.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks to write 同人/同人文/fanfic, fan fiction, or derivative stories based on an existing work, including AU, OOC, or CP requests.'

Include common synonyms and jargon users actually use — 同人文, fanfic, fan fiction, AU, OOC, CP — so the skill surfaces for those phrasings.

Mention the supported modes (canon-gap, AU, OOC, CP) in the description to make the 'what' comprehensive, not just the management facets.

DimensionReasoningScore

Specificity

Names the domain ('基于外部正典创作同人作品') and four concrete facets ('管理正典边界、角色声音与允许偏离'), but coverage has gaps — the AU/OOC/CP modes and output forms from the body are absent, so it is not comprehensive.

4 / 5

Completeness

Has a clear 'what' (create fan-fiction, manage canon boundaries, character voice, permitted deviations) but no 'Use when...' clause or equivalent trigger guidance, which caps this dimension at 3.

3 / 5

Trigger Term Quality

'同人作品' is a natural user phrase, but '正典' is jargon and common variants users actually say ('同人文', 'fanfic', 'fan fiction', 'AU', 'OOC', 'CP') are missing.

3 / 5

Distinctiveness Conflict Risk

Fan-fiction based on external canon is a clear niche unlikely to mis-trigger against general writing skills, but the description lacks explicit distinct trigger phrases, so it is mostly rather than fully distinct.

4 / 5

Total

14

/

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