eslint
ESLint configuration, custom rules, and plugin development.
npx skills add a5c-ai/babysitter --skill eslint --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.
# ESLint Skill Expert assistance for ESLint configuration. ## Capabilities - Configure ESLint - Set up plugins - Create custom rules - Handle TypeScript - Configure for React/Vue ## Configuration ```javascript // eslint.config.js (flat config) import js from '@eslint/js'; import typescript from '@typescript-eslint/eslint-plugin'; import react from 'eslint-plugin-react'; export default [ js.configs.recommended, { plugins: { '@typescript-eslint': typescript, react }, rules: { '@typescript-eslint/no-unused-vars': 'error', 'react/jsx-uses-react': 'off', 'react/react-in-jsx-scope': 'off', }, }, ]; ``` ## Target Processes - code-quality - linting-setup - team-standards
- Capabilities
- Configuration
- Target Processes
What does the eslint skill do?
ESLint configuration, custom rules, and plugin development.
How do I install it?
Run `npx skills add a5c-ai/babysitter --skill eslint --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.