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

79%

Does it follow best practices?

Impact

96%

2.90x

Average score across 6 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/data/1-moltbot-skills/SKILL.md

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 solid, actionable skill with clear workflows and executable API examples. Its main weakness is length—the content format templates and namespace structure documentation inflate the file when they could be referenced externally. The skill effectively balances structure with practical guidance, though it could be more concise by trimming template scaffolding and trusting Claude to interpolate formats from a single example.

Suggestions

Move the detailed content format templates (Concepts, Toolbox, Patterns, References) into a separate FORMATS.md file and reference it from the main skill, reducing the SKILL.md length significantly.

Trim the Philosophy section—Claude doesn't need motivational framing like 'Will future-me thank me for this?' to follow instructions; convert it to a brief bullet list of constraints.

Dimension	Reasoning	Score
Conciseness	The skill is reasonably well-structured but includes some unnecessary content. The Philosophy section's rhetorical question and some of the content format templates are verbose—Claude doesn't need full template scaffolding for concepts, patterns, and references when a single example would suffice. The intent mapping table and anti-patterns are useful but could be tighter.	2 / 3
Actionability	The API usage section provides fully executable bash commands for all CRUD operations with concrete JSON arguments. The namespace structure, content formats, and intent mapping table give Claude specific, copy-paste-ready guidance on exactly what to do in each scenario.	3 / 3
Workflow Clarity	The saving workflow has a clear 4-step sequence (ask → draft → confirm → save+confirm). The anti-patterns section provides explicit guardrails (don't auto-save, check for duplicates first). The 'Maintaining Quality' checklist serves as a validation checkpoint before saves. The intent mapping table clearly sequences actions for each trigger.	3 / 3
Progressive Disclosure	The content is well-organized with clear sections and headers, but it's a long monolithic file (~180 lines) with no references to external files. The detailed content format templates (Concepts, Toolbox, Patterns, References) could be split into separate reference files. No bundle files are provided to support progressive disclosure.	2 / 3
	Total	10 / 12 Passed

Description

82%

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 solid description with strong trigger term coverage and good completeness, explicitly stating both what the skill does and when to use it. Its main weaknesses are slightly abstract capability descriptions (could be more concrete about specific operations like 'create entries', 'search by topic', 'list stored concepts') and moderate overlap risk with other note-taking or memory-related skills.

Suggestions

Replace abstract phrases like 'capturing and retrieving understanding' with concrete actions such as 'create knowledge entries, search stored concepts, list topics, update notes'.

Add distinguishing details about what makes this different from generic note-taking, e.g., mention specific features of the Ensue-powered system or the structure of the toolbox.

Dimension	Reasoning	Score
Specificity	The description names the domain ('personal knowledge base') and some actions ('capturing and retrieving understanding'), but the actions are somewhat abstract rather than listing multiple concrete operations. 'Save knowledge', 'recall', 'manage toolbox' are mentioned but as trigger scenarios rather than specific capabilities.	2 / 3
Completeness	The description clearly answers both 'what' (personal knowledge base for capturing and retrieving understanding) and 'when' (explicit 'Use when' clause with specific scenarios plus a 'Triggers on' list with concrete phrases). Both components are explicitly stated.	3 / 3
Trigger Term Quality	The description includes excellent natural trigger terms that users would actually say: 'save this', 'remember', 'what do I know about', 'add to toolbox', 'my notes on', 'store this concept'. These are natural, varied, and cover multiple ways a user might phrase their intent.	3 / 3
Distinctiveness Conflict Risk	While the trigger terms are fairly specific, 'knowledge base', 'save this', and 'remember' could overlap with general note-taking or memory skills. The mention of 'Ensue' and 'toolbox' adds some distinctiveness, but 'personal knowledge base' is a broad category that could conflict with similar skills.	2 / 3
	Total	10 / 12 Passed

Validation

81%

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 — 9 / 11 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	9 / 11 Passed

Repository: majiayu000/claude-skill-registry
Commit: c3c7445

Reviewed: 1 day 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.