continuous-learning

Automatically extract reusable patterns from Claude Code sessions and save them as learned skills for future use.

Quality

27%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./docs/zh-TW/skills/continuous-learning/SKILL.md

Quality

Content

22%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill reads more like a project README or design document than an actionable skill for Claude. It spends significant tokens on comparisons with other tools, future enhancement ideas, and justifications for design decisions, while lacking the core executable content (the evaluation script) and any validation workflow. The actionable parts (hook config, settings JSON) are useful but insufficient without the actual implementation details.

Suggestions

Remove the 'Comparison Notes' and 'Potential v2 Enhancements' sections entirely, or move them to a separate docs/ file—they are research notes, not operational guidance.

Include the actual evaluate-session.sh script content or at minimum describe its concrete logic (what it reads, how it identifies patterns, what output format it produces).

Add explicit validation steps: how to review extracted skills before they're saved, what to do if a pattern is incorrectly extracted, and how auto_approve=false works in practice.

Remove the 'Why Stop Hook?' section—Claude doesn't need justification for architectural decisions; it needs instructions on what to do.

Dimension	Reasoning	Score
Conciseness	The skill contains significant bloat: a comparison table with Homunculus that is research/notes rather than actionable guidance, explanations of why a Stop hook is used (Claude doesn't need this justification), a 'Potential v2 Enhancements' section that is speculative roadmap content, and a pattern types table that mostly restates obvious concepts. Much of this content doesn't earn its token cost.	1 / 3
Actionability	The hook configuration JSON and config.json are concrete and copy-paste ready, which is good. However, the core mechanism—the actual evaluate-session.sh script—is never shown or described in detail. The skill tells you to set up a hook pointing to a script but doesn't provide the script or explain what it actually does to extract patterns. The 'how it works' section is descriptive rather than instructive.	2 / 3
Workflow Clarity	The three-step 'how it works' description is extremely high-level with no validation checkpoints, no error handling, and no feedback loops. There's no guidance on what to do if pattern extraction fails, how to verify extracted skills are correct, or how to review/approve patterns when auto_approve is false. For a system that automatically writes learned skills, missing validation is a significant gap.	1 / 3
Progressive Disclosure	There are references to external files (docs/continuous-learning-v2-spec.md, config.json, evaluate-session.sh) but no bundle files are provided to support them. The comparison notes and v2 enhancements section should be in a separate document rather than inline. The main content structure has some organization with headers but mixes operational guidance with research notes.	2 / 3
	Total	6 / 12 Passed

Description

32%

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 the general purpose of the skill—extracting patterns from sessions and saving them—but lacks the specificity and explicit trigger guidance needed for reliable skill selection. It would benefit from concrete action verbs, specific trigger terms users might say, and an explicit 'Use when...' clause.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to save a pattern, create a skill, or capture a reusable workflow from the current session.'

List more specific concrete actions, e.g., 'Analyzes conversation history, identifies reusable coding patterns, and writes them as .md skill files in the skills directory.'

Include natural trigger terms users might say, such as 'save this as a skill', 'remember this pattern', 'extract skill', 'create a reusable template'.

Dimension	Reasoning	Score
Specificity	Names the domain (extracting patterns from Claude Code sessions) and a general action (save as learned skills), but doesn't list multiple specific concrete actions like what kinds of patterns, how extraction works, or what formats are saved.	2 / 3
Completeness	Describes what it does (extract reusable patterns and save as skills) but has no explicit 'Use when...' clause or trigger guidance, which per the rubric caps completeness at 2, and the 'what' is also somewhat vague, bringing it to 1.	1 / 3
Trigger Term Quality	Includes some relevant terms like 'patterns', 'Claude Code sessions', 'learned skills', but misses natural user phrases like 'save skill', 'remember this', 'create skill file', 'skill extraction', or '.md skill files'.	2 / 3
Distinctiveness Conflict Risk	The concept of extracting patterns from Claude Code sessions is somewhat specific, but 'reusable patterns' and 'learned skills' could overlap with other meta/learning skills or documentation skills without clearer boundaries.	2 / 3
	Total	7 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: ysyecust/everything-claude-code
Commit: 79cc4e3

Reviewed: 3 months 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.