Scholar Search Workflow

This skill only uses arXiv as the data source. The workflow is fixed:

1. Read user input and parse the search intent.
2. Call the arXiv API (via arxiv_search).
3. Evaluate result quality and decide whether another search round is needed.
4. Output results using the required template.

0) File Layout (Overview)

File Path	Purpose	When to Check
SKILL.md	Main entry: task parsing, query syntax, calling conventions, quality control	Check first at the beginning of every task

1) Parse User Search Requirements

Extract the following constraints first:

1. Topic keywords (Chinese or English).
2. Time preference (for example: "latest", "this year", "last three years").
3. Number of results (for example: 5, 10, 20).
4. Output goal (paper discovery, comparison, or brief survey).
5. Output language (Chinese or English).

Keyword strategy:

1. Use a broad query in round one (topic terms only).
2. Add constraint terms in round two (method terms, task terms, category terms).
3. If results are too few, switch to synonyms or broader terms.

2) arXiv API Guide (Built-in)

2.1 API Endpoint

1. Base endpoint: https://export.arxiv.org/api/query
2. Request methods: GET (common), POST (optional when parameters are very long)

2.2 Core Parameters

1. search_query: query expression
2. id_list: comma-separated list of arXiv IDs
3. start: pagination offset (0-based)
4. max_results: number of returned entries
5. sortBy: relevance / lastUpdatedDate / submittedDate
6. sortOrder: ascending / descending

2.3 search_query Syntax

Common field prefixes:

1. ti (title)
2. au (author)
3. abs (abstract)
4. cat (category)
5. all (all fields)

Boolean operators:

1. AND
2. OR
3. ANDNOT

Time syntax (submittedDate):

1. Range: submittedDate:[200701*+TO+200712*]
2. Specific day: submittedDate:20101225

2.4 Direct URL Examples

1. Topic query: https://export.arxiv.org/api/query?search_query=all:electron
2. Combined query: https://export.arxiv.org/api/query?search_query=au:del_maestro+AND+ti:checkerboard
3. Paginated query: https://export.arxiv.org/api/query?search_query=all:electron&start=0&max_results=10
4. Sorted query: https://export.arxiv.org/api/query?search_query=ti:%22electron+thermal+conductivity%22&sortBy=lastUpdatedDate&sortOrder=descending

2.5 Rate Limits and Stability (Must Follow)

1. Keep request frequency at no more than one request every 3 seconds.
2. Use only one active connection at a time.
3. Avoid high-frequency repeated queries; reuse existing results whenever possible.

3) Calling Conventions (Must Match Actual Use)

Standard call example:

curl -s "https://export.arxiv.org/api/query?search_query=all:multimodal+AND+cat:cs.CL&start=0&max_results=10&sortBy=submittedDate&sortOrder=descending"

Parameter notes:

1. search_query: arXiv query expression (supports field prefixes and boolean operators).
2. start: pagination offset (0-based).
3. max_results: number of returned entries; recommend 5-20.
4. sortBy: recommend submittedDate or lastUpdatedDate.
5. sortOrder: recommend descending.

4) Decide Whether to Continue Searching

Run one more search round if any condition below is met:

1. Too few papers are returned (for example, < 3).
2. Results are clearly off-topic.
3. Key fields are frequently missing (title, link, abstract).

Stop searching when:

1. Result count reaches the target or an acceptable range.
2. Topic relevance is high.
3. Additional search rounds provide low value.

5) Output Requirements

Each paper must use the following structure:

-----------
# {Index}. **{Paper Title}**

**Paper Info**: **Venue/Source**: {journal, conference, or source} | **Publication Date**: {yyyy-mm-dd or unknown} | **Source**: [{source name}]({entry link or paper link}) | **PDF**: [PDF link]({pdf link})

### Research Content
{1-2 objective sentences based on the paper content}

### Main Contributions
- {Contribution 1}
- {Contribution 2}
- {Contribution 3}

Must follow:

1. Add a standalone line ----------- before every paper title.
2. Keep the title as a standalone level-1 header line.
3. Keep "Paper Info" in a single line, separated by |.
4. Keep the PDF field:
   • If a PDF exists: provide a direct link.
   • If no PDF exists: remove the PDF field.
5. Content must be based only on source metadata, abstract, or TLDR. No speculation.
6. Do not add conclusions not explicitly supported by the source.
7. All links must come from tool output. Do not fabricate or guess links.
8. Do not fabricate venue, date, or citation count.
9. Write "Research Content" and "Main Contributions" only from returned fields.

6) Failure Handling

1. API failure: state the reason and the strategies already attempted.
2. No results: provide actionable keyword rewrite suggestions.
3. Missing fields: explicitly mark as "unknown/missing"; do not fill with inferred data.