CtrlK
BlogDocsLog inGet started
Tessl Logo

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".

64

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

57%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured and progresses detail into a real reference file, with mostly concrete guidance. It is held back by some redundancy between sections and inline guidance for two steps that defers code to the reference.

Suggestions

Tighten the Output and Examples sections, which restate the numbered steps; either merge the runnable examples into their steps or keep only a single consolidated example to avoid token redundancy.

Add explicit validation checkpoints (e.g., run the test-connection script and confirm before proceeding to OAuth) so the workflow gates are signaled rather than implied.

Inline minimal executable snippets for Steps 4 (ENML helpers) and 5 (Express OAuth routes), or clearly mark them as intentionally deferred to the implementation guide, so the inline guidance is not descriptive-only.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete env vars and code, but the Output and Examples sections restate content from the numbered steps and could be tightened.

2 / 3

Actionability

Provides executable env config and a copy-paste JS client factory, but Steps 4 and 5 only name helpers/routes without inline code (deferred to the reference), leaving some guidance incomplete.

2 / 3

Workflow Clarity

The 6-step sequence is clearly ordered and Step 6 acts as a verification checkpoint, but checkpoints are implicit rather than flagged as validation gates between steps.

2 / 3

Progressive Disclosure

SKILL.md is an overview with a single clearly-signaled one-level-deep reference (implementation-guide.md, which exists) holding the full implementation; content is appropriately split.

3 / 3

Total

9

/

12

Passed

Description

100%

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 clear, specific, and complete with both an explicit what and when clause plus natural trigger phrases. It is a strong, concise description with no fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "configuring dev environment, setting up sandbox testing, or optimizing development iteration speed" — rather than vague language, matching the score-3 anchor.

3 / 3

Completeness

Explicitly answers both what ("Set up efficient local development workflow for Evernote integrations") and when ("Use when configuring dev environment...") with explicit triggers.

3 / 3

Trigger Term Quality

Natural trigger phrases a user would actually say ("evernote dev setup", "evernote local development", "evernote sandbox", "test evernote locally") give good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

The Evernote-specific niche and evernote-prefixed triggers make it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

13

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-skills
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.