rw-literature-discovery

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

RW Literature Discovery

RW Literature Discovery

围绕具体判断发现、核验和记录文献,并根据证据修改搜索方向。
Discover, verify, and document literature based on specific judgments, and adjust search directions according to evidence.

启动

Startup

  1. 读取
    references/standalone.md
    references/method.md
    references/standards.md
  2. 读取用户本轮提供的材料;没有材料时,只完成当前证据允许的部分。
  3. 需要规则判断时检索
    references/atoms.jsonl
    ;遇到相似任务时读取
    references/cases.md
  4. 需要选择方法或工具时读取
    references/domain-guide.md
    ,并使用
    assets/worksheet.md
    组织交付。
  5. 读取
    references/acceptance.md
    references/behavior-tests.json
    只用于测试,不作为用户任务事实。
  6. 当前文献、API、报告规范和期刊要求可能变化时,打开
    references/source-map.md
    中的官方链接核验并记录日期。
  1. Read
    references/standalone.md
    ,
    references/method.md
    , and
    references/standards.md
    .
  2. Read the materials provided by the user in this round; if no materials are provided, only complete the parts permitted by current evidence.
  3. Retrieve
    references/atoms.jsonl
    when rule-based judgments are required; read
    references/cases.md
    when encountering similar tasks.
  4. Read
    references/domain-guide.md
    when selecting methods or tools, and use
    assets/worksheet.md
    to organize deliverables.
  5. Read
    references/acceptance.md
    .
    references/behavior-tests.json
    is only used for testing and not as factual information for user tasks.
  6. When current literature, APIs, reporting standards, or journal requirements may change, open the official links in
    references/source-map.md
    for verification and record the date.

工作阶段

Work Stages

  1. 把请求改写成需要支持、反驳、界定或解释的具体判断。
  2. 建立概念块、同义词、拼写变体、受控词和排除词。
  3. 按学科选择至少两个互补来源,并记录数据库和检索日期。
  4. 先找种子文献,再做向前、向后和相似文献追踪。
  5. 逐条核验题名、作者、年份、来源、标识符、文献类型和可取得层级。
  6. 按标识符、规范化题名、版本关系和撤回状态去重,不把预印本与期刊版本当成两份独立证据。
  7. 记录纳入用途、排除理由、证据冲突、失败来源和下一轮搜索缺口。
  1. Rewrite the request into a specific judgment that needs to be supported, refuted, defined, or explained.
  2. Establish concept blocks, synonyms, spelling variants, controlled terms, and exclusion terms.
  3. Select at least two complementary sources by discipline, and record the database and retrieval date.
  4. First find seed literature, then conduct forward, backward, and similar literature tracking.
  5. Verify title, author, year, source, identifier, literature type, and access level item by item.
  6. Deduplicate by identifier, standardized title, version relationship, and retraction status; do not treat preprints and journal versions as two separate pieces of evidence.
  7. Record inclusion purposes, exclusion reasons, evidence conflicts, failed sources, and gaps for the next round of search.

运行规则

Operational Rules

  • 文献发现服务于判断,不以文献数量作为完成标准。
  • 探索性检索和可复现系统检索要分开记录。
  • 单一数据库的缺失不能解释为没有研究。
  • 题名相似不能替代 DOI、PMID 或出版元数据核验。
  • 摘要只能支持摘要中明确报告的内容。
  • 预印本、会议摘要、期刊论文和撤稿记录要区分状态。
  • 引用次数可以帮助发现入口,不能直接证明研究质量。
  • 搜索式要保存原样、日期、平台和返回数量。
  • 同义词扩展要与结果噪声一起测试。
  • 遇到反常结果时要搜索替代解释和否定证据。
  • API 失败、限流或覆盖不足时要有人工检索回退。
  • 正式文献清单中的每项都要说明它支持、限制或改变哪个判断。
  • 每条记录标记为全文已核验、仅摘要、仅元数据或无法取得;可支持范围不能超过已取得内容。
  • 搜索失败、权限限制、超时和字段缺失要保留在运行记录中,不能静默删除。
  • 文献筛选使用可解释条件,不用期刊名、作者头衔或固定综合分数代替相关性和证据判断。
  • 涉及数据或文献是否为当前可用版本时,记录数据年份、发表年份、核验日期、预计刷新时间和发布来源。
  • 只有核验过同类来源的更新时间后才写 latest;否则直接写数据版本和发表年份。
  • Literature discovery serves judgment; the number of documents is not used as the completion standard.
  • Exploratory retrieval and reproducible systematic retrieval must be recorded separately.
  • The absence of results in a single database cannot be interpreted as the absence of research.
  • Similar titles cannot replace verification of DOI, PMID, or publication metadata.
  • Abstracts can only support content explicitly reported in the abstract.
  • Distinguish the status of preprints, conference abstracts, journal articles, and retraction records.
  • Citation counts can help find entry points but cannot directly prove research quality.
  • Save search queries as-is, along with the date, platform, and number of returns.
  • Synonym expansion must be tested alongside result noise.
  • When encountering abnormal results, search for alternative explanations and contradictory evidence.
  • Have a manual retrieval fallback when APIs fail, are rate-limited, or have insufficient coverage.
  • Each item in the official literature list must explain which judgment it supports, limits, or changes.
  • Mark each record as full-text verified, abstract-only, metadata-only, or unavailable; the supportable scope cannot exceed the obtained content.
  • Search failures, permission restrictions, timeouts, and missing fields must be retained in the run records and cannot be silently deleted.
  • Use interpretable criteria for literature screening; do not use journal names, author titles, or fixed composite scores as substitutes for relevance and evidence judgments.
  • When determining whether data or literature is the currently available version, record the data year, publication year, verification date, expected refresh time, and publishing source.
  • Only use "latest" after verifying the update time of similar sources; otherwise, directly write the data version and publication year.

输出

Output

  • 带查询、来源、时间和失败项的运行记录。
  • 经核验并标注用途、版本关系和可取得层级的文献清单。
  • 冲突、缺口、停止状态和下一轮查询。
  • Run records with queries, sources, timestamps, and failed items.
  • A verified literature list marked with purposes, version relationships, and access levels.
  • Conflicts, gaps, stop status, and next-round queries.

停止条件

Stop Conditions

  • 无法核验基本书目信息时,不进入正式文献清单。
  • 需要系统综述级完整性时,不能只使用开放聚合 API。
  • 不绕过付费墙或访问控制获取全文。
  • 不把搜索排序、期刊层级或作者身份当成证据等级。
  • Do not include items in the official literature list if basic bibliographic information cannot be verified.
  • When systematic review-level completeness is required, do not only use open aggregation APIs.
  • Do not bypass paywalls or access controls to obtain full texts.
  • Do not treat search rankings, journal tiers, or author status as evidence levels.

独立运行

Standalone Operation

  • 默认不读取私人工作区、个人语料目录或预设 research-lab。
  • 用户提供的文件、文本、链接和数据是当前任务输入,不是安装依赖。
  • 网络不可用时,使用 Skill 内的稳定方法继续;需要当前事实的部分标记为待核验。
  • 本包内其他科研 Skill 存在时可以接续;单独安装时直接返回下一步说明,不停止当前任务。
  • By default, do not read private workspaces, personal corpus directories, or preset research-lab.
  • Files, text, links, and data provided by the user are inputs for the current task, not installation dependencies.
  • When the network is unavailable, use stable methods within the Skill to continue; mark parts requiring current facts as pending verification.
  • Can continue when other research Skills in this package exist; when installed alone, directly return instructions for the next step without stopping the current task.

来源纪律

Source Discipline

  • 把用户材料、公开来源、当前推断和未知事项分开。
  • 报告规范只检查报告透明度,不自动证明设计质量。
  • 公开来源摘要保存在 Skill 内;需要版本、费用、政策、API 或期刊现状时回到官方页面。
  • 不生成不存在的论文、数据、DOI、工具运行结果或期刊要求。
  • Separate user materials, public sources, current inferences, and unknown matters.
  • Reporting standards only check report transparency and do not automatically prove design quality.
  • Abstracts from public sources are stored within the Skill; return to official pages when needing information on versions, fees, policies, APIs, or current journal status.
  • Do not generate non-existent papers, data, DOIs, tool operation results, or journal requirements.