evernote-hello-world

Create a minimal working Evernote example. Use when starting a new Evernote integration, testing your setup, or learning basic Evernote API patterns. Trigger with phrases like "evernote hello world", "evernote example", "evernote quick start", "simple evernote code", "create first note".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

75%

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

A largely actionable and well-structured hello-world skill with executable code and a clean single-level reference. It loses points on conciseness for explaining familiar ENML concepts and on workflow clarity for lacking a validate-then-proceed checkpoint despite documenting error cases.

Suggestions

Trim explanations of concepts Claude already knows (e.g., the ENML 'restricted XHTML subset' and forbidden-element list) and reference the ENML DTD instead of restating rules.

Add an explicit validation checkpoint after createNote (e.g., verify the returned GUID / catch EDAMUserException and re-validate ENML before retrying) so the workflow has a feedback loop.

De-duplicate the ENML boilerplate (XML declaration + DOCTYPE) by defining it once and reusing it in Step 3 rather than repeating the full header verbatim.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable snippets, but it explains ENML mechanics Claude already knows ('a restricted XHTML subset', forbidden elements, inline-style rules) and repeats the ENML boilerplate verbatim across steps, which could be tightened.	2 / 3
Actionability	Provides fully executable JavaScript for client init, note creation, and notebook listing, plus a concrete ENML template and a copy-paste-ready getNote call with flag meanings.	3 / 3
Workflow Clarity	Steps are clearly sequenced, but there is no validation checkpoint for the create-note write operation and no feedback loop for the documented EDAM errors; the guideline capping workflow clarity at 2 for missing validation in write/batch contexts applies.	2 / 3
Progressive Disclosure	SKILL.md is a concise overview with a single clearly signaled, one-level-deep reference ('references/implementation-guide.md') that exists as a real file, and content is appropriately split rather than nested.	3 / 3
	Total	10 / 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.

A well-crafted description that concisely states the capability, provides explicit 'Use when' guidance, and lists natural trigger phrases with strong Evernote-specific distinctiveness. It is in third person and free of fluff.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions: 'Create a minimal working Evernote example' and pairs it with concrete use contexts (starting a new integration, testing setup, learning API patterns).	3 / 3
Completeness	Explicitly answers what ('Create a minimal working Evernote example') and when via a 'Use when...' clause plus concrete trigger phrases, satisfying both halves.	3 / 3
Trigger Term Quality	Lists several natural phrases a user would say ('evernote hello world', 'evernote example', 'evernote quick start', 'simple evernote code', 'create first note') with good coverage of variations.	3 / 3
Distinctiveness Conflict Risk	The Evernote-specific niche and 'evernote'-prefixed trigger phrases make it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 02d6341

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.