bear-notes
Create, search, and manage Bear notes via grizzly CLI.
72
61%
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 ./skills/bear-notes/SKILL.mdQuality
Discovery
50%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 concise and identifies a clear niche (Bear notes via grizzly CLI) with specific actions, making it distinctive. However, it lacks a 'Use when...' clause, which is critical for Claude to know when to select this skill, and it could benefit from additional trigger terms that users might naturally say.
Suggestions
Add a 'Use when...' clause, e.g., 'Use when the user wants to create, search, edit, or organize notes in Bear, or mentions the grizzly CLI.'
Include additional natural trigger terms such as 'Bear app,' 'note-taking,' 'markdown notes,' 'tags,' or 'organize notes' to improve keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Create, search, and manage Bear notes.' Also specifies the tool used: 'grizzly CLI.' | 3 / 3 |
Completeness | Describes what the skill does but has no 'Use when...' clause or equivalent explicit trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and since the 'when' is entirely absent, this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Bear notes' and 'grizzly CLI,' but misses common user variations such as 'note-taking,' 'Bear app,' or specific actions like 'edit,' 'delete,' 'tag,' or 'organize notes.' | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Bear notes' and 'grizzly CLI' creates a very clear niche that is unlikely to conflict with other skills. These are highly specific product/tool names. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
72%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, practical skill for managing Bear notes via the grizzly CLI. Its main strengths are concrete, executable command examples and good structural organization. Its weaknesses are minor verbosity (redundant mentions of token requirements, a 'Notes' section that mostly restates earlier content) and the lack of any verification steps after write operations.
Suggestions
Remove the 'Notes' section or fold its unique content into relevant sections to reduce redundancy (e.g., token requirements are already mentioned in the 'Getting a Bear Token' section header and individual commands).
Add a brief verification step after create/add-text commands, e.g., 'Verify: grizzly open-note --id "NOTE_ID" --enable-callback --json' to confirm the operation succeeded.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but has some unnecessary explanation. The 'Notes' section at the bottom repeats information already implied or stated (e.g., Bear must be running, token requirements mentioned multiple times). The Configuration section with priority order and example TOML is useful but slightly verbose for a skill file. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready bash commands for all common operations. Each command example is concrete with specific flags and piping patterns. The token setup instructions are step-by-step and actionable. | 3 / 3 |
Workflow Clarity | Commands are clearly presented but there's no validation or error handling guidance. For operations that modify notes (add-text, create), there are no verification steps (e.g., confirming the note was created/updated). The token setup is sequential but the overall workflow for a typical session isn't explicitly sequenced. | 2 / 3 |
Progressive Disclosure | For a simple CLI tool skill with no bundle files, the content is well-organized into logical sections (token setup, common commands, options, configuration) that are easy to scan. The skill is under 80 lines and doesn't need external references; sections are appropriately scoped. | 3 / 3 |
Total | 10 / 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
- deepgram/dglabs-deepclaw
- Commit
ec8d4f8
- 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.