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

73

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

85%

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

A dense, actionable production checklist with an executable verification script and proper progressive disclosure to a single real reference file. The only drag is mild redundancy in the Overview/Output/Examples sections.

Suggestions

Remove or merge the 'Output' and 'Examples' sections, which restate items already covered by the checklist, to tighten token use.

Trim the 'Overview' paragraph since the title and section headers already convey the same scope.

Consider moving the static 'Resources' link list into the implementation guide to keep SKILL.md focused on actionable steps.

DimensionReasoningScore

Conciseness

The checklist lines are lean and free of conceptual padding, but the Overview, Output, and Examples sections restate checklist content, and the tail (Resources/Next Steps) adds length beyond what each token strictly earns.

2 / 3

Actionability

Concrete checkboxes with specific values (AES-256-GCM, 100-200ms, 5-10 min TTL, max 255 chars) plus an executable bash verification script with real curl/jq commands and a detailed error table.

3 / 3

Workflow Clarity

Sequenced sections (Prerequisites → category checklists → Deployment → Verification Script → Error Handling) include a post-deploy verification checkpoint and error-recovery/rollback guidance.

3 / 3

Progressive Disclosure

Concise overview with a clearly signaled, verified one-level-deep reference to references/implementation-guide.md, which exists and contains no nested references.

3 / 3

Total

11

/

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 strong, well-structured description that clearly defines capability, explicit use-when triggers, natural trigger phrases, and a distinct niche. All four dimensions land at the top of the scale.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'preparing to deploy Evernote integration to production' and 'auditing production readiness' — rather than vague language.

3 / 3

Completeness

Explicitly states both what it does ('Production readiness checklist for Evernote integrations') and when to use it ('Use when preparing to deploy... or auditing production readiness').

3 / 3

Trigger Term Quality

Provides natural phrases users would say ('evernote production', 'deploy evernote', 'evernote go live', 'production checklist evernote') with good variation coverage.

3 / 3

Distinctiveness Conflict Risk

Scoped tightly to Evernote production deployment with distinct triggers, making it 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.