checkpoint-prompt

Generate next-turn prompts from winner code and evaluation results.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/MinhOmega/marlin-skill --skill checkpoint-prompt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: checkpoint-prompt
Source: https://github.com/MinhOmega/marlin-skill/tree/main/.claude/skills/checkpoint-prompt
Command: npx skills add https://github.com/MinhOmega/marlin-skill --skill checkpoint-prompt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Checkpoint Prompt skill provides a structured mechanism to generate the next-turn prompt that addresses gaps identified in the current evaluation, ensuring improvements are concrete, testable, and compliant with the promotion of quality across agent prompts.

Core Features & Use Cases

  • Generates flowing, implementable next-turn prompts that focus on addressing evaluation gaps in winner code.
  • Enforces guardrails from the anti-LLM prompts and ensures changes are testable, specific, and localized to the winner's code.
  • Use Case: When an evaluation reveals gaps in the implementation, this skill crafts a targeted prompt to guide the next turn toward new tests, edge cases, and concrete changes.

Quick Start

Run the next-turn prompt generation against the active evaluation workspace and save the result as turn_N/turn_N_next_prompt.md

Frequently Asked Questions about checkpoint-prompt

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

FAQPage Schema
How do I generate a next-turn prompt to fix gaps found in code evaluation?

To generate a next-turn prompt, the skill analyzes accepted_baseline.json and turn evaluation results to produce flowing prose targeting concrete file paths and functions, saving the output to turn_N_next_prompt.md.

What is the best way to automate prompt generation for iterative code improvements?

Automating prompt generation for iterative code improvements involves reading prior prompts and evaluation results to craft targeted, testable instructions that enforce guardrails and address specific implementation gaps in the winner's code.

Can I use checkpoint prompts to ensure code changes remain localized to specific functions?

Yes, checkpoint prompts ensure code changes remain localized by generating instructions with explicit references to relevant code locations, file paths, and tests, enforcing guardrails for specific and testable modifications.

Do I need prior evaluation results to generate a focused next-turn prompt?

Yes, you need prior evaluation results. The skill reads accepted_baseline.json, turn_N_evaluation.md, and all prior prompts to analyze gaps and produce a flowing prose prompt targeting concrete code locations.

When should I use automated next-turn prompt generation instead of manual prompt writing?

Use automated next-turn prompt generation when an evaluation reveals implementation gaps and you need to systematically guide the next turn toward new tests, edge cases, and concrete changes without manual prompt crafting.