bear-notes

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

Quality

67%

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

76%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 an efficient, highly actionable command reference with copy-paste-ready examples and complete configuration guidance. Its main weakness is the absence of validation checkpoints for note-editing operations, which caps workflow clarity.

Suggestions

Add a validation checkpoint after editing commands (e.g., re-open the note with `grizzly open-note --id "NOTE_ID" --json` to confirm `add-text` succeeded) so workflow clarity is not capped at 3.

Show a verify-then-proceed pattern for batch or multi-note operations using `--dry-run` before execution, with a re-read loop on failure.

Dimension	Reasoning	Score
Conciseness	The body is a lean command reference with no padding about what Bear or CLIs are; minor instances could be trimmed (e.g., the redundant prose label "Search notes (via open-tag)"), fitting anchor 4 rather than a clean 5.	4 / 5
Actionability	Every section provides copy-paste-ready `grizzly` commands with real flags covering create, open, append, tags, and search, plus complete TOML config and token setup, matching anchor 5's fully executable common-case coverage.	5 / 5
Workflow Clarity	The content is mostly a command catalog, and the note-editing operation (add-text append) modifies content with no verify/re-read checkpoint, so the destructive-operation cap holds workflow clarity at 3.	3 / 5
Progressive Disclosure	The single ~80-line file is well-sectioned with no external references needed, but exceeds the 50-line simple-skill threshold and is entirely inline, fitting anchor 4's "good structure; minor organization gaps".	4 / 5
	Total	16 / 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 specific and distinctive, naming the Bear domain and the grizzly tool with three actions, but it omits any explicit "Use when…" trigger guidance and leans on the vague verb "manage". Adding trigger phrasing and concrete sub-actions would raise completeness and trigger-term quality.

Suggestions

Add an explicit "Use when…" trigger clause (e.g., "Use when the user wants to create, search, or manage notes in Bear on macOS") so completeness is not capped at 3.

Replace the generic "manage" with concrete actions (e.g., "append text, list tags, open notes") to lift specificity toward 5.

Include natural trigger synonyms users would say (e.g., "Bear notes", "append to a note", "list Bear tags") to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Create, search, and manage Bear notes via grizzly CLI" lists three named actions plus the specific tool, matching anchor 4's "several specific actions; minor gaps" — the gap being the broad umbrella "manage".	4 / 5
Completeness	The description gives a clear "what" (create/search/manage Bear notes) but no "when" or "Use when…" clause, so per the rubric guideline completeness is capped at 3.	3 / 5
Trigger Term Quality	The natural phrase "Bear notes" is present but it is essentially the only natural keyword alongside the tool jargon "grizzly CLI", with missing common variations/synonyms, fitting anchor 3.	3 / 5
Distinctiveness Conflict Risk	"Bear notes via grizzly CLI" carves a clear niche with minimal conflict risk, but absent an explicit "Use when…" trigger it has minor overlap risk with a generic notes skill, fitting anchor 4.	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: 017761f

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