bear-notes

Create, search, and manage Bear notes via grizzly CLI.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/bear-notes/SKILL.md

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is an efficient, highly actionable command reference with copy-paste examples and tidy organization. Its main gap is the absence of validation/verification steps for the note-modifying operations and token setup.

Suggestions

Add a verification step after modifying operations, e.g. confirm a create/add-text succeeded with `grizzly open-note --id "NOTE_ID" --enable-callback --json` before declaring success.

Add a quick token-verification check after setup (e.g. run `grizzly tags --json --token-file ~/.config/grizzly/token` to confirm the token works) so the Getting-a-Token workflow has an explicit checkpoint.

Dimension	Reasoning	Score
Conciseness	The body is a lean command reference made almost entirely of executable code blocks, brief flag lists, and a compact config example; it assumes Claude's competence and avoids explaining concepts Claude already knows.	3 / 3
Actionability	Commands like `echo "..." \| grizzly create --title "My Note" --tag work` and `grizzly open-note --id "NOTE_ID" --enable-callback --json` are fully executable and copy-paste ready with concrete flags.	3 / 3
Workflow Clarity	Operations are individually clear, but modifying operations (create, add-text) and token setup lack explicit validation/verification checkpoints, so workflow clarity is capped at 2 per the destructive/batch guidance.	2 / 3
Progressive Disclosure	The skill is a single, well-organized SKILL.md with clearly labeled sections and no external bundle files or nested references, so progressive disclosure is satisfied by the clean section structure alone.	3 / 3
	Total	11 / 12 Passed

Description

67%

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 specific and distinctive, naming concrete actions and a clear niche, but it omits an explicit "Use when..." trigger clause and lacks broader natural keyword coverage. Adding trigger guidance would raise completeness and trigger-term quality.

Suggestions

Append a 'Use when...' clause (e.g. 'Use when the user wants to create, search, or organize notes in Bear on macOS.') to explicitly state when Claude should invoke this skill.

Broaden natural trigger terms beyond 'Bear notes' and 'grizzly CLI' (e.g. 'note-taking', 'Bear app', 'macOS notes') so the description matches phrasings users actually say.

Dimension	Reasoning	Score
Specificity	"Create, search, and manage Bear notes via grizzly CLI" lists multiple concrete actions (create, search, manage) tied to a specific tool, matching the anchor for listing several specific concrete actions.	3 / 3
Completeness	It clearly answers WHAT (create, search, manage Bear notes) but provides no "Use when..." clause or equivalent explicit trigger guidance for WHEN Claude should use it, capping completeness at 2 per the guidelines.	2 / 3
Trigger Term Quality	"Bear notes" and "grizzly CLI" are relevant keywords a user might say, but common variations (e.g. "note-taking", "Apple Notes alternative") are missing and phrasing is not the most natural trigger.	2 / 3
Distinctiveness Conflict Risk	"Bear notes via grizzly CLI" carves out a clear niche (the Bear note-taking app) with a named tool, making it unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 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	13 / 16 Passed

Repository: Bitterbot-AI/bitterbot-desktop
Path: skills/bear-notes/SKILL.md
Commit: e73c717

Reviewed: about 16 hours ago

Table of Contents

Discovery Implementation Validation

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.