evernote-security-basics

Implement security best practices for Evernote integrations. Use when securing API credentials, implementing OAuth securely, or hardening Evernote integrations. Trigger with phrases like "evernote security", "secure evernote", "evernote credentials", "evernote oauth security".

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/evernote-pack/skills/evernote-security-basics/SKILL.md

Quality

Content

57%Weight 40%Scale 1-3

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

The content is well-structured with a clean six-step overview, real executable code, and a properly signaled one-level-deep reference. The main gaps are prose-only steps that defer to the guide and the absence of explicit validation checkpoints in the workflow.

Suggestions

Add a short inline code snippet or concrete command for the prose-only steps (encrypted token storage, input validation, token lifecycle refresh) so each step is actionable without opening the guide.

Insert explicit validation checkpoints (e.g., verify encryption succeeded, validate sanitized ENML before saving) into the multi-step workflow to support error recovery.

Trim prerequisite explanation of basic concepts Claude already knows (e.g., 'Basic cryptography concepts (AES encryption, hashing)') to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with focused code per step, but includes mild unnecessary explanation Claude already knows (e.g., listing 'Basic cryptography concepts (AES encryption, hashing)' as a prerequisite) and could be tightened slightly.	2 / 3
Actionability	Provides executable JavaScript snippets for env validation, CSRF, and token redaction, plus concrete limits (max 255 chars), but Steps 3, 4, and 6 are prose-only and defer detail to the external guide rather than being copy-paste ready inline.	2 / 3
Workflow Clarity	Six steps are clearly sequenced (credential -> OAuth -> storage -> validation -> logging -> lifecycle), but there are no explicit validation checkpoints or feedback loops, capping workflow clarity at 2 for security-sensitive operations.	2 / 3
Progressive Disclosure	The body is a concise overview with a single well-signaled, one-level-deep reference (references/implementation-guide.md) that exists and contains no nested references, keeping navigation easy.	3 / 3
	Total	9 / 12 Passed

Description

90%Weight 40%Scale 1-3

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 strong description that clearly states its Evernote security niche, gives explicit 'Use when' trigger guidance, and lists natural trigger phrases. The only weakness is that the stated capabilities are broad categories rather than granular concrete actions.

Dimension	Reasoning	Score
Specificity	Names the Evernote security domain and three action areas (securing API credentials, OAuth, hardening integrations), but these are broad categories rather than a list of multiple distinct concrete actions.	2 / 3
Completeness	Explicitly answers both what (implement security best practices for Evernote integrations) and when (Use when securing API credentials, implementing OAuth securely, or hardening Evernote integrations) with trigger guidance.	3 / 3
Trigger Term Quality	Provides natural, user-sayable trigger phrases ("evernote security", "secure evernote", "evernote credentials", "evernote oauth security") covering common variations.	3 / 3
Distinctiveness Conflict Risk	Targets a clear Evernote-specific security niche with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 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
Path: plugins/saas-packs/evernote-pack/skills/evernote-security-basics/SKILL.md
Commit: 4c47e33

Reviewed: 3 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.