Skip to content
Skill

Sponsor finder

Find which of a GitHub repository's dependencies are sponsorable via GitHub Sponsors

Install
Scripts
None
Platforms
Claude Code, Codex, Cursor
GitHub stars
41.3K
Last commit
1 day ago
License
MIT
Listing updated
today

When your agent uses it

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").

From the skill's SKILL.md. Your agent reads this description to decide when to load the skill.

What it can access

From a static check of its 1 file (12 KB) on GitHub on 17 November 2026. Nothing was run. Read the files before you install a skill: it can tell your agent to run anything its tools allow.

Install

Copy the skill folder to ~/.claude/skills/sponsor-finder to use it in all your projects:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/github/awesome-copilot.git "$tmp" &&
mkdir -p ~/.claude/skills &&
rm -rf ~/.claude/skills/sponsor-finder &&
cp -R "$tmp/skills/sponsor-finder" ~/.claude/skills/sponsor-finder &&
rm -rf "$tmp"

For one project only, put the folder in .claude/skills/sponsor-finder inside it instead.

Claude Code docs on skills

Copy the skill folder to ~/.agents/skills/sponsor-finder to use it in every repository:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/github/awesome-copilot.git "$tmp" &&
mkdir -p ~/.agents/skills &&
rm -rf ~/.agents/skills/sponsor-finder &&
cp -R "$tmp/skills/sponsor-finder" ~/.agents/skills/sponsor-finder &&
rm -rf "$tmp"

For one repository only, put the folder in .agents/skills/sponsor-finder inside it instead.

Codex docs on skills

Copy the skill folder to ~/.cursor/skills/sponsor-finder to use it in every project:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/github/awesome-copilot.git "$tmp" &&
mkdir -p ~/.cursor/skills &&
rm -rf ~/.cursor/skills/sponsor-finder &&
cp -R "$tmp/skills/sponsor-finder" ~/.cursor/skills/sponsor-finder &&
rm -rf "$tmp"

For one project only, put the folder in .cursor/skills/sponsor-finder inside it instead.

Cursor docs on skills

Run in a terminal (add --scope workspace to install it for the current workspace only):

gemini skills install https://github.com/github/awesome-copilot.git --path skills/sponsor-finder

Or copy the folder to ~/.gemini/skills/sponsor-finder yourself.

Gemini CLI docs on skills

For GitHub Copilot in VS Code, copy the skill folder to ~/.copilot/skills/sponsor-finder:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/github/awesome-copilot.git "$tmp" &&
mkdir -p ~/.copilot/skills &&
rm -rf ~/.copilot/skills/sponsor-finder &&
cp -R "$tmp/skills/sponsor-finder" ~/.copilot/skills/sponsor-finder &&
rm -rf "$tmp"

For one project only, put the folder in .github/skills/sponsor-finder inside it instead.

VS Code docs on skills

Get the folder:

git clone --depth 1 https://github.com/github/awesome-copilot.git

Then copy awesome-copilot/skills/sponsor-finder into your agent's skills folder as sponsor-finder. Agents that support SKILL.md read one folder per skill.

The SKILL.md format

Sponsor finder FAQ

How do I install Sponsor finder in Claude Code?

Copy the skill folder from GitHub to ~/.claude/skills/sponsor-finder to use it in all your projects, or to .claude/skills/sponsor-finder in one project.

Does Sponsor finder run scripts?

No. It is instructions only, with no scripts. This comes from a static check of the files on GitHub; nothing was run. Read the files before you install it.

Which AI agents can use Sponsor finder?

Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose. Each reads skills in the SKILL.md format from its own folder; the install steps on this page list them.

What are the best alternatives to Sponsor finder?

The closest alternatives to Sponsor finder are Rea changelog update, Code review, Gem devops guidelines, PR screenshots and Make repo contribution.

More from github/awesome-copilot

  1. Design or review infrastructure, deployment, CI/CD, Docker, Kubernetes, health checks, rollback, feature flags, production readiness, and mo

    • Open source
    • 41.3K GitHub stars
    • Cloud and infrastructure
  2. Stop coding agents from shipping generic UI

    • Open source
    • 41.3K GitHub stars
  3. Cross-references C# Web API controllers/DTOs against their TypeScript/JavaScript consumers (React, Angular, Vue, Svelte, Node.js, or hand-wr

    • Open source
    • 41.3K GitHub stars
  4. Serves as a reviewer of the codebase with instructions on looking for Apple App Store optimizations or rejection reasons.

    • Open source
    • 41.3K GitHub stars
  5. Triage and resolve Arch Linux issues with pacman, systemd, and rolling-release best practices.

    • Open source
    • 41.3K GitHub stars

Alternatives to Sponsor finder

  1. Prepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Ple

    • Open source
    • 465K GitHub stars
    • Developer tools
  2. Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's docu

    • Open source
    • 326K GitHub stars
    • Developer tools
  3. Design or review infrastructure, deployment, CI/CD, Docker, Kubernetes, health checks, rollback, feature flags, production readiness, and mo

    • Open source
    • 41.3K GitHub stars
    • Cloud and infrastructure
  4. Embed before/after screenshots and annotated images in pull request descriptions

    • Open source
    • 41.3K GitHub stars
    • Developer tools
  5. All changes to code must follow the guidance documented in the repository

    • Open source
    • 41.3K GitHub stars
    • Developer tools