evernote-hello-world
Create a minimal working Evernote example. Use when starting a new Evernote integration, testing your setup, or learning basic Evernote API patterns. Trigger with phrases like "evernote hello world", "evernote example", "evernote quick start", "simple evernote code", "create first note".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill evernote-hello-world80
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 excellent trigger terms and clear 'when to use' guidance. The main weakness is the lack of specific concrete actions - it says 'create a minimal working example' but doesn't specify what that example does (e.g., creates a note, authenticates, lists notebooks). The description would benefit from slightly more specificity about the actual capabilities.
Suggestions
Add specific actions to the description, e.g., 'Create a minimal working Evernote example that authenticates and creates a test note' to clarify what the example actually does.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Evernote) and mentions 'minimal working example' but lacks specific concrete actions like 'create notes', 'authenticate', or 'list notebooks'. The phrase 'minimal working Evernote example' is somewhat vague about what exactly gets created. | 2 / 3 |
Completeness | Clearly answers both what ('Create a minimal working Evernote example') and when ('Use when starting a new Evernote integration, testing your setup, or learning basic Evernote API patterns') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'evernote hello world', 'evernote example', 'evernote quick start', 'simple evernote code', 'create first note'. These are realistic phrases a developer would use when starting out. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche - specifically targets Evernote API beginners/quick starts. The combination of 'Evernote' + 'hello world/example/quick start' creates a clear, non-conflicting trigger space unlikely to overlap with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%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 hello-world skill with excellent actionability - the code examples are complete and executable. However, it's verbose for a 'hello world' example, including both JS and Python versions inline plus extensive ENML documentation that could be referenced externally. The workflow lacks explicit validation steps before proceeding (e.g., 'verify your token works before creating notes').
Suggestions
Add a validation step after client initialization (e.g., 'Test connection: await userStore.getUser()' before proceeding to note creation)
Move the Python version and ENML Quick Reference to separate files, linking to them from the main skill
Remove explanatory text about what ENML is - Claude knows this; just provide the rules and examples
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., 'Evernote uses ENML (Evernote Markup Language), a restricted subset of XHTML') and provides both JavaScript and Python versions which adds bulk. The ENML rules section explains things Claude would know, but the code examples are reasonably tight. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready code examples in both JavaScript and Python. Includes complete working examples with proper imports, initialization, and error handling. The code is concrete and immediately usable. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but there are no validation checkpoints. For API operations that could fail (ENML validation, authentication issues), there's no explicit 'verify before proceeding' guidance. The error handling table is helpful but reactive rather than preventive. | 2 / 3 |
Progressive Disclosure | The skill is quite long (~200 lines) with inline content that could be split out (Python version, ENML reference). References to external resources are provided at the end, but the main content is monolithic. The ENML Quick Reference could be a separate file. | 2 / 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 | |
- 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.