CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

final-editor

피어 리뷰를 반영해 9개 산출물을 일관된 최종본으로 정리한다.

Quality

75%

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 ./skills/final-editor/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.

The body is a model of token-efficient instruction design: a precise role framing, explicit inputs, an exact output skeleton, and three operational rules for edge cases. The only real gap is the implicit workflow ordering and the unspecified use of the revision-priority input.

DimensionReasoningScore

Conciseness

The ~45-line body is lean with zero padding: 역할, 입력, 출력 형식, 규칙 each carry load-bearing instructions and no concept Claude already knows is explained, matching the 'every token earns its place' anchor.

5 / 5

Actionability

The skill provides a copy-paste output template (change-summary table, 1-page summary fields, numbered risk/plan lists) and concrete rules ("[가정]" assumption tagging, unified target phrasing); minor gaps remain, e.g., how to apply the "수정 우선순위" input is never specified.

4 / 5

Workflow Clarity

Inputs, rules, and an exact output format make the single task clear and the conflict-reconciliation rules function as checkpoints, but the consolidation of deliverables 1-8 is implicitly multi-step with no explicit ordering or final consistency-verification step, so it sits at 'clear sequence, minor validation gaps'.

4 / 5

Progressive Disclosure

The skill is under 50 lines, requires no external references (no bundle files exist), and is organized into clean labeled sections, satisfying the simple-skill condition for a top progressive-disclosure score.

5 / 5

Total

18

/

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 uses third person with a clear 'what', anchored in a specific niche (final consolidation of 9 deliverables after peer review). Its main weakness is the absence of any 'Use when...' trigger guidance and limited keyword coverage, which hold completeness and trigger quality at the midpoint.

Suggestions

Add an explicit 'Use when...' clause to the description (e.g., "Use when the user asks for the final revised version, a change summary, or consolidation of deliverables after peer review") to raise completeness above 3.

Broaden natural trigger terms and synonyms in the description — e.g., 최종 검토, 문서 정리, 리비전 반영, 변경 내역 정리 — so users' phrasing matches without relying on the frontmatter triggers list.

Enumerate 1-2 more concrete actions in the description (e.g., reconciling conflicting numbers, unifying target-customer terminology across documents) to sharpen specificity.

DimensionReasoningScore

Specificity

"피어 리뷰를 반영해 9개 산출물을 일관된 최종본으로 정리한다" names the domain and 1-2 concrete actions (reflect peer review, consolidate into a consistent final version), but offers no broader action inventory, matching the 3 anchor.

3 / 5

Completeness

It clearly answers 'what' (consolidate 9 deliverables reflecting peer review into a final version) but the description field itself contains no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

The description contains relevant natural terms ("피어 리뷰", "산출물", "최종본") but misses common variations and synonyms a user might say (e.g., "문서 정리", "최종 검토", "리비전 반영"), fitting the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

"9개 산출물" and "피어 리뷰를 반영해" carve out a distinct final-stage consolidation niche with clear triggers, leaving only minor overlap risk with closely related editing or review skills.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

retention-corp/road-to-founders

Path

skills/final-editor/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.