paperbd-study-paper
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChinesePaperBD Study Paper
使用PaperBD研究论文
Guide the user from paper identification to answering questions in Paper Breakdown.
引导用户完成从论文识别到借助Paper Breakdown解答问题的全流程。
1. Identify the paper
1. 识别论文
First, find the paper's arXiv ID.
- If the user already gave a valid arXiv ID, use it.
- If the user gave only a title, author, or vague description, identify the most likely arXiv paper.
- If multiple papers could match, ask one targeted follow-up question.
- Do not proceed to PaperBD commands until you have a specific arXiv ID.
首先,找到论文的arXiv ID。
- 如果用户已提供有效的arXiv ID,直接使用该ID。
- 如果用户仅提供了标题、作者或模糊描述,识别最匹配的arXiv论文。
- 如果存在多个可能匹配的论文,提出一个针对性的跟进问题。
- 在获取到具体的arXiv ID之前,不要执行PaperBD命令。
2. Verify that paperbd
is installed
paperbd2. 验证paperbd
是否已安装
paperbd- Ask the user to run if needed.
paperbd --help - If is missing, tell them to install it with
paperbd.npm i -g paperbd - Stop and wait for confirmation before continuing.
- 必要时请用户运行。
paperbd --help - 如果未安装,告知用户通过
paperbd进行安装。npm i -g paperbd - 在继续操作前,请等待用户确认安装完成。
3. Verify login status
3. 验证登录状态
- Prefer .
paperbd status - If the CLI indicates the user is not logged in, tell them to run .
paperbd login - Explain that login completes in the browser and then returns to the terminal.
- Stop and wait for confirmation before continuing.
- 优先使用命令。
paperbd status - 如果CLI显示用户未登录,告知用户运行命令。
paperbd login - 说明登录需在浏览器中完成,之后返回终端。
- 在继续操作前,请等待用户确认登录完成。
4. Verify access to the paper
4. 验证论文访问权限
Once you have an arXiv ID and a working logged-in CLI, tell the user to check access with:
bash
paperbd papers | grep <arxiv_id>Replace with the actual arXiv ID.
<arxiv_id>- If the paper appears, continue.
- If the paper does not appear, explain that they do not currently have access to that paper in Paper Breakdown.
- If the user wants to start a new paper review or add a paper that is not already available, tell them to go to to trigger it there first.
paperbreakdown.com
获取到arXiv ID且已完成CLI登录后,告知用户通过以下命令检查访问权限:
bash
paperbd papers | grep <arxiv_id>将替换为实际的arXiv ID。
<arxiv_id>- 如果论文出现在结果中,继续后续操作。
- 如果论文未出现,说明用户当前无法在Paper Breakdown中访问该论文。
- 如果用户希望开始新的论文审阅或添加未收录的论文,告知用户需先前往发起操作。
paperbreakdown.com
5. Tell the user how to ask questions
5. 告知用户如何提问
Run the following in the terminal:
bash
paperbd ask --arxiv <arxiv_id> --query "<question>"- returns actual PDF passages relevant to the question.
paperbd ask - This will print passages directly into the terminal
- Ask simple questions
在终端中运行以下命令:
bash
paperbd ask --arxiv <arxiv_id> --query "<question>"- 会返回与问题相关的PDF原文片段。
paperbd ask - 结果将直接打印在终端中
- 建议提出简单明确的问题
6. Answer the user's question
6. 解答用户的问题
After the paper is identified and access is confirmed, answer the user's actual question about the paper.
- If the user has not asked a concrete question yet, ask one targeted next question.
- Ask targeted questions one at a time.
- Keep follow-ups specific.
在完成论文识别和访问权限验证后,解答用户关于论文的实际问题。
- 如果用户尚未提出具体问题,提出一个针对性的跟进问题。
- 一次仅提出一个针对性问题。
- 跟进问题需具体明确。
Retrieval error handling
检索错误处理
401 Unauthorized- Auth issue. Ask user to paperbd login first
400 Bad Request- Missing one , or
queryarxiv_id
- Missing one
429 Too Many Requests- The user exceeded the CLI rate limit: 5 requests per 60 seconds
- Tell them to wait and follow if present
Retry-After
403 Forbidden- tier cannot use CLI retrieval
FREE - Or monthly CLI quota was exceeded: = 100,
STUDENT= 200RESEARCHER
404 Not Found- The paper is not accessible to that user
- New paper reviews must be started on
paperbreakdown.com
500 Internal Server Error- Unexpected server-side failure, such as retrieval pipeline or backend issues
When explaining an error, state the likely cause and the next action. Do not invent CLI capabilities.
401 Unauthorized- 认证问题,请用户先运行登录
paperbd login
- 认证问题,请用户先运行
400 Bad Request- 缺少或
query参数arxiv_id
- 缺少
429 Too Many Requests- 用户超出CLI请求限制:每60秒最多5次请求
- 告知用户等待,若存在头信息则按提示操作
Retry-After
403 Forbidden- FREE tier用户无法使用CLI检索功能
- 或月度CLI配额已用尽:STUDENT层级为100次,RESEARCHER层级为200次
404 Not Found- 用户无法访问该论文
- 新论文审阅需在上发起
paperbreakdown.com
500 Internal Server Error- 服务器端意外故障,例如检索流程或后端问题
解释错误时,说明可能的原因和下一步操作。请勿虚构CLI的功能。
Response style
回复风格
- Be operational and direct.
- Move the user to the next blocking step quickly.
- When blocked on installation, login, or access, do not continue as if the paper is available.
- Prefer one focused follow-up question over a large questionnaire.
- 注重实用性,表述直接。
- 尽快引导用户解决当前阻塞步骤。
- 若遇到安装、登录或访问权限问题导致阻塞,请勿假设论文可正常访问并继续操作。
- 优先提出一个聚焦的跟进问题,而非一系列问题。