evernote-core-workflow-a
Execute Evernote primary workflow: Note Creation and Management. Use when creating notes, organizing content, managing notebooks, or implementing note-taking features. Trigger with phrases like "create evernote note", "evernote note workflow", "manage evernote notes", "evernote content".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill evernote-core-workflow-a83
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 solid skill description that clearly identifies its Evernote-specific domain and provides explicit trigger guidance. The main weakness is that the capability descriptions are somewhat generic ('organizing content', 'managing notebooks') rather than listing specific concrete actions. The description effectively uses the product name as a distinguishing qualifier.
Suggestions
Add more specific concrete actions like 'add tags to notes', 'search note content', 'move notes between notebooks', or 'attach files to notes' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Evernote) and mentions actions like 'creating notes, organizing content, managing notebooks', but these are somewhat generic and don't list specific concrete operations like 'add tags', 'move notes between notebooks', or 'search notes'. | 2 / 3 |
Completeness | Clearly answers both what ('Note Creation and Management', 'creating notes, organizing content, managing notebooks') and when ('Use when creating notes...', 'Trigger with phrases like...'). Has explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural trigger phrases users would say: 'create evernote note', 'manage evernote notes', 'evernote content', and covers the product name 'Evernote' prominently throughout. Good coverage of natural terms. | 3 / 3 |
Distinctiveness Conflict Risk | The repeated use of 'Evernote' as a qualifier creates a clear niche. Unlikely to conflict with generic note-taking skills or other platform-specific skills due to the explicit Evernote branding throughout. | 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 is a solid, actionable skill with comprehensive executable code examples covering the full CRUD lifecycle for Evernote notes. The main weaknesses are some verbosity in explanatory sections and missing validation checkpoints in the workflow steps, particularly important given ENML's strict formatting requirements.
Suggestions
Add explicit validation steps after ENML generation, e.g., 'Validate ENML structure before calling createNote' with a validation helper or try-catch pattern
Remove the Overview and Output sections - the code and step titles already communicate what the skill does
Add a feedback loop pattern in Step 3 for update operations showing how to handle conflicts or validation failures
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary elements like the Overview section explaining what the workflow covers, and the Output section listing capabilities that are self-evident from the code. The code itself is well-structured but could be more compact. | 2 / 3 |
Actionability | Provides fully executable JavaScript code with complete class implementations, helper methods, and a comprehensive workflow example. Code is copy-paste ready with proper imports and realistic usage patterns. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but lacks explicit validation checkpoints. For operations like ENML manipulation and note updates, there's no validate-then-proceed pattern or error recovery feedback loops despite the error handling table. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections, appropriate external references to documentation and related skills (evernote-core-workflow-b), and content is appropriately structured without deep nesting. The Resources section provides one-level-deep links. | 3 / 3 |
Total | 10 / 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 | |
- 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.