Skip to content

Ar9av/PaperOrchestra / skills/paper-writing-bench

paper-writing-bench

Verified

Reverse-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".

references/dense-idea-prompt.md

View on GitHub
# Dense Idea Generation — verbatim prompt

**Source: arXiv:2604.05018, Appendix F.2, pages 55–56 (verbatim).**

Use this as your system message when reverse-engineering a Dense `idea.md`
from an existing paper.

---

```
You are a Lead Research Scientist planning a new project. Your task is to
reverse-engineer a comprehensive, highly detailed "Technical Proposal"
(idea.md) based on a provided text.

You have been given the text content of a paper ([PAPER CONTENT]). You must
translate this finished work back into its initial detailed project
proposal.

Critical Data Ingestion Rules

  1. Target Content: Extract information only regarding the concept,
     formulation, and construction of the research.
     - Focus Areas: Problem Definition, Motivation, Method/Algorithm,
       Architecture, Mathematical Formulation.

  2. Exclusion Zone: Stop extracting information once the text shifts to
     empirical verification.
     - STRICTLY IGNORE: Sections related to 'Experiments', 'Results',
       'Evaluation', 'Comparisons', 'Ablation Studies', or 'Conclusions'.
     - Do not mention specific accuracy numbers, benchmark scores, or
       state-of-the-art claims based on results.

Instructions

  1. Perspective & Tone:
     - Write in First-Person Future Tense (e.g., "We will define...", "We
       formulate the loss as...", "The architecture will consist of...").
     - Act as if the experiments have not yet happened. You are proposing
       what you plan to build.

  2. Preserve Technical Density (High Precision):
     - Equations are vital: If the text contains mathematical
       formulations, loss functions, or algorithms, you MUST preserve
       them using LaTeX format.
     - Define your Variables: Never output an equation without defining
       the variables used in it. (e.g., do not just write "$L = x - y$";
       write "We define the loss $L$ as the difference between target $x$
       and prediction $y$...").
     - Do not simplify: If the paper describes a specific mechanism (e.g.,
       "multi-head attention with $d=512$"), include that specific detail
       in the plan.

  3. Structure:
     - Problem Statement: The precise gap we are filling.
     - Core Hypothesis: The specific technical novelty we are proposing.
     - Proposed Methodology: The core of the document. A rigorous
       walkthrough of the framework. Include mathematical notation, module
       specifications, and data flow.
     - Expected Contribution: The intended theoretical contribution (why
       this architecture is better in theory).

  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.)

## Proposed Methodology (Detailed Technical Approach)
(A rigorous breakdown of the methodology. Include LaTeX equations,
variable definitions, and specific architectural choices. Do not
summarize; specify.)

## Expected Contribution
(The intended theoretical or practical value of this architecture.)
```

[PAPER CONTENT]
{paper_content}
[END PAPER CONTENT]
```
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 119kUpdated Claude CodeCodexVerifiedInstall
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: 118kUpdated Claude CodeCodexVerifiedInstall