learner
Extract a learned skill from the current conversation
66
58%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/learner/SKILL.mdQuality
Discovery
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 provides a basic understanding of the skill's purpose but is too terse to be effective for skill selection. It lacks explicit trigger conditions and doesn't enumerate the specific actions or outputs involved in skill extraction. The absence of a 'Use when...' clause significantly limits Claude's ability to know when to select this skill.
Suggestions
Add a 'Use when...' clause with trigger terms like 'save this skill', 'remember how to do this', 'create a skill from this conversation', or 'extract what we learned'.
Expand the capability description to include specific actions such as 'analyzes conversation patterns, identifies reusable procedures, generates SKILL.md files'.
Include natural language variations users might say: 'turn this into a skill', 'save this workflow', 'make this reusable'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names a specific action ('Extract a learned skill') and context ('current conversation'), but lacks detail on what extraction entails or what outputs are produced. | 2 / 3 |
Completeness | Describes what it does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Contains some relevant terms ('skill', 'conversation', 'extract') but misses common variations users might say like 'save skill', 'create skill', 'learn from this', or 'remember how to'. | 2 / 3 |
Distinctiveness Conflict Risk | The phrase 'learned skill' and 'current conversation' provide some specificity, but 'extract' is generic and could overlap with other extraction-related skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured meta-skill that effectively teaches Claude how to extract reusable skills. Its strengths are the clear workflow steps, explicit quality gates, and good separation of concerns between expertise and procedure. Minor verbosity in the expertise section (redundant anti-patterns, repeated examples) prevents a perfect conciseness score.
Suggestions
Consolidate the 'Anti-Patterns' section into the 'Quality Gate' - they express the same criteria in different forms
Reduce example redundancy by having fewer but more varied BAD/GOOD pairs across sections
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy - the anti-patterns section largely restates the quality gate negatively, and some examples are repeated across sections. The BAD/GOOD comparisons are helpful but could be tighter. | 2 / 3 |
Actionability | Provides concrete, executable guidance with specific file paths, templates, classification criteria, and exact save locations. The quality gate checklist and skill body template are copy-paste ready with clear decision points. | 3 / 3 |
Workflow Clarity | Clear 4-step sequence with explicit validation (Step 2 Quality Validation acts as a checkpoint). The workflow section is well-separated from expertise, and each step has specific outputs and criteria for proceeding. | 3 / 3 |
Progressive Disclosure | Excellent structure with clear separation between Expertise (updatable domain knowledge) and Workflow (stable procedure). The meta-explanation at the top explains the two-section design, and related commands are appropriately referenced at the end. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- Yeachan-Heo/oh-my-claudecode
- Commit
48ffaac
- 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.