cross-env-setup
Configure cross-env for cross-platform environment variable setting in npm scripts and CLI commands.
npx skills add a5c-ai/babysitter --skill cross-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.
# Cross-Env Setup Configure cross-env for cross-platform environment variables. ## Capabilities - Set up cross-env in package.json - Configure environment variable scripts - Handle platform-specific vars - Integrate with npm scripts ## Generated Patterns ```json { "scripts": { "dev": "cross-env NODE_ENV=development tsx watch src/index.ts", "build": "cross-env NODE_ENV=production tsc", "test": "cross-env NODE_ENV=test vitest", "start:prod": "cross-env NODE_ENV=production node dist/index.js" }, "devDependencies": { "cross-env": "^7.0.3" } } ``` ## Target Processes - cross-platform-cli-compatibility - configuration-management-system - cli-application-bootstrap
- Capabilities
- Generated Patterns
- Target Processes
What does the cross-env-setup skill do?
Configure cross-env for cross-platform environment variable setting in npm scripts and CLI commands.
How do I install it?
Run `npx skills add a5c-ai/babysitter --skill cross-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 a5c-ai/babysitter, a repository with 1,642 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.