From evernote-pack
Implement security best practices for Evernote integrations. Use when securing API credentials, implementing OAuth securely, or hardening Evernote integrations. Trigger with phrases like "evernote security", "secure evernote", "evernote credentials", "evernote oauth security".
How this skill is triggered — by the user, by Claude, or both
Slash command
/evernote-pack:evernote-security-basicsThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Security best practices for Evernote API integrations, covering credential management, OAuth implementation, data protection, and secure coding patterns.
Security best practices for Evernote API integrations, covering credential management, OAuth implementation, data protection, and secure coding patterns.
See implementation guide for detailed steps.
For full implementation details and code examples, load:
references/implementation-guide.md
For production deployment checklist, see evernote-prod-checklist.
| Error | Cause | Resolution |
|---|---|---|
| Authentication failure | Invalid or expired credentials | Refresh tokens or re-authenticate with security |
| Configuration conflict | Incompatible settings detected | Review and resolve conflicting parameters |
| Resource not found | Referenced resource missing | Verify resource exists and permissions are correct |
Basic usage: Apply evernote security basics to a standard project setup with default configuration options.
Advanced scenario: Customize evernote security basics 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