inkos-long-writing

长篇小说的场景构造、人物因果、信息释放与连载节奏。Used by InkOS long-form workers as their shared craft method.

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./packages/core/skills/inkos-long-writing/SKILL.md

Quality

Content

72%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 highly concise and offers specific, actionable craft guidance, but it lacks an explicit sequenced workflow with checkpoints and fails to point at the two existing reference files. Structure is clean yet navigation to bundled detail is missing.

Suggestions

Add explicit links to the reference files where their topics apply, e.g. 'For reader-contract and progression, see references/reader-contract-and-progression.md'.

Sequence the bullets into a light workflow (plan scenes -> draft -> review/repair) with an explicit validation checkpoint such as verifying each passage alters a listed axis.

Briefly state when to consult each reference so the one-level-deep navigation is clear.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: every bullet is actionable craft guidance with no padding and no explanation of basic concepts.	5 / 5
Actionability	Bullets give concrete, specific directives such as mapping a chapter goal to scenes with objective/resistance/turn/consequences; minor gaps remain because guidance is principle-based rather than fully executable steps.	4 / 5
Workflow Clarity	The principles imply a method and include a repair directive ('diagnose and repair the smallest layer'), but there is no explicit sequenced workflow with validation checkpoints.	3 / 5
Progressive Disclosure	Two reference files exist in ./references, but the body never signals or links to them, so references are present but not clearly navigable despite the otherwise well-organized bullet structure.	3 / 5
	Total	15 / 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 conveys a distinct craft niche and several concrete capabilities, but lacks an explicit trigger clause and relies on audience framing rather than natural user phrasing. It is solid but not exemplary on completeness and trigger terms.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers such as drafting or revising a serialized long-form novel, planning scene structure, or pacing a chapter.

Include common synonyms and English equivalents (e.g. 'long-form fiction', 'serial novel', 'scene pacing') to broaden trigger coverage.

Lead with the concrete actions before the audience framing so the 'what' is immediately scannable.

Dimension	Reasoning	Score
Specificity	Names the long-form novel domain and four concrete craft actions (场景构造, 人物因果, 信息释放, 连载节奏), giving several specific capabilities with only minor coverage gaps.	4 / 5
Completeness	The 'what' is clearly stated, but there is no explicit 'Use when...' trigger clause; the 'when' is only weakly implied by 'Used by InkOS long-form workers', which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Relevant domain keywords like 长篇小说 and 连载 are present, but common variations and English synonyms are missing and the English clause describes audience rather than natural user triggers.	3 / 5
Distinctiveness Conflict Risk	Long-form serialized novel craft is a clear niche with distinct triggers and only minor overlap risk with general writing skills.	4 / 5
	Total	14 / 20 Passed

Validation

100%

Warnings & errors only

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-long-writing/SKILL.md
Commit: 0910483

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.