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".
66
59%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/evernote-pack/skills/evernote-deploy-integration/SKILL.mdQuality
Discovery
82%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 reasonably well-structured with clear 'what' and 'when' clauses and explicit trigger phrases, which is a strength. However, the specific capabilities beyond 'deploy to production' are vague—it doesn't detail what the skill actually does (e.g., Docker configuration, CI/CD setup, environment variable management). The Evernote qualifier provides some distinctiveness but the deployment terminology is generic enough to risk overlap with other deployment skills.
Suggestions
Add more specific concrete actions the skill performs, such as 'Configures Docker containers, sets up CI/CD pipelines, manages environment variables for Evernote API integrations'
Clarify what 'cloud platforms' are supported (e.g., AWS, GCP, Heroku) to improve both specificity and distinctiveness
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Evernote integrations, production environments) and mentions some actions (deploying to cloud platforms, configuring production, setting up deployment pipelines), but these actions are fairly generic and not deeply specific about what concrete steps or capabilities the skill provides. | 2 / 3 |
Completeness | The description clearly answers both 'what' (deploy Evernote integrations to production environments) and 'when' (deploying to cloud platforms, configuring production, setting up deployment pipelines), with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | The description includes explicit trigger phrases like 'deploy evernote', 'evernote production deploy', 'release evernote', 'evernote cloud deployment' which are natural terms a user would say. It also includes broader terms like 'cloud platforms', 'deployment pipelines', and 'production' which provide good keyword coverage. | 3 / 3 |
Distinctiveness Conflict Risk | While 'Evernote' is a distinctive qualifier, terms like 'deploy', 'cloud platforms', 'deployment pipelines', and 'production' are very generic and could overlap with other deployment-related skills. The Evernote specificity helps but the deployment actions are broad enough to cause conflicts. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
37%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill covers a broad deployment topic but is uneven in depth: Docker and Cloud Run have executable examples while Lambda, Kubernetes, and verification are vague descriptions. The workflow framing as sequential steps is misleading since these are independent deployment options, and the lack of validation checkpoints for destructive/production operations is a significant gap. The referenced implementation guide doesn't exist in the bundle, leaving critical content inaccessible.
Suggestions
Add executable code for Steps 3-5 (Lambda handler, Kubernetes manifests, verification script) either inline or in an actual bundle reference file.
Restructure the steps to clarify these are alternative deployment paths, not sequential steps, and add explicit validation/verification commands after each deployment option.
Create the referenced 'references/implementation-guide.md' bundle file, or inline the critical content if the bundle is not available.
Remove explanatory sentences about what Cloud Run and Lambda are good for—Claude already knows this—and replace with actionable deployment commands.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanatory text (e.g., 'Cloud Run scales to zero when idle, making it cost-effective for webhook receivers', 'Lambda is ideal for event-driven Evernote integrations') that Claude already knows. Steps 3-5 are vague prose without code, yet the Docker and Cloud Run sections are reasonably tight. | 2 / 3 |
Actionability | Steps 1 and 2 provide executable code (Dockerfile, gcloud command), but Steps 3, 4, and 5 are entirely descriptive with no concrete code, commands, or manifests. The Lambda handler, Kubernetes manifests, and verification script are deferred to a reference file that doesn't exist in the bundle. | 2 / 3 |
Workflow Clarity | The steps are listed sequentially but represent independent deployment options (Cloud Run, Lambda, K8s), not a sequential workflow. There are no validation checkpoints between steps, no feedback loops for error recovery during deployment, and Step 5's verification is vague ('verify: health check endpoint returns connected') with no executable commands. | 1 / 3 |
Progressive Disclosure | The skill references an implementation guide at 'references/implementation-guide.md' which is a good pattern for progressive disclosure, but the bundle has no files, meaning the reference is broken. The error handling table and resources section are well-organized, but the inline content for Steps 3-5 is too thin while Steps 1-2 could arguably be in the reference file for consistency. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Commit
3a2d27d
- 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.