CtrlK
BlogDocsLog inGet started
Tessl Logo

evernote-debug-bundle

Debug Evernote API issues with diagnostic tools and techniques. Use when troubleshooting API calls, inspecting requests/responses, or diagnosing integration problems. Trigger with phrases like "debug evernote", "evernote diagnostic", "troubleshoot evernote", "evernote logs", "inspect evernote".

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 with a clear sequenced workflow and good progressive disclosure to a single real reference file, but it loses points on conciseness (mild restatement/filler), actionability (three steps are described rather than coded and one code snippet is broken), and workflow clarity (no explicit inline validation checkpoints).

Suggestions

Fix the broken Step 2 snippet: replace 'const result = await targetprop;' with 'const result = await target[prop](...args);' so the instrumented client is actually executable.

Provide concrete code for the ENML validator, token inspector, and diagnostic CLI (or at least their key functions) instead of only describing them, to raise actionability.

Weave explicit validation checkpoints into the numbered workflow (e.g., 'validate ENML before saving; if invalid, run auto-fix and re-validate') rather than relying on a separate error-handling table.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete code and steps, but the Overview, Output, and Examples sections restate content and add mild filler ('Comprehensive debugging toolkit...', 'adds zero-config debugging') that could be tightened.

2 / 3

Actionability

Steps 1–2 give concrete executable code, but Steps 3–5 are described and deferred to the reference, and the Step 2 snippet has a bug ('await targetprop' instead of 'target[prop](...args)'), so guidance is incomplete rather than copy-paste ready.

2 / 3

Workflow Clarity

Steps 1–5 are clearly sequenced and an Error Handling table maps issues to diagnostics and solutions, but explicit inline validate-then-proceed checkpoints are missing or implicit within the numbered flow.

2 / 3

Progressive Disclosure

The body is an organized overview with clearly signaled, one-level-deep reference to references/implementation-guide.md (a real bundle file) for the deferred detailed implementations, with easy section-based navigation.

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 specific, complete, and well-triggered, clearly stating what the skill does and when to use it with natural Evernote-centric trigger phrases. It is distinct and unlikely to conflict with other skills.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — 'troubleshooting API calls, inspecting requests/responses, or diagnosing integration problems' — beyond merely naming the Evernote debugging domain.

3 / 3

Completeness

Explicitly answers both 'what' ('Debug Evernote API issues with diagnostic tools and techniques') and 'when' ('Use when troubleshooting API calls...') with explicit trigger guidance.

3 / 3

Trigger Term Quality

Provides natural phrases users would actually say — 'debug evernote', 'evernote diagnostic', 'troubleshoot evernote', 'evernote logs', 'inspect evernote' — with good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Has a clear Evernote-API-debugging niche with evernote-specific trigger phrases, making it unlikely to fire for the wrong skill.

3 / 3

Total

12

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 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

Total

14

/

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.