Name: best-practices-learner
Rating: 62.4 (1 reviews)
Author: fernandezbaptiste

best-practices-learner

Extract learnings and best practices from skill development experience, review findings, and pattern analysis. Task-based operations for pattern extraction, learning documentation, guideline updates, knowledge sharing, and continuous improvement. Use when extracting learnings from completed skills, updating best practices, improving development process, or feeding continuous improvement cycle.

Quality

73%

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 ./.claude/skills/best-practices-learner/SKILL.md

The canonical home for this skill is best-practices-learner in fernandezbaptiste/Skrillz

Quality

Content

63%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 well-structured instruction skill with clear operations, embedded validation, and concrete templates, scoring well on actionability and workflow clarity. Its main weaknesses are verbosity/padding and a monolithic layout that inlines content which could be split into one-level-deep reference files.

Suggestions

Trim motivational lines and repetitive question-bullet prompts (e.g. the 'What worked well/made it easier' lists) to reduce padding and respect Claude's competence.

Move the five per-operation worked examples into separate reference files (e.g. references/extract-patterns.md) linked one level deep from the main operations section.

Add explicit error-recovery feedback loops (validate -> fix -> re-validate) to the operations that update shared guidelines, since those are batch/shared-state changes.

Dimension	Reasoning	Score
Conciseness	The ~480-line body is mostly organized but includes padded motivational lines ('Every skill built teaches us something - capture those lessons') and repetitive question-bullet prompts ('What worked well?', 'What made it easier/faster?') that over-explain steps Claude could infer.	3 / 5
Actionability	Each operation provides numbered process steps plus concrete worked examples with structured output templates (e.g. the 'Pattern Extracted: Quick Reference Section' block), giving mostly executable guidance with only minor gaps.	4 / 5
Workflow Clarity	Operations are clearly sequenced with numbered steps, and validation checkpoints are embedded (Operation 1 step 3 'Validate Pattern', Operation 3 step 4 'Validate Updates'), though error-recovery feedback loops are only implicit.	4 / 5
Progressive Disclosure	The file has good section headers and a Quick Reference, but it is monolithic with no bundle files; the five full operations with examples are inlined where separate reference files would aid navigation.	3 / 5
	Total	14 / 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.

The description is strong: it uses third-person voice, states a clear purpose, lists multiple operations, and provides an explicit 'Use when' trigger clause covering both what and when. It is held back only by slightly abstract action verbs and minor trigger-term synonym gaps.

Dimension	Reasoning	Score
Specificity	Names the domain ('skill development experience, review findings, and pattern analysis') and lists several concrete operations ('pattern extraction, learning documentation, guideline updates, knowledge sharing, and continuous improvement'), but the actions remain somewhat abstract verbs rather than fully concrete procedures.	4 / 5
Completeness	It explicitly answers both 'what' (extract learnings/best practices, task-based operations) and 'when' via a concrete 'Use when extracting learnings... or feeding continuous improvement cycle' clause with explicit trigger phrases.	5 / 5
Trigger Term Quality	The 'Use when' clause surfaces natural phrases a user would say ('extracting learnings from completed skills', 'updating best practices', 'improving development process', 'continuous improvement cycle') with good coverage, though a few common synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	The niche (skill-development meta-process / continuous improvement) is fairly distinct with specific triggers, but it could still overlap with generic analysis or review skills, leaving minor conflict risk.	4 / 5
	Total	17 / 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
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: fernandezbaptiste/Skrillz
Path: .claude/skills/best-practices-learner/SKILL.md
Commit: 93ed392

Reviewed: 1 day 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.