bear-notes
Create, search, and manage Bear notes via grizzly CLI.
Install with Tessl CLI
npx tessl i github:Hung-Reo/hungreo-openclaw --skill bear-notes72
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
40%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 identifies a clear, distinct niche (Bear notes via grizzly CLI) but suffers from incomplete trigger guidance and moderate specificity. The lack of a 'Use when...' clause is a significant gap that would make it harder for Claude to know when to select this skill from a large pool.
Suggestions
Add a 'Use when...' clause with trigger terms like 'Bear app', 'Bear notes', 'grizzly', or when users mention note-taking in Bear specifically.
Expand 'manage' into specific concrete actions such as 'delete notes', 'add tags', 'archive', 'export', or 'organize notes'.
Include natural keyword variations users might say: 'find my notes', 'add a note', 'Bear app', 'note-taking'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Bear notes) and lists three actions (create, search, manage), but 'manage' is vague and doesn't specify concrete operations like delete, archive, tag, or export. | 2 / 3 |
Completeness | Describes what it does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 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'. | 2 / 3 |
Distinctiveness Conflict Risk | Very distinct niche - 'Bear notes' and 'grizzly CLI' are specific enough that this would not conflict with other note-taking or document skills. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that efficiently documents the grizzly CLI for Bear notes management. The content is concise, actionable with executable examples, and appropriately structured. The main weakness is the lack of validation steps or error handling guidance, particularly for token-dependent operations.
Suggestions
Add a verification step after token setup (e.g., 'Verify token works: grizzly tags --json --token-file ~/.config/grizzly/token')
Include common error scenarios and troubleshooting (e.g., what happens if Bear isn't running, or if token is invalid)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only necessary information without explaining what Bear is or how CLI tools work. Every section serves a clear purpose with no padding. | 3 / 3 |
Actionability | All commands are fully executable and copy-paste ready. The examples show real command patterns with proper flags, and the token setup instructions are concrete and specific. | 3 / 3 |
Workflow Clarity | Commands are clearly documented but there's no validation or error handling guidance. For operations requiring tokens, there's no feedback loop for verifying the token works or troubleshooting failures. | 2 / 3 |
Progressive Disclosure | For a skill of this size (~70 lines), the content is well-organized into logical sections (setup, commands, options, configuration, notes) without needing external file references. | 3 / 3 |
Total | 11 / 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 | |
- 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.