CtrlK
BlogDocsLog inGet started
Tessl Logo

common-learning-log

Append a structured learning entry to AGENTS_LEARNING.md whenever an AI agent makes a mistake. Auto-activates as a composite skill when: a pre-write skill violation is detected and auto-fixed, or when the session retrospective finds a correction loop. Also triggers directly when the user corrects the AI mid-session. Use when: mistake, wrong, redo, that's not right, correction, my bad, fix that error, I made a mistake, agent error, learning log, log mistake, AGENTS_LEARNING.md

71

Quality

88%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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 with a clear workflow for logging agent mistakes. Its main weakness is that the critical log entry format is delegated to a reference file that doesn't exist in the bundle, making the skill incomplete in isolation. There are also a few minor typos in the Guidelines section that slightly reduce professionalism.

Suggestions

Include the referenced 'references/log-format.md' in the bundle, or inline a minimal log entry template directly in the SKILL.md so the skill is self-contained enough to execute

Fix typos in Guidelines: 'that wrong' → 'that was wrong', 'what to' → 'what to do', 'all corrections learning signals' → 'all corrections are learning signals'

DimensionReasoningScore

Conciseness

The skill is lean and efficient. Every section serves a purpose—protocol steps, guidelines, and anti-patterns are all tightly written without explaining concepts Claude already knows. No unnecessary preamble or padding.

3 / 3

Actionability

The protocol steps are clear and specific (read file, count headers, append entry), but the actual log entry format is deferred to a reference file that isn't provided in the bundle. The skill also has minor typos ('what to' instead of 'what to do', 'that wrong' instead of 'that was wrong') that slightly reduce clarity. Without the referenced template, Claude can't fully execute the skill.

2 / 3

Workflow Clarity

The 4-step protocol is clearly sequenced with explicit trigger detection, state reading, writing, and continuation. The workflow is simple enough that validation checkpoints aren't critical—appending to a markdown file is non-destructive, and the anti-patterns section covers error prevention (no duplicates, no overwriting, always append).

3 / 3

Progressive Disclosure

The skill appropriately references a separate log-format.md for the entry template, which is good progressive disclosure. However, the bundle files note says no bundle files were provided, meaning the referenced 'references/log-format.md' doesn't actually exist in the bundle, making the reference unresolvable and the skill incomplete without it.

2 / 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 an excellent skill description that clearly defines a specific niche (logging AI agent mistakes to AGENTS_LEARNING.md), provides comprehensive trigger conditions including both automatic and manual activation scenarios, and includes a rich set of natural trigger terms. The description is well-structured, uses third person voice appropriately, and would be easily distinguishable from other skills in a large skill library.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete actions: 'Append a structured learning entry to AGENTS_LEARNING.md', 'pre-write skill violation is detected and auto-fixed', 'session retrospective finds a correction loop', and 'user corrects the AI mid-session'. These are detailed, concrete behaviors.

3 / 3

Completeness

Clearly answers both 'what' (append structured learning entries to AGENTS_LEARNING.md when mistakes occur) and 'when' (explicit 'Use when:' clause with trigger terms, plus detailed auto-activation conditions). Both dimensions are thoroughly covered.

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms users would say: 'mistake', 'wrong', 'redo', 'that's not right', 'correction', 'my bad', 'fix that error', 'I made a mistake', 'agent error', 'learning log', 'log mistake', and the specific file 'AGENTS_LEARNING.md'. These are highly natural phrases.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive niche: logging AI agent mistakes to a specific file (AGENTS_LEARNING.md). The combination of error correction, learning logs, and the specific file target makes it very unlikely to conflict with other skills like general error handling or code fixing.

3 / 3

Total

12

/

12

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation9 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

9

/

11

Passed

Repository
HoangNguyen0403/agent-skills-standard
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.