From evernote-pack
Configure CI/CD pipelines for Evernote integrations. Use when setting up automated testing, continuous integration, or deployment pipelines for Evernote projects. Trigger with phrases like "evernote ci", "evernote github actions", "evernote pipeline", "automate evernote tests".
How this skill is triggered — by the user, by Claude, or both
Slash command
/evernote-pack:evernote-ci-integrationThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Configure continuous integration pipelines for Evernote integrations, including test automation, credential management, and deployment workflows.
Configure continuous integration pipelines for Evernote integrations, including test automation, credential management, and deployment workflows.
For full implementation details and code examples, load:
references/implementation-guide.md
For deployment pipelines, see evernote-deploy-integration.
| Error | Cause | Resolution |
|---|---|---|
| Authentication failure | Invalid or expired credentials | Refresh tokens or re-authenticate with CI/CD |
| 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 ci integration to a standard project setup with default configuration options.
Advanced scenario: Customize evernote ci integration 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