Audit email tone for harshness, ambiguity, and passive aggression

작성자: AILesson5 분 소요테스트::ChatGPT검토일: 2026-08-28

빠른 답변

Identify wording risks in context and revise tone without weakening facts or boundaries. 제공할 내용: Draft email, Relationship and history, Required intent and boundaries. 예상 결과: A phrase-level tone audit, risk explanation, and meaning-preserving revision.

맥락 추가

텍스트는 이 브라우저에 유지됩니다. AILesson Prompts는 이를 모델이나 서버로 보내지 않습니다.

Draft emailRelationship and historyRequired intent and boundaries

프롬프트

채워지지 않은 필드는 플레이스홀더로 표시되므로 프롬프트를 복사하고 편집할 수 있습니다

Audit the draft email for harsh, ambiguous, or passive-aggressive language.

Draft:
[draft]

Relationship, power dynamics, history, and sensitivities:
[context]

Required action, firmness, facts, and boundaries:
[intent]

Evaluate wording in context rather than assuming any direct sentence is rude. Identify exact phrases that may imply blame, sarcasm, threat, false consensus, hidden accusation, vague urgency, or unclear ownership. For each, explain the likely reading, severity, and a meaning-preserving alternative. Also flag ambiguity unrelated to tone. Then provide a revised email that keeps every required fact, deadline, refusal, escalation, and request. Do not erase legitimate accountability, add excessive apology, diagnose the sender, or claim how the recipient will feel.

Playground에서 사용해 보기

기본적으로 비공개프롬프트 구성은 브라우저에서 로컬로 이루어집니다. 조직에서 허용하지 않는 한 기밀 정보를 AI 서비스에 입력하지 마세요.

입력에서 결과까지

적용 예시

구체적인 맥락이 이 레시피를 바로 사용할 수 있는 결과로 바꾸는 방법을 확인하세요

실제 입력

Draft email: As I already explained twice, the figures were due yesterday. I’m sure you understand how this makes the whole team look. Please send the correct file ASAP, or I’ll have no choice but to take this further. Thanks in advance for finally sorting it out.
Relationship and history: A project lead writing to a peer team lead. Two prior reminders were sent, but neither confirmed a deadline. The received file has March rather than April figures. Escalation to both managers is allowed if the corrected file is not received by 15:00 today.
Required intent and boundaries: State that the file contains March data, request April data by 15:00 today, and say both managers will be included after that time. Keep the message firm and brief.

예시 출력

Tone risks: “already explained twice” assigns blame without helping identify the error; medium risk. “Makes the whole team look” uses shame and is unrelated to the requested correction; high risk. “No choice but to take this further” is a vague threat; replace it with the authorized escalation and exact trigger. “Finally sorting it out” is sarcastic; high risk. Clarity issue: “correct file” does not say that April figures are required, and “ASAP” conflicts with the available exact deadline. The claim that figures were due yesterday is unsupported by the history and should be removed.

Revised email: Subject: April figures needed by 15:00 today

Hi—The file received contains March figures. Please send the version containing April figures by 15:00 today. If it is not available by then, I will include both of our managers so we can agree the next step. Please let me know before 15:00 if there is a blocker or if I have referenced the wrong file.

Thanks, [Name]

효과가 있는 이유

1
Phrase-level review distinguishes real tone risk from necessary directness.
2
Explicit invariants keep a friendlier revision from weakening accountability or scope.

결과 확인

Are tone findings tied to exact phrases and the supplied context?
Does the revision preserve every required fact, boundary, and action?
Were clarity problems separated from interpersonal tone?

안심하고 사용하세요

자주 묻는 질문

이 레시피를 언제 사용해야 하는지, 무엇을 제공해야 하는지, 그리고 어떤 부분에서 사람의 검토가 여전히 중요한지에 대한 실용적인 답변

What should I prepare before using “Audit email tone for harshness, ambiguity, and passive aggression”?

For “Audit email tone for harshness, ambiguity, and passive aggression,” prepare Draft email, Relationship and history, and Required intent and boundaries. Replace placeholders only with information you can verify. If a detail is unknown, preserve that uncertainty explicitly instead of asking the model to infer it.

When is the “Audit email tone for harshness, ambiguity, and passive aggression” result not ready to use?

The result is not ready if it does not yet deliver the stated outcome—A phrase-level tone audit, risk explanation, and meaning-preserving revision—from the supplied evidence, or if it relies on unresolved assumptions, missing approvals, or invented details. Use the checks as release gates: revise the source inputs or assign a named, authorized reviewer instead of polishing an unsupported output.

Which AI tools have recorded tests for “Audit email tone for harshness, ambiguity, and passive aggression”?

The published test record for “Audit email tone for harshness, ambiguity, and passive aggression” lists ChatGPT as of 2026-08-28. This confirms recorded runs, not guaranteed compatibility or identical results in later product versions. For another tool or version, keep every constraint visible and repeat the result checks before use.

더 많은 탐색 방법