Flags
vercel/next.js
How to add or modify Next.js experimental feature flags end-to-end.
Spot a bad client before you sign — the warning signs of the projects that turn into unpaid, scope-creeping nightmares, and how to screen, price, or decline them.
MITAuto-check passed
Install Client Red Flags
$ npx skills add mohitagw15856/pm-claude-skills --skill client-red-flags -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills client-red-flags --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/client-red-flags .claude/skills/client-red-flags && 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 "client-red-flags" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/client-red-flags into .claude/skills/client-red-flags/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "client-red-flags", 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/client-red-flagsType 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 client-red-flags -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills client-red-flags --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/client-red-flags .agents/skills/client-red-flags && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "client-red-flags" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/client-red-flags into .agents/skills/client-red-flags/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "client-red-flags", 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 client-red-flags -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills client-red-flags --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/client-red-flags .cursor/skills/client-red-flags && 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 "client-red-flags" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/client-red-flags into .cursor/skills/client-red-flags/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "client-red-flags", 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/client-red-flags--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 client-red-flags -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills client-red-flags --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/client-red-flags .gemini/skills/client-red-flags && 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 "client-red-flags" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/client-red-flags into .gemini/skills/client-red-flags/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "client-red-flags", 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 client-red-flagsInstalls 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 client-red-flags -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/client-red-flags .github/skills/client-red-flags && 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 "client-red-flags" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/client-red-flags into .github/skills/client-red-flags/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "client-red-flags", 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 client-red-flags -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 client-red-flags --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/client-red-flags .opencode/skills/client-red-flags && 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 "client-red-flags" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/client-red-flags into .opencode/skills/client-red-flags/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "client-red-flags", 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
client-red-flags- GitHub stars
- 1.4k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 578 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Spot a bad client before you sign — the warning signs of the projects that turn into unpaid, scope-creeping nightmares, and how to screen, price, or decline them.
- Works in 6 steps: Recognize the classic flags. Aggressive… → Translate to prediction. Each flag tends… → Screen before committing. Ask about… → …
- Asked is this client a red flag
- SKILL.md covers What This Skill Produces, Required Inputs, Framework: Read The Signs,… and Output Format, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Client Red Flags is an agent skill from mohitagw15856/pm-claude-skills. Spot a bad client before you sign — the warning signs of the projects that turn into unpaid, scope-creeping nightmares, and how to screen, price, or decline them. Use when asked is this client a red flag, should I take this client, screening a difficult client, or how to avoid bad clients. Produces a read on the warning signs present (haggling, vagueness, disrespect, urgency, unrealistic expectations), what each predicts, screening questions to ask before committing, protective terms if you proceed anyway, and…
Its SKILL.md is about 1.2k 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 is this client a red flag
- Should I take this client
- Screening a difficult client
- How to avoid bad clients
Example prompts
- “/client-red-flags”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Recognize the classic flags. Aggressive pre-start haggling, vague or shifting requirements, disrespect for your time/expertise…
- Translate to prediction. Each flag tends to forecast a specific future problem — name it so the decision is informed, not just a bad…
- Screen before committing. Ask about budget, who decides, what success looks like, and timeline — the answers reveal risk. A prospect who…
- Protect if you proceed. For borderline cases you still want, use a deposit, milestone payments, a tightly-scoped contract, and clear…
- Decline gracefully when warranted. Some clients cost more than they pay — say no professionally, briefly, without insult, and keep the…
- Weigh your reality. Desperation lowers standards; factor honestly how much you need the work, but know the true cost of a nightmare client.
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
Client Red Flags loads about 1.2k tokens when it runs. Until then it costs about 154 tokens; SKILL.md has 578 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). 578 words, ~1,188 tokens.
Download SKILL.mdSave it as
.claude/skills/client-red-flags/SKILL.md (or your agent's skills folder).- name
- client-red-flags
- description
- Spot a bad client before you sign — the warning signs of the projects that turn into unpaid, scope-creeping nightmares, and how to screen, price, or decline them. Use when asked is this client a red flag, should I take this client, screening a difficult client, or how to avoid bad clients. Produces a read on the warning signs present (haggling, vagueness, disrespect, urgency, unrealistic expectations), what each predicts, screening questions to ask before committing, protective terms if you proceed anyway, and how to decline gracefully — so you avoid the clients who cost more than they pay.
Client Red Flags
Experienced freelancers know: the worst projects announce themselves early. The client who haggles hard before you start, can't describe what they want, disrespects your time, or needs it "yesterday" tends to become the one who scope-creeps, pays late, and drains your energy. This reads the warning signs, tells you what they predict, and helps you screen, protect, or walk — before you're trapped.
What This Skill Produces
- A red-flag read — the warning signs present in this prospect and what each tends to predict (aggressive haggling → payment/scope issues; vagueness → endless revisions; disrespect early → worse later; false urgency → chaos)
- Screening questions — what to ask before committing to surface the risks (budget, decision-maker, success definition, timeline realism)
- Protective terms — if you proceed, the contract/process safeguards (deposit, milestone payments, tight scope, kill fee) that reduce the risk
- A proceed / protect / decline call — a judgment based on the severity and your situation
- A graceful decline — how to say no professionally without burning the bridge
Required Inputs
Ask for these if not provided:
- The prospect — how they've behaved so far (messages, calls, the ask)
- The project — what they want, budget signals, timeline
- The signs — anything that's given you pause
- Your situation — how much you need the work (affects risk tolerance)
- Your terms — what protections you can put in place
Framework: Read The Signs, Screen, Protect Or Pass
- Recognize the classic flags. Aggressive pre-start haggling, vague or shifting requirements, disrespect for your time/expertise, unrealistic timelines/expectations, "this'll lead to more work" in lieu of pay, and reluctance to sign or deposit.
- Translate to prediction. Each flag tends to forecast a specific future problem — name it so the decision is informed, not just a bad feeling.
- Screen before committing. Ask about budget, who decides, what success looks like, and timeline — the answers reveal risk. A prospect who won't engage is itself a signal.
- Protect if you proceed. For borderline cases you still want, use a deposit, milestone payments, a tightly-scoped contract, and clear change/revision terms.
- Decline gracefully when warranted. Some clients cost more than they pay — say no professionally, briefly, without insult, and keep the door open.
- Weigh your reality. Desperation lowers standards; factor honestly how much you need the work, but know the true cost of a nightmare client.
Show full SKILL.md (199 more words)Show less
Output Format
Client screen: [prospect behavior] · project [x]
Red flags present: [flag → what it predicts] (e.g. haggling hard → likely payment/scope trouble). Screen with: ["what's the budget?" · "who signs off?" · "what does success look like?" · "is that timeline firm?"]. If you proceed — protect: [deposit · milestone payments · tight scope · change/revision terms · kill fee]. Call: [take it / take it with protections / decline] — because [severity + your situation]. Graceful decline: "[brief, professional no]".
Quality Checks
- Identifies the specific red flags present
- Translates each into what it tends to predict
- Provides screening questions to surface risk before committing
- Offers protective terms for borderline cases
- Gives a clear proceed/protect/decline call
- Includes a graceful, professional decline
Anti-Patterns
- Ignoring early warning signs because you want the work.
- A vague bad feeling with no specific flag named.
- Proceeding with no protective terms on a risky client.
- Taking every client regardless of cost.
- Declining rudely and burning a bridge.
Example Trigger Phrases
- "Is this client a red flag? They're haggling before we've even started."
- "Should I take this project? Something feels off about the client."
- "How do I screen out bad clients?"
- "This prospect can't tell me what they want — should I be worried?"
- "Help me decline a client politely."
© 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/client-red-flags of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Client Red Flags 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 |
|---|---|---|---|---|---|---|
| Client Red Flags this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Flagsvercel/next.js | 143k | — | ~746 | Automated safety check: Pass | MIT | |
| Document Signingasgeirtj/system_prompts_leaks | 69k | — | ~1.5k | Automated safety check: Pass | CC0-1.0 | |
| Feature Flagssickn33/agentic-awesome-skills | 47k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| SpotLeoYeAI/openclaw-master-skills | 2.2k | — | ~6.2k | Automated safety check: Pass | MIT | |
| Feature Flagsgetsentry/sentry | 46k | — | ~374 | Automated safety check: Pass | Custom licence |
Similar skills
- Official
Document Signing
asgeirtj/system_prompts_leaks
Review documents for signature or prepare a signing packet; verify fields and recipients while keeping sending and signing under explicit user authorization.
Feature Flags
sickn33/agentic-awesome-skills
Implement feature flags for progressive feature rollout using LaunchDarkly, Unleash, or custom solutions.
Spot
LeoYeAI/openclaw-master-skills
Binance Spot request using the Binance API. An agent skill from LeoYeAI/openclaw-master-skills.
- Official
Feature Flags
getsentry/sentry
Gate a Sentry feature behind a FlagPole feature flag. An agent skill from getsentry/sentry.
Continuous LLM Red Teaming With Promptfoo
mukul975/Anthropic-Cybersecurity-Skills
Wires Promptfoo and DeepTeam into CI/CD for automated, repeatable red-teaming of LLM apps against OWASP LLM Top 10, OWASP Agentic, and MITRE ATLAS presets, failing the build when jailbreak or…
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 Client Red Flags
What does Client Red Flags do?
Spot a bad client before you sign — the warning signs of the projects that turn into unpaid, scope-creeping nightmares, and how to screen, price, or decline them. Client Red Flags is an agent skill from mohitagw15856/pm-claude-skills. Spot a bad client before you sign — the warning signs of the projects that turn into unpaid, scope-creeping nightmares, and how to screen, price, or decline them.
When should I use Client Red Flags?
Client Red Flags fits situations like: asked is this client a red flag; should I take this client; screening a difficult client; how to avoid bad clients.
How do I install Client Red Flags in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill client-red-flags -a claude-code`. Or copy the skill folder (skills/client-red-flags in mohitagw15856/pm-claude-skills) into .claude/skills/client-red-flags in your project. Claude Code loads it when a task matches its description.
How do I install Client Red Flags in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill client-red-flags -a codex`. Or copy the skill folder (skills/client-red-flags in mohitagw15856/pm-claude-skills) into .agents/skills/client-red-flags in your project. Codex loads it when a task matches its description.
Can I use Client Red Flags 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 client-red-flags -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/client-red-flags, .gemini/skills/client-red-flags, .github/skills/client-red-flags and .opencode/skills/client-red-flags in your project.
What does Client Red Flags need to run?
SKILL.md names no scripts, command-line tools or credentials: Client Red Flags is instructions for the agent only.
Does Client Red Flags 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 Client Red Flags 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 Client Red Flags use?
Client Red Flags 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 Client Red Flags use?
About 1.2k tokens (SKILL.md is roughly 4.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 Client Red Flags?
Skills that share tags, products or a category with Client Red Flags: Flags (vercel/next.js, 143k stars), Document Signing (asgeirtj/system_prompts_leaks, 69k stars), Feature Flags (sickn33/agentic-awesome-skills, 47k stars) and Spot (LeoYeAI/openclaw-master-skills, 2.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Client Red Flags?
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.