itechmeat/llm-code

deps-dev

deps.dev API v3 package metadata lookup.

First seen Feb 1, 2026

Installation

$ npx skills add itechmeat/llm-code --skill deps-dev

Summary

  • deps.dev API v3 package metadata lookup.
  • Covers version discovery, default/latest version, deprecation and project-status flags, resolved requirements/dependency graphs, URL encoding.
  • Use when querying package versions, checking latest releases, detecting deprecated versions, or looking up dependency metadata via the deps.dev API.
  • Keywords: deps.dev, api.deps.dev, package versions.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from itechmeat/llm-code · top by installs.

npx skills add itechmeat/llm-code

Browse all from itechmeat/llm-code

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 22
License LICENSE
Default branch master
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Version3
More metadata
version
3
release_date
2026-06-09

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,311 B
  • docs SUMMARY.md 400 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 55 installs

SKILL.md

deps.dev (Skill Router)

This file is intentionally introductory.

Open the right note under references/ based on what you need.

Start here (fast)

  • Need the latest/default version of a known package? Read: references/latest-version.md.
  • Handling huge version lists or truncated responses? Read: references/large-responses.md.
  • Not sure how to format/normalize package names per ecosystem? Read: references/naming-and-encoding.md.
  • Need endpoint shapes and fields to parse, including deprecation flags (isDeprecated/deprecatedReason), PyPI projectStatus, or resolved NuGet/Maven requirements? Read: references/api.md.

Primary recipe (one request)

Goal: given {system, packageName}, return the default/latest version.

If isDefault is missing for all versions, stop and ask for an explicit selection rule (e.g., include pre-releases or not) instead of guessing.

isDefault does not imply the version is safe to recommend: also check isDeprecated/deprecatedReason on that version (see references/api.md) before suggesting it.

Critical prohibitions

  • Do not guess the “latest” version by string sorting.
  • Do not output placeholder or “approximate” versions; always wait for API data.
  • Do not parse large JSON via grep or manual truncation; use a JSON parser (jq/Python/Node).
  • Do not silently fall back when isDefault is missing; ask for the desired rule.
  • Do not paste large verbatim chunks from docs; summarize.
  • Do not assume auth or rate limits; treat them as unspecified unless you have evidence.

Links