capture-learnings

Capture and apply accumulated knowledge via structured memory. Use when the user gives feedback, shares preferences, corrects a mistake, or when you discover something worth remembering for future conversations.

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/capture-learnings/SKILL.md

Quality

Content

61%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 solid, actionable instruction-only skill with concrete commands and clear scope guidance. It would benefit from explicit validation checkpoints for its destructive/batch operations and from de-duplicating the Memory Types table against the 'When to Capture' subsections.

Suggestions

Add explicit validation checkpoints for destructive/batch operations: e.g., 'before delete-memory, confirm the memory is not referenced elsewhere; before a shared-scope write, verify scope resolves to the intended organization'.

De-duplicate the Memory Types table and the 'When to Capture' subsections — keep the table as the index and move the per-type examples into a single consolidated section, or vice versa.

Include one fully-worked end-to-end example (e.g., a real save-memory invocation with concrete name/type/description/content) to bridge the remaining actionability gap.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and assumes Claude's intelligence, but the Memory Types table is duplicated by the 'When to Capture' subsections and 'Key Rules' partly restates earlier guidance, offering clear tightening opportunities.	3 / 5
Actionability	Provides concrete, copy-paste-ready commands (save-memory, resource-read, delete-memory, resource-list) with scope guidance and per-type examples, with only minor gaps from placeholders and no fully worked end-to-end example.	4 / 5
Workflow Clarity	A read-before-update sequence is clearly stated, but the skill involves destructive and batch operations (delete-memory, overwriting shared LEARNINGS.md, shared-scope writes) with no explicit validation or verification checkpoints, capping this dimension at 3 per the rubric.	3 / 5
Progressive Disclosure	Well-organized single-file skill with clear section headers and no nested references; minor organization gaps from the table/subsection duplication and a body slightly over the simple-skill line keep it just below a 5.	4 / 5
	Total	14 / 20 Passed

Description

67%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 well-crafted description that clearly states both capability and concrete use triggers, with natural phrasing users would actually produce. Minor room to broaden trigger synonyms and surface the full action set (update/delete).

Dimension	Reasoning	Score
Specificity	Names the domain ('structured memory') and several concrete capture actions with multiple trigger conditions, but does not comprehensively enumerate the full action set (read/update/delete), leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers both what ('Capture and apply accumulated knowledge via structured memory') and when, with a concrete multi-trigger 'Use when...' clause, matching the anchor for clearly and explicitly answering both.	5 / 5
Trigger Term Quality	Includes several natural user phrases ('gives feedback', 'shares preferences', 'corrects a mistake') that a user would actually say, but misses common synonyms like 'remember this', 'note this', or 'save this'.	4 / 5
Distinctiveness Conflict Risk	The structured-memory framing is a clear niche with distinct triggers, with only minor overlap risk against closely related notes or task-tracking skills.	4 / 5
	Total	17 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: BuilderIO/agent-native
Path: .agents/skills/capture-learnings/SKILL.md
Commit: cc2a915

Reviewed: 3 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.