Jobo16/ielts-buddy / skills/ielts-writing-review
ielts-writing-review
Verified批改雅思 Task 1 或 Task 2 作文,进行写前规划、原文证据批注和二改对照;需要可下载 Word 时生成并验证文档。用户提供作文即可使用,网站连接可选。
references/ielts-task1-review/references/review_format.md
View on GitHub# Reviewed DOCX Format
Use this structure for every reviewed IELTS Academic Task 1 document.
## Sections
1. Original DOCX content
- Keep the student's original file content at the start of the reviewed DOCX.
- For DOCX input, this preserves the original prompt and embedded visual, so do not repeat them.
2. Internal visual facts note
- Build this before reviewing, but do not show it in the DOCX by default.
- Include a visible `Visual Facts` section only if the user explicitly asks for it.
3. Reviewed answer content
- Use `review_units.original` to locate the matching original answer paragraph in the copied DOCX.
- Word comments must be anchored directly to specific target words/phrases inside the original paragraph.
- For DOCX input, the matched paragraph must be one of the extracted student answer paragraphs.
- Do not append a second copy of the student's answer just to hold comments.
- Insert the italic rewrite immediately after the matched original paragraph when useful.
- Do not use a visible `Reviewed Answer` heading.
4. Score lines and focused feedback
- Start this page after the reviewed answer content.
- Do not use a visible `Score` heading.
- Task Achievement
- Coherence & Cohesion
- Lexical Resource
- Grammatical Range & Accuracy
- Overall
- Each score may be a whole or half band; do not round criterion estimates to integers.
5. `冲刺 Band 7.5 / 8.0`
- This is the only visible section title retained after the answer review.
- Keep this on the same page as the score lines.
- Mention blockers preventing stable Band 7.5 first.
- Then mention the most useful move toward 8.0.
6. Model answer
- Start this on a new page after the score/focus page.
- Do not use a visible `Model Answer` heading.
- 150-200 words.
- Exactly 4 paragraphs:
1. Introduction: paraphrase the task prompt.
2. Overview: begin with `Overall` and summarize the main features.
3. Body paragraph 1: report the first logical group of details.
4. Body paragraph 2: report the second logical group of details.
- Leave one blank line between model answer paragraphs.
- Accurate to the visual.
- Stable Band 8.0 standard: skilful key feature selection, clear overview, logical grouping, precise data language, natural comparisons, well-managed cohesion, and mostly error-free grammar.
## Filename Rules
- DOCX input: output beside the input file.
- `MyAnswer.docx` -> `MyAnswer(reviewed).docx`
- If that exists, use `MyAnswer(reviewed 2).docx` or another non-overwriting variant.
- Pasted text input: output to the current user's Desktop as `IELTS_Task1_Reviewed_YYYYMMDD_HHMM.docx`.
- Never overwrite the original answer unless explicitly requested.
## Comment Rules
- Use real Word comments.
- Use `Cyber Esme` as the Word comment author.
- Anchor comments to the shortest useful phrase.
- For DOCX input, comments must be placed in the copied original answer paragraphs, not in newly appended duplicate answer text.
- Do not anchor comments to prompt text, image captions, score sections, model answers, or other non-answer paragraphs.
- If a non-empty `target` cannot be found inside the matched answer paragraph, fix the review plan instead of falling back to the whole paragraph.
- Use concise Simplified Chinese. Keep quoted English targets and corrected English phrases unchanged.
- Mark Task Achievement problems early: wrong chart type, wrong units, missing overview, inaccurate values, or poor key feature selection.
## Font And Pagination Rules
- Use Times New Roman for all added review text and comments.
- Preserve the copied DOCX's original `word/document.xml` root namespace declarations and `mc:Ignorable` prefix list.
- Do not include `Visual Facts` in the reviewed DOCX unless specifically requested.
- Do not add big visible section headings such as `Task`, `Reviewed Answer`, `Score`, or `Model Answer`.
- Insert a page break before the score and feedback page.
- Keep the score lines and `冲刺 Band 7.5 / 8.0` together.
- Insert another page break before the model answer.
## Cleanup Rules
- Remove temporary files created only for the review process after final DOCX validation.
- Typical byproducts: `review_plan_*.json`, `系统临时目录/ielts_task1_images_*` scratch image folders, temporary unpacked DOCX folders.
- Prefer writing temporary files to `系统临时目录`.
- Do not delete source answers, final reviewed DOCX files, or bundled Skill references.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |