Query the deps.dev API to get the latest stable version of open-source packages. This is faster and more reliable than searching the web or guessing version numbers, and it catches deprecated packages before you install them.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiondeps-devExecute the skills CLI command in your project's root directory to begin installation:
Fetches deps-dev from trancong12102/agentskills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate deps-dev. Access via /deps-dev in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
3
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
3
stars
Query the deps.dev API to get the latest stable version of open-source packages. This is faster and more reliable than searching the web or guessing version numbers, and it catches deprecated packages before you install them.
| Ecosystem | System ID | Example Package |
|---|---|---|
| npm | npm |
express, @types/node |
| PyPI | pypi |
requests, django |
| Go | go |
github.com/gin-gonic/gin |
| Cargo | cargo |
serde, tokio |
| Maven | maven |
org.springframework:spring-core |
| NuGet | nuget |
Newtonsoft.Json |
package.json, requirements.txt, Cargo.toml, etc. to latestcontext7 instead)DO NOT read script source code. Run scripts directly and use --help for usage.
Identify the ecosystem from project files:
package.json or node_modules → npmrequirements.txt, pyproject.toml, setup.py → pypigo.mod, go.sum → goCargo.toml → cargopom.xml, build.gradle → maven*.csproj, packages.config → nugetRun the script:
python3 scripts/get-versions.py <system> <pkg1> [pkg2] ...
Run python3 scripts/get-versions.py --help if unsure about usage.
python3 scripts/get-versions.py npm express lodash @types/node
python3 scripts/get-versions.py pypi requests django flask
python3 scripts/get-versions.py go github.com/gin-gonic/gin
TSV with header. One line per package:
package version published status
express 5.0.0 2024-09-10 ok
lodash 4.17.21 2021-02-20 ok
Status values: ok, deprecated, not found, error: <detail>.
@types/node) and fetches multiple packages in parallel, so it's both easier and faster.deprecated, tell the user and suggest an alternative if you know one.Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
Useful defaults in deps-dev — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
deps-dev has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend deps-dev for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in deps-dev — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
deps-dev has been reliable in day-to-day use. Documentation quality is above average for community skills.
deps-dev has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in deps-dev — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: deps-dev is focused, and the summary matches what you get after install.
deps-dev has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: deps-dev is focused, and the summary matches what you get after install.
showing 1-10 of 34