CtrlK
BlogDocsLog inGet started
Tessl Logo

evernote-prod-checklist

Production readiness checklist for Evernote integrations. Use when preparing to deploy Evernote integration to production, or auditing production readiness. Trigger with phrases like "evernote production", "deploy evernote", "evernote go live", "production checklist evernote".

67

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

65%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 highly actionable with concrete checklists and executable scripts, and uses a real one-level reference for deeper detail. It is held back by a verification script lacking a real fail-on-error feedback loop and by inline detail that overlaps the bundled guide.

Suggestions

Make the verification script a true feedback loop: use 'set -euo pipefail' with explicit failure checks (e.g. test the curl exit code and jq result) so it exits non-zero and reports which check failed, capping workflow_clarity concerns.

Trim the inline verification script and error-handling table, pointing to references/implementation-guide.md for the full versions, so the SKILL.md stays a lean overview and the guide holds the detail.

Add an explicit ordered go-live sequence (e.g. 1. verify keys -> 2. run checks -> 3. run verification script -> 4. sign off) with validation checkpoints between steps.

DimensionReasoningScore

Conciseness

The body is largely efficient checklists, but the Verification Script embeds a full bash block and the Error Handling and Resources sections repeat information that mostly belongs in the bundled implementation guide, adding tokens beyond what Claude needs.

2 / 3

Actionability

Concrete, copy-paste-ready items throughout: specific config values (`EVERNOTE_SANDBOX=false`), algorithms (AES-256-GCM), TTLs (5-10 min), and an executable verification script with real curl/jq commands.

3 / 3

Workflow Clarity

Sections are logically grouped and there is a post-deploy verification script, but the multi-step go-live process has no explicit sequencing with validation checkpoints; the verification script runs checks sequentially but lacks a feedback loop (it prints PASS unconditionally rather than exiting on failure).

2 / 3

Progressive Disclosure

A single well-signaled one-level reference exists (`references/implementation-guide.md`, confirmed as a real file), but the SKILL.md still inlines substantial detail (full verification script, error table) that overlaps the guide rather than cleanly splitting overview from detail.

2 / 3

Total

9

/

12

Passed

Description

100%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.

The description is concise, uses third person, and clearly states both what the skill does and when to use it, with natural trigger phrases. It is a strong example matching the rubric's top anchors across all dimensions.

DimensionReasoningScore

Specificity

States a concrete capability ('Production readiness checklist for Evernote integrations') and pairs it with two explicit use cases (deploying to production, auditing production readiness), listing multiple specific actions rather than vague language.

3 / 3

Completeness

Explicitly answers both 'what' (production readiness checklist for Evernote integrations) and 'when' (preparing to deploy or auditing production readiness) with an explicit 'Use when...' clause and trigger phrases, matching the 3-anchor example.

3 / 3

Trigger Term Quality

Provides natural trigger phrases a user would actually say ('evernote production', 'deploy evernote', 'evernote go live', 'production checklist evernote'), giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

The narrow Evernote production-deployment niche with distinctive triggers ('evernote go live', 'deploy evernote') makes it clearly distinguishable and unlikely to fire for unrelated skills.

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.