bear-notes

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

Quality

70%

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

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, fully executable reference for the grizzly CLI: concrete commands for every supported operation, clear flag documentation, and a realistic config example. Its only weaknesses are the token-requirement repetition and the lack of a verify-success step after mutating commands.

Dimension	Reasoning	Score
Conciseness	The body is lean and command-driven with no explanation of concepts Claude already knows; the only trimmable redundancy is the token requirement repeated in 'Requirements', 'Getting a Bear Token', and 'Notes' ('Some operations require a valid token').	4 / 5
Actionability	Every operation ships a copy-paste-ready command (e.g. 'echo "Note content here" \| grizzly create --title "My Note" --tag work') plus documented flags and a concrete config.toml example, covering the common cases.	5 / 5
Workflow Clarity	Token acquisition is a clear two-step sequence ('Open Bear → Help → API Token → Copy Token', then save it) and each operation section is unambiguous, but there are no validation checkpoints such as checking the JSON callback output to confirm a note was created.	4 / 5
Progressive Disclosure	Sections (Getting a Bear Token, Common Commands, Options, Configuration, Notes) are well organized with content appropriately inline for a skill this size; at roughly 85 lines the body sits just past the under-50-line bright line for a top score.	4 / 5
	Total	17 / 20 Passed

Description

58%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 names a specific niche with three concrete actions, but it lacks any 'when to use' trigger guidance and offers few natural trigger terms beyond the product name. Adding an explicit 'Use when...' clause with synonyms (note-taking, markdown notes, Bear app) would raise both completeness and trigger quality.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks to create, find, or organize notes in the Bear app on macOS.'

Add natural trigger terms and synonyms such as 'note-taking', 'markdown notes', or 'Bear app' so users' phrasing matches the description.

Replace the generic 'manage' with the concrete operations the skill actually supports (append text, list tags, open notes by ID).

Dimension	Reasoning	Score
Specificity	Names the domain (Bear notes) and three concrete actions ('Create, search, and manage'), though 'manage' is generic and capabilities like append, tags, and open are only implied by the body, not the description.	4 / 5
Completeness	The 'what' is clear ('Create, search, and manage Bear notes via grizzly CLI') but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Relevant keywords ('Bear notes', 'grizzly CLI') are present but natural user phrasings like 'note-taking', 'markdown notes', or 'add to my notes' are missing, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	'Bear notes' plus 'grizzly CLI' carves a distinct niche with minimal conflict risk, but the absence of disambiguating trigger phrasing leaves minor overlap with other note-app skills.	4 / 5
	Total	14 / 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: Bitterbot-AI/bitterbot-desktop
Path: skills/bear-notes/SKILL.md
Commit: 1c7dc1b

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