pilot-service-agents-dev

Run a discovery query against target repositories or registries to fetch public metadata from GitHub, Docker Hub, and crates.io, generating a consolidated report of repository health, popularity, and activity for quick ecosystem comparisons.

The best way to compare repository health across registries is to run a discovery query that surfaces stars, recent events, licenses, and maintainers. This generates a unified view of project popularity and activity for quick shortlisting across ecosystems.

Yes, fetching project metadata requires the pilot-protocol core skill, pilotctl on PATH, a running daemon registered with the backbone (Network 0), and access to the list-agents directory on the overlay to successfully execute discovery and evaluation tasks.

Yes, you can use this skill to surface dependency ecosystem insights and latest releases. It is scoped to discovery and evaluation tasks, fetching public metadata to provide a consolidated view of project health and recent repository events.

A limitation of automated discovery for evaluating registry metadata is that it is scoped strictly to public sources like GitHub and Docker Hub. It requires a registered daemon and overlay access, meaning it cannot fetch private repository data or operate in offline environments.