CtrlK
BlogDocsLog inGet started
Tessl Logo

workthrough

Automatically document all development work and code modifications in a structured workthrough format. Use this skill after completing any development task, bug fix, feature implementation, or code refactoring to create comprehensive documentation.

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

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/workthrough/SKILL.md

The canonical home for this skill is workthrough in bear2u/my-skills

SKILL.md
Quality
Evals
Security

Quality

Content

61%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 well-structured with a usable template and clear output conventions, making it reasonably actionable. It is held back by redundancy across sections and a workflow whose steps blur into qualitative advice rather than crisp procedural checkpoints.

Suggestions

Merge 'When to Use', 'Automation Instructions', 'Output Location', and 'Document Organization' to eliminate repeated output-location and trigger guidance.

Tighten the workflow into concrete executable steps (e.g. 'git diff --stat to list changed files', 'run the project's test command and paste the result') and add an explicit validate-then-fix loop.

Move the 'Quality Standards' list and full example template into a separate reference file, leaving SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

Mostly organized but includes redundant sections (output location restated in 'Document Organization' and 'Output Location'; 'When to Use' overlaps 'Automation Instructions') and obvious guidance in 'Quality Standards', plus a closing platitude ('Good documentation is a gift...') that could be trimmed.

3 / 5

Actionability

Provides a concrete copy-paste-ready markdown template, a clear naming convention (workthrough/YYYY-MM-DD-brief-description.md), and explicit output directory creation guidance; minor gaps in how to gather/verify the build output.

4 / 5

Workflow Clarity

A 4-step sequence (Gather Information → Create Document → Be Comprehensive → Verify Completeness) is present, but 'Be Comprehensive' and 'Gather Information' read as qualities rather than discrete procedural steps and the validation checkpoint ('Verify Completeness') is implicit rather than a concrete command.

3 / 5

Progressive Disclosure

No bundle files exist; the skill is a single self-contained file with clear section headers and a well-placed inline example template. Structure is good, though the ~55-line example template could optionally live in a separate reference file.

4 / 5

Total

14

/

20

Passed

Description

75%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 use it, with natural trigger terms. Its main weakness is breadth — 'document all development work' is generic enough to risk overlap with adjacent documentation skills.

Suggestions

Narrow the trigger to a more distinctive niche (e.g. 'structured workthrough write-up of changes, context, and verification') to reduce overlap with commit-message and changelog skills.

Replace generic verbs ('document', 'create comprehensive documentation') with more specific actions like 'capture before/after code diffs, record build/test results, and log decisions'.

DimensionReasoningScore

Specificity

Names the domain ('development work and code modifications') and a couple concrete actions ('document', 'structured workthrough format'), but the actions are generic ('document', 'create comprehensive documentation') rather than a comprehensive list of specific capabilities.

3 / 5

Completeness

Explicitly answers both what ('document all development work and code modifications in a structured workthrough format') and when ('Use this skill after completing any development task, bug fix, feature implementation, or code refactoring') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural terms developers say ('development task, bug fix, feature implementation, code refactoring') with good coverage; a few synonyms (e.g. 'changelog', 'commit') are missing.

4 / 5

Distinctiveness Conflict Risk

The 'document all development work' framing is fairly broad and could overlap with commit-message, changelog, or general documentation skills; the 'after any development task' trigger increases overlap risk.

3 / 5

Total

15

/

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.