pilot-service-agents-packages

Retrieve package metadata from npm, PyPI, and Maven Central without downloading artifacts.

7|3|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/TeoSlayer/pilot-skills --skill pilot-service-agents-packages
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pilot-service-agents-packages
Source: https://github.com/TeoSlayer/pilot-skills/tree/main/skills/pilot-service-agents-packages
Command: npx skills add https://github.com/TeoSlayer/pilot-skills --skill pilot-service-agents-packages

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Retrieves package metadata from npm, PyPI, and Maven Central without downloading artifacts, helping teams verify versions, maintainers, and dependencies across registries.

Core Features & Use Cases

  • Discover package versions, maintainers, and dependencies across major registries without fetching artifacts.
  • List recent releases and updated metadata for a given package to inform upgrade decisions.
  • Compare cross-registry metadata to support release planning and dependency audits.

Quick Start

Ask the skill to fetch metadata for a package by name across npm, PyPI, or Maven Central.

Frequently Asked Questions about pilot-service-agents-packages

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I query npm package metadata without downloading the actual files?

You can query npm package metadata without downloading artifacts by using a tool that fetches registry data directly. This skill retrieves versions, maintainers, and dependencies for npm packages to support dependency audits and release planning.

Can I compare package versions across npm, PyPI, and Maven Central?

Yes, you can compare cross-registry metadata across npm, PyPI, and Maven Central. The skill retrieves and returns package metadata from all three registries to support cross-registry workflows and dependency verification.

What is the best way to check PyPI package release history for upgrade planning?

Checking PyPI package release history is best done by querying the registry metadata without downloading artifacts. This skill lists recent releases and updated metadata for a given package to inform your upgrade decisions.

Do I need a specific environment setup to query Maven Central metadata with this approach?

Querying Maven Central metadata with this approach requires the pilot-protocol core skill, pilotctl on PATH, a running daemon registered with the backbone, and a reachable list-agents directory agent on the overlay network.

Does querying package metadata this way download the actual dependencies to my local machine?

No, querying package metadata this way does not download the actual dependencies to your local machine. The skill finds and returns metadata for packages across npm, PyPI, and Maven Central without fetching the artifacts themselves.