One-click install
npx skills add https://github.com/wjgoarxiv/autoconference-skill --skill autoconference-resume
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autoconference:resume
Source: https://github.com/wjgoarxiv/autoconference-skill/tree/main/skills/resume
Command: npx skills add https://github.com/wjgoarxiv/autoconference-skill --skill autoconference-resume

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the frustration and wasted compute of restarting an interrupted multi-agent autoconference by recovering the exact last known checkpoint and continuing from there.

Core Features & Use Cases

  • Checkpoint recovery from an event log: Restores state by reading conference_events.jsonl and re-enters the protocol at the correct phase.
  • State validation and integrity checks: Verifies required files like conference.md and conference_events.jsonl, plus consistency between logged events and on-disk outputs.
  • Safe handling of partial work: Reverts mid-iteration researchers to their last kept state and avoids rerunning completed rounds.
  • Works for resuming only: Explicitly prevents restarting a finished conference and continues forward without skipping protocol steps.

Quick Start

Resume your interrupted conference by running the autoconference resume skill when you have a conference directory containing conference.md and conference_events.jsonl.

Frequently Asked Questions about autoconference:resume

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

FAQPage Schema
How do I resume an interrupted multi-agent research conference from a checkpoint?

To resume an interrupted multi-agent research conference, the skill parses the persisted conference_events.jsonl event log to locate the deterministic recovery point, validates on-disk state, reverts incomplete researchers, and continues the orchestration protocol without repeating completed work.

What happens to partial work from researchers when checkpoint recovery is triggered?

During checkpoint recovery, partial work is safely handled by reverting mid-iteration researchers to their last kept state, ensuring that incomplete rounds are not rerun and completed phases are preserved across the multi-agent conference protocol.

How does event sourcing state validation work for conference orchestration directories?

Event sourcing state validation verifies required files like conference.md and conference_events.jsonl exist, then checks consistency between logged events and on-disk outputs to ensure the conference directory state matches the event log before recovery.

Can I restart a finished multi-agent conference using this checkpoint recovery process?

No, this checkpoint recovery process explicitly prevents restarting a finished conference and is designed exclusively for resuming interrupted autoconference orchestration forward without skipping protocol steps.

What files do I need in my conference directory to recover an interrupted autoconference session?

You need a conference directory containing both conference.md and conference_events.jsonl files to recover an interrupted autoconference session, as these files provide the persisted event log and state validation required for checkpoint recovery.