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".
68
62%
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-core-workflow-a/SKILL.mdQuality
Discovery
75%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description is structurally sound with explicit 'Use when' and 'Trigger with' clauses, and the Evernote-specific focus makes it highly distinctive. However, the listed capabilities are somewhat generic ('organizing content', 'managing notebooks') and could benefit from more concrete action verbs. The trigger terms cover the basics but miss natural user phrasings beyond the formulaic 'evernote + action' pattern.
Suggestions
Add more specific concrete actions such as 'create and tag notes, search notebooks, format rich text content, attach files to notes, move notes between notebooks'.
Expand trigger terms with more natural user phrasings like 'save to evernote', 'organize my notes', 'add tags', 'search my evernote', 'note-taking workflow'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Evernote) and some actions ('creating notes, organizing content, managing notebooks'), but these are fairly generic and not highly concrete. It doesn't list specific operations like 'add tags', 'search notes', 'move between notebooks', or 'format note content'. | 2 / 3 |
Completeness | Clearly answers both 'what' (Note Creation and Management - creating notes, organizing content, managing notebooks) and 'when' with an explicit 'Use when...' clause and a 'Trigger with phrases like...' section providing concrete trigger examples. | 3 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'create evernote note', 'manage evernote notes', 'evernote content', and 'notebooks', but misses common natural variations users might say such as 'save to evernote', 'add a note', 'organize my notes', 'tag notes', or 'note-taking app'. | 2 / 3 |
Distinctiveness Conflict Risk | The repeated, specific mention of 'Evernote' throughout the description creates a clear niche. It is unlikely to conflict with generic note-taking or other document management skills due to the platform-specific branding. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides a reasonable structure for Evernote note management with a useful error handling table and one good code example, but most steps lack executable code and read more as descriptions than actionable instructions. The referenced implementation guide is missing from the bundle, creating a broken progressive disclosure chain. Adding validation steps for ENML manipulation and concrete code for steps 2-4 would significantly improve quality.
Suggestions
Add executable code examples for Steps 2-4 (retrieval, updates, organization) instead of just describing the API methods to call.
Include an ENML validation step after content manipulation (e.g., a helper function that checks well-formedness before calling updateNote), and add a validate-fix-retry loop.
Either provide the referenced 'references/implementation-guide.md' bundle file or inline the critical parts of the complete workflow example.
Remove the 'Understanding of ENML format' prerequisite and the Output section's redundant listing—the instructions already cover these.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but includes some unnecessary filler like 'Understanding of ENML format' as a prerequisite and verbose descriptions in steps 2-4 that describe what to do without adding much beyond what Claude already knows about API patterns. The error handling table is useful but the Output section is somewhat redundant given the instructions. | 2 / 3 |
Actionability | Step 1 provides executable code, but Steps 2-4 are descriptive rather than concrete—they mention method names and approaches without providing executable code examples. The 'Complete Workflow Example' defers to a reference file that doesn't exist in the bundle, leaving a gap. | 2 / 3 |
Workflow Clarity | Steps are sequenced logically (create → read → update → organize → full workflow), but there are no validation checkpoints. ENML manipulation is fragile (inserting before closing tags, stripping tags for plain text) yet no validate-then-proceed feedback loops are provided, which should cap this at 2. | 2 / 3 |
Progressive Disclosure | References an implementation guide at 'references/implementation-guide.md' and links to external Evernote docs, which is good structure. However, the bundle has no files, so the referenced implementation guide doesn't exist, undermining the progressive disclosure. Steps 2-4 are thin inline content that could either be fleshed out or properly delegated. | 2 / 3 |
Total | 8 / 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.