CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cut

Proposes cuts and a polish list to finish the game from its brief and what is built; the person picks each cut. A game to sell also gets a release date and a feature freeze. Use when asked what to cut, how to finish or ship it, or for a polish list.

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

90%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 exceptionally dense, highly actionable procedural skill: exact commands, flags, output templates, and error-recovery loops across five well-sequenced phases, with no wasted tokens. The only weaknesses are convoluted nested prose in the Phase 1 freshness logic and inline-buried references rather than clearly signaled ones.

DimensionReasoningScore

Conciseness

Lean and efficient throughout: zero explanation of concepts Claude already knows, no padding, and hyper-compressed operational prose ('Resolved above — use-as. No block → defaults in...'). Every line carries operational instruction, matching the 5 anchor; the 4 anchor's 'minor instances of over-explanation' are absent.

5 / 5

Actionability

Fully executable guidance: exact copy-paste commands with flags (`bash .claude/scripts/cut-read.sh`, `cut-apply.sh --cut <n> "<reason>"`, the `find ... -newer` freshness check, the full git commit invocation) plus a concrete output screen template. Matches the 5 anchor's copy-paste-ready coverage of common cases; the 4 anchor's 'minor gaps' do not apply.

5 / 5

Workflow Clarity

Five clearly sequenced phases with real validation and feedback loops ('bad rows mean nothing was written: fix the arguments and run it again'; a skipped question is asked again; freshness checks before the light check). It falls short of 5 because the 'Fresh first' light-check bullet is convoluted nested prose that is hard to follow sequentially, a minor clarity/checkpoint gap.

4 / 5

Progressive Disclosure

Good structure: well-organized phase sections, and references to project docs (`.claude/docs/automation-modes.md`, `.claude/skills/start/SKILL.md` Phase 4) stay one level deep. Not 5 because those references are buried inline as parentheticals rather than clearly signaled, and dense procedural content (the light-check procedure reaching into another skill's reference doc) is inlined rather than split out; no bundle files exist to offset this.

4 / 5

Total

18

/

20

Passed

Description

83%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.

A strong description in third person that clearly states concrete capabilities and pairs them with an explicit 'Use when' trigger clause. Trigger terms are natural and domain-distinct, with only minor gaps in synonym coverage and slight overlap risk around generic finish/ship phrasing.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Proposes cuts and a polish list', 'gets a release date and a feature freeze', 'the person picks each cut') with only minor coverage gaps (e.g., writing the brief and committing are unmentioned). It is not 5 because coverage is not comprehensive, and not 3 because it goes well beyond 1-2 actions.

4 / 5

Completeness

Explicitly answers both: what ('Proposes cuts and a polish list to finish the game... gets a release date and a feature freeze') and when ('Use when asked what to cut, how to finish or ship it, or for a polish list') with concrete trigger phrases. The explicit 'Use when' clause matches the 5 anchor exactly; the 4 anchor's weaker 'when' does not apply.

5 / 5

Trigger Term Quality

Natural trigger phrases users would say: 'what to cut', 'how to finish or ship it', 'polish list'. A few natural synonyms are missing ('scope', 'trim', 'feature creep', 'release'), so it fits anchor 4 rather than the comprehensive 5, but is clearly above the 3 anchor's partial coverage.

4 / 5

Distinctiveness Conflict Risk

Game-finishing/cutting is a clear niche with distinct triggers ('cut', 'polish list', 'feature freeze'), but 'how to finish or ship it' could fire for non-game software projects and a sibling /scope-check skill covers adjacent ground (the body itself routes between them). Minor overlap risk fits anchor 4, not the minimal-conflict 5.

4 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

Donchitos/Claude-Code-Game-Studios

Path

.claude/skills/cut/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.