Contributor-First PR Merge
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
Say no as an open-source maintainer without burning contributors or yourself — the feature that doesn't fit, the PR that took someone a weekend but can't merge, the company that wants free support…
Install The Maintainers No
$ npx skills add mohitagw15856/pm-claude-skills --skill the-maintainers-no -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills the-maintainers-no --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/the-maintainers-no .claude/skills/the-maintainers-no && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "the-maintainers-no" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/the-maintainers-no into .claude/skills/the-maintainers-no/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "the-maintainers-no", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/the-maintainers-noType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill the-maintainers-no -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills the-maintainers-no --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/the-maintainers-no .agents/skills/the-maintainers-no && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "the-maintainers-no" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/the-maintainers-no into .agents/skills/the-maintainers-no/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "the-maintainers-no", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill the-maintainers-no -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills the-maintainers-no --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/the-maintainers-no .cursor/skills/the-maintainers-no && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "the-maintainers-no" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/the-maintainers-no into .cursor/skills/the-maintainers-no/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "the-maintainers-no", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/the-maintainers-no--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill the-maintainers-no -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills the-maintainers-no --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/the-maintainers-no .gemini/skills/the-maintainers-no && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "the-maintainers-no" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/the-maintainers-no into .gemini/skills/the-maintainers-no/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "the-maintainers-no", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills the-maintainers-noInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill the-maintainers-no -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/the-maintainers-no .github/skills/the-maintainers-no && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "the-maintainers-no" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/the-maintainers-no into .github/skills/the-maintainers-no/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "the-maintainers-no", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill the-maintainers-no -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills the-maintainers-no --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/the-maintainers-no .opencode/skills/the-maintainers-no && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "the-maintainers-no" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/the-maintainers-no into .opencode/skills/the-maintainers-no/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "the-maintainers-no", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
the-maintainers-no- GitHub stars
- 1.4k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 704 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Say no as an open-source maintainer without burning contributors or yourself — the feature that doesn't fit, the PR that took someone a weekend but can't merge, the company that wants free support…
- Works in 6 steps: Diagnose the no. Scope-no (doesn't fit… → Honor effort before delivering… → Show the vision line, not the mood.… → …
- A maintainer says how do I reject this PR nicely
- SKILL.md covers What This Skill Produces, Required Inputs, Framework and Output Format, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
The Maintainers No is an agent skill from mohitagw15856/pm-claude-skills. Say no as an open-source maintainer without burning contributors or yourself — the feature that doesn't fit, the PR that took someone a weekend but can't merge, the company that wants free support, the fork suggestion said kindly. Use when a maintainer says 'how do I reject this PR nicely', 'a company is demanding support', 'this feature request won't die', or is avoiding an issue thread out of guilt. Produces the specific no for the situation, with reasoning shown and the relationship kept.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Open source maintenance. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- A maintainer says how do I reject this PR nicely
- A company is demanding support
- This feature request wont die
- Is avoiding an issue thread out of guilt
Example prompts
- “t fit, the PR that took someone a weekend but can”
- “how do I reject this PR nicely”
- “a company is demanding support”
- “/the-maintainers-no”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Diagnose the no. Scope-no (doesn't fit what this project is) ·
- Honor effort before delivering direction. For PRs especially: name
- Show the vision line, not the mood. "This project deliberately stays
- Bless the fork sincerely. "This is exactly what forks are for — the
- For companies: name the exchange. Volunteer-maintained ≠ SLA. The
- Close the loop physically. The no ends with the issue's fate
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
The Maintainers No loads about 1.4k tokens when it runs. Until then it costs about 129 tokens; SKILL.md has 704 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 704 words, ~1,450 tokens.
Download SKILL.mdSave it as
.claude/skills/the-maintainers-no/SKILL.md (or your agent's skills folder).- name
- the-maintainers-no
- description
- Say no as an open-source maintainer without burning contributors or yourself — the feature that doesn't fit, the PR that took someone a weekend but can't merge, the company that wants free support, the fork suggestion said kindly. Use when a maintainer says 'how do I reject this PR nicely', 'a company is demanding support', 'this feature request won't die', or is avoiding an issue thread out of guilt. Produces the specific no for the situation, with reasoning shown and the relationship kept.
The Maintainer's No Skill
Maintainer burnout is mostly unsent nos: the feature request at 40 comments, the well-meant PR that would triple the maintenance surface, the company that filed "urgent" on a volunteer's project. Every avoided no costs a week of low-grade guilt; the sent no costs five minutes and is almost never received as badly as feared. This skill writes the specific no each situation needs — with the reasoning shown, the effort honored, and a real alternative where one exists — because "no with a why and a path" keeps contributors that "maybe someday" quietly loses.
What This Skill Produces
- The situation-fit no, drafted ready to post: scope-no, PR-no, support-no, urgency-no, or the fork blessing
- The reasoning paragraph: the project-vision line that makes this no consistent instead of personal (and reusable next time)
- An alternative that's real: plugin/extension point, the fork blessing, a linked workaround, a paid-support pointer if one exists — or nothing, stated honestly, if nothing exists
- A policy line worth adding to CONTRIBUTING/README so the next no is half-written
Required Inputs
Ask for (if not already provided):
- The thread/PR/request text, and how long it's been festering
- The real reason it's a no (doesn't fit vision? maintenance cost? just don't want to? — all valid; the phrasing differs)
- Who's asking: first-timer, regular contributor, company, drive-by
- What the maintainer could genuinely offer, if anything (review a smaller PR? accept behind a flag? nothing?)
Framework
- Diagnose the no. Scope-no (doesn't fit what this project is) · cost-no (fits, but the maintenance is forever and it's mine) · PR-no (effort real, direction wrong) · support-no (this is unpaid volunteer time being invoiced) · capacity-no (fits, but not this year — the only no that may honestly become "someday").
- Honor effort before delivering direction. For PRs especially: name something genuinely good in it first (one specific thing, not flattery). The order is: thanks-with-specifics → the no with the why → the path if real. Skipping straight to the no is efficient and expensive.
- Show the vision line, not the mood. "This project deliberately stays [small/zero-dep/single-purpose]; features like X belong in [plugins/forks/other tools]" — a no anchored to a stated principle generalizes; a no anchored to today's energy invites relitigation. If the principle isn't written anywhere yet, this is the moment: the skill drafts the CONTRIBUTING line.
- Bless the fork sincerely. "This is exactly what forks are for — the license means you don't need my permission, and I mean that as an invitation, not a brush-off" defuses more standoffs than any other sentence in open source.
- For companies: name the exchange. Volunteer-maintained ≠ SLA. The reply states what's available free (the issue queue, at volunteer pace), what isn't (deadlines, priority), and — if the maintainer wants it — the paid path ("sponsorship/support contract gets your issue a scheduled slot"). No apology anywhere in it.
- Close the loop physically. The no ends with the issue's fate: closed-wontfix, converted to discussion, or left open behind a named condition. A no that leaves the thread open re-accrues the guilt.
Show full SKILL.md (208 more words)Show less
Output Format
## Diagnosis
[Which no this is, and the real reason in one honest line]
## The reply (ready to post)
[Thanks-with-specifics → the no with the vision line → the real path or
honest nothing → the thread's fate]
## Add to CONTRIBUTING (so the next one is half-written)
[The policy line this no just established]
## If they push back
[The one-paragraph second reply — same decision, warmer, final]Quality Checks
- The no is unambiguous — a reader cannot mistake it for maybe
- Effort is honored with a specific, true observation, not a compliment template
- The reasoning cites a project principle that will still be true next month
- Any offered alternative is real — no "PR welcome" unless a PR would genuinely merge
- The thread's fate is stated (closed / converted / condition), and the pushback reply doesn't reopen the decision
Anti-Patterns
- Do not soften into ambiguity — "maybe down the road" costs you this conversation again in six months, with interest
- Do not apologize for the project's boundaries; gratitude yes, apology no
- Do not match a demanding tone — the calm no in a heated thread is read by every future contributor, not just this one
- Do not invent roadmap promises to escape the moment
- Do not skip the fork blessing out of possessiveness — the license already said yes; saying it warmly is free
Related
[[maintainer-triage]] — the system that catches these before they fester; [[saying-no-kindly]] — the general craft; [[first-maintainer-month]] for setting the boundaries early enough that nos stay rare.
Example Trigger Phrases
- "How do I reject this PR nicely?"
- "Say no to this feature request."
- "A company wants free support from my project."
- "Suggest a fork without burning the contributor."
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/the-maintainers-no of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
The Maintainers No next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| The Maintainers No this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Contributor-First PR MergeHKUDS/OpenHarness | 16k | 1 repos | ~847 | Automated safety check: Pass | MIT | |
| Mole Release Notes Publishertw93/Mole | 70k | — | ~1.9k | Automated safety check: Pass | GPL-3.0 | |
| Chatbox Pro Cherry-Pick Syncchatboxai/chatbox | 42k | — | ~1.2k | Automated safety check: Pass | GPL-3.0 | |
| Pre-Release PR Triagejamiepine/voicebox | 57k | — | ~3.1k | Automated safety check: Pass | MIT | |
| WinAppSDK Triage Meeting Prepmicrosoft/WindowsAppSDK | 4.7k | — | ~2.8k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Mole Release Notes Publisher
tw93/Mole
Publishes curated, bilingual release notes for an existing Mole version tag with gh release edit, including contributor thanks and reactions, after the release workflow finishes.
Chatbox Pro Cherry-Pick Sync
chatboxai/chatbox
Cherry-picks commits from the chatbox-pro repo into the open chatbox repo, skipping mobile-only files and keeping the open package name.
Pre-Release PR Triage
jamiepine/voicebox
Sorts a backlog of open pull requests into must-merge, candidate, superseded and deferred, writes a triage doc and works the merge loop before a release.
- Official
WinAppSDK Triage Meeting Prep
microsoft/WindowsAppSDK
Prepares the triage meeting summary for WinAppSDK Needs-Triage issues, with research-backed area suggestions, draft replies and a diff since the last triage.
React Router PR Finish Line
remix-run/react-router
Takes a blocked community pull request in React Router and adds the missing tests, change file or docs so it can merge, working on the contributor's branch.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Categories
Questions about The Maintainers No
What does The Maintainers No do?
Say no as an open-source maintainer without burning contributors or yourself — the feature that doesn't fit, the PR that took someone a weekend but can't merge, the company that wants free support…. The Maintainers No is an agent skill from mohitagw15856/pm-claude-skills. Say no as an open-source maintainer without burning contributors or yourself — the feature that doesn't fit, the PR that took someone a weekend but can't merge, the company that wants free support, the fork suggestion said kindly.
When should I use The Maintainers No?
The Maintainers No fits situations like: A maintainer says how do I reject this PR nicely; A company is demanding support; this feature request wont die; is avoiding an issue thread out of guilt.
How do I install The Maintainers No in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill the-maintainers-no -a claude-code`. Or copy the skill folder (skills/the-maintainers-no in mohitagw15856/pm-claude-skills) into .claude/skills/the-maintainers-no in your project. Claude Code loads it when a task matches its description.
How do I install The Maintainers No in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill the-maintainers-no -a codex`. Or copy the skill folder (skills/the-maintainers-no in mohitagw15856/pm-claude-skills) into .agents/skills/the-maintainers-no in your project. Codex loads it when a task matches its description.
Can I use The Maintainers No in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill the-maintainers-no -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/the-maintainers-no, .gemini/skills/the-maintainers-no, .github/skills/the-maintainers-no and .opencode/skills/the-maintainers-no in your project.
What does The Maintainers No need to run?
SKILL.md names no scripts, command-line tools or credentials: The Maintainers No is instructions for the agent only.
Does The Maintainers No access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is The Maintainers No safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does The Maintainers No use?
The Maintainers No is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does The Maintainers No use?
About 1.4k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to The Maintainers No?
Skills that share tags, products or a category with The Maintainers No: Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Mole Release Notes Publisher (tw93/Mole, 70k stars), Chatbox Pro Cherry-Pick Sync (chatboxai/chatbox, 42k stars) and Pre-Release PR Triage (jamiepine/voicebox, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains The Maintainers No?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.