gws-keep
Manage Google Keep notes.
55
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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.
This description is too minimal to effectively guide skill selection. It lacks specific actions, provides no trigger guidance, and relies on a single vague verb 'Manage' to describe all capabilities. While 'Google Keep' provides some distinctiveness, the description fails to help Claude understand when to select this skill over others.
Suggestions
Add specific actions like 'Create, edit, delete, search, and organize Google Keep notes, manage labels, set reminders, and work with checklists'
Add a 'Use when...' clause with trigger terms like 'Google Keep', 'Keep notes', 'reminders', 'checklists', 'note labels', or when users mention syncing notes with Google
Include file/format indicators if applicable, such as mentioning integration with Google Workspace or specific note types (text notes, lists, images)
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language ('Manage') without listing any concrete actions. It doesn't specify what managing entails - no mention of creating, editing, deleting, organizing, searching, or any other specific operations. | 1 / 3 |
Completeness | Only weakly addresses 'what' (manage notes) and completely lacks any 'when' guidance. No 'Use when...' clause or explicit trigger guidance is provided. | 1 / 3 |
Trigger Term Quality | Includes 'Google Keep' and 'notes' which are natural terms users might say, but misses common variations like 'Keep notes', 'note-taking', 'reminders', 'checklists', or 'labels' that users might mention. | 2 / 3 |
Distinctiveness Conflict Risk | 'Google Keep' provides some specificity that distinguishes it from generic note skills, but 'notes' is generic enough to potentially conflict with other note-taking skills (Notion, Evernote, Apple Notes, etc.). | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
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 well-structured, concise skill that efficiently documents the Google Keep CLI wrapper. Its main weakness is the lack of concrete usage examples - while it tells you what methods exist and how to discover their schemas, it doesn't show actual invocations with parameters. The destructive 'delete' operation would benefit from a verification workflow.
Suggestions
Add 1-2 concrete examples showing actual command invocations with --params or --json flags (e.g., creating a note, listing with pagination)
Add a verification step or warning pattern for the destructive 'delete' operation since it 'cannot be undone'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what Google Keep is or how APIs work. Every line serves a purpose - command syntax, resource listing, and discovery commands. | 3 / 3 |
Actionability | Provides concrete CLI commands and method listings, but lacks executable examples showing actual usage (e.g., creating a note with specific params, downloading media with alt=media). The discovery commands are helpful but don't substitute for concrete examples. | 2 / 3 |
Workflow Clarity | The 'Discovering Commands' section provides a workflow for exploring the API, but there's no validation or error handling guidance. For destructive operations like 'delete' (which 'cannot be undone'), there should be verification steps. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear reference to shared skill file for auth/security, concise overview of resources, and well-signaled discovery commands. Appropriately delegates common concerns to gws-shared/SKILL.md. | 3 / 3 |
Total | 10 / 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.
Validation — 8 / 11 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 | 8 / 11 Passed | |
- 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.