Ieee Figure Table logo

Ieee Figure Table

Community
CloudWave818
ieee-figure-table

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.

Overview

PublisherCloudWave818
Repositoryieee-skills
Skill nameieee-figure-table
Stars
405
Forks
22
Bundled files
46
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.

  • 46 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 Figure Table 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-figure-table
  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-figure-table .claude/skills/ieee-figure-table
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Ieee Figure Table 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 Figure Table 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 Figure Table 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 Figure Table Router

Use this skill to make figures and tables function as professional IEEE evidence. The goal is not decoration; it is readable, fair, claim-aligned visual proof that still works after IEEE column scaling.

Do not rely on general design intuition alone. 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:
    • visual_type: line-plot / bar-chart / scatter / confusion-matrix / comparison-table / ablation-table / architecture-diagram / algorithm-flowchart / multi-panel / generic.
    • check_type: readability / accessibility / caption / layout / evidence-mapping / statistical-presentation.
    • failure_mode: blurry-figure / bad-axis / overlapping-legend / misleading-scale / inconsistent-precision / weak-caption / unreadable-two-column.
    • stage: audit / redesign / caption-writing / latex-placement.
    • backend: python / r / hybrid / no-plot. Use hybrid when a figure is partly generated from data/code and partly finished in a vector/design tool. Use no-plot for audit-only, caption-only, table-only, or LaTeX-placement tasks that do not generate plotting code or image files.
  4. For plotting/redrawing tasks, resolve backend by explicit request, input workflow, or saved preference. If the intended output is a mechanism schematic, graphical workflow, polished composite, annotated experiment pipeline, or figure that cannot be cleanly produced end-to-end in Python/R, choose hybrid. If no preference exists for a pure plotting task, ask once: Python or R? I will remember this as your default for IEEE figures.
  5. State the detected axes in one short line.
  6. Load only the matching fragments.
  7. For plotting/redrawing, establish an IEEE figure contract before code: core engineering claim, evidence-panel map, final column size, metric/condition definitions, export formats, visual style target, and QA risks.
  8. Map each figure/table to the claim it supports.
  9. For Python plotting, prefer the bundled scripts/ieee_plot_style.py helper or mirror its API when writing standalone manuscript code. For hybrid figures, separate data-generated layers from manually edited vector/layout layers and keep an edit log.
  10. Report first-impression risks before cosmetic suggestions.

Output Contract

Default output:

text
Detected axes: visual_type=..., check_type=..., failure_mode=..., stage=..., backend=...

Figure/table audit
Item | Supported claim | First-impression risk | Technical issue | Fix

Priority fixes
1. ...

For caption writing, return revised captions plus missing information placeholders.

For redesign requests, provide concrete plot/table changes rather than generic advice.

For plotting or redraw requests, return:

text
IEEE figure contract
- Core claim:
- Evidence map:
- Final size:
- Visual style:
- Export bundle:

Files or code:
- ...

QA notes:
- ...

Red Lines

Do not recommend misleading axis scaling.

Do not invent experimental results or statistical significance.

Do not make visual changes that obscure fair comparison, uncertainty, or negative results.

Do not use the official IEEE logo, IEEE marks, or invented acceptance/compliance claims in figures.

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 Figure Table AI skill do?

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

Why use Ieee Figure Table on TypingMind?

Because you install it once and use it with any model. Ieee Figure Table 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 Figure Table in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/CloudWave818/ieee-skills/tree/main/skills/ieee-figure-table. 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 Figure Table?

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 Figure Table?

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

Is the Ieee Figure Table 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 👇