CtrlK
BlogDocsLog inGet started
Tessl Logo

workthrough

Use this skill proactively and automatically after completing ANY development work. AI agent summarizes: what was done, what was changed/improved, and suggests future additions/improvements - all concisely in Korean.

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 ./skills/workthrough-v2/SKILL.md
SKILL.md
Quality
Evals
Security

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 content is a compact, well-structured single-purpose skill with a copy-paste template and a clear two-branch VitePress workflow. Its main gap is workflow clarity: it lacks an explicit validation/fix feedback loop for the build step.

DimensionReasoningScore

Conciseness

The body is lean — short bullet '핵심' list, a compact copy-paste markdown template, and minimal prose — matching 'efficient; minor instances of over-explanation that could be trimmed' (e.g. the decorative emoji headers and the trailing '끝.' line); not a 5 only because of those few ornamental tokens.

4 / 5

Actionability

It provides a concrete, copy-paste markdown template plus specific commands ('pnpm install && pnpm dev', 'pnpm build') and a concrete file path convention, matching 'mostly executable guidance with minor gaps'; not a 5 because the '핵심 코드 (필요시만)' block is a placeholder rather than a runnable example.

4 / 5

Workflow Clarity

It sequences a two-branch workflow (first run vs. subsequent run) with numbered steps and one verification cue ('pnpm build로 빌드 확인만'), matching 'steps listed but validation gaps; checkpoints present but implicit'; not a 4 because there is no explicit validate-and-fix feedback loop or failure-handling step.

3 / 5

Progressive Disclosure

The skill is a single-purpose, under-50-line document with no bundle files and well-organized section headers (핵심 / 문서 내용 / VitePress 처리 / 중요), so the simple-skill exception applies: well-organized sections alone warrant a 5; there are no nested references to penalize.

5 / 5

Total

16

/

20

Passed

Description

63%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 both what the skill does and when to run it, with several concrete actions and a defined language output. Its main weakness is a generic, overly broad trigger ('after completing ANY development work') that risks overlap with other summary/documentation skills.

Suggestions

Narrow the trigger with concrete cues, e.g. 'Use when the user asks for a workthrough, development summary, or recap after finishing a coding task.'

Add natural synonyms such as 'dev log', 'change log', or 'work recap' so it matches phrasings users actually say.

Specify the output artifact more distinctly (a dated Korean markdown file under workthrough/) to reduce overlap with general commit-message or summary skills.

DimensionReasoningScore

Specificity

Quotes 'summarizes: what was done, what was changed/improved, and suggests future additions/improvements' list several concrete actions (summarize done/changed/improved, suggest future), matching the 'lists several specific actions' anchor; not a 5 because coverage is limited to summary-generation actions only.

4 / 5

Completeness

It explicitly answers both 'what' (summarizes what was done/changed/improved and suggests future additions) and 'when' ('after completing ANY development work'), matching the 'has both what and when' anchor; not a 5 because the when-clause is generic rather than a concrete trigger phrase like 'Use when the user mentions X'.

4 / 5

Trigger Term Quality

Quotes 'after completing ANY development work' give a usable trigger but no natural synonyms or file-type cues; it matches 'some relevant keywords but missing common variations' rather than the comprehensive synonym coverage of a 4.

3 / 5

Distinctiveness Conflict Risk

The 'concisely in Korean' + workthrough-doc niche narrows it somewhat, but 'after completing ANY development work' is broad and overlaps with general summary/commit-message skills, fitting 'somewhat specific but could still overlap with similar skills'; not a 4 because the trigger is not tightly bounded.

3 / 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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
bear2u/my-skills
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.