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/proposals-en.md
View on GitHub# Proposals
**English** | [简体中文](proposals-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-013 · Problem statement
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: Explain the affected group, current obstacle and consequences. Describe
scale and urgency only when supported; remove grand openings and unsupported
self-justification.
Output: A problem statement identifying affected users, obstacle, consequence and
evidence.
Input material:
Background: [fill in]
Affected users: [fill in]
Evidence: [fill in]
Related case: EX-05 in examples-en.md
## DW-014 · Research objectives
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: Separate research questions, planned actions and assessable outputs. Keep
objectives distinct from achieved results; avoid vague attempts that cannot
be evaluated.
Output: Objectives with the research question, planned action and assessable output.
Input material:
Research questions: [fill in]
Resources: [fill in]
Objectives draft: [fill in]
Related case: EX-05 in examples-en.md
## DW-015 · Novelty without inflation
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: Compare additions against prior approaches with evidence. Avoid first-ever
claims without a sufficient search, while retaining supported contributions
without ritual modesty.
Output: A comparison of prior approaches, the proposed addition and evidence; then
novelty copy.
Input material:
Proposed additions: [fill in]
Prior approaches: [fill in]
Search scope: [fill in]
Related case: EX-04 in examples-en.md
## DW-016 · Technical approach
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: Describe stages, inputs, outputs, dependencies and decision points. Keep
prerequisites and fallback paths; remove nonoperational caution without
inventing experimental parameters.
Output: Stages with inputs, actions, outputs, dependencies and decision points.
Input material:
Stages: [fill in]
Dependencies: [fill in]
Known parameters: [fill in]
Options: [fill in]
Related case: EX-06 in examples-en.md
## DW-017 · Feasibility assessment
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: Separate available capabilities, pending resources and untested assumptions.
Assess feasibility proportionately; do not treat all risk as failure or
planned resources as available.
Output: Available, pending and unverified conditions; then a feasibility assessment
with grounds.
Input material:
Current resources: [fill in]
Dependencies: [fill in]
Preliminary results: [fill in]
Related case: EX-06 in examples-en.md
## DW-018 · Risks and fallbacks
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: Include only risks that change selection, cost or schedule. Give trigger,
impact and response; do not invent probabilities. State what information is
needed for unresolved assessments.
Output: Risk triggers, impacts, responses and priorities.
Input material:
Goal: [fill in]
Resources: [fill in]
Dependencies: [fill in]
Fallback actions: [fill in]
Related case: EX-06 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 |