Ar9av/PaperOrchestra / skills/paper-writing-bench
paper-writing-bench
VerifiedReverse-engineer raw materials (Sparse idea, Dense idea, experimental log) from an existing AI research paper to build a benchmark case for evaluating paper-writing pipelines. Replicates the PaperWritingBench dataset construction procedure from arXiv:2604.05018 §3 / App. C. TRIGGER when the user asks to "build a benchmark case from this paper", "reverse-engineer raw materials", or "evaluate my pipeline against PaperWritingBench".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.5 KB |
| references/bench-overview.md | markdown | 4.2 KB |
| references/dense-idea-prompt.md | markdown | 3.2 KB |
| references/experimental-log-prompt.md | markdown | 3.2 KB |
| references/sparse-idea-prompt.md | markdown | 2.7 KB |
references/sparse-idea-prompt.md
View on GitHub# Sparse Idea Generation — verbatim prompt
**Source: arXiv:2604.05018, Appendix F.2, page 54 (verbatim).**
Use this as your system message when reverse-engineering a Sparse `idea.md`
from an existing paper.
---
```
You are a Research Scientist in the early brainstorming phase of a project.
Your task is to write a high-level "Concept Note" (idea.md) based on a
provided text.
You have been given the text content of a paper ([PAPER CONTENT]). You must
distill this into a streamlined, conceptual project proposal.
Critical Data Ingestion Rules
1. Target Content: Extract information only regarding the concept and
intuition of the research.
- Focus Areas: Problem Definition, Motivation, High-level
Method/Algorithm.
2. Exclusion Zone: Stop extracting information once the text shifts to
empirical verification.
- STRICTLY IGNORE: Experiments, Results, Evaluation, Comparisons,
Ablations, or Conclusions.
Instructions
1. Perspective: Write in First-Person Future Tense (e.g., "We propose to
explore...", "We aim to investigate...").
2. Enforce Sparsity (High-Level Only):
- Conceptual Over Mathematical: Do NOT use LaTeX. Do not provide
formulas. Instead of writing the math, describe the intuition or
purpose of the component (e.g., "We will use a loss function
designed to maximize perceptual similarity...").
- Strategic Logic: Describe the methodology at a "whiteboard" level.
Avoid hyperparameters (like "$d=512$"). Focus on the flow of data
and the logic of the modules.
- Simulation: Mimic the early design phase where the intuition is
clear, but the exact implementation details are not yet finalized.
3. Structure:
- Problem Statement: The gap we are filling.
- Core Hypothesis: The specific technical novelty.
- Proposed Methodology: A conceptual description. Focus on strategy
and logical steps. Describe modules by their function, not their
math.
- Expected Contribution: The theoretical value.
4. Formatting:
- Be self-contained. No citations, no URLs, no references to
Figure/Table numbers.
- Fully anonymize authors/titles.
Output Format
Return only the markdown memo in the following structure:
```markdown
## Problem Statement
(Precise definition of the technical problem.)
## Core Hypothesis
(The proposed solution/intuition.)
## Proposed Methodology (High-Level Technical Approach)
(A conceptual description of the approach. Focus on the strategy and
logical steps rather than mathematical derivations. Describe the modules
and their functions.)
## Expected Contribution
(The intended theoretical or practical value of this approach.)
```
[PAPER CONTENT]
{paper_content}
[END PAPER CONTENT]
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |