ts-paper-experiment

Repairs AI-generated LaTeX paper drafts by running feasible experiments and enforcing claim-evidence consistency.

1.1k|19|Updated Jun 18, 2026
One-click install
npx skills add https://github.com/Spark-To-Paper-Skills/spark-to-paper-skills --skill ts-paper-experiment-spark-to-paper-skills
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ts-paper-experiment
Source: https://github.com/Spark-To-Paper-Skills/spark-to-paper-skills/tree/main/skills/ts-paper-experiment
Command: npx skills add https://github.com/Spark-To-Paper-Skills/spark-to-paper-skills --skill ts-paper-experiment-spark-to-paper-skills

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? AI-generated scientific paper drafts often contain unsupported claims, untraceable numbers, missing experiments, and fabricated references. This Skill diagnoses such drafts, runs only feasible experiments, rewrites the experiment section, and repairs the full LaTeX manuscript so every claim is backed by traceable evidence. ## Core Features & Use Cases - Diagnosis and experiment planning: Maps the paper's logic, identifies missing experiments and unsupported claims, and plans a minimal feasible experiment set with pre-run cost approval gates. - Traceable experiment execution: Runs experiments with dataset license checks, recomputes reported values from per-seed raw logs, and audits code-paper consistency across six mandatory reports. - Full manuscript repair: Edits the LaTeX source directly in ./paper/, verifies every reference, checks the rendered PDF layout, and syncs the repaired manuscript to Overleaf via Git. - Use Case: You receive an AI-drafted ML paper with blank result tables. The skill downloads the named datasets, runs the experiments, fills the tables with real numbers, weakens unsupported claims, verifies citations, and pushes the honest repaired manuscript to Overleaf. ## Quick Start Repair the AI-generated paper draft staged under ./input/draft/ by diagnosing it, running feasible experiments, and updating the manuscript in ./paper/ for claim-evidence consistency.

Frequently Asked Questions about ts-paper-experiment

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

FAQPage Schema
How do I repair an AI-generated paper draft with real experiments?

Place the draft under ./input/draft/ or as ./draft_overleaf.zip, then the skill diagnoses the paper, plans a minimal feasible experiment set, runs it with traceable logs, and rewrites the experiment section and full manuscript inside ./paper/ so claims match evidence.

What happens when an experiment cannot be run?

The skill never fabricates results. It writes an EXPERIMENT_REQUIREMENTS.md report describing what is needed, and unsupported claims are weakened, removed, or marked AUTHOR_TODO instead of being filled with invented numbers.

Does the skill sync the repaired manuscript to Overleaf?

Yes. The ./paper/ directory is an independent Git repository that can push to an Overleaf remote using OVERLEAF_GIT_URL and OVERLEAF_TOKEN from a local .env file. Overleaf sync can be disabled via paper_config.yaml.

How does the skill verify reported numbers are real?

A mandatory consistency gate audits result provenance, experiment completeness, code-paper consistency, design correctness, and artifact completeness. Every table value must be recomputable from per-seed raw logs, and failures force claim weakening or removal.

Can the skill download external datasets automatically?

Only after a dataset license gate reports the source, size, license terms, disk, and runtime, and expensive or external-data experiments require explicit user approval through a pre-run plan before anything is downloaded or executed.

What are the limitations of automated paper repair?

The skill cannot run experiments without available data and code, and it will not invent results to fill gaps. Blocked experiments produce requirements reports, and major changes like altering the core contribution always require user approval.