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".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill evernote-local-dev-loop85
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 term coverage and clear when/what guidance. The main weakness is the somewhat abstract capability description - it tells you the goal (efficient workflow) but not the specific actions the skill enables (e.g., API configuration, authentication setup, mock data creation).
Suggestions
Add 2-3 concrete actions the skill performs, such as 'configure OAuth credentials', 'set up sandbox API keys', or 'create test notebook structures' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Evernote integrations) and mentions some actions (configuring dev environment, setting up sandbox testing, optimizing iteration speed), but lacks concrete specific actions like 'install dependencies', 'configure OAuth', or 'create test notebooks'. | 2 / 3 |
Completeness | Clearly answers both what (set up local development workflow for Evernote integrations) and when (configuring dev environment, sandbox testing, optimizing iteration speed) with explicit 'Use when' and 'Trigger with' clauses. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'evernote dev setup', 'evernote local development', 'evernote sandbox', 'test evernote locally'. These are realistic terms developers would use. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Evernote development workflows specifically. The combination of 'Evernote' + 'local development' + 'sandbox' creates a distinct trigger profile unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%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, highly actionable skill with excellent executable code examples and clear workflow steps. The main weakness is length - at nearly 300 lines, it could benefit from splitting detailed implementations (ENML utilities, OAuth routes) into separate reference files while keeping the SKILL.md as a leaner overview with quick-start guidance.
Suggestions
Extract ENML utilities into a separate ENML.md reference file and link to it from the main skill
Consider moving the full OAuth implementation to a separate OAUTH.md file, keeping only a minimal example in the main skill
Trim explanatory comments in code examples - Claude can infer purpose from well-named functions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some unnecessary verbosity. The project structure explanation and some comments could be tightened. The ENML utility section is extensive when a reference to external docs might suffice. | 2 / 3 |
Actionability | Excellent actionability with fully executable code throughout - complete bash commands, working JavaScript files, package.json scripts, and curl commands for testing. All code is copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear 7-step sequence with explicit validation via test scripts. The development workflow section provides concrete terminal commands, and the test-note.js includes cleanup. Error handling table provides troubleshooting guidance. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the skill is quite long and monolithic. The ENML utilities and OAuth implementation could be split into separate reference files. References to external resources and next steps are present but the main content could benefit from better separation. | 2 / 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 | |
- 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.