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 ./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 critically lacks a 'Use when...' clause, which means Claude may not know when to select this skill from a large pool. Adding trigger guidance and more natural user-facing keywords would significantly improve it.
Suggestions
Add a 'Use when...' clause such as 'Use when the user asks to create, search, edit, or organize notes in Bear, or mentions the grizzly CLI.'
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 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', 'organize notes'. | 2 / 3 |
Distinctiveness Conflict Risk | Very distinct niche — Bear notes via grizzly CLI is a specific tool combination unlikely to conflict with other skills. The mention of both 'Bear' and 'grizzly CLI' creates a clear, unique identity. | 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, actionable CLI reference skill with concrete, executable examples for all major Bear note operations via grizzly. Its main weakness is the lack of workflow sequencing and validation steps (e.g., verifying token validity, confirming note creation), and some minor redundancy in repeating token requirements across sections. The organization and progressive disclosure are appropriate for the skill's scope.
Suggestions
Add a brief validation step after token setup, e.g., 'Verify token works: `grizzly tags --enable-callback --json --token-file ~/.config/grizzly/token`'
Remove redundant mentions of which operations require tokens — state it once in the token section and reference it, rather than repeating in Notes and individual commands
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but has some redundancy — the Notes section repeats information already covered (e.g., token requirements mentioned in multiple places), and the 'Requirements' line about Bear being installed is obvious. The configuration section is useful but slightly verbose for a skill file. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready bash commands for all common operations. The token setup instructions are concrete with exact steps, and the config file example is complete and usable. | 3 / 3 |
Workflow Clarity | Commands are clearly presented but there's no sequenced workflow with validation checkpoints. For example, there's no guidance on verifying a note was created successfully, checking if the token is valid, or handling errors when Bear isn't running. The skill presents isolated commands rather than connected workflows. | 2 / 3 |
Progressive Disclosure | For a single-purpose CLI skill with no bundle files, the content is well-organized into logical sections (token setup, common commands, options, configuration, notes) that are easy to scan. No external references are needed given the scope. | 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
- trpc-group/trpc-agent-go
- Commit
9f4b734
- 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.