Error Handling
affaan-m/ECC
Patterns for robust error handling across TypeScript, Python, and Go.
Handle scope creep on client work without torching the relationship — classify the ask against the agreement, respond with the goodwill/change-order/renegotiate move that fits, and install the…
MITAuto-check passed
Install Scope Creep Response
$ npx skills add mohitagw15856/pm-claude-skills --skill scope-creep-response -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills scope-creep-response --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/scope-creep-response .claude/skills/scope-creep-response && 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 "scope-creep-response" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/scope-creep-response into .claude/skills/scope-creep-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scope-creep-response", 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/scope-creep-responseType 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 scope-creep-response -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills scope-creep-response --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/scope-creep-response .agents/skills/scope-creep-response && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "scope-creep-response" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/scope-creep-response into .agents/skills/scope-creep-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scope-creep-response", 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 scope-creep-response -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills scope-creep-response --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/scope-creep-response .cursor/skills/scope-creep-response && 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 "scope-creep-response" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/scope-creep-response into .cursor/skills/scope-creep-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scope-creep-response", 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/scope-creep-response--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 scope-creep-response -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills scope-creep-response --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/scope-creep-response .gemini/skills/scope-creep-response && 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 "scope-creep-response" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/scope-creep-response into .gemini/skills/scope-creep-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scope-creep-response", 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 scope-creep-responseInstalls 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 scope-creep-response -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/scope-creep-response .github/skills/scope-creep-response && 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 "scope-creep-response" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/scope-creep-response into .github/skills/scope-creep-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scope-creep-response", 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 scope-creep-response -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 scope-creep-response --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/scope-creep-response .opencode/skills/scope-creep-response && 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 "scope-creep-response" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/scope-creep-response into .opencode/skills/scope-creep-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scope-creep-response", 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
scope-creep-response- GitHub stars
- 1.4k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 715 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Handle scope creep on client work without torching the relationship — classify the ask against the agreement, respond with the goodwill/change-order/renegotiate move that fits, and install the…
- Works in 5 steps: Classify against text, not feelings:… → Grant goodwill deliberately and say so:… → The change order is the boundary: for… → …
- Asked my client keeps adding requests
- SKILL.md covers What This Skill Produces, Required Inputs, Framework: The Graduated… and Output Format, plus 7 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Scope Creep Response is an agent skill from mohitagw15856/pm-claude-skills. Handle scope creep on client work without torching the relationship — classify the ask against the agreement, respond with the goodwill/change-order/renegotiate move that fits, and install the prevention language for next time. Use when asked my client keeps adding requests, is this scope creep, how do I say that's out of scope nicely, or write a change order email. Produces the classification of the ask, the graduated response with ready-to-send wording, and the contract language that prevents the rerun.
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.
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
- Asked my client keeps adding requests
- Is this scope creep
- How do I say thats out of scope nicely
- Write a change order email
Example prompts
- “/scope-creep-response”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Classify against text, not feelings: read the ask against the written scope, steelmanning the client's interpretation. Gray zones are…
- Grant goodwill deliberately and say so: small extras can be smart — but visibly: "Happy to include this one — it's beyond the original…
- The change order is the boundary: for real additions, enthusiasm + process: "Great addition. It's outside the current scope — here's a…
- Name patterns at the pattern level: the twelfth small ask gets a zoom-out, not a twelfth skirmish: "These small additions are adding up to…
- Prevention is contract language: next agreement carries: enumerated deliverables, revision counts ("two revision rounds; further rounds at…
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
Scope Creep Response loads about 1.4k tokens when it runs. Until then it costs about 133 tokens; SKILL.md has 715 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). 715 words, ~1,366 tokens.
Download SKILL.mdSave it as
.claude/skills/scope-creep-response/SKILL.md (or your agent's skills folder).- name
- scope-creep-response
- description
- Handle scope creep on client work without torching the relationship — classify the ask against the agreement, respond with the goodwill/change-order/renegotiate move that fits, and install the prevention language for next time. Use when asked my client keeps adding requests, is this scope creep, how do I say that's out of scope nicely, or write a change order email. Produces the classification of the ask, the graduated response with ready-to-send wording, and the contract language that prevents the rerun.
Scope Creep Response Skill
Scope creep is rarely malicious — it's a client who genuinely can't tell the difference between "small tweak" and "new workstream," talking to a freelancer afraid that any boundary costs the relationship. The damage comes from the two failure modes: absorbing everything silently (resentment, then a blowup over something trivial) or lawyering every request (death by friction). This skill runs the middle path: classify honestly, respond proportionally, and make the structure hold the boundary so the person doesn't have to.
What This Skill Produces
- The classification — in-scope / gray / clearly-out, argued against the actual agreement text, including the honest case for the client's reading
- The graduated response — goodwill grant, flag-and-track, change order, or renegotiation — with ready-to-send wording
- The change-order artifact — small, friendly, priced; a form not a confrontation
- The prevention layer — scope language, revision counts, and the "great idea — phase 2" ritual for the next contract
Required Inputs
Ask for these if not provided:
- What the agreement actually says — the scope text verbatim; if scope was never written down, that's the finding, and the response changes (you can't cite what doesn't exist)
- The asks so far — list them; one gray-zone request and a drip of twelve "tiny things" are different situations
- Relationship context — client value, history, how earlier extras were handled (silently absorbed extras set precedent that must be un-set gently)
- Their goal — keep the client happily, get paid for the extras, or exit gracefully — the same classification routes to different responses
Framework: The Graduated Response Rules
- Classify against text, not feelings: read the ask against the written scope, steelmanning the client's interpretation. Gray zones are usually real ambiguity — treat them as shared drafting failure, not bad faith. No written scope? Then the move is defining it forward ("let me write up what's in the remaining work so we're aligned"), not litigating backward.
- Grant goodwill deliberately and say so: small extras can be smart — but visibly: "Happy to include this one — it's beyond the original scope, but it's quick." Invisible generosity reads as included-all-along and becomes the new baseline.
- The change order is the boundary: for real additions, enthusiasm + process: "Great addition. It's outside the current scope — here's a quick change order: [thing], [price], [timeline impact]. Approve and I'll start." The form does the confronting; the freelancer just does paperwork.
- Name patterns at the pattern level: the twelfth small ask gets a zoom-out, not a twelfth skirmish: "These small additions are adding up to real time — let's set up a monthly bucket of N hours for odds and ends so you can just send them over." Sells the fix as convenience, because it is.
- Prevention is contract language: next agreement carries: enumerated deliverables, revision counts ("two revision rounds; further rounds at $X"), an explicit exclusions line, and a change-request clause. The phase-2 parking lot ("love it — capturing for phase 2") lets you say yes-later instead of no.
Show full SKILL.md (231 more words)Show less
Output Format
Scope Response: [client, ask(s)]
Classification
[In / gray / out — quoting the agreement text · the client's plausible reading, stated fairly · pattern or one-off]
The Move
[Which response and why, given their goal]
Ready to send:
[The email/message, verbatim — warm, brief, boundary carried by process not tone]
Change Order (if applicable)
[Thing · price · timeline impact · approval line — 5 lines, friendly]
Prevention (next contract / next phase)
[Scope language to add · revision counts · exclusions line · the phase-2 ritual]
Quality Checks
- Classification quotes the agreement (or names its absence as the root cause)
- The client's interpretation is steelmanned before being answered
- Goodwill grants are labeled as such in the wording — never silent
- The send-ready text is warm; the boundary lives in the process, not the tone
- Prevention language included whenever the pattern is recurring
Anti-Patterns
- Do not absorb silently — every unlabeled extra resets the baseline
- Do not meet a gray-zone ask with contract-lawyer tone — ambiguity is shared fault
- Do not litigate the past on an unwritten scope — define forward instead
- Do not fight the twelfth small ask individually — name the pattern and sell the structural fix
- Do not say "no" where "yes, via change order" or "yes, in phase 2" is true — those keep the relationship AND the boundary
Example Trigger Phrases
- "My client keeps adding requests."
- "Is this scope creep?"
- "How do I say that's out of scope nicely?"
- "Write a change order email."
© 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/scope-creep-response of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Scope Creep Response 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 |
|---|---|---|---|---|---|---|
| Scope Creep Response this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Error Handlingaffaan-m/ECC | 277k | 1 repos | ~2.7k | Automated safety check: Pass | MIT | |
| HTTP Response HandlingHKUDS/OpenSpace | 7.8k | — | ~1k | Automated safety check: Pass | MIT | |
| Responsive Unitsthedaviddias/Front-End-Checklist | 74k | — | ~472 | Automated safety check: Pass | MIT | |
| Error Handlingthedaviddias/Front-End-Checklist | 74k | — | ~416 | Automated safety check: Pass | MIT | |
| Error Handlingaffaan-m/ECC | 276k | — | ~2.4k | Automated safety check: Pass | MIT |
Similar skills
HTTP Response Handling
HKUDS/OpenSpace
Handle websites requiring JavaScript by using curl with browser headers and validating file types.
Responsive Units
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing stylesheets, component styles, and responsive behavior related to Use relative units for responsive layouts.
Error Handling
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing scripts, client components, bundles, or runtime behavior related to Implement proper error handling.
Error Handling
affaan-m/ECC
TypeScript、Python、Goにわたる堅牢なエラー処理のパターン。型付きエラー、エラー境界、リトライ、サーキットブレーカー、ユーザー向けエラーメッセージをカバーします。
Incident Response
sickn33/agentic-awesome-skills
Handle security incidents with IR playbooks and procedures. An agent skill from sickn33/agentic-awesome-skills.
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.
Questions about Scope Creep Response
What does Scope Creep Response do?
Handle scope creep on client work without torching the relationship — classify the ask against the agreement, respond with the goodwill/change-order/renegotiate move that fits, and install the…. Scope Creep Response is an agent skill from mohitagw15856/pm-claude-skills. Handle scope creep on client work without torching the relationship — classify the ask against the agreement, respond with the goodwill/change-order/renegotiate move that fits, and install the prevention language for next time.
When should I use Scope Creep Response?
Scope Creep Response fits situations like: asked my client keeps adding requests; is this scope creep; how do I say thats out of scope nicely; write a change order email.
How do I install Scope Creep Response in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill scope-creep-response -a claude-code`. Or copy the skill folder (skills/scope-creep-response in mohitagw15856/pm-claude-skills) into .claude/skills/scope-creep-response in your project. Claude Code loads it when a task matches its description.
How do I install Scope Creep Response in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill scope-creep-response -a codex`. Or copy the skill folder (skills/scope-creep-response in mohitagw15856/pm-claude-skills) into .agents/skills/scope-creep-response in your project. Codex loads it when a task matches its description.
Can I use Scope Creep Response 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 scope-creep-response -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/scope-creep-response, .gemini/skills/scope-creep-response, .github/skills/scope-creep-response and .opencode/skills/scope-creep-response in your project.
What does Scope Creep Response need to run?
SKILL.md names no scripts, command-line tools or credentials: Scope Creep Response is instructions for the agent only.
Does Scope Creep Response 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 Scope Creep Response 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 Scope Creep Response use?
Scope Creep Response 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 Scope Creep Response use?
About 1.4k tokens (SKILL.md is roughly 5.5k 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 Scope Creep Response?
Skills that share tags, products or a category with Scope Creep Response: Error Handling (affaan-m/ECC, 277k stars), HTTP Response Handling (HKUDS/OpenSpace, 7.8k stars), Responsive Units (thedaviddias/Front-End-Checklist, 74k stars) and Error Handling (thedaviddias/Front-End-Checklist, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Scope Creep Response?
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.