From evernote-pack
Execute Evernote primary workflow: Note Creation and Management. Use when creating notes, organizing content, managing notebooks, or implementing note-taking features. Trigger with phrases like "create evernote note", "evernote note workflow", "manage evernote notes", "evernote content".
How this skill is triggered — by the user, by Claude, or both
Slash command
/evernote-pack:evernote-core-workflow-aThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Primary workflow for creating, organizing, and managing notes in Evernote. This covers the essential CRUD operations that form the foundation of any Evernote integration.
Primary workflow for creating, organizing, and managing notes in Evernote. This covers the essential CRUD operations that form the foundation of any Evernote integration.
evernote-install-auth setupFor full implementation details and code examples, load:
references/implementation-guide.md
| Error | Cause | Solution |
|---|---|---|
BAD_DATA_FORMAT | Invalid ENML | Use wrapInENML helper, validate content |
LIMIT_REACHED | Too many notebooks (250 max) | Clean up unused notebooks |
DATA_REQUIRED | Missing title or content | Validate inputs before API call |
INVALID_USER | Token expired | Re-authenticate user |
For search and retrieval workflows, see evernote-core-workflow-b.
Basic usage: Apply evernote core workflow a to a standard project setup with default configuration options.
Advanced scenario: Customize evernote core workflow a for production environments with multiple constraints and team-specific requirements.
npx claudepluginhub terrylica/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