Skip to content

Jobo16/ielts-buddy / skills/ielts-writing-review

ielts-writing-review

Verified

批改雅思 Task 1 或 Task 2 作文,进行写前规划、原文证据批注和二改对照;需要可下载 Word 时生成并验证文档。用户提供作文即可使用,网站连接可选。

FileKindSize
SKILL.mdskill md2.1 KB
agents/openai.yamlconfig263 B
licenses/ielts-writing-review-skills.txtmarkdown1.0 KB
licenses/third-party-skill-sources.txtmarkdown1.2 KB
manifest.jsonconfig214 B
references/api-access.mdmarkdown1.1 KB
references/browser-routes.mdmarkdown587 B
references/ielts-task1-review/WORKFLOW.mdmarkdown12.0 KB
references/ielts-task1-review/references/review_format.mdmarkdown4.4 KB
references/ielts-task1-review/references/review_plan_example.jsonconfig3.6 KB
references/ielts-task1-review/references/scoring_guide.mdmarkdown1.9 KB
references/ielts-task1-review/references/teacher_style.mdmarkdown2.8 KB
references/ielts-task1-review/references/visual_analysis_protocol.mdmarkdown3.0 KB
references/ielts-task2-review/WORKFLOW.mdmarkdown10.8 KB
references/ielts-task2-review/references/review_format.mdmarkdown5.3 KB
references/ielts-task2-review/references/review_plan_example.jsonconfig4.0 KB
references/ielts-task2-review/references/scoring_guide.mdmarkdown2.0 KB
references/ielts-task2-review/references/teacher_style.mdmarkdown3.3 KB
references/skill-taxonomy.jsonconfig1.5 KB
references/writing-revision-loop/WORKFLOW.mdmarkdown5.7 KB
references/writing-task-planning/WORKFLOW.mdmarkdown3.2 KB
references/writing-vocabulary-handoff.mdmarkdown1.4 KB
scripts/ielts-task1-review/create_and_validate_task1_review.pyscript2.4 KB
scripts/ielts-task1-review/create_task1_review_docx.pyscript34.7 KB
scripts/ielts-task1-review/extract_docx_images.pyscript1.5 KB
scripts/ielts-task1-review/extract_task1_input.pyscript6.1 KB
scripts/ielts-task1-review/validate_task1_review_docx.pyscript9.1 KB
scripts/ielts-task2-review/create_review_docx.pyscript34.3 KB
scripts/ielts-task2-review/extract_task2_input.pyscript9.8 KB
scripts/ielts-task2-review/validate_review_docx.pyscript9.1 KB
scripts/writing-revision-loop/create_revision_report_docx.pyscript13.9 KB
scripts/writing-revision-loop/validate_revision_report_docx.pyscript3.3 KB

references/ielts-task1-review/references/visual_analysis_protocol.md

View on GitHub
# Visual Analysis Protocol

Inspect the visual before reading the student's answer in detail. This is mandatory: do not score, rewrite, or generate a model answer from the student's text alone.

## Universal Checklist

- Identify visual type: bar chart, line graph, table, pie chart, map, process, mixed chart.
- Read the task instruction and visual title.
- Record units: percentage, number, money, age, years, stages, locations.
- Identify categories, legends, axes, labels, and time periods.
- Identify the main features before details.
- Check whether exact values are printed or must be estimated.
- Do not invent precise values when the chart only supports approximation.

## Bar Charts

- Identify categories on each axis and legend groups.
- Find highest and lowest bars.
- Compare major groups rather than list every bar.
- Use `approximately`, `around`, `just under`, `slightly above`, and `roughly`.
- Watch for percentage/proportion wording.

## Line Graphs

- Identify starting and ending values, peaks, troughs, and major trend changes.
- Group lines by similar trends where possible.
- Avoid describing every small movement.
- Use trend language: rose, declined, remained stable, fluctuated, peaked, reached a low.

## Tables

- Identify row and column categories.
- Select key highest/lowest values, major contrasts, and exceptions.
- Avoid turning the table into a list.
- Group data by meaningful similarities.

## Pie Charts

- Identify each category and percentage/share.
- Compare largest and smallest shares.
- If there are multiple pies, compare changes across time or groups.

## Maps

- Identify before/after or location differences.
- Describe major changes in layout, land use, facilities, roads, and orientation.
- Use location language: to the north, in the centre, adjacent to, replaced by.

## Process Diagrams

- Identify start and end points.
- Count stages.
- Group stages if the process is long.
- Use passive voice where natural.
- Do not add causes or opinions.

## Mixed Charts

- Identify what each visual contributes.
- Summarize the relationship between visuals.
- Avoid overloading the answer with every value.

## Internal Visual Facts Note

Before reviewing, create a compact internal note:

```text
Type:
Units:
Categories/time:
Main overview:
Key comparisons:
Potential student traps:
```

Keep this note internal by default. Use it to drive comments, rewrites, scoring, and the model answer; only show it in the reviewed DOCX if the user asks for it.

## Review Focus By Visual Type

After identifying the visual type, use the type to choose the first Task Achievement comments:

- Bar chart, line graph, table, and pie chart: check measurement wording, overview, key feature selection, grouping, and comparison accuracy.
- Map: check before/after orientation, changed facilities, replaced areas, and location language.
- Process: check start/end points, sequence, stage grouping, passive voice, and whether the answer invents causes.
- Mixed visual: check whether the answer explains the relationship between visuals instead of listing values mechanically.
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 implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall