<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta>
      <journal-title-group>
        <journal-title>R. Celebi, J. Rebelo Moreira, A. A. Hassan, S. Ayyar, L. Ridder, T. Kuhn, M. Dumontier, Towards
FAIR protocols and workflows: the OpenPREDICT use case, PeerJ Computer Science</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="doi">10.5281/ZENODO.10723608</article-id>
      <title-group>
        <article-title>Intelligent Assistants in the Era of LLMs: A New Methodology for Reusing Research Software from Documentation</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Carlos Utrilla Guerrero</string-name>
          <email>carlos.utrilla.guerrero@alumnos.upm.es</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="editor">
          <string-name>Research Software Reuse, Multi-agent systems, Intelligent Assistant, Artificial Intelligent</string-name>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Doctoral Symposium on Natural Language Processing</institution>
          ,
          <addr-line>25</addr-line>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Ontology Engineering Group (OEG), Universidad Politécnica de Madrid (UPM)</institution>
          ,
          <addr-line>Madrid</addr-line>
          ,
          <country country="ES">Spain</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2016</year>
      </pub-date>
      <volume>6</volume>
      <issue>2020</issue>
      <fpage>341</fpage>
      <lpage>352</lpage>
      <abstract>
        <p>As intelligent assistants driven by generative Artificial Intelligent (AI) such as Large Language Model (LLM) have shown remarkable capabilities in supporting software development tasks, including code generation through natural language, a critical question arises: how can these intelligent assistants aid in the reuse of research software from its documentation? This thesis investigates how the research community can benefit from the LLM revolution, specifically in the context of research software (RS) reuse. To this end, this thesis will propose a new methodology that enables AI-based intelligent assistants to interpret, reason, plan and act upon reuseoriented software documentation-such as README files and procedural guides. By extracting, transforming, and executing procedural instructions, such intelligent assistants have the potential to reduce cognitive and technical burdens on researchers, improve the sustainability of RS, and may alleviate certain pressures associated with modern scientific careers.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        Today, many researchers are not only generating new knowledge using software but are also increasingly
reusing digital infrastructure—such as tools, software, and services—developed by others. A key
facilitator of this reuse process is human-generated documentation, particularly README files, which
typically provide step-by-step instructions on how to install, configure, and run research software (RS)[
        <xref ref-type="bibr" rid="ref1">1</xref>
        ].
      </p>
      <p>
        These instructions commonly follow established methods—such as package managers, containers, source
builds, and/or setup scripts—intended to reduce friction and facilitate reuse[
        <xref ref-type="bibr" rid="ref2 ref3">2, 3</xref>
        ]. However, even when
