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".
74
70%
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 solid description with clear 'what' and 'when' clauses, explicit trigger phrases, and a distinctive niche. Its main weakness is that the capabilities described are somewhat high-level—it could benefit from listing more concrete actions beyond 'configure' and 'manage'. Overall it performs well for skill selection purposes.
Suggestions
Add more specific concrete actions such as 'create environment-specific config files', 'set API keys per environment', or 'manage OAuth tokens across environments' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It 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' (explicit 'Use when' clause for setting up dev/staging/production environments, plus explicit trigger phrases). | 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. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche combining Evernote integrations with multi-environment configuration. The combination of 'Evernote' + 'multi-environment' makes it highly unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides a reasonable structure for multi-environment Evernote setup with some concrete code examples, but falls short on actionability for key steps (client factory, Docker compose) which are described rather than shown. The workflow lacks validation checkpoints, and the referenced implementation guide doesn't exist in the bundle, leaving significant gaps in the guidance.
Suggestions
Add executable code for the client factory (Step 3) and Docker Compose configuration (Step 4)—these are core deliverables that are currently just prose descriptions.
Add a validation checkpoint after environment setup (e.g., a script or command that verifies key/environment matching before proceeding to Docker or deployment steps).
Either include the referenced 'references/implementation-guide.md' as a bundle file or inline the critical content it supposedly contains.
Remove explanatory sentences like 'The EVERNOTE_SANDBOX flag controls which Evernote endpoint the SDK connects to'—Claude can infer this from the code and config structure.
| 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 prose without code, which is both verbose and not actionable. 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—just vague instructions like 'Build a factory that creates properly configured Evernote clients.' The client factory is arguably the most critical piece and is missing entirely from the body. | 2 / 3 |
Workflow Clarity | Steps are numbered and sequenced, but there are no validation checkpoints between steps. Step 3 mentions 'Include validation that production never uses sandbox tokens' but doesn't show how. There's no feedback loop for verifying the environment setup is correct before proceeding, and the health check in Step 5 is post-hoc rather than a build-time validation gate. | 2 / 3 |
Progressive Disclosure | The skill references 'references/implementation-guide.md' and other skills like 'evernote-ci-integration' and 'evernote-observability', which is good structure. However, no bundle files are provided, so the referenced implementation guide doesn't exist, and critical content (client factory, Docker setup) is deferred to a missing file rather than being included inline or in an actual bundle. | 2 / 3 |
Total | 8 / 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.