agentleFS
prospapledge88prospapledge88/claude-skills/skills/strategy/high-stakes-responder/SKILL.md

high-stakes-responder

Skill0 starsChanged 7 months agoNo licenceView on GitHub

Draft evidence-based responses for high-stakes business conversations including negotiations, conflicts, debates, investor pitches, vendor discussions, partnership talks, stakeholder disagreements, and difficult counterpart interactions. Use when the user needs to reply to a difficult email, prepare talking points for a high-stakes meeting, draft a response to pushback, write a negotiation script, debrief a tense transcript, or handle any written/verbal business exchange where something important is at stake. Triggers include: negotiate a deal, respond to pushback, reply to a difficult email, draft a negotiation response, counter-offer, handle a difficult conversation, deal with a conflict, investor pitch, partner negotiation, vendor discussion, board meeting prep, cofounder disagreement, stakeholder conflict, pressure from X, walk away from a deal, disagree with a decision, set a boundary, respond to escalation. Do NOT use for: drafting articles, blog posts, or marketing content (use seo-content or content-research-writer), writing landing pages or sales copy (use direct-response-copy), drafting routine non-conflict emails or messages, or writing newsletter editions (use newsletter). Routing guide: this skill is for adversarial or high-stakes communication where something is at risk. If the user just wants to "draft" or "reply" to something routine, do not use this skill.

The file

Show its rules and text

We split this skill into the rules it gives an agent

42 rules. About 0 are common, 41 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈41

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.