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.
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
Anti-Patterns
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."
1---2name: the-maintainers-no-23description: "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."4disable-model-invocation: true # skill-optimizer5metadata:6 source: https://skillmd.com/skills/slipcast-dev/the-maintainers-no-27---89# The Maintainer's No Skill1011Maintainer burnout is mostly unsent nos: the feature request at 40 comments,12the well-meant PR that would triple the maintenance surface, the company13that filed "urgent" on a volunteer's project. Every avoided no costs a14week of low-grade guilt; the sent no costs five minutes and is almost never15received as badly as feared. This skill writes the *specific* no each16situation needs — with the reasoning shown, the effort honored, and a real17alternative where one exists — because "no with a why and a path" keeps18contributors that "maybe someday" quietly loses.1920## What This Skill Produces2122- The **situation-fit no**, drafted ready to post: scope-no, PR-no,23 support-no, urgency-no, or the fork blessing24- The **reasoning paragraph**: the project-vision line that makes this no25 consistent instead of personal (and reusable next time)26- An **alternative that's real**: plugin/extension point, the fork blessing,27 a linked workaround, a paid-support pointer if one exists — or nothing,28 stated honestly, if nothing exists29- A **policy line** worth adding to CONTRIBUTING/README so the next no is30 half-written3132## Required Inputs3334Ask for (if not already provided):35- The thread/PR/request text, and how long it's been festering36- The real reason it's a no (doesn't fit vision? maintenance cost? just37 don't want to? — all valid; the phrasing differs)38- Who's asking: first-timer, regular contributor, company, drive-by39- What the maintainer could genuinely offer, if anything (review a smaller40 PR? accept behind a flag? nothing?)4142## Framework43441. **Diagnose the no.** Scope-no (doesn't fit what this project is) ·45 cost-no (fits, but the maintenance is forever and it's mine) · PR-no46 (effort real, direction wrong) · support-no (this is unpaid volunteer47 time being invoiced) · capacity-no (fits, but not this year — the only48 no that may honestly become "someday").492. **Honor effort before delivering direction.** For PRs especially: name50 something genuinely good in it first (one specific thing, not flattery).51 The order is: thanks-with-specifics → the no with the why → the path if52 real. Skipping straight to the no is efficient and expensive.533. **Show the vision line, not the mood.** "This project deliberately stays54 [small/zero-dep/single-purpose]; features like X belong in55 [plugins/forks/other tools]" — a no anchored to a stated principle56 generalizes; a no anchored to today's energy invites relitigation.57 If the principle isn't written anywhere yet, this is the moment: the58 skill drafts the CONTRIBUTING line.594. **Bless the fork sincerely.** "This is exactly what forks are for — the60 license means you don't need my permission, and I mean that as an61 invitation, not a brush-off" defuses more standoffs than any other62 sentence in open source.635. **For companies: name the exchange.** Volunteer-maintained ≠ SLA. The64 reply states what's available free (the issue queue, at volunteer pace),65 what isn't (deadlines, priority), and — if the maintainer wants it —66 the paid path ("sponsorship/support contract gets your issue a67 scheduled slot"). No apology anywhere in it.686. **Close the loop physically.** The no ends with the issue's fate:69 closed-wontfix, converted to discussion, or left open behind a named70 condition. A no that leaves the thread open re-accrues the guilt.7172## Output Format7374```75## Diagnosis76[Which no this is, and the real reason in one honest line]7778## The reply (ready to post)79[Thanks-with-specifics → the no with the vision line → the real path or80honest nothing → the thread's fate]8182## Add to CONTRIBUTING (so the next one is half-written)83[The policy line this no just established]8485## If they push back86[The one-paragraph second reply — same decision, warmer, final]87```8889## Quality Checks9091- [ ] The no is unambiguous — a reader cannot mistake it for maybe92- [ ] Effort is honored with a specific, true observation, not a compliment93 template94- [ ] The reasoning cites a project principle that will still be true next95 month96- [ ] Any offered alternative is real — no "PR welcome" unless a PR would97 genuinely merge98- [ ] The thread's fate is stated (closed / converted / condition), and the99 pushback reply doesn't reopen the decision100101## Anti-Patterns102103- [ ] Do not soften into ambiguity — "maybe down the road" costs you this104 conversation again in six months, with interest105- [ ] Do not apologize for the project's boundaries; gratitude yes,106 apology no107- [ ] Do not match a demanding tone — the calm no in a heated thread is108 read by every future contributor, not just this one109- [ ] Do not invent roadmap promises to escape the moment110- [ ] Do not skip the fork blessing out of possessiveness — the license111 already said yes; saying it warmly is free112113## Related114115[[maintainer-triage]] — the system that catches these before they fester;116[[saying-no-kindly]] — the general craft; [[first-maintainer-month]] for117setting the boundaries early enough that nos stay rare.118119## Example Trigger Phrases120121- "How do I reject this PR nicely?"122- "Say no to this feature request."123- "A company wants free support from my project."124- "Suggest a fork without burning the contributor."