Standardize Sci Images logo

Standardize Sci Images

Community
zhoy0409-debug
standardize-sci-images

Scientific image standardization for microscopy, fluorescence, histology, pathology, and electron-microscopy image batches. Use when the user has raw or derived scientific raster images needing non-destructive processing, locked tone settings, equal dimensions, calibrated scale bars, manifests, montages, duplicate-image screening, 图片查重, or image audit trails. Do not use for raw CSV/Excel charting or final-only SVG layout polishing.

Overview

Publisherzhoy0409-debug
Repositorypolish-sci-figures
Skill namestandardize-sci-images
Stars
70
Forks
5
Bundled files
7
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.

  • 7 bundled files

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

  • Open source

    Published by zhoy0409-debug on GitHub. Read the source before you install it.

Installation

Install the Standardize Sci Images 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/zhoy0409-debug/polish-sci-figures/tree/main/skills/standardize-sci-images
  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/zhoy0409-debug/polish-sci-figures.git /tmp/polish-sci-figures
mkdir -p .claude/skills
cp -r /tmp/polish-sci-figures/skills/standardize-sci-images .claude/skills/standardize-sci-images
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Standardize Sci Images 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 Standardize Sci Images 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 Standardize Sci Images 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.

Standardize Scientific Images

Prepare comparable scientific images as a documented batch. Preserve raw files, apply only declared global operations, and fail when an honest scale bar or comparable display cannot be produced.

Start with the manifest

Read references/image_contract.md, then create a CSV manifest. At minimum it needs file, output_name, and um_per_pixel when a scale bar is requested. Add batch when images were acquired under different settings. The same comparison batch must share calibration and display settings.

bash
python scripts/standardize_images.py manifest.csv \
  --outdir standardized --scale-bar-um 20

The command center-crops every image to a common pixel canvas and writes three practical derivatives: an unannotated display raster, a labelled preview, and an SVG panel whose faithful raster content remains embedded while scale bars and text stay editable vector/live layers. It also builds a montage and writes CSV/JSON audits containing source hashes and every operation. It never overwrites the source.

The requested overlay font defaults to Arial and must be installed. Use --allow-font-fallback only for draft previews; the audit records requested font, actual font, font file, fallback status, and whether the output is allowed for final delivery.

By default, the SVG physical width is set to the largest size that preserves 300 dpi. Use --panel-width-mm only for a known final slot; the command refuses a width that would fall below 300 dpi instead of inventing pixels.

Scientific integrity rules

  • Treat raw acquisition files as immutable. Write derivatives to a new directory and record source SHA-256 hashes.
  • Never invent a scale bar. Require calibration from image metadata, acquisition software, or an authoritative record.
  • Do not infer calibration from another image unless the acquisition record proves they share it.
  • Apply the same crop policy, intensity window, gamma, and LUT to images in the same comparison batch. Do not tune each experimental group separately.
  • Default to no tone adjustment. If display adjustment is needed, declare fixed display_min, display_max, gamma, and lut settings in the manifest.
  • Keep higher-bit-depth single-channel data at their native depth until display mapping. Require an explicit native-unit display window; never silently cast 16-bit data to 8-bit.
  • Preserve a quantitative image/table separately. Display normalization is not a substitute for quantitative preprocessing.
  • Do not erase, clone, selectively blur, locally enhance, or move biological structures.
  • Do not resample by default. Equalize size by a common crop. If resampling is scientifically justified, perform it in a documented downstream workflow and update calibration.

Read references/integrity_and_layout.md before processing fluorescence composites, electron micrographs, unequal calibrations, or images used for quantification.

Layout rules

  • Use one target canvas per comparison set, with identical output pixel dimensions and equal gutters.
  • Use one physical SVG panel size per slot class and verify effective raster dpi at that final size.
  • Use the same scale-bar length and placement within a comparable batch when it fits the shared field of view.
  • Center the scale-bar label over the bar; do not right-align it to the bar endpoint. Keep this alignment and type size identical across the batch.
  • Keep scale bars inside a safety margin and choose black or white from the local background for contrast.
  • Do not add panel letters, serial numbers, per-image titles, or conclusions by default. Add only explicitly requested sample labels that are necessary to interpret the image.
  • Keep captions, acquisition settings, and interpretation outside the image montage.
  • Do not stretch images to make them fit. Crop consistently and record the crop box.
  • Keep scale bars and their labels editable in the SVG delivery layer. Treat the underlying scientific image as faithful raster content, not as a fully vector-editable object.
  • Judge scale-bar and sample-label size in the final panel or montage, not while zoomed into the source. Use one readable label hierarchy and baseline within each slot class.

Check the batch for reused images

When the user asks for image QA or before assembling a batch of scientific images, screen the available source images for accidental reuse using the complete suite from its root:

bash
python sci_figures.py duplicates image-a.png image-b.tif image-c.png --out image-check

Compare 2–60 raster images per batch. For a source-batch check, choose one source per acquired image instead of mixing its raw file with known display derivatives. Supply source images or individual image panels; a flattened montage remains one image and is not automatically divided into panels. SVG-embedded raster images can also be screened. Preserve raw files, calibration and processing records throughout. For larger sets, document which batches were compared; independent batches do not check pairs spanning different batches.

Review exact duplicates and suspected rotated, flipped, resized or cropped overlaps against original files and acquisition records. Related channels and deliberately reused controls can match legitimately. Retain matching evidence and the report; do not automatically delete, alter or relabel images. Report findings as candidates for review, not misconduct determinations, and do not treat no detected matches as a guarantee of uniqueness. See the image duplicate guide.

Finish with the polish skill

Use $polish-sci-figures for final multi-panel grid assembly, font selection, whitespace control, overlap checks, and placement in the manuscript or slide. A visually aligned montage does not pass if calibration, processing provenance, or comparability is unresolved.

Read references/professional_basis.md for the image-integrity, publication-layer, calibration, metadata, and reporting sources behind these safeguards. The implementation is original to this repository.

Acceptance gate

Do not deliver if any raw file was changed, calibration is absent or guessed, comparison-batch display settings differ, crops remove different scientific regions without justification, outputs differ in size, a scale bar is clipped, incorrect, or too small at final size, or unrequested labels/titles/serial numbers appear.

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 Standardize Sci Images AI skill do?

Scientific image standardization for microscopy, fluorescence, histology, pathology, and electron-microscopy image batches. Use when the user has raw or derived scientific raster images needing non-destructive processing, locked tone settings, equal dimensions, calibrated scale bars, manifests, montages, duplicate-image screening, 图片查重, or image audit trails. Do not use for raw CSV/Excel charting or final-only SVG layout polishing.

Why use Standardize Sci Images on TypingMind?

Because you install it once and use it with any model. Standardize Sci Images 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 Standardize Sci Images in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/zhoy0409-debug/polish-sci-figures/tree/main/skills/standardize-sci-images. 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 Standardize Sci Images?

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 Standardize Sci Images?

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

Is the Standardize Sci Images AI skill free?

Yes. It is published on GitHub by zhoy0409-debug 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 👇