deps-dev▌
trancong12102/agentskills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
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.
Latest Package Version Lookup
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.
Supported Ecosystems
| 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 |
When to Use
- Adding a new dependency and need the current version
- Updating
package.json,requirements.txt,Cargo.toml, etc. to latest - Checking whether a package has been deprecated
- Comparing versions across multiple packages at once
When NOT to Use
- Private or internal packages (deps.dev only indexes public registries)
- Looking up documentation or usage examples (use
context7instead)
Workflow
DO NOT read script source code. Run scripts directly and use --help for usage.
-
Identify the ecosystem from project files:
package.jsonornode_modules→ npmrequirements.txt,pyproject.toml,setup.py→ pypigo.mod,go.sum→ goCargo.toml→ cargopom.xml,build.gradle→ maven*.csproj,packages.config→ nuget
-
Run the script:
python3 scripts/get-versions.py <system> <pkg1> [pkg2] ...
Run python3 scripts/get-versions.py --help if unsure about usage.
Examples
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
Output Format
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>.
Rules
- Use the script instead of manual curl — it handles URL encoding (especially for scoped npm packages like
@types/node) and fetches multiple packages in parallel, so it's both easier and faster. - Flag deprecated packages — if the status column says
deprecated, tell the user and suggest an alternative if you know one. - Batch lookups when possible — the script accepts multiple package names in one call, which is faster than running it once per package.
How to use deps-dev on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add deps-dev
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches deps-dev from GitHub repository trancong12102/agentskills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate deps-dev. Access the skill through slash commands (e.g., /deps-dev) or your agent's skill management interface.
Security & Verification Notice
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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
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
Competitive Analysis
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
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
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
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ 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.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.5★★★★★34 reviews- ★★★★★Chaitanya Patil· Dec 24, 2024
Useful defaults in deps-dev — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Hana Gill· Dec 20, 2024
deps-dev has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Dev Kapoor· Dec 12, 2024
I recommend deps-dev for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Valentina Torres· Dec 8, 2024
Useful defaults in deps-dev — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★William Wang· Nov 27, 2024
deps-dev has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Piyush G· Nov 15, 2024
deps-dev has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Chinedu Park· Nov 11, 2024
Useful defaults in deps-dev — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Hana Ghosh· Nov 3, 2024
Solid pick for teams standardizing on skills: deps-dev is focused, and the summary matches what you get after install.
- ★★★★★Arya Choi· Oct 22, 2024
deps-dev has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Valentina Jain· Oct 18, 2024
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