RS is encapsulated in portable environments like Docker containers or Python packages, researchers are
often still required to manually inspect the documentation, make decisions about procedural steps, and
resolve ambiguity. Executing these instructions accurately is not a trivial task: it involves modeling the
structure of the installation process, locating where install commands may break down, and reasoning
through multiple layers of document complexity without standards. These unstructured narratives
present a major obstacle [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] to interpreting and executing instructions by both humans and machines,
ultimately limiting the automation of research software reuse from documentation [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. As a result,
the full potential of automated research software reuse from documentation cannot be realized until
we understand what set of procedural language processing, reasoning and planning capabilities are
required to enable machines—or AI-based assistants—to efectively read, interpret, execute, and validate
complex reuse instructions contained in human-generated documentation [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. Here, we tackle this
challenge by exploring a multidimensional approach encompassing these following tasks: (1) extracting
install-related instructions from README files and (2) transforming them into a format that can be
(3) executed by machines at a minimum cost.
      </p>
      <p>
        The problem of automating software reuse (in general) has long been recognized in the field of AI and
software engineering [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ], but has come to prominence recently with the emergence of contemporary
CEUR
Workshop
      </p>
      <p>
        ISSN1613-0073
generative AI, particularly Large Language Models (LLMs). The possibility of using networks of
LLMbased Assistants 1 to solve of interacting with documentation, generating code and performing complex
reasoning tasks. These LLM-powered assistants have greatly shown strong potential in automating
scientific workflows [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] and software engineering activities such as bug fixing, test generation, and
code synthesis [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ].
      </p>
      <p>Despite these potential advancements, the usage of IAs to automated reuse from documentation
remains an open challenge (central research problem). It requires not only natural language
understanding, but also robust planning, disambiguation, and execution capabilities. Documentation—especially
when unstructured, unintelligible, or inconsistent—demands that assistants interpret complex
instructions, fill in implicit semantic knowledge, and reason through a plan or conflicting sequential steps.
Automating this process involves constructing executable representations of intent from loosely defined
human-generated procedural narratives.</p>
      <p>To date, there has been no research study of how we can develop and evaluate a method to aid in the
RS reuse process from its documentation automatically. This gap produces a substantial obstacle for
researchers who need a reliable and scalable solution for reusing RS across a wide variety of domains.
Given the critical role that software plays in the scientific research-and the growing serious possibility of
using networks of AI-based agents (particularly those equipped by contemporary LLMs), this research
seeks to answer a key question: how can we develop and evaluate an AI-based Intelligent Assistant
methodology capable of automatically supporting the reuse of research software exclusively from its
documentation?</p>
    </sec>
    <sec id="sec-2">
      <title>2. Background and related work</title>
      <p>Prior related work can be divided under three major topics: Software reuse in the research community,
automated approaches for RS reuse, and LLMs as Intelligent Assistants:</p>
      <sec id="sec-2-1">
        <title>2.1. Software reuse in the research community</title>
        <p>
          The benefits of reusing software (e.g., reducing duplication of efort) —are broadly acknowledged since
early days in the software engineering field [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ]. In spite of its promise, RS reuse has not become
standard practice in RS development yet [
          <xref ref-type="bibr" rid="ref12 ref13">12, 13</xref>
          ]. Systematic eforts to enhance the reusability of
digital scientific objects have evolved over time. In early 2000s, the Semantic Web initiative, under the
power movement of World Wide Web Consortium (W3C), introduced standards such as the Resource
Description Framework (RDF) and the Web Ontology Language (OWL) [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ] to convert heterogeneous
1In this thesis, intelligent assistant (IA) (or Agent) is a computer system endowed with artificial intelligence and/or machine
learning techniques capable of intelligently assisting researchers [
          <xref ref-type="bibr" rid="ref8 ref9">8, 9</xref>
          ]
knowledge across the web infrastructure into machine-readable format. Following these foundations,
the 2014 Lorentz Conference on the FAIR Principles—Findable, Accessible, Interoperable, and Reusable—
marked a single milestone in aligning good practices for representing digital scientific objects with the
aim of solving their reuse problem [
          <xref ref-type="bibr" rid="ref15">15</xref>
          ]. In 2022, the research software community adapted the FAIR
principles to create FAIR Principles for research software [
          <xref ref-type="bibr" rid="ref16">16</xref>
          ] in order to maximize its value.
        </p>
        <p>Over a decade later, many individuals in the research community still regards RS reuse as potentially a
powerful means of improving the research productivity and improving software engineering practices in
scientific domains [ 17]. Among others, research initiatives such as Codemeta, SoFAIR, ADORE.software
and EVERSE have emerged recently to enhance research software reuse by standardizing metadata,
automating lifecycle management, and promoting software quality.</p>
      </sec>
      <sec id="sec-2-2">
        <title>2.2. Automated approaches for RS reuse from documentation</title>
        <p>
          In an efort to reduce human intervention in the reuse process, understanding how to enable machines
to learn efective representation from natural language have always enjoyed academic interest using
formal methods [
          <xref ref-type="bibr" rid="ref4">4</xref>
          ], traditional machine learning models [18], symbolic approaches [19, 20], and, more
recently, generative models [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ]. Most prior research eforts on the development of automated approaches
for supporting software documentation tasks are focused on generating unit test [ 21], bugs [22] and
issue [23, 24] reports with summarization techniques, generating pull requests [25], recommending
good practices for ML [26], classifying README content [27] and its simplification [ 28], documenting
program changes [29] as well as checking conflicts and libraries vulnerabilities [ 30].
        </p>
      </sec>
      <sec id="sec-2-3">
        <title>2.3. LLMs as Intelligent Assistants</title>
        <p>
          Recent work has initiated to explore the power of LLM-based Intelligent Assistants in software
engineering tasks [31] and scientific discovery [ 32]. Notable among these are typically repository-level tasks [33]
that aim to exploit the vast amount of code openly available in repositories. Several research projects
explore automated solutions to generate unit test [21], bugs [22] and issue [24] reports with
summarization techniques for README files [ 28] as well as checking conflicts and libraries vulnerabilities [ 30].
However, a key research challenge remains insuficiently understood, which is how suitable are
LLMpowered agents to assist RS reuse from documentation. Recent work has initiated to explore the power
of LLM-based IAs in software engineering tasks [ 34, 35] and scientific discovery [
          <xref ref-type="bibr" rid="ref11">32, 11, 36</xref>
          ]. Notable
among these are typically classified as LLM-based using a single or multi-agent approach [ 35, 37, 38]. A
newly research trend is shown into the transition from LLMs to Large Action Models (LAM) designed
for action generation and execution in real-world scenario is promising, albeit robust empirical studies
and formal evaluation framework remains an open question [39].
        </p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>3. Description of the proposed research</title>
      <sec id="sec-3-1">
        <title>3.1. Research Problem Statement</title>
        <p>We define the machine problem of automatic reuse of Research Software (RS) as follows: given access
to openly available RS documentation (e.g., a URL to a public Git repository), what actions should a
system—such as an artificial intelligent assistant—perform to automatically convert human-generated
installation instructions into actionable, machine-executable commands, and execute them within a
virtual environment?</p>
        <p>
          Unlike prior work that addresses isolated challenges or narrow tasks, our objective is to explore what
kind of grounded language processing model is needed for enabling machines to support researchers in
the reuse-tasks of RS, covering the full range of problems summarized in Table 1. A robust solution
to enable RS reuse at scale would need to proceed as follows: to overcome the lack of standardization
in RS documentation, including inconsistent (or siloed) machinery reuse-procedural narratives (P1
and P2), an machine first would need to extract all software metadata and alternative reuse methods
described in the README (and other files), then transforms each method’s sequence of procedural
steps into a structured format. To tackle P3 (e.g., automation in managing complex environments and
configurations) and P4 (e.g., automated solutions for execution of RS), the research community utilises
continuous and development solutions such as Github-based features; however these are relying on
permission and might not be fully automated. Therefore, a machine would need to provide detailed
thinking process (e.g., adopting the approach introduced in our previous work [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ]: the PlanStep in
which a machine first breaks down a complex install methods found in a README file such ”from
source” into several subtasks, and then apply reasoning to generate a plan for each subtask in a fixed,
sequential order) before generating the two targeted outputs: i) an isolated environment (e.g., via
Docker or virtual environments) and another to configure and install the RS within that environment.
Finally, the machine should evaluate outcomes concerning correctness, reliability, and accuracy (see
Figure 1).
        </p>
      </sec>
      <sec id="sec-3-2">
        <title>3.2. Research Hypothesis</title>
        <p>In light of the problems and potential solutions outlined above, the following central research hypothesis
is proposed:
“An Intelligent Assistant, powered by AI methods, particularly Large Language Models, can be designed
to autonomously interpret, reason and act upon research software documentation—such as README
ifles—by extracting, transforming, and executing procedural instructions. The assistant can generalize
across domains by modeling reuse tasks within documentation as sequences of machine commands and
developing automation strategies to execute them accurately.”</p>
      </sec>
      <sec id="sec-3-3">
        <title>3.3. Research Questions</title>
        <p>The main research question (RQ) addressed by this thesis can be formulated as follows:
RQ: How can we develop and evaluate an AI-based Intelligent Assistant that is capable of automatically
supporting the reuse of research software exclusively from its documentation?
We further decompose the main RQ into various sub-questions (Sub-RQs):
• Sub-RQ1: What AI-based techniques and methodologies are suitable for automating the
extraction, transformation, and execution of reuse instructions from research software documentation?
• Sub-RQ2: How can these techniques and methodologies be evaluated considering the hierarchical
structure of reuse tasks and the complexity of documentation?
• Sub-RQ3: What system architecture is efective for enabling AI-based assistants to interpret,
reason, plan, and execute reuse tasks from research software documentation?
• Sub-RQ4: What evaluation framework and quality indicators are needed to assess the AI-based
assistant’s performance across diverse software and documentation types?</p>
      </sec>
      <sec id="sec-3-4">
        <title>3.4. Research Objectives</title>
        <p>To address the main RQ and subsequent sub-research questions (Sub-RQs), this thesis will aim to
achieve the following objectives (depicted in Figure 2): (RO1) Review and catalog existing methods
that support software reuse from documentation, including their core techniques and evaluation
strategies; (RO2) Develop and implement an AI-based Intelligent Assistant methodology capable of
autonomously assisting with a range of reuse tasks from its documentation; and (RO3) Evaluate and
validate empirically the methodology to assess its efectiveness in executing reuse-related tasks at scale
as well as defining and applying relevant quality indicators to research software documentation and
(re)-usability.</p>
        <p>Systematic Review</p>
        <p>Mining Study
Experiment</p>
        <p>(RO3) Evaluate</p>
        <p>Assess efectiveness
our new methodology at scale and
define quality indicators.</p>
        <p>(RO2) Develop</p>
        <p>Design a new AI-based
assistant for research software reuse
tasks and its evaluation framework.</p>
        <p>(RO1) Review
Catalog existing methods and techniques
that support research software reuse</p>
        <p>from documentation.</p>
      </sec>
      <sec id="sec-3-5">
        <title>3.5. Research Methodology</title>
        <p>To tackle the above research questions, we apply the Design Science Research (DSR) methodology [42],
which relies on an iterative process of investigating the problem, generating a solution, implementing it,
and evaluating its efectiveness in a research context. Our research objectives previously presented, align
with the DSR approach, as it strives to create a method designed to tackle the challenge of automating
reuse processes in research software from documentation.</p>
        <p>In our research context, this DSR methodology is structured into three unique phases (Ps) as illustrated
in Figure 3: (1) Review and collect prior work: a comprehensive systematic literature review on
existing methods that support software reuse from documentation, including their core techniques
and evaluation strategies; (2) design and implement an AI-based Intelligent Assistant framework
capable of autonomously assisting with a range of reuse tasks (e.g., installation, configuration and
execution of research software); (3) Evaluation and Validation: empirically evaluate and validate the
methodology to assess its efectiveness in executing reuse-related tasks at scale as well as defining and
applying relevant quality indicators to research software documentation and (re)-usability.</p>
        <sec id="sec-3-5-1">
          <title>P1. Review prior work P2. Design &amp; Implementation</title>
        </sec>
        <sec id="sec-3-5-2">
          <title>P3. Evaluation &amp; Validation</title>
          <p>Sub-RQ1:
Scoping survey</p>
          <p>Sub-RQ2:
Collect existing
benchmarks</p>
          <p>Sub-RQ2:
Create reuse
task taxonomy
Sub-RQ3:
Propose IA
Framework
eval. by
Refinement Loop
Sub-RQ4:
Automatic
Evaluation</p>
          <p>Sub-RQ4:
Domain Experts
Validation</p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4. Proposed Research Methods</title>
      <p>This thesis investigates the feasibility of adapting AI-based techniques for the reuse scenario from
documentation, and how to evaluate them. To answer the previously defined research question, we
propose the following empirical methods:
1. Systematic Literature Review: This review will provide a foundational and comprehensive
overview of existing methods for automating research software reuse from documentation,
propose a taxonomy of reuse tasks to be accomplished by an assistant, and define the evaluation
criteria.
2. Quantitative Analysis and Mining Study: The goal of this study is to characterise research
software documentation complexity, extract reuse-relevant elements, identify their properties
such as installation plans and steps associated, and formulate a taxonomy of tasks that reflect
real-world reuse activities across diferent scientific domains. Based on these findings, we will
create a benchmark and evaluation corpus for assessing intelligent assistants in reuse scenarios.
This benchmark will consist of an automated approach to annotate software documentation in
real-world reuse scenarios. It is expected to use this benchmark to evaluate task performance in
areas such as instruction extraction, interpretation, planning, reasoning and automated execution.
3. Experiments: The goal of this computational experiment is to evaluate the suitability of AI-based
Intelligent Assistants to aid in the reuse-task of researchers in real-world scenarios. We have
recently explored a first minimal prototype of a Large Language Model (LLM)-based
agent—designed to assist researchers in research software reuse by extracting human-generated installation
instructions from documentation (e.g., GitHub README files), transforming them into structured
sequential steps, and executing them in a virtual environment (so called ETE-Agent 2 which
architectural approach is shown in Figure 4).
2The proposed agent is publicly available at https://github.com/carlosug/agent.rse</p>
    </sec>
    <sec id="sec-5">
      <title>Acknowledgments</title>
      <p>This work is supported by the Ontology Engineering Group (OEG) under the PhD in Artificial
Intelligence Program with Universidad Politécnica de Madrid, and through the exceptional support of the
research team supervisor Dr. Prof. Daniel Garijo and director Dr. Prof. Oscar Corcho. The author would
also like to warmly thank the mentors for their wise and thoughtful comments, which significantly
helped improve the quality and clarity of this work.</p>
    </sec>
    <sec id="sec-6">
      <title>Declaration on Generative AI</title>
      <p>The author(s) have not employed any Generative AI tools.
level automated scientific discovery via agentic tree search, arXiv preprint arXiv:2504.08066 (2025).
[37] B. Liu, X. Li, J. Zhang, J. Wang, T. He, S. Hong, H. Liu, S. Zhang, K. Song, K. Zhu, et al., Advances and
challenges in foundation agents: From brain-inspired intelligence to evolutionary, collaborative,
and safe systems, arXiv preprint arXiv:2504.01990 (2025).
[38] J. He, C. Treude, D. Lo, Llm-based multi-agent systems for software engineering: Literature review,
vision and the road ahead, ACM Transactions on Software Engineering and Methodology (2024).
[39] L. Wang, F. Yang, C. Zhang, J. Lu, J. Qian, S. He, P. Zhao, B. Qiao, R. Huang, S. Qin, et al., Large
action models: From inception to implementation, arXiv preprint arXiv:2412.10047 (2024).
[40] A. Mao, D. Garijo, S. Fakhraei, Somef: A framework for capturing scientific software metadata
from its documentation, in: 2019 IEEE International Conference on Big Data (Big Data), 2019, pp.
3032–3037. doi:10.1109/BigData47090.2019.9006447.
[41] D. Guo, D. Yang, H. Zhang, J. Song, R. Zhang, R. Xu, Q. Zhu, S. Ma, P. Wang, X. Bi, et al.,
Deepseek-r1: Incentivizing reasoning capability in llms via reinforcement learning, arXiv preprint
arXiv:2501.12948 (2025).
[42] K. Pefers, T. Tuunanen, M. A. Rothenberger, S. Chatterjee, A design science research methodology
for information systems research, Journal of management information systems 24 (2007) 45–77.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>N. P.</given-names>
            <surname>Chue Hong</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D. S.</given-names>
            <surname>Katz</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Barker</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.-L.</given-names>
            <surname>Lamprecht</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Martinez</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F. E.</given-names>
            <surname>Psomopoulos</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Harrow</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L. J.</given-names>
            <surname>Castro</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Gruenpeter</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P. A.</given-names>
            <surname>Martinez</surname>
          </string-name>
          , T. Honeyman,
          <source>FAIR Principles for Research Software (FAIR4RS Principles)</source>
          (
          <year>2021</year>
          ). doi:
          <volume>10</volume>
          .15497/RDA00068.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>C.</given-names>
            <surname>Utrilla Guerrero</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Corcho</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Garijo</surname>
          </string-name>
          ,
          <source>Automated Extraction of Research Software Installation Instructions from README Files: An Initial Analysis, Lecture Notes in Computer Science 14770 LNAI</source>
          (
          <year>2024</year>
          )
          <fpage>114</fpage>
          -
          <lpage>133</lpage>
          . doi:
          <volume>10</volume>
          .1007/978- 3-
          <fpage>031</fpage>
          - 65794-
          <issue>8</issue>
          _
          <fpage>8</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>H.</given-names>
            <surname>Gao</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Treude</surname>
          </string-name>
          , M. Zahedi, ”
          <article-title>Add more config detail”: A Taxonomy of Installation Instruction Changes</article-title>
          ,
          <year>2023</year>
          . URL: http://arxiv.org/abs/2312.03250.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>L.</given-names>
            <surname>Salerno</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Treude</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Thongtanunam</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Thongtatunam</surname>
          </string-name>
          ,
          <article-title>Challenges and Strategies For Novice Developers</article-title>
          ,
          <source>Technical Report</source>
          ,
          <year>2024</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>S.</given-names>
            <surname>Yuan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Song</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Chen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Tan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Shen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Kan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Yang</surname>
          </string-name>
          ,
          <article-title>EASYTOOL: Enhancing LLM-based Agents with Concise Tool Instruction</article-title>
          ,
          <year>2024</year>
          . URL: http://arxiv.org/abs/2401.06201.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <surname>M. M. Wagner</surname>
            ,
            <given-names>W. R.</given-names>
          </string-name>
          <string-name>
            <surname>Hogan</surname>
            ,
            <given-names>J. D.</given-names>
          </string-name>
          <string-name>
            <surname>Levander</surname>
            ,
            <given-names>M. Diller,</given-names>
          </string-name>
          <article-title>Towards machine-fair: Representing software and datasets to facilitate reuse and scientific discovery by machines</article-title>
          ,
          <source>Journal of biomedical informatics 154</source>
          (
          <year>2024</year>
          )
          <fpage>104647</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>P.</given-names>
            <surname>Naur</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Randell</surname>
          </string-name>
          ,
          <article-title>Software engineering: Report on a conference by the nato science commitee</article-title>
          ,
          <source>NATO Scientific Afairs Division</source>
          ,
          <string-name>
            <surname>Brüssel</surname>
          </string-name>
          (
          <year>1968</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>R. S.</given-names>
            <surname>Sutton</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A. G.</given-names>
            <surname>Barto</surname>
          </string-name>
          , et al.,
          <article-title>Reinforcement learning: An introduction</article-title>
          , volume
          <volume>1</volume>
          , MIT press Cambridge,
          <year>1998</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>S. J.</given-names>
            <surname>Russell</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Norvig</surname>
          </string-name>
          ,
          <article-title>Artificial intelligence: a modern approach</article-title>
          , pearson,
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>S. M.</given-names>
            <surname>Narayanan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. D.</given-names>
            <surname>Braza</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.-R.</given-names>
            <surname>Grifiths</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Bou</surname>
          </string-name>
          , G. Wellawatte,
          <string-name>
            <given-names>M. C.</given-names>
            <surname>Ramos</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Mitchener</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S. G.</given-names>
            <surname>Rodriques</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A. D.</given-names>
            <surname>White</surname>
          </string-name>
          ,
          <article-title>Training a scientific reasoning model for chemistry</article-title>
          ,
          <source>arXiv preprint arXiv:2506.17238</source>
          (
          <year>2025</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>Z.</given-names>
            <surname>Luo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Z.</given-names>
            <surname>Yang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Z.</given-names>
            <surname>Xu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Yang</surname>
          </string-name>
          ,
          <string-name>
            <surname>X. Du,</surname>
          </string-name>
          <article-title>Llm4sr: A survey on large language models for scientific research</article-title>
          ,
          <source>arXiv preprint arXiv:2501.04306</source>
          (
          <year>2025</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>C.</given-names>
            <surname>Goodwin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Woolley</surname>
          </string-name>
          ,
          <article-title>Barriers to device longevity and reuse: A vintage device empirical study</article-title>
          ,
          <source>Journal of Systems and Software</source>
          <volume>211</volume>
          (
          <year>2024</year>
          )
          <fpage>111991</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>M.</given-names>
            <surname>Karimzadeh</surname>
          </string-name>
          ,
          <string-name>
            <surname>M. M. Hofman</surname>
          </string-name>
          ,
          <article-title>Top considerations for creating bioinformatics software documentation</article-title>
          ,
          <source>Briefings in Bioinformatics</source>
          <volume>19</volume>
          (
          <year>2018</year>
          )
          <fpage>693</fpage>
          -
          <lpage>699</lpage>
          . doi:
          <volume>10</volume>
          .1093/bib/bbw134.
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <given-names>N.</given-names>
            <surname>Shadbolt</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Berners-Lee</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Hall</surname>
          </string-name>
          ,
          <article-title>The semantic web revisited</article-title>
          ,
          <source>IEEE intelligent systems 21</source>
          (
          <year>2006</year>
          )
          <fpage>96</fpage>
          -
          <lpage>101</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <surname>M. D. Wilkinson</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Dumontier</surname>
            ,
            <given-names>I. J.</given-names>
          </string-name>
          <string-name>
            <surname>Aalbersberg</surname>
            , G. Appleton,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Axton</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Baak</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          <string-name>
            <surname>Blomberg</surname>
            ,
            <given-names>J.-W.</given-names>
          </string-name>
          <string-name>
            <surname>Boiten</surname>
            ,
            <given-names>L. B. da Silva</given-names>
          </string-name>
          <string-name>
            <surname>Santos</surname>
            ,
            <given-names>P. E.</given-names>
          </string-name>
          <string-name>
            <surname>Bourne</surname>
          </string-name>
          , et al.,
          <article-title>The fair guiding principles for scientific data management and stewardship</article-title>
          ,
          <source>Scientific data 3</source>
          (
          <year>2016</year>
          )
          <fpage>1</fpage>
          -
          <lpage>9</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <given-names>M.</given-names>
            <surname>Barker</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N. P.</given-names>
            <surname>Chue Hong</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D. S.</given-names>
            <surname>Katz</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A. L.</given-names>
            <surname>Lamprecht</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Martinez-Ortiz</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Psomopoulos</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Harrow</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L. J.</given-names>
            <surname>Castro</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Gruenpeter</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P. A.</given-names>
            <surname>Martinez</surname>
          </string-name>
          , T. Honeyman,
          <article-title>Introducing the FAIR Principles for research software</article-title>
          ,
          <source>Scientific Data</source>
          <volume>9</volume>
          (
          <year>2022</year>
          ). doi:
          <volume>10</volume>
          .1038/s41597- 022- 01710- x.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>