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".
77
73%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/evernote-pack/skills/evernote-multi-env-setup/SKILL.mdQuality
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 description with strong completeness and distinctiveness. It clearly identifies both what the skill does and when to use it, with explicit trigger phrases. The main weakness is that the specific capabilities could be more concrete—listing actual actions like configuring API keys, setting up OAuth per environment, or creating environment config files would strengthen it.
Suggestions
Add more concrete actions beyond 'configure' and 'manage', such as 'set up API keys per environment', 'configure OAuth credentials', or 'create environment-specific config files' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Evernote integrations, multi-environment setup) and mentions some actions (setting up dev/staging/production, managing environment-specific configurations), but doesn't list concrete specific actions like 'create config files', 'set API keys per environment', or 'manage OAuth credentials'. | 2 / 3 |
Completeness | Clearly answers both 'what' (configure multi-environment setup for Evernote integrations) and 'when' (setting up dev/staging/production environments, managing environment-specific configurations), with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes explicit natural trigger phrases like 'evernote environments', 'evernote staging', 'evernote dev setup', 'multiple environments evernote', plus terms like 'dev', 'staging', 'production environments'. These are terms users would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of 'Evernote' + 'multi-environment setup' is a very specific niche. The trigger terms are narrowly scoped to Evernote environment configuration, making it unlikely to conflict with general environment setup or general Evernote skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill has good structure and progressive disclosure, with a clear overview that delegates to references appropriately. However, it falls short on actionability by leaving the most critical components (client factory, Docker setup) as prose descriptions rather than executable code. Adding validation checkpoints between steps and completing the missing code examples would significantly improve the skill.
Suggestions
Add executable code for Step 3 (Environment-Aware Client Factory) including the production/sandbox token validation logic, as this is the core component of the skill.
Add executable code for Step 4 (Docker Compose) showing the actual docker-compose.yml configuration.
Add a validation checkpoint after Step 2 (e.g., a script or command to verify environment variables are correctly set and keys match the expected environment) to create a feedback loop before proceeding to client creation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanatory text (e.g., 'The EVERNOTE_SANDBOX flag controls which Evernote endpoint the SDK connects to') and descriptive prose that Claude could infer. Steps 3 and 4 are described in words rather than code, which adds verbosity without adding actionability. However, it's not egregiously padded. | 2 / 3 |
Actionability | Steps 1, 2, and 5 have concrete code examples, but Steps 3 and 4 are purely descriptive with no executable code—the client factory (arguably the most important piece) is described but not shown. The reference to an implementation guide for the 'full' versions suggests the skill itself is incomplete. | 2 / 3 |
Workflow Clarity | Steps are numbered and sequenced, but there are no validation checkpoints between steps. Step 3 mentions validating that production never uses sandbox tokens but doesn't show how. There's no feedback loop for catching misconfiguration before deployment, which is important for a multi-environment setup involving production credentials. | 2 / 3 |
Progressive Disclosure | The skill provides a clear overview with well-structured sections, delegates the full implementation details to a single reference file (references/implementation-guide.md), and links to related skills (evernote-ci-integration, evernote-observability). Navigation is one level deep and clearly signaled. | 3 / 3 |
Total | 9 / 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
70e9fa4
- 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.