evernote-install-auth
Install and configure Evernote SDK and OAuth authentication. Use when setting up a new Evernote integration, configuring API keys, or initializing Evernote in your project. Trigger with phrases like "install evernote", "setup evernote", "evernote auth", "configure evernote API", "evernote oauth".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill evernote-install-auth85
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 strong trigger terms and clear 'when to use' guidance. The main weakness is that the capabilities could be more specific about what configuration steps are actually performed (e.g., token management, sandbox vs production setup). The explicit trigger phrases section is a notable strength for skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Evernote SDK) and some actions (install, configure, OAuth authentication), but lacks comprehensive detail about what specific configuration steps or capabilities are involved beyond setup. | 2 / 3 |
Completeness | Clearly answers both what (install and configure Evernote SDK and OAuth authentication) and when (setting up new integration, configuring API keys, initializing Evernote) with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'install evernote', 'setup evernote', 'evernote auth', 'configure evernote API', 'evernote oauth' - these are realistic phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche focused on Evernote SDK setup and OAuth - unlikely to conflict with other skills due to the specific product name and setup/authentication focus. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with complete executable code for both Node.js and Python OAuth flows. The workflow is clearly sequenced with verification steps and good error handling coverage. However, the content is somewhat verbose for a skill file and could benefit from tighter organization with some details moved to reference files.
Suggestions
Move the detailed OAuth callback implementation (Step 5b) and error handling table to a separate OAUTH-DETAILS.md file, keeping only the essential setup in the main skill
Remove the 'Output' section as it lists obvious results that don't add actionable value
Consolidate the Python examples or move them to a separate PYTHON-SETUP.md to reduce the main file length
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some unnecessary sections like the detailed 'Output' section listing obvious results, and the 'Next Steps' section. The error handling table and token expiration info are useful but could be more compact. | 2 / 3 |
Actionability | Provides fully executable code examples for both Node.js and Python, complete OAuth flow implementation with callback handling, and copy-paste ready environment configuration. All code is concrete and runnable. | 3 / 3 |
Workflow Clarity | Clear 6-step sequence with explicit validation in Step 6. The OAuth flow is broken into logical sub-steps (5a, 5b) with session management. Error handling table provides clear recovery paths for common issues. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but the skill is quite long (~180 lines) and could benefit from splitting detailed OAuth implementation or error handling into separate reference files. The Resources section provides good external links but internal organization could be improved. | 2 / 3 |
Total | 10 / 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 | |
- 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.