CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

72

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

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

A lean, well-structured instruction skill: no filler, concrete format templates, and a clear approval-gated workflow. The main gaps are the unspecified persistence target for the rule and the absence of any post-persist verification, plus body length slightly over the simple-skill threshold.

Suggestions

Specify exactly where the LEARNED section or project memory lives (a concrete file path or memory location) so the persist step in the Workflow is executable without guesswork.

Add a brief post-persist confirmation step (e.g., re-read the stored rule and report it back) to close the feedback loop and lift workflow clarity.

Consider moving the 8-row categories table and one of the two example blocks into a small reference file to keep the body under the ~50-line simple-skill threshold.

DimensionReasoningScore

Conciseness

Every section earns its place: the workflow is four terse steps, the format is given as copy-paste blocks, categories live in a compact table, and the only environment-specific detail ("The capture hook auto-detects `Wiki: <slug>` and links the learning to that wiki via `learnings_wiki`") is genuinely non-obvious. There is no explanation of concepts Claude already knows, matching the lean anchor.

5 / 5

Actionability

The `[LEARN]` format blocks and the worked example are concrete and reusable, and the categories table makes rule classification actionable. However, the persistence step ("persist to LEARNED section or project memory") never specifies where that section or memory lives, leaving a minor execution gap that keeps it out of the fully copy-paste-ready 5 anchor.

4 / 5

Workflow Clarity

The four-step sequence (identify → format → propose and wait for approval → persist) is clear, and the approval gate acts as an explicit checkpoint before the state-changing write. It falls short of 5 because there is no post-persist verification or error-recovery loop (e.g., confirming the rule was stored or what to do on a failed write).

4 / 5

Progressive Disclosure

The skill is self-contained with no bundle files and well-organized sections (Trigger, Workflow, Format, Categories, Example, Guardrails, Output), so nothing needs external references. At ~69 body lines it exceeds the under-50-line simple-skill exception, and the categories table plus two example blocks could arguably live in a reference file, matching the "good structure; minor organization gaps" 4 anchor rather than 5.

4 / 5

Total

17

/

20

Passed

Description

96%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person, concise, concrete about capabilities, and explicit about both what it does and when to use it, with natural trigger phrases. The only weakness is mild overlap risk between its trigger terms and generic memory-related skills.

DimensionReasoningScore

Specificity

"Capture a correction or lesson as a persistent learning rule with category, mistake, and correction. Stores, categorises, and retrieves rules" lists multiple concrete actions covering the skill's full lifecycle, matching the comprehensive-coverage anchor. It is a clear fit for 5; score 4 would require minor coverage gaps, but capture, store, categorise, and retrieve leave none.

5 / 5

Completeness

It explicitly answers what ("Capture a correction or lesson as a persistent learning rule... Stores, categorises, and retrieves rules") and when ("Use after mistakes or when the user says 'remember this'...") with concrete trigger phrases, matching the 5 anchor exactly. A missing or weak 'when' clause would cap it at 3, which is not the case.

5 / 5

Trigger Term Quality

The description includes natural user phrasings — "remember this", "don't forget", "note this", "learn from this" — plus "after mistakes", giving comprehensive synonym coverage of how users would naturally request this. Score 4 would mean missing common variations, and none are absent.

5 / 5

Distinctiveness Conflict Risk

The learning-rule niche is clear, but triggers like "remember this" carry minor overlap risk with general memory/persistence skills, matching the "mostly distinct; minor overlap risk" anchor. It is not a 5 because those phrases are not uniquely bound to this skill, and not a 3 since the category/mistake/correction framing is distinctive.

4 / 5

Total

19

/

20

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

Validation for skill structure

No warnings or errors.

Repository

rohitg00/pro-workflow

Path

skills/learn-rule/SKILL.md

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.