evernote-multi-env-setup
Configure multi-environment setup for Evernote integrations. Use when setting up dev, staging, and production environments, or managing environment-specific configurations. Trigger with phrases like "evernote environments", "evernote staging", "evernote dev setup", "multiple environments evernote". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill evernote-multi-env-setup --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Evernote Multi-Environment Setup ## Overview Configure separate development, staging, and production environments for Evernote integrations with proper isolation, configuration management, and environment-aware client factories. ## Prerequisites - Multiple Evernote API keys (sandbox for dev/staging, production for prod) - Environment management infrastructure - CI/CD pipeline (see `evernote-ci-i
What does the evernote-multi-env-setup skill do?
Configure multi-environment setup for Evernote integrations. Use when setting up dev, staging, and production environments, or managing environment-specific configurations. Trigger with phrases like "evernote environments", "evernote staging", "evernote dev setup", "multiple environments evernote". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill evernote-multi-env-setup --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.