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 ./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
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 Bear note management via grizzly CLI. Its main strengths are actionability and good organization. Minor weaknesses include some redundant explanatory notes and a lack of workflow sequencing showing how commands chain together (e.g., creating a note and then using the returned ID).
Suggestions
Remove or trim the 'Notes' section at the bottom, as most of its content is already evident from the commands and options sections.
Add a brief workflow example showing a chained operation, such as creating a note with --enable-callback --json, extracting the note ID from the response, and then appending text to it.
| 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, use --enable-callback when reading data). The token setup instructions are reasonable but slightly verbose. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready bash commands for all common operations. Each command includes concrete flags and piping patterns. The config file example is also complete and usable. | 3 / 3 |
Workflow Clarity | Commands are clearly presented individually, but there's no sequenced workflow showing a typical multi-step process (e.g., create note → get its ID from callback → append to it). For a CLI tool skill, the individual commands are clear, but the token setup could be more explicitly sequenced as a prerequisite check before operations. | 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 external references are needed and the structure supports easy scanning. | 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 | |
af8bd5f
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.