Yila-AI/awesome-defensive-writing / skills/yila-clear-writing
yila-clear-writing
VerifiedDiagnose and revise AI defensive padding in drafts, reports, emails, research prose and public explanations when the user requests less hedging or clearer claims. Preserve evidence strength and meaningful reader guidance.
references/collaboration-en.md
View on GitHub# Collaboration
**English** | [简体中文](collaboration-zh.md)
Choose a task, copy a prompt and add your material. Follow the case link for supplied facts, a revision and the reasoning behind it.
## DW-025 · Progress follow-up
Make the supplied material clear, direct and informative. Organize it around
the judgment or action the reader needs. Remove repetitive retreat and empty
preambles. Ground facts, numbers, scope, responsibility and commitments in
the material; keep meaningful conditions next to the claims they qualify.
List missing facts separately.
Task: Ask about a specific deliverable, agreed timing and needed reply. Preserve
courtesy, remove repeated apologies and do not turn a target date into a
prior commitment.
Output: A short follow-up naming the deliverable, actual agreement and requested
reply.
Input material:
Deliverable: [fill in]
Actual agreement: [fill in]
Requested information: [fill in]
Related case: EX-25 in examples-en.md
## DW-026 · Disagree with reasons
Make the supplied material clear, direct and informative. Organize it around
the judgment or action the reader needs. Remove repetitive retreat and empty
preambles. Ground facts, numbers, scope, responsibility and commitments in
the material; keep meaningful conditions next to the claims they qualify.
List missing facts separately.
Task: State the disagreement, evidence, impact and alternative. Keep useful
relational courtesy without pretending agreement or presenting preferences
as facts.
Output: A sendable disagreement with its reason and alternative.
Input material:
Proposal: [fill in]
Disagreement: [fill in]
Evidence: [fill in]
Alternative: [fill in]
Related case: EX-09 in examples-en.md
## DW-027 · Decline an added request
Make the supplied material clear, direct and informative. Organize it around
the judgment or action the reader needs. Remove repetitive retreat and empty
preambles. Ground facts, numbers, scope, responsibility and commitments in
the material; keep meaningful conditions next to the claims they qualify.
List missing facts separately.
Task: State the supported scope and what cannot be committed to, with a relevant
reason or viable alternative. Do not erase existing obligations or invent
concessions.
Output: Accepted scope, the added work that cannot be committed to and viable
alternatives.
Input material:
Request: [fill in]
Responsibilities: [fill in]
Resources: [fill in]
Alternatives: [fill in]
Related case: EX-09 in examples-en.md
## DW-028 · Ask for help
Make the supplied material clear, direct and informative. Organize it around
the judgment or action the reader needs. Remove repetitive retreat and empty
preambles. Ground facts, numbers, scope, responsibility and commitments in
the material; keep meaningful conditions next to the claims they qualify.
List missing facts separately.
Task: State the goal, attempts and specific blocker, then an answerable request.
Remove self-deprecation without assuming the recipient owes a complete
solution.
Output: A help request with goal, attempted steps, blocker and a specific question.
Input material:
Problem: [fill in]
Attempted steps: [fill in]
Requested help: [fill in]
Related case: EX-10 in examples-en.md
## DW-029 · Contact a supervisor
Make the supplied material clear, direct and informative. Organize it around
the judgment or action the reader needs. Remove repetitive retreat and empty
preambles. Ground facts, numbers, scope, responsibility and commitments in
the material; keep meaningful conditions next to the claims they qualify.
List missing facts separately.
Task: Organize the email around real identity, relevant experience, research
interest and a specific request. Preserve courtesy; do not fabricate fit,
reading experience or availability.
Output: An email subject and body with actual identity, relevant experience and a
specific request.
Input material:
Identity: [fill in]
Actual experience: [fill in]
Interests: [fill in]
Purpose: [fill in]
Related case: EX-10 in examples-en.md
## DW-030 · Apology and repair
Make the supplied material clear, direct and informative. Organize it around
the judgment or action the reader needs. Remove repetitive retreat and empty
preambles. Ground facts, numbers, scope, responsibility and commitments in
the material; keep meaningful conditions next to the claims they qualify.
List missing facts separately.
Task: Keep acknowledgment, actual impact and feasible repair. Remove repetitive
self-blame and excuses without turning an apology into a responsibility-free
status update.
Output: An apology and repair note stating what happened, impact and feasible
remedy.
Input material:
Facts: [fill in]
Responsibility: [fill in]
Impact: [fill in]
Feasible repair: [fill in]
Related case: EX-10 in examples-en.md
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |