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".
80
77%
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-hello-world/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 well-structured description with strong completeness and excellent trigger term coverage. Its main weakness is that the 'what' portion is somewhat vague—'create a minimal working example' could be more specific about what the example includes (e.g., authenticating, creating a note, listing notebooks). Overall it performs well for skill selection purposes.
Suggestions
Add more specific concrete actions to the 'what' portion, e.g., 'Creates a minimal Evernote integration that authenticates, creates a note, and lists notebooks.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (Evernote) and a general action ('Create a minimal working Evernote example'), but doesn't list multiple specific concrete actions like creating notes, authenticating, listing notebooks, etc. | 2 / 3 |
Completeness | Clearly answers both 'what' (create a minimal working Evernote example) and 'when' (starting a new integration, testing setup, learning basic API patterns) with explicit trigger phrases. | 3 / 3 |
Trigger Term Quality | Includes a good range of natural trigger phrases users would actually say: 'evernote hello world', 'evernote example', 'evernote quick start', 'simple evernote code', 'create first note'. These cover common variations well. | 3 / 3 |
Distinctiveness Conflict Risk | The Evernote-specific focus creates a clear niche that is unlikely to conflict with other skills. The trigger terms are distinctly tied to Evernote getting-started scenarios. | 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 executable code examples and clear step-by-step structure. Its main weaknesses are moderate verbosity in explaining ENML concepts that could be more concise, and the lack of explicit validation checkpoints before making API calls. The referenced implementation guide file is not present in the bundle, weakening progressive disclosure.
Suggestions
Add an explicit ENML validation step before calling createNote (e.g., check XML well-formedness) to create a feedback loop for the most common error case.
Trim the ENML explanation in Step 2 to just the code example with brief inline comments about forbidden elements, rather than a separate prose paragraph.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., 'Evernote uses ENML (Evernote Markup Language), a restricted XHTML subset' and the description of forbidden elements could be more terse). The ENML format section explains concepts that could be conveyed more efficiently through the code example alone. However, it's not egregiously verbose. | 2 / 3 |
Actionability | The skill provides fully executable JavaScript code examples for client initialization, ENML content creation, note creation, and notebook listing. Code is copy-paste ready with environment variable usage and clear API calls. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (1-4) and logically ordered, but there are no explicit validation checkpoints. For an API operation that can fail with ENML formatting errors, there should be a validate-then-proceed step (e.g., validate ENML before calling createNote). The error handling table is helpful but reactive rather than preventive. | 2 / 3 |
Progressive Disclosure | The skill references an implementation guide at 'references/implementation-guide.md' but no bundle files are provided, making this reference unverifiable. The content is reasonably structured with sections, but the inline ENML explanation and error table could potentially be split out. The external resource links are helpful but the internal reference is unsupported. | 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 | |
- Commit
3a2d27d
- 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.