codex-deepseek-paper-protocol

Coordinate a two-agent academic writing workflow with Codex planning and DeepSeek drafting.

2|1|Updated May 7, 2026
One-click install
npx skills add https://github.com/shenmuxing/EtaSkill --skill codex-deepseek-paper-protocol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codex-deepseek-paper-protocol
Source: https://github.com/shenmuxing/EtaSkill/tree/main/skill-examples/codex-deepseek-paper-protocol
Command: npx skills add https://github.com/shenmuxing/EtaSkill --skill codex-deepseek-paper-protocol

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires deepseek-agent, muxing-style-review, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill coordinates academic writing workflows where Codex plans and reviews while DeepSeek drafts or revises the manuscript, keeping prose authorship separated from protocol control.

Core Features & Use Cases

  • Two-agent workflow control: Assigns Codex as the planner, reviewer, and integration controller while DeepSeek performs the actual writing and revision.
  • Revision loop management: Supports bounded review cycles, acceptance checks, and structured feedback until the text is ready or the round limit is reached.
  • Style and safety oversight: Uses companion style review guidance to check clarity, evidence, terminology, and unsupported claims before accepting prose.
  • Use case: A researcher wants a section of a paper rewritten without directly authoring the prose themselves; this Skill prepares the brief, delegates the writing, reviews the result, and requests revisions as needed.

Quick Start

Use the codex-deepseek-paper-protocol skill to coordinate a manuscript revision by having Codex review the context and DeepSeek write the requested section.

Frequently Asked Questions about codex-deepseek-paper-protocol

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

FAQPage Schema
How do I coordinate two AI agents for academic manuscript revision?

Academic manuscript revision uses a two-agent workflow where one agent plans, reviews, and integrates while the other drafts and revises text. This separation keeps prose authorship distinct from protocol control, applying structured feedback until acceptance checks pass or rounds reach their limit.

Can I use DeepSeek to draft paper sections while another agent handles style review?

DeepSeek drafts paper sections while a companion style review mechanism checks clarity, evidence, terminology, and unsupported claims. The planner agent delegates writing tasks, reviews the returned text, and requests bounded revisions until the prose meets structured acceptance criteria.

What is a two-agent workflow for academic writing and peer review?

A two-agent academic writing workflow assigns planning and reviewing roles to one agent and drafting or revising roles to another. It manages bounded review cycles, applies style and safety oversight, and ensures supported claims, consistency, and format before accepting the revised manuscript text.

Do I need companion skills to run the codex-deepseek-paper-protocol?

The paper protocol requires companion skills for DeepSeek execution and style review to function. These dependencies provide the actual manuscript text generation and the stylistic oversight needed to verify evidence, terminology, and unsupported claims during the bounded revision loops.

How do I manage bounded review cycles for manuscript text revisions?

Bounded review cycles for manuscript text revisions are managed by setting a round limit and applying structured acceptance checks. The reviewing agent evaluates the drafted text for consistency and supported claims, requesting further revisions until the prose is ready or the limit is reached.

When should I avoid using a multi-agent workflow for manuscript writing?

Multi-agent manuscript workflows are not ideal when a task requires direct prose authorship without protocol control or bounded review loops. Tasks needing unbounded creative iteration or lacking clear role separation between drafting and reviewing will not benefit from this structured revision process.