Skip to content
cccskills
FreePublished on GitHub

ieee-response

Draft, diagnose, and improve IEEE rebuttals, revision plans, cover letters, response letters, and point-by-point replies using routed reviewer-comment handling. Use when responding to IEEE reviewer or editor comments about novelty, scope, method, experiments, baselines, figures, tables, citations, writing, LaTeX formatting, limitations, compliance, technical correctness, or reviewer comments that appear generic, contradictory, unsupported, careless, or possibly AI-generated.

The English summary is being prepared. Showing the original description.

CloudWave818/ieee-skills
See how to install

Files included (40)

  • SKILL.md2.8 KB
  • agents/openai.yaml213 B
  • manifest.yaml4.4 KB
  • static/core/output-format.md431 B
  • static/core/response-pattern.md1.3 KB
  • static/core/stance.md396 B
  • static/core/workflow.md599 B
  • static/fragments/action_type/acknowledge-limitation.md381 B
  • static/fragments/action_type/add-citation.md260 B
  • static/fragments/action_type/add-experiment.md235 B
  • static/fragments/action_type/add-explanation.md242 B
  • static/fragments/action_type/correct-error.md265 B
  • static/fragments/action_type/disagree-with-evidence.md284 B
  • static/fragments/action_type/improve-figure-table.md250 B
  • static/fragments/action_type/revise-text.md232 B
  • static/fragments/comment_type/baseline.md388 B
  • static/fragments/comment_type/citation.md376 B
  • static/fragments/comment_type/experiment.md406 B
  • static/fragments/comment_type/figure-table.md389 B
  • static/fragments/comment_type/format.md356 B
  • static/fragments/comment_type/limitation.md309 B
  • static/fragments/comment_type/method.md398 B
  • static/fragments/comment_type/novelty.md359 B
  • static/fragments/comment_type/review-quality.md895 B
  • static/fragments/comment_type/scope.md395 B
  • static/fragments/comment_type/technical-error.md320 B
  • static/fragments/comment_type/writing.md371 B
  • static/fragments/evidence_status/evidence-added.md263 B
  • static/fragments/evidence_status/evidence-planned.md260 B
  • static/fragments/evidence_status/evidence-unavailable.md217 B
  • static/fragments/evidence_status/text-only-fix.md201 B
  • static/fragments/response_stage/cover-letter.md288 B
  • static/fragments/response_stage/major-revision.md263 B
  • static/fragments/response_stage/minor-revision.md184 B
  • static/fragments/response_stage/rebuttal.md219 B
  • static/fragments/response_stage/resubmission.md266 B
  • static/fragments/tone/concise.md185 B
  • static/fragments/tone/firm.md285 B
  • static/fragments/tone/standard.md184 B
  • static/fragments/tone/very-polite.md278 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

IEEE Response Router

Use this skill to convert reviewer criticism into manuscript actions and precise, respectful point-by-point replies.

Do not write a defensive response. Do not promise changes that the manuscript does not make. Follow the routing protocol and load the selected fragments.

Routing Protocol

  1. Read manifest.yaml.
  2. Read every file listed under always_load.
  3. Detect the axes:
    • comment_type: novelty / scope / method / experiment / baseline / figure-table / citation / writing / format / limitation / technical-error / review-quality.
    • action_type: add-experiment / add-explanation / revise-text / correct-error / add-citation / improve-figure-table / acknowledge-limitation / disagree-with-evidence.
    • response_stage: rebuttal / major-revision / minor-revision / resubmission / cover-letter.
    • evidence_status: evidence-added / evidence-planned / evidence-unavailable / text-only-fix.
    • tone: standard / concise / very-polite / firm.
  4. State the detected axes in one short line when useful.
  5. Load only the matching fragments.
  6. For each reviewer comment, produce:
    • issue classification,
    • required manuscript action,
    • evidence needed,
    • response wording,
    • revision-location placeholder if exact page/line is unknown.
  7. For review-quality concerns, respond to the observable inconsistency or lack of support. Do not accuse the reviewer of using AI unless the user provides direct evidence.

