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".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill evernote-deploy-integration79
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-structured skill description that clearly defines its scope around Evernote deployment and provides explicit trigger guidance. The main weakness is that the specific actions (deploying, configuring, setting up pipelines) are somewhat generic deployment concepts rather than Evernote-specific capabilities. Overall, it should perform well in skill selection scenarios.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Evernote integrations, production environments) and mentions actions like 'deploying to cloud platforms, configuring production, setting up deployment pipelines', but these are somewhat generic deployment concepts rather than highly specific concrete actions unique to Evernote. | 2 / 3 |
Completeness | Clearly answers both what ('Deploy Evernote integrations to production environments') and when ('Use when deploying to cloud platforms, configuring production, or setting up deployment pipelines') with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'deploy evernote', 'evernote production deploy', 'release evernote', 'evernote cloud deployment'. Also includes contextual triggers like 'cloud platforms', 'production', 'deployment pipelines'. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of 'Evernote' with deployment-specific terminology creates a clear niche. The explicit trigger phrases with 'evernote' make it unlikely to conflict with generic deployment skills or other integration skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides comprehensive, executable deployment configurations across multiple cloud platforms, making it highly actionable. However, it suffers from being overly verbose by including all deployment options in a single file rather than using progressive disclosure. The workflow lacks explicit validation checkpoints between deployment steps, which is important for production deployments.
Suggestions
Split platform-specific deployments into separate files (e.g., AWS-DEPLOY.md, GCP-DEPLOY.md, K8S-DEPLOY.md) and keep SKILL.md as a concise overview with links
Add explicit validation steps between deployment stages (e.g., 'Verify image pushed successfully before proceeding to ECS update')
Integrate the deployment checklist into the workflow steps rather than having it as a separate section at the end
Add rollback procedures and error recovery guidance for failed deployments
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill provides extensive deployment configurations across multiple platforms, which is useful but verbose. Some sections could be consolidated, and the sheer volume (6+ deployment options) may exceed what's needed for a single skill file. | 2 / 3 |
Actionability | Excellent actionability with complete, executable configurations for Docker, AWS CloudFormation, GitHub Actions, GCP Cloud Build, Serverless, and Kubernetes. All code is copy-paste ready with proper syntax. | 3 / 3 |
Workflow Clarity | Steps are numbered but lack explicit validation checkpoints between deployment stages. The deployment checklist at the end is helpful but should be integrated into the workflow. Missing feedback loops for deployment failures beyond the verification script. | 2 / 3 |
Progressive Disclosure | Content is monolithic with all deployment options inline rather than split into separate files. The skill would benefit from a brief overview with links to platform-specific deployment guides (e.g., AWS-DEPLOY.md, GCP-DEPLOY.md). | 2 / 3 |
Total | 9 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (577 lines); consider splitting into references/ and linking | Warning |
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 | 8 / 11 Passed | |
- 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.