菜单
Get npm package name suggestions and autocomplete from NPMS.io. Use when the user asks for package name suggestions, wants to autocomplete a package name, or search for packages by name pattern.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when the user needs help with path queries, JSON transformations, schema validation, or safe JSON editing workflows. Triggered by questions about JSON operations, data extraction, file merging, or validation strategies.
Scan project dependencies for known vulnerabilities. Automatically detect and parse package files (package.json, requirements.txt, Gemfile, go.mod, pom.xml) and check all dependencies against the CVE database. Use when you want to audit a project for security vulnerabilities, check if dependencies have known CVEs, or generate a vulnerability report for compliance.
Search for Common Vulnerabilities and Exposures (CVEs) by ID (e.g., CVE-2024-1086) or by product name (e.g., OpenSSL, Apache Tomcat). Get detailed vulnerability information including severity scores, affected software versions, and references. Use when the user wants to look up CVE information, check if a product has known vulnerabilities, or research security issues.
Validate a JSON file against the schema referenced in its $schema property. Use when the user asks to check JSON against its own schema, validate self-describing JSON, auto-validate JSON files, or verify JSON with embedded schema reference.
Validate JSON data against a JSON Schema. Use when the user asks to validate JSON against a schema, check if JSON conforms to a schema, test JSON data validity, or verify JSON structure matches a schema definition.
Validate that a JSON Schema is well-formed and conforms to the JSON Schema specification. Use when the user asks to check if a schema is valid, verify schema syntax, validate schema structure, or check a JSON Schema file for errors.
| name | npms-suggest |
| description | Get npm package name suggestions and autocomplete from NPMS.io. Use when the user asks for package name suggestions, wants to autocomplete a package name, or search for packages by name pattern. |
Get package name suggestions and autocomplete from NPMS.io based on a search query.
npx tsx scripts/suggest.ts <query> [options]
| Argument | Required | Description |
|---|---|---|
query | Yes | Search query (minimum 2 characters) |
| Option | Description |
|---|---|
--size=N | Number of suggestions to return (default: 25, max: 250) |
--no-cache | Bypass cache and fetch fresh data from API |
Suggestions for "react" (25 results)
------------------------------------
1. react
Score: 1000000
URL: https://www.npmjs.com/package/react
2. react-dom
Score: 950000
URL: https://www.npmjs.com/package/react-dom
3. react-redux
Score: 923000
URL: https://www.npmjs.com/package/react-redux
...
Top 10 suggestions:
react, react-dom, react-redux, react-router, react-scripts,
react-native, react-hook-form, react-query, react-test-renderer
npx tsx scripts/suggest.ts <query> [options]
Options:
--size=N - Number of suggestions to return (default: 25, max: 250)--no-cache - Bypass cache and fetch fresh data from APIRun from the npms-io plugin directory: ~/.claude/plugins/cache/npms-io/
GET https://api.npms.io/v2/search/suggestions?q={query}
| Parameter | Required | Description |
|---|---|---|
q | Yes | Search query (minimum 2 characters) |
Get suggestions:
https://api.npms.io/v2/search/suggestions?q=react
Scoped packages:
https://api.npms.io/v2/search/suggestions?q=@babel
The response contains an array of package suggestions:
[
{
"name": "react",
"score": 1000000,
"searchScore": 1000000
},
{
"name": "react-dom",
"score": 950000,
"searchScore": 950000
}
]
Fields:
name - Package namescore - Package quality score (higher is better)searchScore - Relevance to the search query (higher is better)@scope/ prefix to search within a scopeSuggestions are cached for 1 hour. The package registry changes relatively slowly, and suggestion results remain stable for reasonable periods.
Use the --no-cache flag to bypass the cache.
npms-analyze to analyze specific package qualitynpms-compare to compare multiple packagesnpm-search for full-text search by keyword and descriptionFind exact package name:
npx tsx scripts/suggest.ts react
Find packages starting with a prefix:
npx tsx scripts/suggest.ts react-
Search within a scope:
npx tsx scripts/suggest.ts @babel/
npx tsx scripts/suggest.ts @types/react
Find packages containing a term:
npx tsx scripts/suggest.ts express
npx tsx scripts/suggest.ts router
Discover packages when you know part of the name:
npx tsx scripts/suggest.ts redux
Implement autocomplete for package input:
npx tsx scripts/suggest.ts --size=10 reac
Find related packages by name pattern:
npx tsx scripts/suggest.ts router
Explore packages in a specific scope:
npx tsx scripts/suggest.ts @babel/
npx tsx scripts/suggest.ts @types/
- to find packages with specific prefixes@scope/ to browse scoped packagesnpms-analyze to review package quality before usingnpms-compare to evaluate multiple packages| Feature | npms-suggest | npm-search |
|---|---|---|
| Searches | Package names only | Names, descriptions, keywords |
| Speed | Very fast (name-only) | Slower (full-text) |
| Results | Name-based matches | Semantic matches |
| Best for | Autocomplete, name discovery | General package search |
npm-search