New: Earn 20% as an AgentAlley affiliate. Share your link and earn on every sale you refer. Join now New: Earn 20% as an affiliate. Join now

Decline requests without damaging relationships

Saying No Kindly Skill

by mohitagw15856 · MIT license · ★ 1,395 on GitHub · updated Sep 23

Saying No Kindly Skill cover

Decline requests without damaging relationships or your standing — the fast-clear-warm formula, the alternative-attached no, the no-to-the-boss version (tradeoffs, not refusal), and scripts for the asks that recur. Use when asked how do…

---
name: saying-no-kindly
description: "Decline requests without damaging relationships or your standing — the fast-clear-warm formula, the alternative-attached no, the no-to-the-boss version (tradeoffs, not refusal), and scripts for the asks that recur. Use when asked how do I say no to this, turn down a request, decline extra work politely, I say yes to everything and drown, push back on my manager, or protect the roadmap from a pet feature. Produces the decline scripts by relationship, the tradeoff framing, and the exact wording tuned to who is asking."
---

# Saying No Kindly Skill

Chronic yes is a scheduling decision made by fear — each yes reasonable, the sum unworkable, and the real casualties are the commitments already made (every new yes quietly taxes them). The working no is *fast* (a slow no wastes the asker's planning time and reads worse than the decline itself), *clear* (soft-nos — "maybe later," "let me think" — are heard as yes-pending and return with interest), and *warm* (the relationship is preserved by tone and alternatives, not by capitulation). Upward, the form changes entirely: nos to the boss are *tradeoff conversations* — "yes is available; here's what it displaces; you pick."

## What This Skill Produces

- **The scripts** — the decline by relationship (peer, report, boss, external), each fast-clear-warm
- **The alternative menu** — the smaller yes, the later yes, the redirect, the resource — attached where honest
- **The upward version** — the tradeoff frame that converts refusal into prioritization the boss owns
- **The yes-audit** — the current commitments reviewed for the over-capacity that made no necessary ([task-triage-matrix](../task-triage-matrix/SKILL.md) supplies the evidence)

## Required Inputs

Overview

Chronic yes is a scheduling decision made by fear — each yes reasonable, the sum unworkable, and the real casualties are the commitments already made (every new yes quietly taxes them). The working no is fast (a slow no wastes the asker's planning time and reads worse than the decline itself), clear (soft-nos — "maybe later," "let me think" — are heard as yes-pending and return with interest), and warm (the relationship is preserved by tone and alternatives, not by capitulation). Upward, the form changes entirely: nos to the boss are tradeoff conversations — "yes is available; here's what it displaces; you pick."

Manual install (npx, ZIP)
Claude Codenpx skills add mohitagw15856/pm-claude-skills --skill saying-no-kindly -g -a claude-code
Claude Code (manual)mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/mohitagw15856/pm-claude-skills/tar.gz/f6ca79348c55 \ | tar -xz -C ~/.claude/skills --strip-components=2 pm-claude-skills-f6ca79348c55/skills/saying-no-kindly
Windows (PowerShell)New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/8778b111818bd76d3836/saying-no-kindly.zip" -OutFile "$env:TEMP\saying-no-kindly.zip"; Expand-Archive "$env:TEMP\saying-no-kindly.zip" -DestinationPath "$HOME\.claude\skills" -Force
Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md5.5 KB
Read the files here
mohitagw15856/f6ca7931 file
Shared references4SKILL.md reads these from elsewhere in the repo. Not in the ZIP.Get them on GitHub ↗
SKILL.md
Show the full text64 lines

Saying No Kindly Skill

Chronic yes is a scheduling decision made by fear — each yes reasonable, the sum unworkable, and the real casualties are the commitments already made (every new yes quietly taxes them). The working no is fast (a slow no wastes the asker's planning time and reads worse than the decline itself), clear (soft-nos — "maybe later," "let me think" — are heard as yes-pending and return with interest), and warm (the relationship is preserved by tone and alternatives, not by capitulation). Upward, the form changes entirely: nos to the boss are tradeoff conversations — "yes is available; here's what it displaces; you pick."

What This Skill Produces

  • The scripts — the decline by relationship (peer, report, boss, external), each fast-clear-warm
  • The alternative menu — the smaller yes, the later yes, the redirect, the resource — attached where honest
  • The upward version — the tradeoff frame that converts refusal into prioritization the boss owns
  • The yes-audit — the current commitments reviewed for the over-capacity that made no necessary (task-triage-matrix supplies the evidence)

Required Inputs

Ask for these if not provided:

  • The ask and the asker — what's requested, by whom, with what relationship and power direction; the script's form follows
  • The real reason — capacity? Wrong person? Wrong project? The no's honesty level calibrates (capacity-nos can say so; judgment-nos need more care)
  • What's honestly offerable — the smaller/later/redirect alternatives that exist; alternatives invented to soften become new commitments, which is the disease again
  • The pattern, if any — recurring asks from the same source get the structural answer (the norm conversation), not the fifteenth artisanal decline

Framework: The Decline Rules

  1. Fast beats polished: the no within a day — "I can't take this on" today outperforms the perfect decline on Thursday, because the asker's alternative plans age by the hour. Sitting on asks to avoid the discomfort transfers the cost to them, with interest.
  2. Clear kills the zombie: "I'm not able to do this" — complete sentence, no "right now" unless later is a real offer, no "maybe" as anesthesia. Soft-nos return; every returned ask costs the decline and the resentment of having to repeat it.
  3. Warm is tone plus (honest) alternatives: "I can't own this — but [name] has the context, or I could do the 30-minute review version" — the alternative converts a door closing into a door pointing. The discipline: only alternatives that are true (a fake redirect burns the third party; an unaffordable smaller-yes is the original problem in a smaller size).
  4. Upward nos are tradeoff menus: never "no," always "here's the board: taking X means Y slips to [date] or Z drops — which trade do you want?" — the boss keeps the priority call (their job), the capacity truth lands (your job), and the meeting-prep-pack-grade specificity ("X costs the two Thursday blocks that ship the launch") is what separates this from whining. Most bosses pick sanely when shown the board; the ones who say "all of it" have now chosen the overload — on the record, revisitable.
  5. The audit ends the era: the standing commitments get the same treatment as new asks — which current yeses would be nos today? (recurring-meeting-pruner for meetings; the drop-list ceremony for tasks) — because saying no at the door of a full house is maintenance, and the audit is the renovation.

Output Format

The No: [ask] from [asker/relationship]

The Script

[The decline, verbatim: fast-clear-warm · the alternative if honest · the full-stop where none is]

If Upward: The Tradeoff Board

["Yes to X displaces: [specific costs with dates] — which trade?" · the on-the-record note if overridden]

The Pattern Answer (if recurring)

[The structural fix: the norm, the routing, the office-hours lane — instead of decline #15]

The Yes-Audit

[Current commitments that would be nos today → their exit moves]

Quality Checks

  • The no ships within a day of the ask
  • No soft-no language survives unless later is a real offer
  • Every attached alternative is honestly affordable or honestly routed
  • Upward nos present specific tradeoffs, never bare refusal
  • Recurring asks got the structural answer

Anti-Patterns

  • Do not slow-no — the delay is a cost you're charging the asker to spare yourself
  • Do not soften into zombie-maybes — they return, with interest and a grudge
  • Do not invent alternatives as anesthetic — fake redirects and unaffordable smaller-yeses are new debts
  • Do not say bare no upward — the tradeoff board is both more honest and more survivable
  • Do not decline the new while hoarding the old — the audit is where capacity actually returns
1---
2name: saying-no-kindly
3description: "Decline requests without damaging relationships or your standing — the fast-clear-warm formula, the alternative-attached no, the no-to-the-boss version (tradeoffs, not refusal), and scripts for the asks that recur. Use when asked how do I say no to this, turn down a request, decline extra work politely, I say yes to everything and drown, push back on my manager, or protect the roadmap from a pet feature. Produces the decline scripts by relationship, the tradeoff framing, and the exact wording tuned to who is asking."
4---
5 
6# Saying No Kindly Skill
7 
8Chronic yes is a scheduling decision made by fear — each yes reasonable, the sum unworkable, and the real casualties are the commitments already made (every new yes quietly taxes them). The working no is *fast* (a slow no wastes the asker's planning time and reads worse than the decline itself), *clear* (soft-nos — "maybe later," "let me think" — are heard as yes-pending and return with interest), and *warm* (the relationship is preserved by tone and alternatives, not by capitulation). Upward, the form changes entirely: nos to the boss are *tradeoff conversations* — "yes is available; here's what it displaces; you pick."
9 
10## What This Skill Produces
11 
12- **The scripts** — the decline by relationship (peer, report, boss, external), each fast-clear-warm
13- **The alternative menu** — the smaller yes, the later yes, the redirect, the resource — attached where honest
14- **The upward version** — the tradeoff frame that converts refusal into prioritization the boss owns
15- **The yes-audit** — the current commitments reviewed for the over-capacity that made no necessary ([task-triage-matrix](../task-triage-matrix/SKILL.md) supplies the evidence)
16 
17## Required Inputs
18 
19Ask for these if not provided:
20- **The ask and the asker** — what's requested, by whom, with what relationship and power direction; the script's form follows
21- **The real reason** — capacity? Wrong person? Wrong project? The no's honesty level calibrates (capacity-nos can say so; judgment-nos need more care)
22- **What's honestly offerable** — the smaller/later/redirect alternatives that exist; alternatives invented to soften become new commitments, which is the disease again
23- **The pattern, if any** — recurring asks from the same source get the structural answer (the norm conversation), not the fifteenth artisanal decline
24 
25## Framework: The Decline Rules
26 
271. **Fast beats polished:** the no within a day — "I can't take this on" today outperforms the perfect decline on Thursday, because the asker's alternative plans age by the hour. Sitting on asks to avoid the discomfort transfers the cost to them, with interest.
282. **Clear kills the zombie:** "I'm not able to do this" — complete sentence, no "right now" unless *later* is a real offer, no "maybe" as anesthesia. Soft-nos return; every returned ask costs the decline *and* the resentment of having to repeat it.
293. **Warm is tone plus (honest) alternatives:** "I can't own this — but [name] has the context, or I could do the 30-minute review version" — the alternative converts a door closing into a door pointing. The discipline: only alternatives that are *true* (a fake redirect burns the third party; an unaffordable smaller-yes is the original problem in a smaller size).
304. **Upward nos are tradeoff menus:** never "no," always "here's the board: taking X means Y slips to [date] or Z drops — which trade do you want?" — the boss keeps the priority call (their job), the capacity truth lands (your job), and the [meeting-prep-pack](../meeting-prep-pack/SKILL.md)-grade specificity ("X costs the two Thursday blocks that ship the launch") is what separates this from whining. Most bosses pick sanely when shown the board; the ones who say "all of it" have now *chosen* the overload — on the record, revisitable.
315. **The audit ends the era:** the standing commitments get the same treatment as new asks — which current yeses would be nos today? ([recurring-meeting-pruner](../recurring-meeting-pruner/SKILL.md) for meetings; the drop-list ceremony for tasks) — because saying no at the door of a full house is maintenance, and the audit is the renovation.
32 
33## Output Format
34 
35# The No: [ask] from [asker/relationship]
36 
37## The Script
38[The decline, verbatim: fast-clear-warm · the alternative if honest · the full-stop where none is]
39 
40## If Upward: The Tradeoff Board
41["Yes to X displaces: [specific costs with dates] — which trade?" · the on-the-record note if overridden]
42 
43## The Pattern Answer (if recurring)
44[The structural fix: the norm, the routing, the [office-hours](../office-hours-design/SKILL.md) lane — instead of decline #15]
45 
46## The Yes-Audit
47[Current commitments that would be nos today → their exit moves]
48 
49## Quality Checks
50 
51- [ ] The no ships within a day of the ask
52- [ ] No soft-no language survives unless later is a real offer
53- [ ] Every attached alternative is honestly affordable or honestly routed
54- [ ] Upward nos present specific tradeoffs, never bare refusal
55- [ ] Recurring asks got the structural answer
56 
57## Anti-Patterns
58 
59- [ ] Do not slow-no — the delay is a cost you're charging the asker to spare yourself
60- [ ] Do not soften into zombie-maybes — they return, with interest and a grudge
61- [ ] Do not invent alternatives as anesthetic — fake redirects and unaffordable smaller-yeses are new debts
62- [ ] Do not say bare no upward — the tradeoff board is both more honest and more survivable
63- [ ] Do not decline the new while hoarding the old — the audit is where capacity actually returns
64 
View all files on GitHub →

Details

Updated
Sep 23, 2026
License
MIT
Stars on the repo
★ 1,395
Checked
Source
mohitagw15856/pm-claude-skills ↗
Creator
mohitagw15856 · 193 listings
View creator

Made with saying-no-kindly

Saying No Kindly Skill — Galaxy 3D — fly through all 1170 skills as a glowing constellation you orbit and click into (from the mohitagw15856/pm-claude-skills README)
Saying No Kindly Skill — Galaxy 3D — fly through all 1170 skills as a glowing constellation you orbit and click into (from the mohitagw15856/pm-claude-skills README)

by mohitagw15856

Saying No Kindly Skill — PM Skills Wrapped — your practice turned into a shareable, Spotify-Wrapped-style story (from the mohitagw15856/pm-claude-skills README)
Saying No Kindly Skill — PM Skills Wrapped — your practice turned into a shareable, Spotify-Wrapped-style story (from the mohitagw15856/pm-claude-skills README)

by mohitagw15856

Similar skills

See all →
MCP3-5 days | Agents: 6 | Gate Keepers: DevOps Automator +⚙️ Phase 2 Playbook — Foundation & Scaffoldingmsitarzewski/agency-agents · by msitarzewski> Duration: 3-5 days | Agents: 6 | Gate Keepers: DevOps Automator + Evidence Collector★ 154k GitHub starsMCPNEXUS transforms The Agency's independent AI specialists🌐 NEXUS — Network of EXperts, Unified in Strategymsitarzewski/agency-agents · by msitarzewski> NEXUS transforms The Agency's independent AI specialists into a synchronized intelligence network. This is not a prompt collection — it…★ 154k GitHub starsSkillGenerate an Ansoff Matrix analysis mapping growth strategiesphuryn/pm-skills · by phurynGenerate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.★ 26.6k GitHub starsSkillSurvey any codebase as a senior advisorImproveshadcn/improve · by shadcnSurvey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on source code — never implements, fixes, or refactors anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX), suggest features or where to take the project next (roadmap, product direction), or generate handoff plans for another agent to implement.★ 9.2k GitHub starsSkillTranslate skills from one industry to anotherCareer changer translatorParamchoudhary/ResumeSkills · by ParamchoudharyTranslate skills from one industry to another, identify transferable skills★ 2.4k GitHub starsSkillA collection of 37 battle-tested marketing skillsOpenClaw Marketing SkillsLeoYeAI/openclaw-marketing-skills · by LeoYeAIA collection of 37 battle-tested marketing skills for OpenClaw agents. Use when you want to install or reference any marketing skill including: CRO (page-cro, signup-flow-cro, onboarding-cro, form-cro, popup-cro, paywall-upgrade-cro), copywriting, copy-editing, cold-email, email-sequence, social-content, seo-audit, ai-seo, programmatic-seo, site-architecture, schema-markup, content-strategy, paid-ads, ad-creative, ab-test-setup, analytics-tracking, referral-program, free-tool-strategy, churn-prevention, revops, sales-enablement, launch-strategy, pricing-strategy, competitor-alternatives, marketing-ideas, marketing-psychology, lead-magnets, product-marketing-context, and data connectors (google-ads-connect, search-console-connect, meta-ads-connect, x-twitter-connect). Start with product-marketing-context to set up your product context document, then use any other skill naturally. Powered by MyClaw.ai.★ 1k GitHub stars

More from mohitagw15856

SkillDesign a 360-degree feedback survey or write a structured360-Degree Feedback Template Skillmohitagw15856/pm-claude-skills · by mohitagw15856Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.★ 1.4k GitHub starsSkillDesign statistically rigorous A/B tests for product featuresA/B Test Planner Skillmohitagw15856/pm-claude-skills · by mohitagw15856Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.★ 1.4k GitHub starsSkillGenerate a WCAG 2.2 accessibility audit checklistAccessibility Audit Skillmohitagw15856/pm-claude-skills · by mohitagw15856Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.★ 1.4k GitHub starsSkillBuild a structured account plan for any key customerAccount Plan Skillmohitagw15856/pm-claude-skills · by mohitagw15856Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.★ 1.4k GitHub starsSkillOptimize an article for Answer Engine Optimization so AIAEO Optimizer Skillmohitagw15856/pm-claude-skills · by mohitagw15856Optimize an article for Answer Engine Optimization (AEO) so AI engines like ChatGPT, Perplexity, and Claude can extract, quote, and cite it. Use when asked to AEO-optimize, make content AI-readable, improve AI citation chances, or adapt an article for answer engines. Produces an AEO-optimised rewrite with question headings, 50–80 word answer capsules, a paragraph-length audit, and flagged trust signals.★ 1.4k GitHub starsSkillConduct a structured ethical review of an AI or ML featureAI Ethics Review Skillmohitagw15856/pm-claude-skills · by mohitagw15856Conduct a structured ethical review of an AI or ML feature, model, or product. Use when preparing to deploy an AI system, assessing algorithmic risk, auditing a model for bias, or producing a responsible AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with a risk tier score, pre-deployment checklist, and prioritised mitigations.★ 1.4k GitHub stars