Diagnose observable writing problems without unreliable claims about whether AI produced the text. 제공할 내용: Draft and context, Audience and voice reference, Review scope. 예상 결과: An evidence-linked style audit with priorities, revision operations, and a human verification pass.
1
맥락 추가
텍스트는 이 브라우저에 유지됩니다. AILesson Prompts는 이를 모델이나 서버로 보내지 않습니다.
2
프롬프트
채워지지 않은 필드는 플레이스홀더로 표시되므로 프롬프트를 복사하고 편집할 수 있습니다
Audit the supplied content for observable repetition, vagueness, and formulaic writing.
Exact draft, purpose, format, status, and known authorship context:
[draft]
Audience, effect, approved samples, terminology, invariant facts, and style boundaries:
[voice]
Diagnosis or revision scope, depth, priorities, length, and protected text:
[scope]
Do not claim to detect whether AI wrote the text; authorship cannot be reliably inferred from style alone. Instead cite exact locations and diagnose observable effects: repeated claims or structure, empty abstraction, unsupported generalization, generic transitions, excessive symmetry, uniform sentence rhythm, redundant conclusion, vague actors or verbs, nominalization, cliché, unexplained jargon, false precision, abrupt tone shifts, and voice mismatch. Distinguish intentional repetition from accidental redundancy and conventional genre language from genuine weakness. For each issue state evidence, reader effect, severity, confidence, and a revision operation. Preserve facts, meaning, quotations, terminology, and author intent. If revision is authorized, provide a minimal revised passage plus a change log; otherwise do not rewrite. End with a priority order and checks requiring human judgment of voice and factual fidelity.
기본적으로 비공개프롬프트 구성은 브라우저에서 로컬로 이루어집니다. 조직에서 허용하지 않는 한 기밀 정보를 AI 서비스에 입력하지 마세요.
입력에서 결과까지
적용 예시
구체적인 맥락이 이 레시피를 바로 사용할 수 있는 결과로 바꾸는 방법을 확인하세요
실제 입력
Draft and context
LinkedIn draft: In today's fast-paced world, effective handoffs are more important than ever. Handoffs are important because they help teams work effectively. By optimizing handoffs, organizations can unlock efficiency, enhance collaboration, and drive meaningful outcomes. First, clarify ownership. Second, clarify expectations. Third, clarify communication. Ultimately, clear handoffs are the key to success. In conclusion, organizations should prioritize clear handoffs to achieve success.
Audience and voice reference
Operations leads who prefer direct, evidence-aware advice. Approved voice sample starts with a concrete workflow symptom, uses 'owner,' 'accepter,' and 'acceptance evidence,' and avoids broad business claims. Invariant idea: a handoff needs an owner and accepter; no measured outcome evidence supplied.
Review scope
Diagnose and minimally revise. Under 700 characters. Prioritize vagueness and repetition. Preserve the distinction between owner and accepter. Do not add statistics, personal anecdotes, or claims about success.
예시 출력
Authorship note: these patterns do not establish whether AI or a person wrote the draft.
High priority
• Opening: “today's fast-paced world” provides no situation or decision. Reader effect: delays the usable point. Replace with a concrete stalled-review symptom. High confidence.
• Outcome claims: “unlock efficiency, enhance collaboration, and drive meaningful outcomes” are abstract and unsupported. Reader effect: sounds promotional but gives nothing to verify. Remove rather than strengthen.
• Conclusion: “key to success” and the final sentence repeat the same unsupported claim. Keep one practical CTA instead.
Medium priority
• Three-item sequence repeats “clarify” while hiding who decides what. Replace generic nouns with owner, accepter, acceptance evidence, and escalation. The parallel structure itself is not a problem; its categories are vague.
Minimal revision
“Work is marked ready, but nobody knows who can accept it. Check one recurring handoff: Who owns the current step? Who accepts it next? What evidence counts as accepted? Who resolves a delay or disagreement? A status field can display these answers, but the team still has to define them. Audit one handoff before adding another reminder.”
Change log: removed two generic openings, three unsupported outcome phrases, and duplicate success conclusions; replaced vague categories with the approved operational terms; preserved the owner-versus-accepter distinction. Human check: confirm “status field” fits the account voice and that the final CTA matches the intended product context.
효과가 있는 이유
1
Observable diagnosis improves prose without pretending style can prove authorship.
2
Reader-effect and confidence labels prevent mechanical deletion of intentional choices.
결과 확인
Does every diagnosis cite exact text and an observable reader effect?
Does the audit avoid unsupported AI-authorship judgments?
Do revisions preserve facts, voice, intentional repetition, and protected text?
안심하고 사용하세요
자주 묻는 질문
이 레시피를 언제 사용해야 하는지, 무엇을 제공해야 하는지, 그리고 어떤 부분에서 사람의 검토가 여전히 중요한지에 대한 실용적인 답변
What should I prepare before using “Audit content for repetition, vagueness, and machine-like writing”?
For “Audit content for repetition, vagueness, and machine-like writing,” prepare Draft and context, Audience and voice reference, and Review scope. 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 content for repetition, vagueness, and machine-like writing” result not ready to use?
The result is not ready if it does not yet deliver the stated outcome—An evidence-linked style audit with priorities, revision operations, and a human verification pass—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 content for repetition, vagueness, and machine-like writing”?
The published test record for “Audit content for repetition, vagueness, and machine-like writing” 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.
ChatGPT
