bear-notes

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

3.57x

Quality

73%

Does it follow best practices?

Impact

100%

3.57x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

The canonical home for this skill is bear-notes in Hung-Reo/hungreo-openclaw

Quality

Content

82%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 body is a tight, highly actionable CLI reference: every common Bear operation has an executable command, and setup/auth/config are covered concretely. Only minor issues remain — triplicated token-requirement text and the absence of explicit post-write verification.

Dimension	Reasoning	Score
Conciseness	The body is lean: requirements, token setup, copy-paste commands, a flag table, and a config example with no explanation of concepts Claude already knows. It is not a 5 because the token requirement (add-text, tags, open-note --selected) is repeated nearly verbatim in three places (Requirements, Getting a Bear Token, Notes).	4 / 5
Actionability	Every operation has a fully executable copy-paste grizzly command (create with piped content, open-note, add-text append, tags, open-tag search), plus concrete flags (--dry-run, --print-url, --enable-callback, --json, --token-file), a numbered token setup, and a working config.toml example. Not below 5 because the common cases are all covered with runnable commands.	5 / 5
Workflow Clarity	The token setup is a clear numbered sequence and each task maps to one unambiguous command, with --dry-run and --json/--enable-callback as verification aids. It does not reach 5 because write operations like add-text have no explicit verify-after-write step (e.g. re-reading the note to confirm), leaving a minor validation gap.	4 / 5
Progressive Disclosure	There are no bundle files (references/, scripts/, assets/ absent) and the ~82-line body is organized into well-labeled sections (token, commands, options, configuration, notes) with all content appropriately inline. It falls just short of the 5 anchor's simple-skill criterion (under 50 lines / clear split into reference files), but exceeds anchor 3's 'content that should be separate is inline'.	4 / 5
	Total	17 / 20 Passed

Description

65%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, concrete, and clearly scoped to the Bear/grizzly niche, with good natural trigger terms. Its main weakness is the missing "Use when..." clause, which caps completeness, and the generic verb "manage" diluting specificity.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user mentions Bear, Bear notes, or asks to create, search, or organize notes in the Bear app."

Replace or expand the generic "manage" with the concrete operations the skill actually supports, e.g. "create, search, append to, and tag Bear notes".

Include a few natural synonyms/extensions users would say ("Bear app", "note-taking", "tags") to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	"Create, search, and manage Bear notes via grizzly CLI" names the domain plus two concrete actions (create, search), but "manage" is generic filler. It sits between anchor 3 (1-2 concrete actions) and anchor 4; it does not list several specific actions with only minor gaps, so anchor 3 is the better fit.	3 / 5
Completeness	The "what" is clear (create, search, manage Bear notes via grizzly), but there is no "Use when..." clause or equivalent trigger guidance; the guidelines explicitly cap this at 3. Not anchor 2 because the "what" is concrete, not vague.	3 / 5
Trigger Term Quality	"Bear notes" and "grizzly CLI" are exactly the natural phrases a user would say for this task, and the verbs (create, search) add trigger surface. Missing common variations like "Bear app", "note-taking", or "tags", so it does not reach anchor 5's comprehensive synonym coverage.	4 / 5
Distinctiveness Conflict Risk	"Bear notes" plus the "grizzly CLI" tool name pin a narrow niche (the Bear note-taking app on macOS) with distinct triggers and minimal conflict risk against generic notes or document skills. Not anchor 4 because there is no meaningful overlap with closely related skills.	5 / 5
	Total	15 / 20 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: trpc-group/trpc-agent-go
Path: openclaw/skills/bear-notes/SKILL.md
Commit: 9bb1c42

Reviewed: 5 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.