CtrlK
BlogDocsLog inGet started
Tessl Logo

inkos-play-world

品类中立的开放世界与分支互动推进方法。Used by InkOS Play workers for coherent action, state, time, and scene progression.

59

Quality

68%

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-play-world/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 tight, actionable set of principles that assumes Claude's intelligence and wastes no tokens, performing strongly on conciseness and actionability; the main gap is that the existing reference file is not linked from the body, and no worked example or consistency-validation checkpoint is provided.

Suggestions

Link the existing references/world-turn-continuity.md from the body (e.g. a 'See world-turn-continuity.md for ...' line) so the bundle is signaled.

Add one short worked beat example showing a player action advanced one adjacent step, to lift actionability to fully copy-paste-ready clarity.

Add an explicit consistency self-check (e.g. verify every prose change has a matching graph fact) as a validation checkpoint.

DimensionReasoningScore

Conciseness

The body is lean and efficient: every bullet earns its place, assumes Claude's competence, and explains no general concepts, matching the 5 anchor (lean and efficient; every token earns its place).

5 / 5

Actionability

Directives are concrete and specific ("Advance one adjacent dramatic beat", "stop at the nearest new pressure point", "Preserve negation exactly"), giving mostly executable guidance; it stays at 4 rather than 5 because no worked beat example demonstrates the principle end-to-end.

4 / 5

Workflow Clarity

This is a simple single-purpose instruction skill, so the simple-skill exception applies; the core action (advance one adjacent beat) is unambiguous and the principles are clearly grouped, but it lacks an explicit validation/feedback checkpoint for consistency, keeping it at 4 rather than 5.

4 / 5

Progressive Disclosure

The body is well-organized into clean thematic bullets under 50 lines and a real reference file (references/world-turn-continuity.md) exists, but that file is never linked or signaled from the body, a minor organization gap that holds it at 4 rather than 5.

4 / 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 is concise and names a clear niche, but it lacks an explicit "Use when..." trigger clause and leans on domain jargon over natural user phrasing, capping completeness and trigger quality at the midpoint.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger situations (e.g. open-world play, branching scenes, time/state advancement).

Replace some domain jargon with natural phrases a user would actually say when requesting this skill.

Lead with concrete action verbs (advance, branch, sustain) instead of describing a 'method'.

DimensionReasoningScore

Specificity

Names the domain (open world, branching interaction) and lists concrete things advanced ("coherent action, state, time, and scene progression"), but frames the skill as a method rather than enumerating multiple concrete actions, matching the 3 anchor (domain + 1-2 concrete actions, not comprehensive).

3 / 5

Completeness

Has a clear "what" (a progression method for action/state/time/scene) but no "Use when..." clause or explicit trigger guidance, so per the rubric guideline a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Includes relevant terms like "open world", "branching interaction", and "scene progression", but these are domain-jargon leaning and miss common natural variations a user might actually say; matches the 3 anchor (some relevant keywords, missing common synonyms).

3 / 5

Distinctiveness Conflict Risk

"Used by InkOS Play workers" plus "open world" / "branching interaction" carve a clear niche with distinct triggers and only minor overlap risk, fitting the 4 anchor (mostly distinct) rather than 3 (could still overlap).

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.

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.