CtrlK
BlogDocsLog inGet started
Tessl Logo

evernote-deploy-integration

Deploy Evernote integrations to production environments. Use when deploying to cloud platforms, configuring production, or setting up deployment pipelines. Trigger with phrases like "deploy evernote", "evernote production deploy", "release evernote", "evernote cloud deployment".

69

Quality

86%

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

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

A well-structured, token-efficient deployment overview that uses progressive disclosure effectively and provides executable code for Docker and Cloud Run. It is held back by descriptive (non-executable) Lambda/Kubernetes steps and the absence of an explicit verification feedback loop in the workflow.

Suggestions

Add at least minimal executable snippets for the AWS Lambda and Kubernetes steps (e.g., a Lambda handler skeleton and a Deployment/Secret manifest) instead of describing them in prose.

Turn Step 5 verification into an explicit gate with a feedback loop — e.g., 'If the health check fails or the test note cannot be created, review the Error Handling table, fix, redeploy, and re-verify before declaring success.'

Reference the implementation-guide.md sections by name from within Steps 3–5 so the reader knows exactly where the deferred executable detail lives.

DimensionReasoningScore

Conciseness

Lean body with no padding of concepts Claude already knows (no explanations of Docker, Kubernetes, or Cloud Run fundamentals); every section earns its place, and the few asides guide platform choice rather than re-teaching basics.

3 / 3

Actionability

Steps 1 and 2 give copy-paste-ready Dockerfile and gcloud commands, but Steps 3 and 4 (Lambda, Kubernetes) only describe the approach ('Package the webhook handler as a Lambda function behind API Gateway') without executable code, leaving the guidance incomplete in-body.

2 / 3

Workflow Clarity

The five-step sequence is clear and Step 5 provides verification checks, but there is no explicit validate→fix→retry gate or 'only proceed when valid' checkpoint, so for production deployment the feedback loop is only implicit via the error table.

2 / 3

Progressive Disclosure

SKILL.md acts as an overview with a single, well-signaled one-level-deep reference to references/implementation-guide.md (a real file) for the full Lambda handler, Kubernetes manifests, and verification scripts; content is appropriately split.

3 / 3

Total

10

/

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.

A strong, third-person description that pairs concrete deployment actions with an explicit Use-when clause and literal trigger phrases. It cleanly answers what the skill does and when to invoke it.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'Deploy Evernote integrations to production environments', 'deploying to cloud platforms', 'configuring production', 'setting up deployment pipelines' — matching the multi-action anchor.

3 / 3

Completeness

Clearly answers both 'what' (deploy Evernote integrations to production) and 'when' via an explicit 'Use when deploying to cloud platforms, configuring production, or setting up deployment pipelines' clause.

3 / 3

Trigger Term Quality

Explicit natural trigger phrases users would say: "deploy evernote", "evernote production deploy", "release evernote", "evernote cloud deployment", giving good coverage.

3 / 3

Distinctiveness Conflict Risk

Niche is sharply scoped to Evernote production deployment with distinct triggers, making conflict with other skills unlikely.

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.