evernote-local-dev-loop
Set up efficient local development workflow for Evernote integrations. Use when configuring dev environment, setting up sandbox testing, or optimizing development iteration speed. Trigger with phrases like "evernote dev setup", "evernote local development", "evernote sandbox", "test evernote locally".
77
73%
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-local-dev-loop/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 trigger terms and clear 'when' guidance, making it easy for Claude to select appropriately. Its main weakness is that the 'what' portion is somewhat vague—it describes the goal (efficient local dev workflow) without listing the specific concrete actions or steps involved. Adding more specific capabilities would strengthen it.
Suggestions
Add specific concrete actions to the description, e.g., 'Configures Evernote API sandbox credentials, sets up local OAuth flow, installs SDK dependencies, and creates test notebooks for integration testing.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Evernote local development) and some actions (configuring dev environment, setting up sandbox testing, optimizing iteration speed), but these are fairly high-level and not concrete specific actions like 'install SDK', 'configure OAuth tokens', or 'set up mock API endpoints'. | 2 / 3 |
Completeness | Clearly answers both 'what' (set up efficient local development workflow for Evernote integrations) and 'when' (configuring dev environment, setting up sandbox testing, optimizing development iteration speed) with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes explicit natural trigger phrases like 'evernote dev setup', 'evernote local development', 'evernote sandbox', 'test evernote locally', plus contextual terms like 'dev environment', 'sandbox testing', and 'development iteration speed'. Good coverage of terms a user would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of 'Evernote' + 'local development workflow' + 'sandbox' creates a very specific niche that is unlikely to conflict with other skills. The trigger terms are highly specific to this particular use case. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is well-organized with good progressive disclosure and a logical structure, but suffers from incomplete actionability—two key steps (ENML helpers and Express server) describe what to build without providing executable code. The workflow lacks validation checkpoints between steps, and some prose could be trimmed to improve conciseness.
Suggestions
Add executable code for Steps 4 and 5 (ENML helpers and Express server) or explicitly state these are in the implementation guide reference, removing the descriptive placeholders.
Add validation checkpoints after Steps 2 and 3 (e.g., 'Verify env loads correctly with `node -e "require('dotenv').config(); console.log(process.env.EVERNOTE_SANDBOX)"`').
Remove explanatory sentences before code blocks (e.g., 'Create a client factory that switches between...') since the code and heading make the purpose clear.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanatory text (e.g., 'Create a client factory that switches between Developer Token...' before the code block, explaining what ENML helpers do). Several steps describe what to build rather than showing it, adding words without adding value. However, it's not egregiously verbose. | 2 / 3 |
Actionability | Steps 1-3 and 6 provide concrete code/commands, but Steps 4 and 5 are purely descriptive with no executable code—they tell Claude to 'build helper functions' and 'set up a local Express server' without providing the actual implementations. The reference to an implementation guide defers the real content. | 2 / 3 |
Workflow Clarity | Steps are clearly sequenced and logically ordered, but there are no validation checkpoints between steps. Step 6 provides a test script at the end, but there's no feedback loop (e.g., 'if connection fails, check X and retry'). For a setup workflow that could fail at multiple points, explicit validation after environment config and after server setup would be expected. | 2 / 3 |
Progressive Disclosure | The skill provides a clear overview with well-structured sections, then appropriately defers full implementation details to a single reference file (references/implementation-guide.md). Navigation to next steps (evernote-sdk-patterns) and external resources is clearly signaled. One level deep, no nesting. | 3 / 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
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.