strategy
Skill1 starsChanged 4 months agoMITView on GitHub
Choose the negotiation play and write the game plan — target number, sequence, escalation ladder, deadlines. Use once evidence is gathered (bill audited, prices benchmarked, assistance screened).
22 other projects use a version of this.
Adopted by
Most recently taken up by
- galiprandi/job-seekertheir own version, first seen Nov 14, 2026
- thesun4sky/jobstacktheir own version, first seen Nov 10, 2026
- ChainGPT-org/chaingpt-claude-skilltheir own version, first seen Nov 1, 2026
- HKTITAN/isb-skillstheir own version, first seen Nov 1, 2026
- DayDreamingSheep/tennis-teamtheir own version, first seen Oct 25, 2026
- Merriban/LaunchPilottheir own version, first seen Oct 20, 2026
Used with
Projects with it also use north-star, brand-voice and 4 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
UMwaiSkillnorth-star
Evaluate whether current work serves the project's ultimate goal. Scores branches, goals, and commits against declared pillars/objectives. Flags drift and misalignment.
Also in 3 projects that use this
Dokkabei97Skillbrand-voice
Defines and enforces brand voice guidelines for startups. Creates tone, style, messaging frameworks and provides consistency checks across all content. Ensures every piece of communication sounds like it comes from the same brand.
Also in 4 projects that use this
MetaSkillroadmap
Build, continue, inspect, or visualize a source-grounded mathematical roadmap and theorem DAG in an existing Autoform Markdown blueprint. Use for source research, repository-wide inventories of existing and planned mathematics, scope, coverage, milestones, and roadmap articles; do not create repository infrastructure or prove Lean declarations.
Also in 3 projects that use this
AnthropicSkillbrief
Generate contextual briefings for legal work — daily summary, topic research, or incident response. Use when starting your day and need a scan of legal-relevant items across email, calendar, and contracts, when researching a specific legal question across internal sources, or when a developing situation (data breach, litigation threat, regulatory inquiry) needs rapid context.
Also in 4 projects that use this
AWSSkillretro
Conduct a retrospective on a coding session.
Also in 3 projects that use this
OpenAISkillaudit
Audit or critique a product flow, journey, workflow, funnel, onboarding path, checkout path, settings path, screen, or multi-step product experience by capturing screenshots first, then reporting UX, design, and accessibility findings inline from that evidence. Use Figma only when the user explicitly asks for a board. Use when the user asks to audit, review, critique, inspect, assess, analyze, evaluate, or give feedback on a product experience.
Also in 3 projects that use this
Other versions22 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 22
- menkesu/awesome-pm-skills★ 441same name
- andreaskelm/pm-brain★ 235same name
- thesun4sky/jobstack★ 216same name
- galiprandi/job-seeker★ 136same name
- rainday/smart-blog-skills★ 35same name
- skyf0xx/gambit★ 29same name
- superuser-pal/awesome-second-brain★ 14same name
- ChainGPT-org/chaingpt-claude-skill★ 7same name
- BhaskarManam/pstack★ 4same name
- EmanueleMinotto/minottobot★ 4same name
12 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- benchmark-priceSkill
- collectionsSkill
- draft-emailSkill
- financial-assistanceSkill
- insurance-appealSkill
- intakeSkill
- phone-prepSkill
- review-billSkill
- send-letterSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 19 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 54
Every phone commitment gets a same-day written recap.
- Distinctive: line 55
No payment until settlement terms are confirmed in writing ("payment in full," account number, amount, signature block).
“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Strategy — pick the play
Inputs from the case file: audit findings, benchmark table, assistance
screening, insurance posture, collections status, what the user can pay.
Output: a written game plan in case.md the user signs off on.
The decision tree (first match wins as PRIMARY play; others stack behind it)
- Court summons exists → not a negotiation. Legal aid, answer the summons, pause everything else.
- Collector involved & validation window open → validate first
(
collectionsskill), negotiate after. - Charity-care screening says likely eligible → apply (
financial- assistance); hold all payment; negotiation only for any remainder. - No Surprises Act facts (OON provider at in-network facility,
emergency OON, or bill > GFE + $400) → rights-based dispute / PPDR
(
rights-and-laws.md§1,templates/letters/nsa-complaint.md), not a discount request. - Confirmed billing errors → error dispute letter first; negotiate the corrected balance after they respond.
- Insurance denied/underpaid wrongly →
insurance-appealbefore paying anything. - Bill is real, priced absurdly (the common case) → evidence-based settlement: benchmark table + written offer.
- Bill is real and fairly priced (rare, but happens — say so honestly) → hardship adjustment request + interest-free payment plan sizing.
Writing the game plan
Put in case.md:
- Primary play + stacked plays, in order, each with its trigger ("if FAP denied → settlement offer at $X").
- Numbers: walk-away target, opening offer, absolute max the user can pay. Anchor all three to the benchmark table.
- Channel sequence: written where possible; phone to locate the right
human, letters to commit positions. Certified mail for anything
rights-based (
send-letter). - Deadlines: theirs and ours (validation clock, 240-day FAP window, PPDR 120 days, promised response dates). Every deadline gets a date.
- Escalation ladder with the specific next rung named
(
knowledge/tactics.md).
Rules of engagement
- One position at a time: never simultaneously claim "I can't afford this" and "I'll pay $X today" to the same office. Sequence: rights/errors → assistance → money.
- Every phone commitment gets a same-day written recap.
- No payment until settlement terms are confirmed in writing ("payment in full," account number, amount, signature block).
- Present the plan to the user in dollars: "billed $14,200 → target $3,100, here's the path" — then get their go before executing.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

