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 names specific actions (create, search, manage) tied to a clear domain (Bear notes via grizzly CLI), giving it strong specificity and distinctiveness. However, it lacks a 'Use when...' clause, which is critical for Claude to know when to select this skill, and it could benefit from more natural trigger terms users might use.
Suggestions
Add a 'Use when...' clause, e.g., 'Use when the user wants to create, search, edit, or organize notes in the Bear app, or mentions Bear, grizzly, or note management.'
Include additional natural trigger terms users might say, such as 'Bear app', 'note-taking', 'find notes', 'add a note', or 'organize notes'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Create, search, and manage Bear notes' and specifies the tool used ('grizzly CLI'). These are clear, actionable verbs tied to a specific domain. | 3 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, 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 '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', 'delete note'. | 2 / 3 |
Distinctiveness Conflict Risk | Very distinct niche — Bear notes via grizzly CLI is highly specific and unlikely to conflict with other skills. The combination of the Bear app and grizzly CLI tool creates a clear, unique trigger space. | 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 that provides clear, executable commands for managing Bear notes via grizzly CLI. Its main strengths are actionability and good organization. Weaknesses include some redundancy around token requirements and lack of validation/verification steps (e.g., how to confirm setup works).
Suggestions
Remove redundant mentions of token requirements — state it once in the token section and reference it, rather than repeating in the intro, token section, and notes section.
Add a quick verification step after token setup, e.g., `grizzly tags --enable-callback --json --token-file ~/.config/grizzly/token` to confirm everything works.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but has some unnecessary explanation. The 'Notes' section at the bottom restates things already implied by the commands (e.g., Bear must be running, token requirements mentioned multiple times). The token requirement is mentioned in three separate places. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready bash commands for all common operations. The token setup instructions are concrete with exact steps. Flag descriptions are specific and useful. | 3 / 3 |
Workflow Clarity | Commands are clearly presented but there's no sequenced workflow for common multi-step tasks (e.g., create a note then append to it, or search then open). The token setup is a clear sequence, but there's no validation step to confirm the token works or that Bear is running. | 2 / 3 |
Progressive Disclosure | For a skill of this size and scope, the content is well-organized into logical sections (token setup, common commands, options, configuration) with clear headers. No need for external file references given the content volume. | 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
- qsimeon/openclaw-engaging
- Commit
4467e04
- 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.