From evernote-pack
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".
How this skill is triggered — by the user, by Claude, or both
Slash command
/evernote-pack:evernote-sdk-patternsThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Production-ready patterns for working with the Evernote SDK, including search, filtering, batch operations, and resource handling.
Production-ready patterns for working with the Evernote SDK, including search, filtering, batch operations, and resource handling.
evernote-install-auth and evernote-hello-worldSee implementation guide for detailed steps.
For full implementation details and code examples, load:
references/implementation-guide.md
| Error | Cause | Solution |
|---|---|---|
RATE_LIMIT_REACHED | Too many API calls | Use rateLimitDuration, add delays |
BAD_DATA_FORMAT | Invalid ENML | Validate before sending |
DATA_CONFLICT | Concurrent modification | Refetch and retry |
QUOTA_REACHED | Account storage full | Check user's remaining quota |
See evernote-core-workflow-a for note creation and management workflows.
Basic usage: Apply evernote sdk patterns to a standard project setup with default configuration options.
Advanced scenario: Customize evernote sdk patterns for production environments with multiple constraints and team-specific requirements.
npx claudepluginhub aiminnovations/claude-code-plugins-plus --plugin evernote-packGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.
4plugins reuse this skill
First indexed Jul 11, 2026