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".
89
79%
Does it follow best practices?
Impact
96%
2.90xAverage score across 6 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/1-moltbot-skills/SKILL.mdQuality
Discovery
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 answering both what the skill does and when to use it. The main weakness is that the capability description is somewhat abstract ('capturing and retrieving understanding') rather than listing concrete specific actions. The trigger terms are well-chosen and natural, though some like 'save this' and 'remember' could potentially conflict with other memory or note-taking skills.
Suggestions
Replace abstract language like 'capturing and retrieving understanding' with concrete actions such as 'save notes, tag concepts, search stored knowledge, organize learnings by topic'.
Add more specific capability details to improve distinctiveness, e.g., mention what makes this different from generic note-taking (Ensue-specific features, knowledge graph, concept linking, etc.).
| 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 like 'create notes, tag concepts, search entries, export knowledge'. | 2 / 3 |
Completeness | Clearly answers both 'what' (personal knowledge base for capturing and retrieving understanding) and 'when' (explicit 'Use when' clause plus a 'Triggers on' list with specific phrases). Both components are explicitly stated. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would actually say: 'save this', 'remember', 'what do I know about', 'add to toolbox', 'my notes on', 'store this concept'. These are realistic, varied phrases that match how users naturally express knowledge management needs. | 3 / 3 |
Distinctiveness Conflict Risk | The knowledge base / notes domain is somewhat specific, and the 'Ensue' platform reference helps distinguish it. However, terms like 'save this' and 'remember' are generic enough that they could overlap with general note-taking or memory skills. The 'toolbox' concept adds some distinctiveness but could still conflict with other knowledge management skills. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
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 inline content templates and comprehensive reference material make it a long single file that could benefit from progressive disclosure via bundle files. The content is well-structured and provides good guardrails through anti-patterns and security rules.
Suggestions
Extract the four content format templates (Concepts, Toolbox, Patterns, References) into a separate TEMPLATES.md file referenced from the main skill to reduce token footprint.
Move the API operations section into a separate API-REFERENCE.md, keeping only the most common operation (search + create) inline as quick examples.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-structured but includes some unnecessary verbosity. The Philosophy section and some explanatory prose ('Not a note dump', 'Will future-me thank me for this?') add flavor but consume tokens without adding actionable value. The content formats section is quite lengthy with templates that could be more compact. However, it avoids explaining basic concepts Claude already knows. | 2 / 3 |
Actionability | The skill provides fully executable bash commands for all API operations, concrete content templates with clear field structures, a complete namespace hierarchy, and a detailed intent mapping table. Every operation has a copy-paste ready command example. | 3 / 3 |
Workflow Clarity | The saving workflow has a clear 4-step sequence (ask → draft → confirm → save+confirm). The interaction rules section provides explicit validation checkpoints ('Before saving, verify' checklist). Anti-patterns serve as guardrails. The intent mapping table clearly sequences user intent to action. Delete operations require confirmation. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and headers, but it's entirely monolithic — all content formats, API usage, setup, security, and intent mapping are inline in a single file. The namespace structure, content templates, and API reference could benefit from being split into separate referenced files. No bundle files are provided to offload detail. | 2 / 3 |
Total | 10 / 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.
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-data
- Commit
b1a95aa
- 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.