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".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill evernote-core-workflow-b82
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
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 well-structured skill description with strong completeness and trigger term coverage. The explicit 'Use when' clause and trigger phrases make it easy for Claude to select appropriately. The main weakness is that the specific capabilities could be more concrete (e.g., 'search by tag', 'filter by date range', 'full-text search').
Suggestions
Add more concrete action verbs describing specific search capabilities (e.g., 'search by tags, filter by notebook, perform full-text queries, retrieve notes by date range')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Evernote search/retrieval) and mentions some actions like 'search features', 'finding notes', 'filtering content', 'building search interfaces', but these are somewhat generic and not highly concrete actions like specific API operations or detailed capabilities. | 2 / 3 |
Completeness | Clearly answers both what (execute Evernote search and retrieval workflow) and when (implementing search features, finding notes, filtering content) with explicit 'Use when' clause and specific trigger phrases. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'search evernote', 'find evernote notes', 'evernote search', 'query evernote'. These are realistic user queries with good variation coverage. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with 'Evernote' as a specific product name and 'secondary workflow' designation. The combination of Evernote + search/retrieval creates a clear niche unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 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 skill provides comprehensive, executable code for Evernote search functionality with excellent actionability and good progressive disclosure. However, it suffers from verbosity with unnecessary JSDoc comments and repeated patterns that Claude doesn't need. The workflow lacks explicit validation checkpoints for API operations that could fail.
Suggestions
Remove obvious JSDoc comments (e.g., '/** Search in specific notebook */') that describe what the method name already conveys - Claude can infer these
Consolidate repeated code patterns - getDefaultResultSpec() is defined multiple times across steps; show it once and reference it
Add explicit validation steps after API calls, such as checking for empty results or handling rate limits inline rather than just in a reference table
Consider condensing Steps 3-5 into a single 'Advanced Search Patterns' section since they extend the same SearchService class
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but overly verbose for its purpose. Many method implementations include obvious JSDoc comments that Claude doesn't need, and some patterns are repeated across steps (e.g., getDefaultResultSpec appears multiple times). The content could be significantly condensed. | 2 / 3 |
Actionability | Excellent actionability with fully executable JavaScript code throughout. The SearchService class, QueryBuilder, and complete workflow example are copy-paste ready with specific method signatures, proper Evernote SDK usage, and concrete examples. | 3 / 3 |
Workflow Clarity | Steps are numbered and build logically, but there are no validation checkpoints or error recovery patterns within the workflow. The error handling section is a reference table rather than integrated validation steps. For API operations that could fail, explicit validation would improve reliability. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from foundation to advanced features. The quick reference table, error handling table, and external resource links provide appropriate layering. References to related skills (evernote-install-auth, evernote-common-errors) are one level deep and clearly signaled. | 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 |
|---|---|---|
skill_md_line_count | SKILL.md is long (679 lines); consider splitting into references/ and linking | Warning |
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 | 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.