second-brain

Personal knowledge base powered by Ensue for capturing and retrieving understanding. Use when user wants to save knowledge, recall what they know, manage their toolbox, or build on past learnings. Triggers on "save this", "remember", "what do I know about", "add to toolbox", "my notes on", "store this concept".

2.90x

Quality

—

Does it follow best practices?

Impact

96%

2.90x

Average score across 6 eval scenarios

Securityby

Passed

No known issues

Quality

Content

65%

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

The body is highly actionable with concrete API commands and templates, and is well-organized, but it is a long monolithic file with redundant quality/philosophy/anti-pattern sections and lacks validation feedback loops for destructive operations. The referenced ensue-api.sh script is not present in the bundle.

Suggestions

Consolidate the overlapping Philosophy, Maintaining Quality, and Anti-Patterns sections into one to remove redundancy (e.g. the 'no credentials/secrets' and 'written for future self' guidance each appears multiple times).

Add explicit validation/verification steps to the update and delete workflows (e.g. verify the entry exists and show a diff before delete; confirm the API call succeeded after update) so destructive operations have feedback loops.

Move the content-format templates and/or API Usage reference into separate reference files under references/ and provide the missing scripts/ensue-api.sh so the referenced bundle path actually exists, turning the monolithic SKILL.md into a lean overview with one-level-deep references.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with no padding about concepts Claude already knows, but the Philosophy, 'Maintaining Quality', and 'Anti-Patterns' sections overlap (e.g. 'No credentials', 'Written for future self', 'Don't save unused tools' each repeat across sections) and could be tightened; not the lean 'every token earns its place' level 3.	2 / 3
Actionability	Provides copy-paste-ready API commands ('ensue-api.sh discover_memories {"query":...}') plus exact content-format templates and an intent-mapping table — fully concrete, executable guidance rather than vague direction.	3 / 3
Workflow Clarity	Saving has a clear 4-step sequence including a post-save confirmation, but destructive update/delete flows ('Fetch, show diff, update'; 'Confirm, delete') lack validation/verification feedback loops; per the rubric, missing validation in destructive workflows caps this at 2 rather than 3.	2 / 3
Progressive Disclosure	Well-sectioned but a single ~260-line monolithic file with everything inline (format templates, API usage, toolbox index) that could be split into reference files, and the one referenced bundle path '{baseDir}/scripts/ensue-api.sh' has no corresponding scripts/ directory in the bundle — 'content that should be separate is inline' rather than a clean one-level-deep reference structure.	2 / 3
	Total	9 / 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.

The description is strong: it states a concrete domain, lists multiple capabilities, and provides explicit 'Use when' guidance plus a set of natural trigger phrases. It clearly answers both what the skill does and when to invoke it.

Dimension	Reasoning	Score
Specificity	Names the domain ('Personal knowledge base powered by Ensue') and lists multiple concrete actions — 'capturing and retrieving understanding', 'save knowledge, recall what they know, manage their toolbox', 'build on past learnings' — matching the 'lists multiple specific concrete actions' anchor rather than the single-domain anchor at 2.	3 / 3
Completeness	Answers both what ('Personal knowledge base... for capturing and retrieving understanding') and when ('Use when user wants to... Triggers on...') with explicit triggers, matching the top anchor; it is not the level below where 'when' is only implied.	3 / 3
Trigger Term Quality	Explicit natural phrases users would say — 'save this', 'remember', 'what do I know about', 'add to toolbox', 'my notes on', 'store this concept' — giving good coverage of natural terms rather than technical jargon.	3 / 3
Distinctiveness Conflict Risk	The Ensue-powered second-brain/toolbox/concepts niche with distinctive triggers ('add to toolbox', 'what do I know about') is unlikely to conflict with other skills, fitting the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	12 / 12 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: majiayu000/claude-skill-registry
Commit: 8271354

Reviewed: about 16 hours 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.