Add sponsor-finder skill

[ashleywolf]

Sponsor Finder Skill

Teaches Copilot how to scan a GitHub repo's dependencies and find which ones accept sponsorship via GitHub Sponsors, Open Collective, Ko-fi, etc.

How it works

Users ask naturally: "find sponsorable dependencies in expressjs/express"

The skill teaches Copilot to:

1. Fetch package.json from the target repo
2. Resolve each dependency to its source GitHub repo via the npm registry
3. Check the npm funding field + .github/FUNDING.yml for sponsorship info
4. Group results by funding destination and present a report with direct sponsor links

Test results (expressjs/express)

• 28 dependencies found
• 9 have funding info (32%)
• 3 unique funding destinations:
  • 🟠 Open Collective: express (7 deps)
  • 💜 ljharb via GitHub Sponsors (1 dep)
  • 💜 sindresorhus via GitHub Sponsors (1 dep)

Files changed

• skills/sponsor-finder/SKILL.md — new skill
• docs/README.skills.md — added to skills table

Use cases

• OSPO teams evaluating which dependencies to sponsor
• Building a sponsorship strategy for an org
• Auditing dependency funding coverage

No bundled assets, no external dependencies — just a SKILL.md that uses get_file_contents and web_fetch.

[Copilot]

Pull request overview

Adds a new Agent Skill (“sponsor-finder”) that guides Copilot through identifying funding/sponsorship options for a repository’s dependencies (primarily Node/npm), and indexes the skill in the skills catalog.

Changes:

• Added skills/sponsor-finder/SKILL.md defining the sponsor-finding workflow (npm registry + FUNDING.yml checks) and report format.
• Updated docs/README.skills.md to include the new skill in the skills table.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.

File	Description
skills/sponsor-finder/SKILL.md	New skill definition for scanning dependency manifests and producing a funding report.
docs/README.skills.md	Adds “sponsor-finder” to the skills index table for discoverability.

Comments suppressed due to low confidence (1)

skills/sponsor-finder/SKILL.md:139

• Step 6 says to group by GitHub Sponsors username from FUNDING.yml, but earlier steps explicitly treat npm funding URLs (including Open Collective, Ko-fi, etc.) as a primary source, and the output format includes non-GitHub destinations. As written, dependencies that only have npm funding (or non-GitHub FUNDING.yml entries) won’t fit the grouping logic. Please define grouping in terms of a normalized “funding destination” (platform + identifier/URL), not only GitHub Sponsors usernames.

## Step 6: Group by Maintainer

After checking all repos, group sponsorable dependencies by their GitHub Sponsors username (from the `github` field in FUNDING.yml).

For each maintainer, track:
- Their GitHub Sponsors URL
- How many dependencies they maintain (from this repo's dependency tree)
- The names of those dependencies

Sort maintainers by **number of dependencies** (most impact first).