How do I install the Update Sponsor skill?

Run npx skillmds@latest add hathach/update-sponsor in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Update Sponsor safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Update Sponsor?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Update Sponsor free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Update Sponsor?

hathach (@hathach) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Update Sponsor by hathach — Agent Skill

Name: Update Sponsor
Author: hathach

Update Sponsor

Use when a GitHub sponsor joins, upgrades, cancels, or switches between public and private; when the README sponsor sections are stale or show "be the first!" despite active sponsors; or when new issues, PRs, or discussions still need sponsor, priority, or Adafruit triage labels.

hathach Updated Sep 17, 2026

File contents

Update Sponsors

Rewrite README.rst's sponsor blocks and backfill triage labels from live GitHub Sponsors data.

S=.claude/skills/update-sponsor/update_sponsor.py
python3 $S --rules      # tier -> README section -> labels, and the privacy rules
python3 $S --help       # flags
python3 $S --dry-run    # preview; every run previews and asks before applying

Run from the repo root as hathach — the script refuses any other account, whose sponsors are not the ones this README lists. Hand-edited data lives in config.json, documented in that file.

Agents: the confirmation prompt needs a terminal and a tool-call shell has none, so the script refuses to apply rather than guessing. Run --dry-run, show the maintainer the preview, get their answer, then re-run with --yes. Never --yes on the first call — the preview is the point. Applying dirties tracked files (README.rst, sometimes tools/codespell/ignore-words.txt); leave them unstaged for the maintainer, as make-release does.

.github/workflows/labeler.yml owns the label rules. It applies the same labels when a ticket is opened; this script only backfills what that workflow cannot reach — tickets older than it, and private sponsors its GITHUB_TOKEN cannot see. Changing the policy means changing both.

Frequently asked questions