sponsors

Sync GitHub Sponsors listings across README and website files using the GraphQL API.

611|63|Updated Sep 26, 2017
One-click install
npx skills add https://github.com/markuplint/markuplint --skill sponsors
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sponsors
Source: https://github.com/markuplint/markuplint/tree/main/.claude/skills/sponsors
Command: npx skills add https://github.com/markuplint/markuplint --skill sponsors

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeping sponsor listings consistent across multiple files is error-prone: the markuplint project displays GitHub Sponsors in four separate locations (two READMEs and two website pages), and manual updates often miss one file or misapply tier rules.

Core Features & Use Cases

  • Active Sponsor Fetching: Queries the GitHub GraphQL API via gh api graphql to retrieve current active sponsors, their avatars, and tier pricing.
  • Tier-Based Listing Rules: Applies tier incentives correctly — Corporate ($100/mo) and Personal ($10/mo) sponsors get README/website listings, while $5/mo Badge sponsors are excluded.
  • Synchronized Multi-File Updates: Updates all 4 listing files in sync, handles new sponsors, moves ended sponsors to Past sponsors, and reflects tier changes.
  • Use Case: Run a periodic check to detect that a sponsor downgraded from $10 to $5, then remove their avatar from the README and website while keeping listings consistent everywhere.

Quick Start

Check the current active GitHub Sponsors for the markuplint organization and update all four listing files to match.

Frequently Asked Questions about sponsors

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

FAQPage Schema
How do I list GitHub Sponsors on my project README?

Fetch active sponsors using the GitHub GraphQL API via `gh api graphql` with the sponsorshipsAsMaintainer query, then add sponsor avatars as `<img>` tags in the README. Match the markup style of existing entries, using larger widths for corporate sponsors.

How to fetch active GitHub Sponsors with the GraphQL API?

Use `gh api graphql` with a query on the organization's sponsorshipsAsMaintainer field with activeOnly set to true. The response includes each sponsor's login, name, avatarUrl, and tier monthly price in dollars.

Which GitHub Sponsors tiers should appear on the README?

In this project, Corporate ($100/mo) and Personal ($10/mo) tiers get README and website listings, while the $5/mo Badge tier receives only a GitHub badge and is not listed. Tier changes require adding or removing listings accordingly.

What happens when a GitHub sponsor ends their sponsorship?

Ended sponsors are removed from the active listings in all files. On the README the line is simply removed, while on the website the Profile component is removed and the sponsor's login link is added to the top of the Past sponsors list.

Why must sponsor listings be updated in multiple files at once?

The project displays sponsors in four locations: the root README, the package README, and the English and Japanese website community pages. Updating only one file causes inconsistent sponsor displays across the project.