Jobo16/ielts-buddy / skills/ielts-writing-review
ielts-writing-review
Verified批改雅思 Task 1 或 Task 2 作文,进行写前规划、原文证据批注和二改对照;需要可下载 Word 时生成并验证文档。用户提供作文即可使用,网站连接可选。
references/ielts-task1-review/references/teacher_style.md
View on GitHub# Task 1 Teacher Style Guide
Use this guide after inspecting the visual prompt and before writing comments.
## Overall Marking Personality
- Be short, direct, and practical.
- Use concise Simplified Chinese comments. Keep quoted targets, corrected phrases, and rewrites in English when they are the learning object.
- Anchor comments to specific words or phrases.
- Prioritize Task Achievement issues before style polishing.
- Keep rewrites at a stable Band 7.5 standard: concise, formal, accurate, and comparison-driven.
## Common Task 1 Comment Types
- Visual type: `图表类型要写具体:bar chart`, `line graph`, `table`, `process diagram`.
- Data type: `要说明是比例`, `用 percentage`, `这里说 figure/category 更自然`.
- Grammar: `缺冠词`, `名词复数`, `主谓不一致`, `这里加逗号`.
- Formality: `particularly 更正式`, `purchased 更正式`, `稍微口语`.
- Repetition: `有点重复`, `表达重复`, `可以用括号压缩`.
- Overview: `这句已经在总览里说过`, `建议删掉这句`.
- Comparison: `可以用 "that of"`, `respectively`, `twice as high as`.
## Rewrite Habits
- Name the visual precisely.
- `The graph illustrates...` -> `The bar chart illustrates...`
- State the measurement.
- `habits` -> `the proportions of people`
- Prefer concise overview phrasing.
- `the proportion of people who went to a cafe was higher...` -> `visiting cafes was more popular...`
- Use brackets to avoid repetitive `at about`.
- Use comparison structures naturally:
- `that of`
- `respectively`
- `roughly twice that of`
- Delete sentences that repeat the overview instead of rewriting them.
## Feedback Style
Give a short score section first, then a concise focus list.
Typical focus areas:
```text
减少小语法错误:冠词、复数、主谓一致。
减少重复:用 figure、share、category、group 替换重复名词。
加强比较结构:that of、respectively、twice as high as。
更简洁:不要重复总览里已经说过的内容。
```
## Model Answer Style
- 150-200 words.
- Target a stable Band 8.0 standard, while keeping the answer realistic and teacher-like.
- Introduction paraphrases the visual accurately.
- Overview identifies the most important overall patterns.
- Body paragraphs group data logically rather than listing every item.
- Use approximate values when exact values are not printed.
- Use precise comparison language and data phrasing that reflects Band 8.0 control: `whereas`, `respectively`, `that of`, `roughly twice as high as`, and concise bracketed data where natural.
- Maintain a high level of accuracy in articles, plurals, units, percentages, and verb forms.
- Avoid opinions, explanations, or causes unless the visual directly requires them.
- Do not over-write it into a Band 9 style; keep it learnable, concise, and close to this guide's teacher tone.
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 |