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

ieee-summarize

Summarize, organize, and normalize messy research materials into an IEEE-ready writing brief before manuscript drafting. Use when Codex needs to process a folder or collection of experiment logs, code files, AI chat exports, idea notes, literature summaries, related-work notes, copied introduction excerpts, Zotero-derived paper summaries, tables, figures, or scattered Markdown/text records and convert them into structured inputs for ieee-writing, ieee-experiment, ieee-citation, ieee-reviewer, or ieee-response.

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

설치 방법 보기

포함된 파일(6)

  • SKILL.md3.6 KB
  • agents/openai.yaml259 B
  • manifest.yaml2.6 KB
  • references/folder-ingestion.md2.2 KB
  • references/research-brief-template.md1.8 KB
  • scripts/inventory_research_folder.py3.5 KB

SKILL.md(원문)

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

IEEE Summarize Router

Use this skill before ieee-writing when the user's research materials are scattered, chronological, duplicated, or not yet in manuscript structure. The output is not final prose; it is an evidence-grounded research brief that later writing skills can use.

Do not turn messy notes into polished claims by guessing. Preserve uncertainty, source paths, missing evidence, and contradictions.

Routing Protocol

  1. Read manifest.yaml.
  2. Read every file listed under always_load.
  3. Detect the request axes:
    • material_scope: folder / pasted-notes / code-and-logs / literature-pack / mixed.
    • output_target: research-brief / writing-input / experiment-summary / related-work-seed / claim-evidence-seed.
    • cleanup_level: inventory / standard / deep.
  4. State the detected axes in one short line.
  5. If a folder path is provided, inventory first:
    • Prefer scripts/inventory_research_folder.py <folder>.
    • If the script is unsuitable, use rg --files <folder>.
    • Do not read every large file blindly. Select representative and high-signal files by category.
  6. Map raw material into IEEE evidence slots:
    • problem object and operating condition,
    • engineering harm or practical motivation,
    • method idea and implementation clues from notes/code,
    • datasets, baselines, metrics, ablations, robustness, complexity, and reproducibility,
    • related-work families and closest-prior-work candidates,
    • contribution candidates and conclusion candidates.
  7. Preserve provenance. Every important extracted point should include a file path, heading, filename, or note source when available.
  8. Mark solid, partial, unclear, or missing for each evidence block.
  9. Hand off to the next skill explicitly: ieee-writing, ieee-experiment, ieee-citation, ieee-reviewer, or ieee-polishing.

Output Contract

Default output:

Detected axes: material_scope=..., output_target=..., cleanup_level=...

Material inventory
- Notes:
- Code:
- Experiments:
- Literature:
- Figures/tables:
- Unknown / skipped:

IEEE Research Brief
- Working title:
- Research object:
- Operating condition / constraints:
- Engineering harm:
- Core method:
- Implementation clues:
- Experiment evidence:
- Related-work seed:
- Contribution candidates:
- Conclusion candidates:
- Missing evidence:
- Contradictions / risks:

Next skill handoff
- Recommended next skill:
- Prompt-ready brief:

For folder-level work, create or update a Markdown file only when the user asks for a file. Suggested filename: ieee-research-brief.md.

Red Lines

Do not invent paper titles, citations, datasets, numerical results, code behavior, reviewer comments, or experiment outcomes.

Do not treat AI chat exports as verified evidence. Label them as ideation unless confirmed by code, logs, data, or papers.

Do not summarize copied paper introductions into plagiarism-ready text. Extract reusable background logic, domain motivation, and citation roles instead.

Do not remove negative results or failed experiments; classify them as limitation, ablation clue, or future-work evidence.

리뷰

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

댓글

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

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

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. 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-skills3912026년 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-skills3912026년 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-skills3912026년 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-skills3912026년 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-skills3912026년 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-skills3912026년 8월 12일 업데이트

CloudWave818의 스킬 모두 보기

이 스킬의 문제 신고