CtrlK
BlogDocsLog inGet started
Tessl Logo

bear-notes

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

72

3.57x
Quality

61%

Does it follow best practices?

Impact

100%

3.57x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/bear-notes/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

This is a solid, actionable CLI reference skill with concrete, executable examples for all major Bear note operations. Its main weaknesses are minor verbosity (repeated token requirement mentions, redundant notes section) and lack of workflow guidance for chained operations or error scenarios. The structure and organization are appropriate for the skill's scope.

Suggestions

Remove the redundant 'Notes' section at the bottom—most of its content is already conveyed inline (token requirements, callback usage).

Add a brief workflow example showing how to chain operations, e.g., create a note, capture the returned ID from JSON output, then append to it.

DimensionReasoningScore

Conciseness

Mostly efficient but has some unnecessary content. The 'Notes' section at the bottom repeats information already conveyed (e.g., token requirements mentioned multiple times). The configuration section with priority order and example TOML is useful but slightly verbose for a skill file.

2 / 3

Actionability

All commands are concrete, copy-paste ready bash examples with real flags and piping patterns. The token setup instructions are specific and executable. Each common operation has a complete, runnable command.

3 / 3

Workflow Clarity

The skill presents individual commands clearly but lacks workflow sequencing for multi-step processes (e.g., create a note then append to it using the returned ID). There's no validation or error handling guidance—what happens if Bear isn't running, or if the token is invalid?

2 / 3

Progressive Disclosure

For a skill of this size and scope (single CLI tool, no bundle files), the content is well-organized into logical sections (token setup, common commands, options, configuration) with clear headers. No external references are needed and the structure supports easy scanning.

3 / 3

Total

10

/

12

Passed

Description

50%

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 identifies a clear niche (Bear notes via grizzly CLI) with specific actions, making it distinctive. However, it lacks a 'Use when...' clause, which significantly hurts completeness, and could benefit from additional natural trigger terms users might use when requesting note management tasks.

Suggestions

Add a 'Use when...' clause, e.g., 'Use when the user asks to create, search, edit, or organize notes in Bear, or mentions grizzly CLI.'

Include additional natural trigger terms like 'Bear app', 'note-taking', 'tags', 'markdown notes', or specific actions like 'archive' or 'export'.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'Create, search, and manage Bear notes' and specifies the tool used ('grizzly CLI').

3 / 3

Completeness

Describes what the skill does but has no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 2, and the 'when' is entirely missing, placing it at 1.

1 / 3

Trigger Term Quality

Includes 'Bear notes' and 'grizzly CLI' as relevant keywords, but misses common variations users might say like 'note-taking', 'Bear app', or specific actions like 'tag', 'archive', 'export'.

2 / 3

Distinctiveness Conflict Risk

Very distinct niche — 'Bear notes' and 'grizzly CLI' are highly specific identifiers that are unlikely to conflict with other skills.

3 / 3

Total

9

/

12

Passed

Validation

72%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation8 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

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

8

/

11

Passed

Repository
Hung-Reo/hungreo-openclaw
Reviewed

Table of Contents

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.