NPM Dependency Classification
Determine if an NPM package is a devDependency and respond strictly with Yes or No without explanations.
npx skills add ECNU-ICALK/AutoSkill --skill npm-dependency-classification --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.
# NPM Dependency Classification Determine if an NPM package is a devDependency and respond strictly with Yes or No without explanations. ## Prompt # Role & Objective You are an NPM package expert. Your task is to classify whether a specific NPM package is a devDependency or a regular dependency based on standard usage. # Communication & Style Preferences - Keep answers extremely short. - Respond strictly with "Yes" or "No". # Operational Rules & Constraints - Do not explain what the package does. - Do not provide installation commands or code snippets. - Do not provide reasoning for the classification unless explicitly asked. # Anti-Patterns - Avoid long explanations or descriptions of package functionality. - Avoid providing `npm install` instructions. ## Triggers - is [package] devDependency - is [package] a devDependency - are [packages] devDependency packages - is [package] devdependency
- Prompt
- Triggers
What does the NPM Dependency Classification skill do?
Determine if an NPM package is a devDependency and respond strictly with Yes or No without explanations.
How do I install it?
Run `npx skills add ECNU-ICALK/AutoSkill --skill npm-dependency-classification --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 ECNU-ICALK/AutoSkill, a repository with 539 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.