gws-keep
Manage Google Keep notes.
51
40%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/gws-keep/SKILL.mdQuality
Discovery
22%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 far too terse—it names the target service but provides no concrete actions, no trigger guidance, and no 'Use when...' clause. While 'Google Keep' is a distinctive product name that helps with selection, the lack of specificity and completeness severely limits Claude's ability to confidently choose this skill.
Suggestions
List specific concrete actions such as 'Create, edit, archive, pin, and label Google Keep notes and checklists'.
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Google Keep, sticky notes, checklists, reminders, or note management.'
Include natural trigger term variations like 'Keep notes', 'checklists', 'reminders', 'labels', 'to-do lists' to improve keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the domain ('Google Keep notes') with a single vague action ('Manage'). It does not list any concrete actions like creating, editing, archiving, labeling, or searching notes. | 1 / 3 |
Completeness | The 'what' is extremely vague ('Manage') and there is no 'when' clause or explicit trigger guidance at all, which per the rubric caps completeness at 2 at best—and the weak 'what' brings it to 1. | 1 / 3 |
Trigger Term Quality | 'Google Keep' and 'notes' are natural keywords a user might say, but the description misses common variations like 'checklist', 'reminder', 'to-do list', 'sticky notes', or 'Keep labels'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Google Keep' is a fairly specific product, which helps distinguish it from generic note-taking skills, but the vague 'Manage' verb could overlap with other note or task management skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a reasonable overview of the Google Keep CLI wrapper with good progressive disclosure via the shared skill reference. However, it lacks concrete executable examples (e.g., creating a note with actual --params) and misses validation/safety guidance for the irreversible delete operation. The API resource descriptions contain some verbosity that Claude doesn't need.
Suggestions
Add at least one concrete, copy-paste-ready example showing a full command (e.g., `gws keep notes create --params 'title=My Note' --json '{"body": {"text": {"text": "Hello"}}}'`).
Add a warning or validation step for the destructive `delete` method, such as recommending a `get` before `delete` to confirm the correct note.
Trim verbose API descriptions—remove explanations of page tokens, 400 errors, and OWNER role requirements that Claude can discover via `gws schema`.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient, but includes some unnecessary verbosity in API descriptions (e.g., explaining what page tokens are, explaining 400 error for media download). These are details Claude already knows or could discover via the schema command. | 2 / 3 |
Actionability | Provides the CLI pattern and schema discovery commands, but lacks concrete executable examples of actual note creation, listing, or deletion. The user is told to use `gws schema` but no example output or complete command invocation is shown. | 2 / 3 |
Workflow Clarity | The discovery workflow (help → schema → build command) is present but implicit. There's no explicit validation or error-handling guidance for destructive operations like `delete`, which is noted as irreversible. Missing feedback loops for destructive operations caps this at 2. | 2 / 3 |
Progressive Disclosure | Appropriately delegates shared auth/security concerns to `../gws-shared/SKILL.md` with a clear prerequisite callout. The skill itself is concise and well-structured with clear sections. One level of reference depth. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 10 / 11 Passed | |
- Repository
- googleworkspace/cli
- Commit
a3768d0
- 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.