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".

Quality

86%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

72%

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 the rule capture format, categories, and guardrails. Its main weakness is the vagueness around the actual persistence mechanism — it tells Claude to 'persist to LEARNED section or project memory' without specifying the concrete file path, tool, or command to use. The wiki-scoping feature is a nice addition but also lacks specifics on how the 'capture hook' works.

Suggestions

Specify the exact persistence mechanism: which file to write to (e.g., `LEARNED.md` or `.claude/memory.md`), and what tool/command to use (e.g., `write_to_file` or appending to a specific section).

Add a verification step after persistence (e.g., 'Read back the file to confirm the rule was appended correctly') to close the feedback loop on this potentially important operation.

Dimension	Reasoning	Score
Conciseness	The skill is lean and efficient. It avoids explaining concepts Claude already knows, uses tables and structured formats to convey information densely, and every section serves a clear purpose. The guardrails section efficiently distinguishes good from bad rules with concrete examples.	3 / 3
Actionability	The skill provides a clear format template and a concrete example, but the persistence mechanism is vague — 'persist to LEARNED section or project memory' doesn't specify how (which file, what tool, what command). The workflow steps are descriptive rather than executable, leaving ambiguity about the actual implementation.	2 / 3
Workflow Clarity	The 4-step workflow is clearly sequenced and includes a user approval checkpoint (step 3), which is good. However, there's no validation step to verify the rule was actually persisted correctly, and the persistence target ('LEARNED section or project memory') is ambiguous — it's unclear where exactly to write or how to confirm success.	2 / 3
Progressive Disclosure	For a skill of this size and scope (~60 lines, single-purpose), the content is well-organized with clear sections (Trigger, Workflow, Format, Categories, Example, Guardrails, Output). No bundle files are needed, and the structure supports easy scanning and discovery without unnecessary nesting.	3 / 3
	Total	10 / 12 Passed

Description

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 what the skill does (captures and stores learning rules with structured fields), when to use it (after mistakes or specific user phrases), and uses third-person voice throughout. It provides natural trigger terms that users would realistically say and occupies a distinct niche that minimizes conflict with other skills.

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 natural trigger phrases users would actually say: 'remember this', 'don't forget', 'note this', 'learn from this', and contextual triggers like 'after mistakes'. These are realistic user utterances with good coverage.	3 / 3
Distinctiveness Conflict Risk	Has a clear niche around persistent learning rules and corrections with distinct trigger terms. Unlikely to conflict with other skills since the domain of capturing and storing correction rules is quite specific and the trigger phrases are distinctive.	3 / 3
	Total	12 / 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: rohitg00/pro-workflow
Commit: 5c313e2

Reviewed: 14 days 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.