본문으로 건너뛰기
cccskills
무료GitHub에 공개

ieee-reviewer

Review IEEE conference, journal, Transactions, Letters, or magazine manuscripts from a technical reviewer perspective using routed IEEE review gates. Use when evaluating scope fit, novelty, validity, data, clarity, compliance, advancement, engineering significance, method soundness, experiment sufficiency, baseline fairness, figure/table quality, formatting risks, rejection risk, major revision strategy, pre-submission readiness, or the quality and specificity of reviewer comments that may be generic, careless, contradictory, or possibly AI-generated.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(38)

  • SKILL.md2.7 KB
  • agents/openai.yaml207 B
  • manifest.yaml3.4 KB
  • static/core/output-format.md318 B
  • static/core/stance.md471 B
  • static/core/workflow.md461 B
  • static/fragments/domain/ai-ml.md169 B
  • static/fragments/domain/circuits.md137 B
  • static/fragments/domain/communications.md158 B
  • static/fragments/domain/control.md155 B
  • static/fragments/domain/embedded-systems.md152 B
  • static/fragments/domain/general-engineering.md156 B
  • static/fragments/domain/power-energy.md169 B
  • static/fragments/domain/robotics.md129 B
  • static/fragments/domain/signal-processing.md149 B
  • static/fragments/review_scope/abstract-intro.md283 B
  • static/fragments/review_scope/experiments.md201 B
  • static/fragments/review_scope/figures-tables.md349 B
  • static/fragments/review_scope/full-manuscript.md221 B
  • static/fragments/review_scope/method.md260 B
  • static/fragments/review_scope/rebuttal-readiness.md309 B
  • static/fragments/review_scope/review-comment-audit.md1.3 KB
  • static/fragments/strictness/harsh.md194 B
  • static/fragments/strictness/quick.md84 B
  • static/fragments/strictness/standard.md128 B
  • static/fragments/venue/conference.md211 B
  • static/fragments/venue/generic.md111 B
  • static/fragments/venue/journal.md144 B
  • static/fragments/venue/letter.md167 B
  • static/fragments/venue/magazine.md138 B
  • static/fragments/venue/transaction.md181 B
  • static/gates/advancement.md337 B
  • static/gates/clarity.md383 B
  • static/gates/compliance.md447 B
  • static/gates/data.md382 B
  • static/gates/novelty.md278 B
  • static/gates/scope.md316 B
  • static/gates/validity.md309 B

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

IEEE Reviewer Router

Use this skill to simulate a strict IEEE-style technical review. The goal is to find rejection risks and actionable fixes, not to flatter the manuscript.

Do not invent reviewer identities or editorial decisions. Review only the supplied manuscript facts and clearly mark missing materials.

Routing Protocol

  1. Read manifest.yaml.
  2. Read every file listed under always_load.
  3. Detect the axes:
    • venue_type: transaction / journal / letter / conference / magazine / generic.
    • review_scope: full-manuscript / abstract-intro / method / experiments / figures-tables / rebuttal-readiness / review-comment-audit.
    • domain: ai-ml / communications / control / signal-processing / power-energy / circuits / robotics / embedded-systems / general-engineering.
    • strictness: quick / standard / harsh.
  4. State the detected axes in one short line.
  5. Load only the matching fragments and gates.
  6. Review using IEEE gates in this order:
    • scope,
    • novelty,
    • validity,
    • data,
    • clarity,
    • compliance,
    • advancement.
  7. Add first-impression checks for figures, tables, formatting, notation, and language.
  8. For review-comment audits, judge observable quality problems rather than accusing a reviewer of using AI.
  9. Return findings ordered by severity.

Output Contract

Default output:

Review setup
- Detected axes:
- Assessment boundary:
- Central claim:
- Visible evidence:

Major rejection risks
- [severity] issue -> why it matters -> fix

Technical review
- Scope:
- Novelty:
- Validity:
- Data and experiments:
- Clarity:
- Compliance:
- Advancement:

Presentation and first impression
- Figures/tables:
- Formatting/notation:
- Writing:

Actionable revision plan
1. ...

Likely decision posture
- [bounded, non-editorial assessment]

Use Critical, Major, and Minor severity labels.

Red Lines

Do not claim the editor's final decision.

Do not invent experiments, results, citations, line numbers, figure contents, or reviewer biographies.

Do not turn the review into author rebuttal unless the user asks for ieee-response.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

CloudWave818/ieee-skills4042026년 8월 12일 업데이트

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

CloudWave818/ieee-skills4042026년 8월 12일 업데이트

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

CloudWave818/ieee-skills4042026년 8월 12일 업데이트

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

CloudWave818/ieee-skills4042026년 8월 12일 업데이트

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

CloudWave818/ieee-skills4042026년 8월 12일 업데이트

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

CloudWave818/ieee-skills4042026년 8월 12일 업데이트

CloudWave818의 스킬 모두 보기

이 스킬의 문제 신고