refine

End-of-session reflection. Reviews friction encountered during the session and proposes updates to docs/ to capture lessons learned.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/refine/SKILL.md

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 lean, well-structured, actionable reflection workflow with a clear five-step sequence. Its only real weakness is the absence of an explicit validation checkpoint before reporting doc changes.

Dimension	Reasoning	Score
Conciseness	The body is lean (~33 lines), assumes Claude's competence, and contains no padding or explanations of concepts Claude already knows; every line earns its place. Matches the score-5 anchor 'Lean and efficient; assumes Claude's competence; every token earns its place'.	5 / 5
Actionability	Provides a concrete command (`git diff main...HEAD --stat`), specific doc paths, and named friction categories, but some guidance ('Think about: what was slow...') is prompting rather than executable steps. Fits score 4 'Mostly executable guidance; concrete code or commands with minor gaps'; not a 5 because not every instruction is copy-paste ready.	4 / 5
Workflow Clarity	Five clearly numbered steps (identify, read, propose, apply, report) form a coherent sequence, but there is no explicit validation/review checkpoint confirming doc changes are accurate before reporting. Matches score 4 'Clear sequence with most checkpoints present; minor validation gaps'; not a 5 because no explicit validation step or feedback loop exists.	4 / 5
Progressive Disclosure	The skill is under 50 lines with no external references needed and is organized into well-signaled sections (Instructions, Rules). Per the guideline, such simple skills can score 5 with just well-organized sections; no bundle files exist to evaluate further.	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 conveys a clear purpose and a couple of concrete actions but lacks an explicit 'Use when...' trigger clause, which caps its completeness and trigger-term quality. It is reasonably distinct but would benefit from natural user-facing trigger phrases.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers (e.g., 'Use at the end of a session when the user asks to capture lessons learned or update the docs').

Expand the action list to be more comprehensive (e.g., 'reviews friction, drafts doc updates, applies minimal edits, and reports changes').

Include common natural phrasings users would say, such as 'lessons learned', 'retrospective', or 'update the docs'.

Dimension	Reasoning	Score
Specificity	Names the domain ('End-of-session reflection') and two concrete actions ('Reviews friction encountered', 'proposes updates to docs/'), but coverage is not comprehensive. Matches the score-3 anchor 'Names domain and 1-2 concrete actions, but not comprehensive'; not a 4 because it does not list several specific actions.	3 / 5
Completeness	The 'what' is clear ('Reviews friction... proposes updates to docs/') but there is no 'Use when...' clause, so per the guideline a missing explicit trigger caps completeness at 3. The 'when' is only weakly implied by 'End-of-session', matching the score-3 anchor; not a 4 because 'when' is not explicitly stated.	3 / 5
Trigger Term Quality	Phrases like 'End-of-session reflection', 'friction', and 'lessons learned' are relevant but a user would more naturally say 'update the docs' or 'what did we learn'; common variations are missing. Fits score 3 'Some relevant keywords but missing common variations or synonyms' rather than 4's broader coverage.	3 / 5
Distinctiveness Conflict Risk	The end-of-session reflection + docs/ lessons-learned niche is mostly distinct from other skills with only minor overlap risk against general documentation skills. Matches score 4 'Mostly distinct; minor overlap risk'; not a 5 because the triggers are not maximally concrete.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: windmill-labs/windmill
Path: .agents/skills/refine/SKILL.md
Commit: 2fb7903

Reviewed: 26 minutes ago

Table of Contents

Discovery Implementation Validation

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.