auto-review-loop-minimax

Automates iterative multi-round document reviews with MiniMax feedback and fixes.

2|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/satsuki-64/MiniAgentWorkflow --skill auto-review-loop-minimax-satsuki-64
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-review-loop-minimax
Source: https://github.com/satsuki-64/MiniAgentWorkflow/tree/main/.skills/auto-review-loop-minimax
Command: npx skills add https://github.com/satsuki-64/MiniAgentWorkflow --skill auto-review-loop-minimax-satsuki-64

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of conducting autonomous, multi-round external reviews for research artifacts using MiniMax, reducing manual back-and-forth and improving turnaround.

Core Features & Use Cases

  • Multi-round evaluation loop: review → implement fixes → re-review until a positive assessment or MAX_ROUNDS is reached.
  • Persistent state: logs and progress are saved to REVIEW_STATE.json and AUTO_REVIEW.md to resume after interruptions.
  • Flexible backend: uses MiniMax MCP tool when available, with a curl fallback, and reads API keys from environment variables.
  • Applicable scenarios: for research papers, code submissions, and experiments requiring rigorous external critique and iterative improvement.

Quick Start

Trigger the skill by saying "auto review loop minimimax" to start the autonomous review process.

Frequently Asked Questions about auto-review-loop-minimax

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate multi-round external research reviews for a manuscript?

Automate multi-round external research reviews by triggering an autonomous loop where MiniMax critiques submissions, implements fixes, and re-reviews until acceptance criteria are met. This reduces manual back-and-forth and improves turnaround for research artifacts.

How does state persistence work when an autonomous review loop is interrupted?

State persistence saves logs and progress to REVIEW_STATE.json and AUTO_REVIEW.md files, allowing the multi-round research review process to resume seamlessly after interruptions without losing tracked evaluation rounds.

Do I need an API key to use MiniMax for iterative research critique?

Yes, you need an API key read from environment variables to use MiniMax for iterative research critique. The Skill integrates with MiniMax via MCP tool, with a curl fallback for flexible backend execution.

What is the best way to apply iterative feedback loops to research projects?

The best way to apply iterative feedback loops is using an autonomous review system that performs review, fix implementation, and re-evaluation until a positive assessment or maximum rounds are reached.

Can I use this autonomous review loop for code submissions and experiments?

Yes, you can use this autonomous review loop for code submissions and experiments. It applies rigorous external critique and iterative improvement to research papers, code, and experiments requiring multi-round evaluation.

What happens when a research artifact fails to meet acceptance criteria after multiple review rounds?

When a research artifact fails to meet acceptance criteria, the loop continues implementing fixes and re-reviewing until a positive assessment is achieved or the defined MAX_ROUNDS limit is reached, terminating the autonomous process.