Menu

Individual skill

saying-no

0upvotes

Decline a request, push back on scope, or protect priorities without burning the relationship. Use when asked how to say no, turn down a request, push back on your boss/stakeholder, decline extra work, or protect the roadmap from a pet feature. Produces a graceful, firm response — the no, the honest why, an alternative or trade-off, and the exact wording, tuned to who's asking.

plugins/pm-comms/skills/saying-no/SKILL.md

Read pinned source

Source commit f7c90bc09ee05dc25cf257bdb1826f2c2552c2cb

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,540
Repository last updated
Nov 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Saying No Skill

Most people say yes to things they should decline because they don't know how to say no without seeming
difficult — and then over-commit, miss what matters, or resent it. A good no is clear, respectful, and
offers a path: it declines the request while honouring the relationship and, often, reframes it as a
trade-off rather than a flat refusal. This skill writes that no.

## Required Inputs

Ask for these only if they aren't already provided:

- **The request** — what's being asked, by whom (boss, peer, customer, exec), and the relationship/power dynamic.
- **Why you want to decline** — capacity, priorities, fit, or it's the wrong call (the honest reason shapes the no).
- **Constraints** — can you offer an alternative, a later yes, or a trade-off? Is a flat no required?
Back to top