Output Contract

Default point-by-point format:

Reviewer comment:

Classification:
- comment_type:
- action_type:
- evidence_status:

Response:
[polite, specific response]

Manuscript revision:
[what changed and where]

Evidence:
[new experiment/result/citation/figure/textual clarification]

For multiple comments, add a Revision action list before the detailed responses.

For cover letters, summarize major changes, added experiments, figure/table improvements, and remaining limitations without overselling.

Red Lines

Do not invent page numbers, line numbers, experiments, results, citations, or editor instructions.

Do not say "we have addressed all concerns" unless every concern is visibly addressed.

Do not dismiss reviewer comments as misunderstandings without first improving manuscript clarity.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

ieee-citation

Free

Check, clean, verify, and improve IEEE citations, references, BibTeX entries, citation positioning, related-work logic, DOI metadata, venue names, and reference formatting using routed citation and metadata guidance. Use when preparing IEEE manuscripts, fixing bibliography errors, verifying reference completeness, improving related work, checking whether citations support claims, or identifying missing classic/recent baselines.

The English summary is being prepared. Showing the original description.

CloudWave818/ieee-skills391Updated Aug 12, 2026

ieee-experiment

Free

Design, audit, and strengthen experimental validation for IEEE manuscripts using routed claim-evidence checks. Use when planning experiments, selecting baselines, designing ablations, choosing metrics, checking fairness, adding robustness tests, explaining results, analyzing complexity, building claim-to-evidence matrices, or responding to reviewer concerns about insufficient experiments.

The English summary is being prepared. Showing the original description.

CloudWave818/ieee-skills391Updated Aug 12, 2026

ieee-figure-table

Free

Audit, redesign, generate, and improve IEEE manuscript figures, tables, captions, result presentation, plotting scripts, visual polish, hybrid Python/R plus vector-editor workflows, publication-ready matplotlib house style, and layout using routed visual-evidence checks. Use when checking or creating plot readability, axes, legends, line overlap, table structure, metric reporting, captions, grayscale accessibility, IEEE one-column/two-column layout, figure/table placement, claim-evidence mapping, reviewer first-impression risks, matplotlib/seaborn or ggplot2 figure code, SVG/PDF/TIFF/PNG export, Illustrator/Inkscape/PowerPoint/Figma finishing plans, or IEEE-style engineering evidence graphics.

The English summary is being prepared. Showing the original description.

CloudWave818/ieee-skills391Updated Aug 12, 2026

ieee-latex

Free

Diagnose, fix, and improve IEEEtran LaTeX manuscripts using routed template, layout, float, equation, algorithm, table, bibliography, and PDF-compliance guidance. Use when fixing IEEE LaTeX compile errors, overfull boxes, float placement, two-column layout, figure sizing, tables, equations, algorithms, BibTeX, citation commands, template compliance, or final submission PDF checks.

The English summary is being prepared. Showing the original description.

CloudWave818/ieee-skills391Updated Aug 12, 2026

ieee-paper-reader

Free

Read, decompose, and analyze IEEE-style papers using routed technical-reading workflows. Use when extracting problem setting, object-method-condition logic, contributions, method pipeline, equations, datasets, baselines, metrics, ablations, limitations, replication details, citation role, related-work positioning, implementation notes, or reviewer-style assessment from a paper, PDF, abstract, or manuscript excerpt.

The English summary is being prepared. Showing the original description.

CloudWave818/ieee-skills391Updated Aug 12, 2026

ieee-polishing

Free

Polish, translate, diagnose, and restructure technical manuscript text into IEEE-style academic English using routed failure-mode guidance. Use for IEEE abstracts, introductions, related work, methods, experiments, conclusions, figure captions, rebuttals, Chinese-to-English technical writing, AI-like or template-like academic prose, and engineering prose that needs clearer problem logic, contribution framing, method rationale, evidence discipline, natural author voice, or reviewer-ready wording.

The English summary is being prepared. Showing the original description.

CloudWave818/ieee-skills391Updated Aug 12, 2026

See all skills by CloudWave818

Report a problem with this skill