eslint-config
Use when configuring ESLint - covers flat config, TypeScript integration, and custom rules
Third-Party Agent Skill: Review the code before installing. Agent skills execute in your AI assistant's environment and can access your files. Learn more about security
Installation for Agentic Skill
View all platforms →skilz install mcclowes/lea/eslint-configskilz install mcclowes/lea/eslint-config --agent opencodeskilz install mcclowes/lea/eslint-config --agent codexskilz install mcclowes/lea/eslint-config --agent geminiFirst time? Install Skilz: pip install skilz
Works with 22+ AI coding assistants
Cursor, Aider, Copilot, Windsurf, Qwen, Kimi, and more...
Extract and copy to ~/.claude/skills/ then restart Claude Desktop
git clone https://github.com/mcclowes/leacp -r lea/.claude/skills/eslint-config ~/.claude/skills/Need detailed installation help? Check our platform-specific guides:
Related Agentic Skills
tailwind-shadcn-setup
by vanman2024
Setup Tailwind CSS and shadcn/ui component library for Next.js projects. Use when configuring Tailwind CSS, installing shadcn/ui, setting up design...
spanish-language-tutor
by sandraschi
Comprehensive Spanish language expert covering grammar, conversation, regional dialects, and language learning strategies
frontend-dev-guidelines
by diet103
Frontend development guidelines for React/TypeScript applications. Modern patterns including Suspense, lazy loading, useSuspenseQuery, file organiz...
torch-geometric
by davila7
Graph Neural Networks (PyG). Node/graph classification, link prediction, GCN, GAT, GraphSAGE, heterogeneous graphs, molecular property prediction, ...
Agentic Skill Details
- Repository
- lea
- Stars
- 3
- Type
- Technical
- Meta-Domain
- development
- Primary Domain
- javascript
- Market Score
- 16
Agent Skill Grade
A Score: 91/100 Click to see breakdown
Score Breakdown
Areas to Improve
- Missing TOC in 162-line file
- Reference files lack TOC
- No workflow steps for setup
Recommendations
- Add trigger phrases to description for discoverability
- Add table of contents for files over 100 lines
Graded: 2026-01-24
Developer Feedback
I've been looking at how teams standardize their linting setup, and your eslint-config skill caught my attention—the way you've structured the progressive disclosure is really efficient for something that could easily become overwhelming. With a 91/100, I'm curious what trade-offs you made between comprehensiveness and usability.
Links:
TL;DR
You're at 91/100, A territory—that's production-ready work based on Anthropic's skill best practices. Your Progressive Disclosure Architecture is the strong suit (27/30), which makes sense given the complexity of ESLint configs. The weakest pillar is Spec Compliance (12/15), mostly because your description could use a couple more trigger phrases to help discoverability.
What's Working Well
- Layered reference structure: Splitting SKILL.md (162 lines) from detailed references/rules.md and references/plugins.md is the right call. Keeps the entry point clean while letting people drill down into rule configurations and plugin integrations without noise.
- Practical code examples: Your quick start with flat config syntax and the concrete examples for TypeScript, testing, and production contexts show real understanding of developer workflows. This isn't theoretical stuff.
- Token-efficient writing: 9/10 on token economy—you're saying what needs to be said without the fluff. That matters when Claude's reading this to help someone.
The Big One: Add a Table of Contents
Your main SKILL.md file sits at 162 lines without a TOC. When developers are using this skill, they need quick navigation to "Quick Start," "Core Configuration," "Common Patterns," "Scripts," etc. Same issue in references/rules.md (147 lines) and references/plugins.md (191 lines).
Fix: Add a simple markdown TOC aft...
Browse Category
More development Agentic SkillsReport Security Issue
Found a security vulnerability in this agent skill?
Report Security Issue
Thank you for helping keep SkillzWave secure. We'll review your report and take appropriate action.
Note: For critical security issues that require immediate attention, please also email security@skillzwave.ai directly.