Agent skill · data analytics · github
sponsor-finder
Find which of a GitHub repository's dependencies are sponsorable via GitHub Sponsors. Uses deps.dev API for dependency resolution across npm, PyPI, Cargo, Go, RubyGems, Maven, and NuGet. Checks npm funding metadata, FUNDING.yml files, and web search. Verifies every link. Shows direct and transitive dependencies with OSSF Scorecard health data. Invoke with /sponsor followed by a GitHub owner/repo (e.g. "/sponsor expressjs/express").
Why this skill is useful
Adds specific API commands and workflows for resolving dependencies across multiple ecosystems that the AI wouldn't reliably generate on its own.
What it needs
Requires curl installed locally. Requires deps.dev account access. About 7k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
Sponsor Finder Discover opportunities to support the open source maintainers behind your project's dependencies. Accepts a GitHub owner/repo (e.g. /sponsor expressjs/express), uses the deps.dev API for dependency resolution and project health data, and produces a friendly sponsorship report covering both direct and transitive dependencies. Your Workflow When the user types /sponsor {owner/repo} or provides a repository in owner/repo format: 1. Parse the input — Extract owner and repo. 2. Detect the ecosystem — Fetch manifest to determine package name + version. 3. Get full dependency tree — deps.dev GetDependencies (one call). 4. Resolve repos — deps.dev GetVersion for each dep → relatedProjects gives GitHub repo. 5. Get project health — deps.dev GetProject for unique repos → OSSF Scorecard. 6. Find funding links — npm funding field, FUNDING.yml, web search fallback. 7. Verify every link — fetch each URL to confirm it's live. 8. Group and report — by funding destination, sorted by impact. --- Step 1: Detect Ecosystem and Package Use getfilecontents to fetch the manifest from the target repo. Determine the ecosystem and extract the package name + latest version: File Ecosystem Package name from Version from ------ ----------- ------------------- -------------- package.json NPM name field version field requirements.txt PYPI list of package names use latest (omit version in deps.dev call) pyproject.toml PYPI [project.dependencies] use latest Cargo.toml CARGO [package] name [package] version go.mod GO module path extract from go.mod Gemfile RUBYGEMS gem names use latest pom.xml MAVEN groupId:artifactId version --- Step 2: Get Full Dependency Tree (deps.dev) This is the key step. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/sponsor-finder