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".
83
81%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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 terms. Its main weakness is that the 'what' portion is somewhat vague—'create a minimal working Evernote example' could be more specific about what the example actually does (e.g., authenticate, create a note, list 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 and creates a first note' to improve specificity.
| 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 | Very specific niche targeting Evernote hello-world/quickstart scenarios. The combination of 'Evernote' with 'hello world', 'quick start', and 'first note' makes it highly 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 is a solid hello-world skill with executable code examples and good progressive disclosure. Its main weaknesses are some unnecessary ENML explanation that Claude doesn't need and the lack of inline validation steps in the workflow (e.g., verifying the note was created before proceeding to listing). The error handling table is useful but disconnected from the workflow steps.
Suggestions
Trim Step 2's ENML explanation to just the template and a one-line note about the DTD constraint, removing the list of forbidden elements and style restrictions.
Add a validation checkpoint after Step 3 (e.g., 'Verify: check that createdNote.guid is returned and log it before proceeding to Step 4').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ENML format explanation in Step 2 includes some unnecessary detail (forbidden elements, inline styles) that Claude could infer from the DTD reference. The overview and prerequisites are slightly verbose but not egregiously so. | 2 / 3 |
Actionability | Provides fully executable JavaScript code for client initialization, 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 (initialize → understand format → create note → list/retrieve), but there are no validation checkpoints. No verification step to confirm the note was actually created successfully, and no error recovery loop despite the error handling table being separate from the workflow. | 2 / 3 |
Progressive Disclosure | Clean structure with a concise overview, step-by-step instructions, and clear references to an implementation guide for advanced content. External resources and next steps are well-signaled and one level deep. | 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 | |
- 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.