| name | sciatlas-trend-report |
| description | Use only SciAtlas search-papers to take a novice user from zero setup to a final timeline-oriented research trend report, including setup, registration guidance, configuration, retrieval, artifact reading, and synthesis. Trigger when the user asks for topic history, field evolution, recent trends, representative papers over time, or emerging directions. |
SciAtlas Trend Report
Use this skill to build a trend report from search-papers evidence only.
Operating Contract
- Do not call any SciAtlas downstream command. The only SciAtlas retrieval command allowed is
search-papers.
- Own the end-to-end novice flow: install or locate the CLI, guide registration, configure environment variables, run retrieval, inspect artifacts, and write the trend report.
- Ask the user only for email, verification code, token, or the desired time range if it is essential.
- Do not ask the user to run shell commands when tool access is available.
- Do not reveal the full token.
Zero-Start Bootstrap
- Check whether the
sciatlas executable exists without invoking a SciAtlas command: use Get-Command sciatlas -ErrorAction SilentlyContinue on Windows PowerShell or command -v sciatlas on macOS/Linux. Install if needed with python -m pip install -e ./sciatlas or python -m pip install "git+https://github.com/zjunlp/SciAtlas.git#subdirectory=sciatlas".
- If there is no
SCIATLAS_API_KEY, guide registration at http://sciatlas.openkg.cn/register, asking for email/code/token only when needed.
- Configure:
$env:SCIATLAS_API_BASE_URL = "http://sciatlas.openkg.cn"
$env:SCIATLAS_API_KEY = "<token>"
setx SCIATLAS_API_BASE_URL "http://sciatlas.openkg.cn"
setx SCIATLAS_API_KEY "<token>"