Create, search, and manage Bear notes via grizzly CLI.
74
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
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 from a large pool. Adding trigger guidance and more natural keyword variations would significantly improve it.
Suggestions
Add a 'Use when...' clause, e.g., 'Use when the user asks to create, search, edit, or organize notes in Bear, or mentions the grizzly CLI.'
Include natural keyword variations users might say, such as 'Bear app', 'note-taking', 'find notes', 'add a note', or 'delete note'.
| 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 at 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 a highly specific tool and application combination that is unlikely to conflict with other skills. | 3 / 3 |
Total | 9 / 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.
A solid, actionable skill that provides clear CLI examples for all common Bear note operations via grizzly. The main weakness is minor redundancy in explaining token requirements across multiple sections and some content that Claude would already understand (like 'Bear must be running'). Overall well-structured and immediately usable.
Suggestions
Remove the redundant Notes section at the bottom — the token requirement info and callback explanation are already covered inline with the commands.
Drop obvious statements like 'Bear app installed and running' as a requirement since Claude can infer this.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but has some redundancy — the token requirement is mentioned three times (intro, section header, and Notes section), and the Notes section at the bottom repeats information already covered. The 'Requirements' line about Bear being installed is obvious. | 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 | This is a simple CLI tool skill with individual commands rather than a multi-step destructive workflow. Each operation is clearly presented with its exact command syntax. The token setup is a clear 2-step sequence. No destructive/batch operations that would require validation checkpoints. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the configuration section with the TOML example and the Notes section add bulk that could potentially be in a separate reference file. For a skill of this size (~60 lines of content), it's borderline acceptable but slightly heavy for a single file. | 2 / 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 | |
09cce3e
Table of Contents
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.