bear-notes

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

3.57x

Quality

—

Does it follow best practices?

Impact

100%

3.57x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

100%

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, fully actionable CLI reference with well-organized sections and no filler. It models the lean style the rubric rewards.

Dimension	Reasoning	Score
Conciseness	The body is lean: no preamble explaining what Bear or a CLI is, direct command examples, and tight flag tables. The only minor redundancy is the token requirement appearing in multiple sections, but it is brief and useful context.	3 / 3
Actionability	Every operation ships a copy-paste-ready bash invocation with real flags (e.g. `grizzly open-note --id "NOTE_ID" --enable-callback --json`), plus a concrete token-setup sequence and config example.	3 / 3
Workflow Clarity	This is a simple single-purpose CLI skill; the commands are unambiguous and the token-acquisition flow is a clear numbered 2-step sequence. No destructive/batch operations are present that would demand validation checkpoints.	3 / 3
Progressive Disclosure	The skill has no bundle files and needs none for a CLI cheat sheet; content is well-organized into clearly headed sections (Getting a Token, Common Commands, Options, Configuration), so the single-file structure is appropriate.	3 / 3
	Total	12 / 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 but stops short of stating when Claude should reach for it. Adding an explicit "Use when..." trigger clause would raise completeness and trigger-term quality.

Suggestions

Add a "Use when..." clause naming natural triggers, e.g. "Use when the user wants to create, search, or manage notes in Bear on macOS."

Include common user phrasings like "search notes", "tag notes", or "append to a Bear note" to improve trigger-term coverage.

Mention macOS-only constraint in the description to set expectations upfront.

Dimension	Reasoning	Score
Specificity	"Create, search, and manage Bear notes" lists multiple concrete actions (create, search, manage) tied to a specific target, matching the multiple-specific-actions anchor.	3 / 3
Completeness	It answers "what" (create, search, manage Bear notes) but has no "Use when..." clause or equivalent trigger guidance, so the "when" is missing and capped at 2 per the guidelines.	2 / 3
Trigger Term Quality	"Bear notes" and "grizzly CLI" are relevant keywords a user might say, but coverage is thin and lacks common variations like "search notes" or "tag notes" that the body actually supports.	2 / 3
Distinctiveness Conflict Risk	"Bear notes via grizzly CLI" carves a clear niche (Bear app + grizzly) that is unlikely to trigger for unrelated note or document 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: trpc-group/trpc-agent-go
Commit: dfab3c6

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.