Ieee Response logo

Ieee Response

Community
CloudWave818
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.

Overview

PublisherCloudWave818
Repositoryieee-skills
Skill nameieee-response
Stars
405
Forks
22
Bundled files
39
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 39 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by CloudWave818 on GitHub. Read the source before you install it.

Installation

Install the Ieee Response AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/CloudWave818/ieee-skills/tree/main/skills/ieee-response
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/CloudWave818/ieee-skills.git /tmp/ieee-skills
mkdir -p .claude/skills
cp -r /tmp/ieee-skills/skills/ieee-response .claude/skills/ieee-response
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Ieee Response in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Ieee Response on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Ieee Response is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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:

text
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.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Ieee Response AI skill do?

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.

Why use Ieee Response on TypingMind?

Because you install it once and use it with any model. Ieee Response is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Ieee Response in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/CloudWave818/ieee-skills/tree/main/skills/ieee-response. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Ieee Response?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Ieee Response?

As many as you like. As long as a model supports skills, you can use Ieee Response with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Ieee Response AI skill free?

Yes. It is published on GitHub by CloudWave818 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