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".
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-install-auth/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 skill description that clearly defines its scope (Evernote SDK installation and OAuth setup), provides explicit 'Use when' guidance, and includes natural trigger phrases. Its main weakness is that the capability description could be slightly more specific about what concrete actions it performs beyond 'install and configure'. Overall, it's a strong description that would enable accurate skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Evernote SDK) and two actions (install/configure SDK, OAuth authentication), but doesn't list multiple concrete actions beyond setup—e.g., no mention of token management, sandbox vs production, or specific configuration steps. | 2 / 3 |
Completeness | Clearly answers both 'what' (install and configure Evernote SDK and OAuth authentication) and 'when' (setting up a new Evernote integration, configuring API keys, initializing Evernote), with explicit trigger phrases. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'install evernote', 'setup evernote', 'evernote auth', 'configure evernote API', 'evernote oauth'. These are phrases users would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive—focuses specifically on Evernote SDK setup and OAuth configuration, which is a clear niche unlikely to conflict with other skills. The trigger terms are all Evernote-specific. | 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 has good structural organization with clear step numbering, a useful error handling table, and appropriate external references. However, it falls short on actionability in the critical OAuth flow steps (5-6), which are described in vague prose rather than executable code. The referenced bundle file (references/oauth-flow.md) doesn't exist, leaving a significant gap in the implementation guidance.
Suggestions
Add executable code for Steps 5 and 6—show the actual OAuth request token acquisition, callback handling, and getUser() verification call with expected output.
Provide the referenced 'references/oauth-flow.md' bundle file, or inline the essential OAuth callback code if the bundle won't be provided.
Replace the prose-based Examples section with actual code snippets showing developer token initialization and production OAuth client setup.
Add an explicit verification checkpoint after Step 6 showing what successful output looks like (e.g., expected console output from getUser()).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary padding (the Overview section restates what the title already conveys, the Output section lists obvious outcomes, and the Examples section describes workflows in prose rather than showing code). However, it's not egregiously verbose—most sections carry useful information. | 2 / 3 |
Actionability | Steps 1-4 provide concrete commands and code, but Steps 5 and 6 are vague prose descriptions ('Set up request token acquisition...', 'Create an authenticated client...') without executable code. The Examples section also describes workflows in prose rather than providing copy-paste ready code. Key parts of the actual OAuth implementation are missing from the skill body. | 2 / 3 |
Workflow Clarity | The steps are clearly sequenced and numbered, but Steps 5 and 6 lack concrete validation checkpoints. Step 6 says 'call getUser() to confirm authentication succeeds' but doesn't show what success or failure looks like, and there's no explicit error recovery loop (e.g., if verification fails, do X). For an auth setup workflow, missing verification feedback loops caps this at 2. | 2 / 3 |
Progressive Disclosure | The skill references 'references/oauth-flow.md' for detailed OAuth implementation and links to external resources, which is good structure. However, no bundle files are provided, meaning the referenced file doesn't exist, and the inline content for Steps 5-6 is too thin—it defers critical implementation details to a non-existent file rather than providing a usable overview. | 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.