/refine

Iteratively revise research artifacts until a target review score is reached.

Updated May 23, 2026
One-click install
npx skills add https://github.com/duany049/multi-skill-orchestration --skill refine-duany049
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: /refine
Source: https://github.com/duany049/multi-skill-orchestration/tree/main/.claude/skills/refine
Command: npx skills add https://github.com/duany049/multi-skill-orchestration --skill refine-duany049

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires review.

What problem does it solve?

Refining research artifacts often stalls due to vague feedback, missing gaps, or incomplete revisions, making progress hard to measure and iterate reliably.

Core Features & Use Cases

  • General-purpose iterative improvement loop: repeatedly calls review, extracts actionable items, and applies fixes until the artifact meets a target quality score.
  • Artifact-agnostic support: improves ideas, experiment plans, methods, paper drafts, or output drafts referenced by wiki slugs or file paths.
  • Wiki-aware improvement: updates relevant wiki entities and rebuilds derived context (edges/open questions) when knowledge changes are made.
  • Score-guided termination: stops when the target score is reached, when the review verdict is ready, or when convergence/max rounds occur.

Quick Start

Run the refine skill on the wiki page for a paper draft by providing its slug and letting it iterate until the target review score is achieved.

Frequently Asked Questions about /refine

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

FAQPage Schema
How do I iteratively improve a research paper draft until it reaches a target quality score?

Iteratively improving a research paper draft involves a multi-round review-driven revision loop that applies fixes in place until a target quality score is reached. It extracts actionable items from each review to systematically close content gaps.

What is the best way to detect and fix content gaps in an experiment plan?

Detecting and fixing content gaps in an experiment plan is best handled by a multi-round review process that extracts actionable items and applies targeted revisions. This loop continues until the artifact reaches the target review score or convergence.

Can I use automated content revision on experiment plans and methods, or just paper drafts?

Automated content revision works on experiment plans and methods, not just paper drafts. This artifact-agnostic refinement loop applies to any research artifact referenced by wiki slugs or file paths until the target score is achieved.

Does iterative research review require a wiki graph to update context after revisions?

Iterative research review leverages a wiki graph to update relevant entities and rebuild derived context edges after applying knowledge changes. This ensures wiki-backed context remains accurate after each revision loop.

When does the iterative improvement loop stop applying revisions to a research artifact?

The iterative improvement loop terminates when the target review score is reached, the review verdict is ready, or convergence and max rounds occur. It then outputs a final report containing the score trajectory and any unresolved issues.