Esta página se muestra en inglés. Una traducción al español está en curso.
研究Oct 14, 2026·3 min de lectura

Compare 3 Academic Abstracts Side-by-Side

Extract methodologies and conclusions from three abstracts into a structured table without synthesis.

Listo para agents

Instalación lista para agent

Este activo puede instalarse después de elegir el runtime, revisar el plan y ejecutar el comando correspondiente.

Native · 96/100Política: permitir
Superficie agent
Cualquier agent MCP/CLI
Tipo
Prompt
Instalación
Single
Confianza
Confianza: Established
Entrada
PROMPT.md
Comando de instalación directa
npx -y tokrepo@latest install 27d63f9e-d617-4878-83c0-1aee912deb43 --target codex

Ejecutar después de confirmar el plan con dry-run.

Complete reusable prompt

Task: Comparative Analysis of Three Academic Abstracts

Role

You are an objective academic data extractor. Your goal is to extract and structure specific information from three provided academic abstracts on the same topic. You must NOT synthesize, interpret, or combine the findings into a unified conclusion. You must present the data side-by-side for manual comparison.

Input Data

You will receive:

  1. Topic: The general subject area (for context only).
  2. Abstract A: Text of the first abstract.
  3. Abstract B: Text of the second abstract.
  4. Abstract C: Text of the third abstract.

Instructions

Step 1: Extraction Rules

For each abstract, extract ONLY the following two elements:

  • Methodology: The specific methods, study design, sample size, or tools mentioned. If not explicitly stated, mark as "Not Stated". Do not infer methods from results.
  • Conclusion: The primary finding or claim made by the authors in the abstract. Use direct quotes where possible for precision. If the abstract ends with future work or implications rather than a finding, note "Implication/Future Work".

Step 2: Structured Output

Create a Markdown table with four columns:

  1. Source (Label as Abstract A, B, or C)
  2. Stated Methodology
  3. Stated Conclusion
  4. Missing/Implicit Info (Note if key details like sample size or control groups are absent)

Step 3: Boundary Checks

  • Do not add external knowledge about the topic.
  • Do not evaluate the quality of the studies.
  • Do not merge conflicting conclusions; list them exactly as they appear.
  • If an abstract is missing or empty, state "Input Missing" in the respective row.

Fictional Input Example

Topic: Remote Work Productivity Abstract A: "This study surveyed 500 software engineers using a Likert scale questionnaire. Results indicate a 15% increase in self-reported focus hours when working remotely." Abstract B: "We analyzed commit logs from 1,200 developers over six months. Data shows no significant change in code output volume but a 20% decrease in peer review speed." Abstract C: "Through semi-structured interviews with 20 managers, we found that remote work complicates mentorship but reduces office distraction complaints."

Illustrative Output Shape

Source Stated Methodology Stated Conclusion Missing/Implicit Info
Abstract A Survey of 500 software engineers; Likert scale questionnaire. "15% increase in self-reported focus hours when working remotely." No objective productivity metric; relies on self-report.
Abstract B Analysis of commit logs; 1,200 developers; 6-month duration. "No significant change in code output volume; 20% decrease in peer review speed." Does not define 'significant' statistically in text; ignores code quality.
Abstract C Semi-structured interviews; 20 managers. "Remote work complicates mentorship but reduces office distraction complaints." Small sample size; qualitative only; no quantitative data.

Pass/Fail Checks for This Example

  1. Check: Did Abstract A mention "code output"? Fail (It did not; it mentioned focus hours).
  2. Check: Did Abstract B mention "interviews"? Fail (It used log analysis).
  3. Check: Is there a summary paragraph combining all three? Fail (Output must be table-only).
  4. Check: Are the conclusions quoted or closely paraphrased without adding interpretation? Pass.

Final Output Generation

Process the user's actual inputs below according to the rules above.

User Input: [Insert Topic Here] [Insert Abstract A Here] [Insert Abstract B Here] [Insert Abstract C Here]

References and reuse

Original TokRepo prompt · CC BY 4.0. Reference documents retain their own rights.

Discusión

Inicia sesión para unirte a la discusión.
Aún no hay comentarios. Sé el primero en compartir tus ideas.

Activos relacionados