continuous-learning
Automatically extract reusable patterns from Claude Code sessions and save them as learned skills for future use.
39
36%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./docs/zh-TW/skills/continuous-learning/SKILL.mdQuality
Discovery
50%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 communicates the core purpose reasonably well—extracting patterns from Claude Code sessions to create reusable skills—but lacks the specificity and explicit trigger guidance needed for reliable skill selection. It would benefit from listing concrete actions and adding a 'Use when...' clause with natural trigger terms.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to save a workflow, create a skill file, remember a pattern, or extract a reusable technique from the current session.'
List more specific concrete actions, e.g., 'Analyzes conversation history, identifies repeatable workflows, generates SKILL.md files with proper frontmatter and instructions.'
Include natural trigger terms users might say, such as 'save this as a skill', 'remember how to do this', 'create a skill file', 'SKILL.md'.
| 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 lacks an explicit 'Use when...' clause or trigger guidance, which per the rubric caps completeness at 2. | 2 / 3 |
Trigger Term Quality | Includes some relevant terms like 'patterns', 'Claude Code sessions', 'learned skills', but misses natural user phrases like 'save skill', 'create skill file', 'SKILL.md', 'remember this pattern', or 'extract workflow'. | 2 / 3 |
Distinctiveness Conflict Risk | The concept of extracting patterns from sessions is somewhat specific, but 'reusable patterns' and 'learned skills' are broad enough to potentially overlap with other meta-learning or documentation skills. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
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 design document or README 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 logic and validation steps needed for Claude to actually perform continuous learning. The configuration examples are useful but insufficient without the actual extraction implementation.
Suggestions
Remove the 'Comparison Notes' and 'Potential v2 Enhancements' sections entirely, or move them to a separate docs/ file—they consume tokens without helping Claude execute the skill.
Add the actual evaluate-session.sh script content or describe the concrete steps Claude should take to analyze a session and extract patterns, with executable examples.
Add explicit validation and review steps: how to verify an extracted skill is correct, what to do when auto_approve is false, and how to handle extraction failures.
Remove the 'Why Stop Hook?' section—Claude doesn't need justification for architectural decisions, just 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' roadmap section, and pattern type descriptions that are largely self-evident. Much of the content is informational rather than instructional. | 1 / 3 |
Actionability | The hook configuration JSON and config.json are concrete and copy-paste ready, which is good. However, the actual core script (evaluate-session.sh) is never shown or described in terms of what it does internally. There's no executable code for the pattern extraction logic itself—just configuration and setup. | 2 / 3 |
Workflow Clarity | The three-step workflow (evaluate → detect → extract) is described at a very high level with no validation checkpoints, no error handling, no feedback loops. There's no guidance on what happens if extraction fails, how to verify learned skills are correct, or how to review/approve extracted patterns when auto_approve is false. | 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 has some structure with headers but mixes operational guidance with research notes. | 2 / 3 |
Total | 6 / 12 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- ysyecust/everything-claude-code
- Commit
79cc4e3
- 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.