bear-notes

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

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

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

Quality

Content

68%Weight 40%Scale 1-5

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

The skill body is a lean, well-organized CLI reference with concrete, executable commands and useful configuration guidance. Its main gaps are the absence of validation guidance for note-modifying operations and the irrelevant migration metadata section.

Suggestions

Add a validation step for write operations, e.g. 'Run add-text with --dry-run (or --print-url) first to confirm the target note before modifying it.'

Remove the 'PilotDeck Migration Note' section — it is review metadata with no operational value to the skill's execution.

Deduplicate the token requirement (stated in Requirements, Getting a Bear Token, and Notes) and show how to extract a NOTE_ID from the `--json` output so the read/append workflow is self-contained.

Dimension	Reasoning	Score
Conciseness	The body is lean — short sections, executable one-line commands, no explanation of concepts Claude already knows — with minor trimmable redundancy: the token requirement is stated three times (Requirements, Getting a Bear Token, Notes), 'Bear must be running' is repeated, and the 'PilotDeck Migration Note' section is review metadata irrelevant to skill execution. This fits anchor 4 ('efficient; minor instances of over-explanation that could be trimmed') rather than 5's 'every token earns its place'.	4 / 5
Actionability	Commands are concrete and copy-paste ready with real flags (e.g. `echo "Additional content" \| grizzly add-text --id "NOTE_ID" --mode append --token-file ~/.config/grizzly/token`), covering create, read, append, tags, and tag search — matching anchor 4 ('mostly executable guidance; concrete code or commands with minor gaps'). Not 5: the workflow stops short of showing how to obtain NOTE_ID from `--json` output, and no example covers listing or finding notes generally.	4 / 5
Workflow Clarity	The token setup is a clear 2-step sequence and commands are grouped by task, but note-modifying operations (add-text) have no explicit validation workflow — `--dry-run` and `--print-url` are documented as flags but the skill never instructs verifying before writing, and the guideline caps workflow clarity at 3 for destructive/modifying operations without validation. This matches anchor 3 ('steps listed but validation gaps; checkpoints missing or implicit') rather than 4's 'most checkpoints present'.	3 / 5
Progressive Disclosure	The body is well-organized into clear sections (Requirements, Token, Common Commands, Options, Configuration, Notes) with no bundle files and no nested references — content is appropriately inlined for a single-file CLI skill of this size, matching anchor 4 ('good structure; most content is appropriately placed'). Not 5: the extraneous 'PilotDeck Migration Note' section and some content that could be tightened (repeated token notes) leave minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

57%Weight 40%Scale 1-5

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 specific to a clear niche, but lacks any explicit 'Use when' trigger guidance and uses the generic verb 'manage'. Adding a trigger clause and more concrete operations (append text, tags) would raise completeness and specificity.

Suggestions

Add an explicit trigger clause, e.g. 'Use when working with Bear notes on macOS, or when the user mentions Bear, note-taking, or grizzly.'

Replace or expand the generic 'manage' with concrete operations the skill supports, such as 'append text to notes and list tags'.

Include natural synonyms users would say — 'note-taking', 'markdown notes', 'Bear app' — to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	"Create, search, and manage Bear notes via grizzly CLI" names the domain (Bear notes) and two concrete actions (create, search), but "manage" is generic — matching anchor 3 ('names domain and 1-2 concrete actions, but not comprehensive') rather than anchor 4, which expects several specific actions with only minor gaps.	3 / 5
Completeness	The 'what' is clear (create, search, manage Bear notes), but there is no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3 ('clear what but when is missing or only weakly implied').	3 / 5
Trigger Term Quality	"Bear notes" and "grizzly CLI" are relevant keywords a user might say, but common variations and synonyms (note-taking, markdown notes, Bear app, macOS) are absent — fitting anchor 3 ('some relevant keywords but missing common variations or synonyms') rather than 4's 'good keyword coverage'.	3 / 5
Distinctiveness Conflict Risk	"Bear notes via grizzly CLI" carves out a clear niche — the Bear note-taking app accessed through the grizzly tool — so it is clearly distinguishable from generic notes or document skills with minimal conflict risk, matching anchor 5; anchor 4 would require noticeable overlap with a closely related skill, which is not the case.	5 / 5
	Total	14 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: OpenBMB/PilotDeck
Path: skills/bear-notes/SKILL.md
Commit: 66bfd09

Reviewed: 2 days 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.