evernote-core-workflow-b
Execute Evernote secondary workflow: Search and Retrieval. Use when implementing search features, finding notes, filtering content, or building search interfaces. Trigger with phrases like "search evernote", "find evernote notes", "evernote search", "query evernote".
77
73%
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 ./plugins/saas-packs/evernote-pack/skills/evernote-core-workflow-b/SKILL.mdQuality
Discovery
89%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 is a solid skill description that clearly identifies its niche (Evernote search and retrieval), provides explicit trigger phrases, and answers both what and when. Its main weakness is that the specific capabilities could be more concrete — listing actual operations like searching by tag, date range, or notebook would strengthen the specificity dimension.
Suggestions
Add more concrete actions beyond 'search features' and 'filtering content' — e.g., 'search notes by tag, date range, notebook, or full-text query' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Evernote search and retrieval) and some actions (search features, finding notes, filtering content, building search interfaces), but the actions are somewhat generic and not deeply specific about concrete operations like 'search by tag', 'full-text search', or 'filter by notebook'. | 2 / 3 |
Completeness | Clearly answers both 'what' (execute Evernote search and retrieval workflow) and 'when' (use when implementing search features, finding notes, filtering content, or building search interfaces), with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes explicit natural trigger phrases like 'search evernote', 'find evernote notes', 'evernote search', 'query evernote' which are terms users would naturally say. Also includes related terms like 'filtering content' and 'search interfaces'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific combination of 'Evernote' and 'search/retrieval' — this is a clear niche that is unlikely to conflict with other skills. The trigger phrases are all Evernote-specific. | 3 / 3 |
Total | 11 / 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.
The skill provides a reasonable structure for Evernote search and retrieval with a useful search grammar reference table and some concrete code examples. However, it falls short on actionability for Steps 3-5 which are purely descriptive, and the workflow lacks validation checkpoints despite involving API operations with rate limits and quotas. The progressive disclosure is well done with clear references to external resources.
Suggestions
Add executable code examples for Steps 3-5 (pagination async generator, findRelated call, and enrichment mapping) instead of prose descriptions
Integrate validation/verification into the workflow steps, e.g., checking for empty results, verifying rate limit status before pagination continues
Make the Examples section at the end include actual executable code rather than just scenario descriptions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some unnecessary explanation (e.g., 'Comprehensive search and retrieval workflow for Evernote, including search grammar, filters, pagination, related notes discovery, and result enrichment with notebook/tag names' in the overview). Steps 3-5 describe what to do in prose without adding much value beyond what Claude could infer. The search grammar table is useful reference material though. | 2 / 3 |
Actionability | Steps 1-2 have concrete code examples, but Steps 3-5 are purely descriptive with no executable code—just vague instructions like 'Use an async generator' and 'Cache notebook and tag lookups.' The QueryBuilder class is referenced but never implemented. The examples section at the end describes scenarios without providing actual code. | 2 / 3 |
Workflow Clarity | The 5-step sequence is clearly laid out and logically ordered, but there are no validation checkpoints or feedback loops. For a workflow involving API calls with rate limits and quota concerns, there's no explicit verification step (e.g., checking search results are valid, handling empty results). Error handling is listed in a table but not integrated into the workflow steps. | 2 / 3 |
Progressive Disclosure | Good structure with a clear overview, step-by-step sections, a quick reference table, and a single-level reference to an implementation guide. External resources are well-organized and clearly signaled. Content is appropriately split between the skill file and the referenced implementation guide. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
70e9fa4
- 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.