evernote-multi-env-setup
Configure multi-environment setup for Evernote integrations. Use when setting up dev, staging, and production environments, or managing environment-specific configurations. Trigger with phrases like "evernote environments", "evernote staging", "evernote dev setup", "multiple environments evernote".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill evernote-multi-env-setup79
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 with excellent completeness and trigger term coverage. It explicitly includes 'Use when' and 'Trigger with' clauses, making selection criteria clear. The main weakness is that the capabilities could be more specific about what concrete actions the skill performs beyond 'configure' and 'manage'.
Suggestions
Add specific concrete actions like 'create environment config files', 'set up API credentials per environment', or 'validate environment-specific settings' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Evernote integrations, multi-environment setup) and mentions some actions (setting up environments, managing configurations), but lacks concrete specific actions like 'create config files', 'set API keys', or 'validate environment variables'. | 2 / 3 |
Completeness | Clearly answers both what (configure multi-environment setup for Evernote integrations) and when (setting up dev/staging/production, managing environment-specific configs) with explicit 'Use when' and 'Trigger with' clauses. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'evernote environments', 'evernote staging', 'evernote dev setup', 'multiple environments evernote'. Also includes natural terms like 'dev', 'staging', 'production environments'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche combining 'Evernote' with 'multi-environment setup'. The combination of Evernote-specific triggers and environment management creates a clear, distinct scope unlikely to conflict with generic environment or 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 is a comprehensive, actionable skill with excellent code examples that are immediately usable. However, it's overly long for a SKILL.md file and would benefit from splitting detailed configurations (Docker, CI/CD) into separate reference files. The workflow lacks explicit validation checkpoints between environment setup steps, which is important for production deployment scenarios.
Suggestions
Add explicit validation checkpoints between steps, such as 'Verify configuration loads correctly: node -e "console.log(require('./config').getAll())"' after Step 3
Move Docker Compose and CI/CD configurations to separate reference files (e.g., DOCKER.md, CICD.md) and link to them from the main skill
Add a verification step after Step 4 to test the client factory before proceeding to infrastructure setup
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary verbosity. The environment strategy table and extensive code examples are useful, but some sections like the Docker Compose and CI/CD configuration could be more concise or referenced externally given their standard nature. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready code examples throughout. Configuration files, JavaScript modules, Docker Compose, and GitHub Actions workflows are all complete and specific with concrete values and patterns. | 3 / 3 |
Workflow Clarity | Steps are numbered and sequenced clearly (Steps 1-8), but lacks explicit validation checkpoints between steps. For a multi-environment setup involving production deployments, there should be explicit verification steps (e.g., 'validate config before deploying') rather than just a final health check endpoint. | 2 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but the skill is monolithic at ~350 lines. The Docker Compose, CI/CD, and health check sections could be split into separate reference files. Only one external reference exists ('evernote-observability' at the end). | 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 (580 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.