evernote-sdk-patterns
Advanced Evernote SDK patterns and best practices. Use when implementing complex note operations, batch processing, search queries, or optimizing SDK usage. Trigger with phrases like "evernote sdk patterns", "evernote best practices", "evernote advanced", "evernote batch operations".
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-sdk-patterns/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 that clearly identifies its niche (Evernote SDK advanced patterns), provides explicit trigger guidance, and answers both what and when. Its main weakness is that the specific capabilities listed are somewhat abstract—terms like 'complex note operations' and 'optimizing SDK usage' could be more concrete with specific examples of what those operations entail.
Suggestions
Replace abstract phrases like 'complex note operations' with concrete actions such as 'create notes with attachments, manage notebooks, handle note metadata and tags'.
Add more specific SDK optimization examples like 'rate limiting, pagination handling, error retry strategies' to strengthen specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Evernote SDK) and mentions some actions like 'complex note operations, batch processing, search queries, optimizing SDK usage', but these are somewhat abstract rather than concrete specific actions (e.g., doesn't specify what 'complex note operations' entails). | 2 / 3 |
Completeness | Clearly answers both 'what' (advanced Evernote SDK patterns covering complex note operations, batch processing, search queries, SDK optimization) and 'when' (explicit 'Use when' clause and 'Trigger with phrases like' section). | 3 / 3 |
Trigger Term Quality | Includes explicit trigger phrases like 'evernote sdk patterns', 'evernote best practices', 'evernote advanced', 'evernote batch operations' which are natural terms a developer would use. Also includes terms like 'search queries' and 'batch processing' in the body. | 3 / 3 |
Distinctiveness Conflict Risk | Evernote SDK is a very specific niche domain, and the description clearly scopes to advanced patterns and best practices. This is unlikely to conflict with other skills unless there's a basic Evernote SDK skill, in which case the 'advanced' qualifier helps distinguish. | 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 useful code examples for the first two patterns and a helpful error handling table. However, it's weakened by three patterns that are described only in prose without executable code, and the batch operations workflow lacks explicit validation/retry feedback loops. The content could be tightened by removing explanations Claude already knows and either providing complete code for all patterns or more clearly deferring to the reference file upfront.
Suggestions
Add executable code examples for Patterns 3, 4, and 5 (error handling wrapper, batch operations, tag/notebook management) or remove the prose descriptions and consolidate the reference to implementation-guide.md
Add an explicit validate-fix-retry feedback loop for the batch operations pattern, showing concrete code for rate limit detection and retry with delay
Remove the Prerequisites section and explanatory sentences like 'This avoids fetching full note content when only metadata is needed'—Claude already understands these concepts
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some unnecessary explanation (e.g., 'This avoids fetching full note content when only metadata is needed' and the Prerequisites section explaining what Claude should already know). Patterns 3-5 are described abstractly without code, which is wasted space since the descriptions don't add much actionable value. | 2 / 3 |
Actionability | Patterns 1 and 2 have executable code examples, but Patterns 3, 4, and 5 are described only in prose with no concrete code—just vague descriptions like 'Process items sequentially with configurable delay.' The examples section at the end describes scenarios but provides no executable code. Key implementations are deferred to a reference file. | 2 / 3 |
Workflow Clarity | The patterns are listed but lack explicit validation checkpoints. Batch operations (Pattern 4) mention rate limit retry but don't show a concrete feedback loop with validation steps. The error handling table is helpful but disconnected from the workflow steps. For batch/destructive operations, the missing explicit validate-fix-retry sequence caps this at 2. | 2 / 3 |
Progressive Disclosure | The skill provides a clear overview with well-signaled references: an implementation guide for complete code, external API/SDK links, and a next-steps pointer to a related workflow skill. Content is appropriately split between the overview here and detailed implementations in the reference file. | 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.