learn-rule
Capture a correction or lesson as a persistent learning rule with category, mistake, and correction. Stores, categorises, and retrieves rules for future sessions. Use after mistakes or when the user says "remember this", "don't forget", "note this", or "learn from this".
95
92%
Does it follow best practices?
Impact
100%
3.70xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that clearly communicates its purpose, lists concrete actions, and provides explicit trigger guidance with natural user phrases. It uses proper third-person voice throughout and is concise without being vague. It serves as a strong example of an effective skill description.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Capture a correction or lesson as a persistent learning rule', 'with category, mistake, and correction', 'Stores, categorises, and retrieves rules for future sessions'. These are concrete, well-defined capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (capture corrections/lessons as persistent learning rules, store/categorize/retrieve them) and 'when' (after mistakes, or when user says 'remember this', 'don't forget', 'note this', 'learn from this') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes highly natural trigger phrases users would actually say: 'remember this', 'don't forget', 'note this', 'learn from this', plus contextual triggers like 'after mistakes'. These are realistic user utterances with good coverage. | 3 / 3 |
Distinctiveness Conflict Risk | Occupies a clear niche around persistent learning rules and corrections with distinct trigger terms. The combination of 'correction', 'lesson', 'persistent learning rule', and the specific trigger phrases makes it unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 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, concise skill that clearly defines when to trigger, what format to use, and includes good guardrails around user approval. Its main weakness is the vagueness around the actual persistence mechanism — it says 'persist to LEARNED section or project memory' without specifying the concrete tool call or file path, which reduces actionability.
Suggestions
Specify the concrete persistence mechanism: which file to write to (e.g., `memory.md`, `.claude/learned_rules.md`) and/or which tool to use (e.g., file write commands).
Add an example showing the complete end-to-end flow including the actual persistence step (e.g., appending to a specific file with a code block showing the final file content).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. Every section serves a purpose — trigger conditions, workflow, format, categories, example, and guardrails. No unnecessary explanations of concepts Claude already knows. | 3 / 3 |
Actionability | The format template and example are concrete, but the persistence step ('persist to LEARNED section or project memory') is vague — it doesn't specify how or where to write the rule (e.g., which file, what tool to use). The workflow describes what to do conceptually but lacks executable commands or tool invocations. | 2 / 3 |
Workflow Clarity | The 4-step workflow is clearly sequenced with an explicit approval checkpoint before persisting. The guardrails reinforce the validation step ('Always wait for user approval before persisting'). For this type of conversational skill, the workflow is appropriately detailed. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines with no need for external references, the content is well-organized into clear sections (Trigger, Workflow, Format, Categories, Example, Guardrails, Output) that are easy to scan and navigate. | 3 / 3 |
Total | 11 / 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
- rohitg00/pro-workflow
- Commit
1de1554
- 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.