es-toolkit plugin
es-toolkit for agents: setup and import help, lodash code migration and a choice between the strict and compat APIs
- 11,383 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The skills allow the Bash, Read, Grep and Glob tools: the agent runs `node` commands in your project and reads its files.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/es-toolkitDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The skills allow the Bash, Read, Grep and Glob tools: the agent runs `node` commands in your project and reads its files.
This is third-party code. Review the repository files before installing.
What it does
The `es-toolkit` plugin from the `es-toolkit-plugin` marketplace installs two skills. `guide` picks installation and imports for the project's environment: it detects npm, Yarn, pnpm or Bun from the lockfile, accounts for Node.js, Deno and the browser, and warns about `import * as _`, which breaks tree-shaking. `migrate` converts lodash code and explains the difference between strict `es-toolkit` and the compatible `es-toolkit/compat`. Both skills first look at the package installed in the project: they locate its `package.json` through `require.resolve` and read `exports` and types. That way the agent checks whether a function exists at the right entry point instead of leaning on a remembered list. For each function `migrate` returns a before-and-after version, a documentation link and a table of behaviour differences.
Who it is for. People moving JavaScript and TypeScript projects off lodash or choosing utilities who want an agent's help in shrinking the bundle.
Good fit when
- A project pulls in lodash for a handful of functions and you are moving imports to es-toolkit.
- The agent picks the es-toolkit install command for Deno, Bun or a browser build.
- Before replacing `debounce` or `get`, you need to know how the strict API differs from `compat`.
- A blanket swap of lodash for `es-toolkit/compat` is set up through a bundler alias and you want a list of side effects.
- The code contains `import * as _` and you want tree-shaking back.
Not a fit when
- You do not use JavaScript or TypeScript: the plugin knows only this package.
- You need an exact figure for the size gain: the skill points to the official pages and stores no measurements.
- The task is developing es-toolkit itself: the repository has separate maintainer skills for that.
Example request
Replace the lodash imports in this project with es-toolkit: for each function show whether it lives in the strict API or in compat, and what changes in behaviour.Limitations
Plugin version 0.1.0 holds only `guide` and `migrate` and answers only about es-toolkit; general JavaScript utility questions are out of scope. The skills read the installed package and run `node` commands in the project, so they need access to `node_modules` and are allowed the Read, Grep, Glob and Bash tools. The skill gives no exact size or speed figures and points to the es-toolkit.dev pages. The marketplace install needs Claude Code, while other agents use `npx skills add`.
How to disable. In Claude Code disable or remove the `es-toolkit` plugin through `/plugin`. Delete skills installed through `npx skills` from the agent's skills directory.
FAQ
Which command connects the es-toolkit plugin?
Run `/plugin marketplace add toss/es-toolkit`, then `/plugin install es-toolkit@es-toolkit-plugin`. Other agents install the same skills with `npx skills add toss/es-toolkit`.
How does `es-toolkit` differ from `es-toolkit/compat`?
The strict `es-toolkit` gives a simplified API for common cases and may differ from lodash at the edges. `es-toolkit/compat` aims to pass lodash tests within a defined scope, but weighs more.
Why are `get` and `set` only in compat?
es-toolkit does not implement functions that modern JavaScript replaces, such as optional chaining `?.` or `Object.hasOwn()`. The `migrate` skill explains this for each such function.
How can I speed up a migration across hundreds of files?
The skill recommends three techniques: a bundler alias from `lodash` to `es-toolkit/compat`, the ESLint rule `no-restricted-imports` for leftovers, and a jscodeshift codemod for complex cases.
How do I install es-toolkit in Deno?
With `deno add jsr:@es-toolkit/es-toolkit`, keeping the `jsr:` prefix. In code the import path is `@es-toolkit/es-toolkit`, while npm projects use `es-toolkit`.
Discussion
No questions or reviews yet.
Related
PluginsA set of 116 skills, 44 agents and safety hooks for Claude Code, Cursor, Codex, Gemini CLI and nine more editors
Oxc migration skills for Oxlint and Oxfmt
Oxc migration skills
Two official Oxc skills: the agent moves a project from ESLint to the Oxlint linter and from Prettier or Biome to the Oxfmt formatter
Two skills for the tsdown bundler: setting up TypeScript library builds and migrating a project from tsup
AI Code Toolkit
aicode-toolkit
Plugins and MCP servers for coding agents: template-based projects, patterns before a file edit and review against YAML rules.
Official Effect skills that point the agent to the guide in node_modules and drive a project migration from version 3 to 4.
Shopify's official agent plugin: docs and API schema search, GraphQL and Liquid validation, and store management
README in short
The README calls es-toolkit a modern JavaScript utility library that is 2–3 times faster than lodash and up to 97 percent smaller. The AI section lists skill installation through `npx skills` and the Claude Code marketplace, and a link leads to the AI integration guide.