bear-notes
Create, search, and manage Bear notes via grizzly CLI.
74
Quality
63%
Does it follow best practices?
Impact
100%
3.57xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./openclaw/skills/bear-notes/SKILL.mdQuality
Discovery
40%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 identifies a clear, distinct niche (Bear notes via grizzly CLI) but suffers from incomplete trigger guidance and moderate specificity. The lack of a 'Use when...' clause is a significant gap that would make it harder for Claude to know when to select this skill from a large pool.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user mentions Bear app, Bear notes, grizzly, or wants to manage markdown notes in Bear.'
Expand 'manage' into specific concrete actions such as 'edit, delete, tag, archive, or export Bear notes'
Include natural keyword variations users might say: 'Bear app', 'note-taking', 'find my notes', 'new note'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Bear notes) and lists three actions (create, search, manage), but 'manage' is vague and doesn't specify concrete operations like delete, archive, tag, or export. | 2 / 3 |
Completeness | Describes what it does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes 'Bear notes' and 'grizzly CLI' which are relevant keywords, but misses common variations users might say like 'note-taking', 'Bear app', or specific actions like 'find notes', 'add note'. | 2 / 3 |
Distinctiveness Conflict Risk | Very distinct niche - 'Bear notes' and 'grizzly CLI' are specific enough that this would not conflict with other note-taking or document skills. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
87%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-crafted skill that provides clear, actionable guidance for using the grizzly CLI with Bear notes. The content is appropriately concise and all examples are executable. The main weakness is the lack of validation steps or error handling guidance for operations that modify notes.
Suggestions
Add a brief note about how to verify a note was created/modified successfully (e.g., using open-note to confirm changes)
Include common error scenarios and how to handle them (e.g., what happens if Bear isn't running, invalid token, note ID not found)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only necessary information without explaining what Bear is or how CLI tools work. Every section serves a clear purpose with no padding. | 3 / 3 |
Actionability | All commands are fully executable and copy-paste ready. The examples show real command patterns with proper flags, and the token setup instructions are concrete and specific. | 3 / 3 |
Workflow Clarity | Commands are clearly documented but there's no validation or error handling guidance. For operations that modify notes (add-text, create), there's no feedback loop to verify success or handle failures. | 2 / 3 |
Progressive Disclosure | For a skill of this size (~70 lines), the content is well-organized with clear sections (Commands, Options, Configuration, Notes). No external references needed and the structure allows quick scanning. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 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 |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
- Repository
- trpc-group/trpc-agent-go
- Commit
50ef2f3
- 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.