Agent skill

Sciatlas Trend Report

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…

MITAuto-check passedKnowledge Management

Install Sciatlas Trend Report

skills CLI

$ npx skills add zjunlp/SciAtlas --skill sciatlas-trend-report -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install zjunlp/SciAtlas sciatlas-trend-report --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/zjunlp/SciAtlas.git skills-src && mkdir -p .claude/skills && cp -r skills-src/agent-skill/sciatlas-trend-report .claude/skills/sciatlas-trend-report && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "sciatlas-trend-report" agent skill from https://github.com/zjunlp/SciAtlas/tree/main/agent-skill/sciatlas-trend-report into .claude/skills/sciatlas-trend-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sciatlas-trend-report", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/zjunlp/SciAtlas/tree/main/agent-skill/sciatlas-trend-report

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add zjunlp/SciAtlas --skill sciatlas-trend-report -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install zjunlp/SciAtlas sciatlas-trend-report --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/zjunlp/SciAtlas.git skills-src && mkdir -p .agents/skills && cp -r skills-src/agent-skill/sciatlas-trend-report .agents/skills/sciatlas-trend-report && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "sciatlas-trend-report" agent skill from https://github.com/zjunlp/SciAtlas/tree/main/agent-skill/sciatlas-trend-report into .agents/skills/sciatlas-trend-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sciatlas-trend-report", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add zjunlp/SciAtlas --skill sciatlas-trend-report -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install zjunlp/SciAtlas sciatlas-trend-report --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/zjunlp/SciAtlas.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/agent-skill/sciatlas-trend-report .cursor/skills/sciatlas-trend-report && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "sciatlas-trend-report" agent skill from https://github.com/zjunlp/SciAtlas/tree/main/agent-skill/sciatlas-trend-report into .cursor/skills/sciatlas-trend-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sciatlas-trend-report", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/zjunlp/SciAtlas.git --path agent-skill/sciatlas-trend-report

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add zjunlp/SciAtlas --skill sciatlas-trend-report -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install zjunlp/SciAtlas sciatlas-trend-report --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/zjunlp/SciAtlas.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/agent-skill/sciatlas-trend-report .gemini/skills/sciatlas-trend-report && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "sciatlas-trend-report" agent skill from https://github.com/zjunlp/SciAtlas/tree/main/agent-skill/sciatlas-trend-report into .gemini/skills/sciatlas-trend-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sciatlas-trend-report", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install zjunlp/SciAtlas sciatlas-trend-report

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add zjunlp/SciAtlas --skill sciatlas-trend-report -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/zjunlp/SciAtlas.git skills-src && mkdir -p .github/skills && cp -r skills-src/agent-skill/sciatlas-trend-report .github/skills/sciatlas-trend-report && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "sciatlas-trend-report" agent skill from https://github.com/zjunlp/SciAtlas/tree/main/agent-skill/sciatlas-trend-report into .github/skills/sciatlas-trend-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sciatlas-trend-report", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add zjunlp/SciAtlas --skill sciatlas-trend-report -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install zjunlp/SciAtlas sciatlas-trend-report --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/zjunlp/SciAtlas.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/agent-skill/sciatlas-trend-report .opencode/skills/sciatlas-trend-report && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "sciatlas-trend-report" agent skill from https://github.com/zjunlp/SciAtlas/tree/main/agent-skill/sciatlas-trend-report into .opencode/skills/sciatlas-trend-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sciatlas-trend-report", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: sciatlas-trend-report
GitHub stars: 160
Token cost: ~965 tokens
SKILL.md length: 361 words
Files: 2
Skills in repo: 7
Repo updated: Sep 30, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

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…

Works in 4 steps: Check whether the sciatlas executable… → If there is no SCIATLAS_API_KEY, guide… → Configure → …
The user asks for topic history
SKILL.md covers Operating Contract, Zero-Start Bootstrap, Search Plan and Reading Artifacts, plus 2 more sections
Calls python; reaches sciatlas.openkg.cn; needs SCIATLAS_API_KEY

What it does

Sciatlas Trend Report is an agent skill from zjunlp/SciAtlas. 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.

Its SKILL.md is about 970 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Knowledge Management. The repository describes itself as: A Large-Scale Knowledge Graph for Automated Scientific Research. The licence is MIT.

When your agent uses it

The user asks for topic history
Field evolution
Representative papers over time
Emerging directions

Example prompts

“/sciatlas-trend-report”

Requirements

Python 3
A credential in SCIATLAS_API_KEY

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

Check whether the sciatlas executable exists without invoking a SciAtlas command: use Get-Command sciatlas -ErrorAction SilentlyContinue…
If there is no SCIATLAS_API_KEY, guide registration at http://sciatlas.openkg.cn/register, asking for email/code/token only when needed.
Configure
Use search-papers --top-k 1 as the only token smoke test if needed.

What it can do on your machine

Read from SKILL.md and the folder at commit e8873a9. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- python
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- sciatlas.openkg.cn
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
- SCIATLAS_API_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Sciatlas Trend Report loads about 965 tokens when it runs. Until then it costs about 94 tokens; SKILL.md has 361 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~94
When it runs · the whole SKILL.md, loaded when a task matches: ~965

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from zjunlp/SciAtlas at commit e8873a9, republished under its MIT licence (© zjunlp). 361 words, ~965 tokens.

Download SKILL.mdSave it as .claude/skills/sciatlas-trend-report/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

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:

powershell

$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>"

bash

export SCIATLAS_API_BASE_URL="http://sciatlas.openkg.cn"
export SCIATLAS_API_KEY="<token>"

Use search-papers --top-k 1 as the only token smoke test if needed.

Search Plan

Run only search-papers. Use a time range whenever possible:

bash

sciatlas search-papers --retrieval-mode hybrid --query "<topic>" --time-range "<start-end>" --keyword "high:<core topic>" --top-k 12 --top-keywords 0 --max-titles 0 --max-refs 0 --bias-citation high --bias-exploration middle --ranking-profile impact --report-max-items 12

If the user asks for "recent trends", default to the last five complete years unless the current year matters.

If the field has older foundations, run one foundation search without the recent time range:

bash

sciatlas search-papers --retrieval-mode hybrid --query "<topic> foundational work" --keyword "high:<core topic>" --top-k 6 --top-keywords 0 --max-titles 0 --max-refs 0 --bias-citation high --ranking-profile impact --report-max-items 6

Show full SKILL.md (147 more words)Show less

Reading Artifacts

Read report.md and response.json. Build a timeline ledger:

Paper title.
Year.
Main contribution.
Theme.
Whether it is foundation, transition, consolidation, or emerging direction.
Evidence phrase.

Trend Analysis Method

Sort papers by year.
Bucket years into phases. Use natural breaks in the result set, not arbitrary equal chunks.
For each phase, identify the dominant problem, method, and evaluation pattern.
Track what changed: data scale, model architecture, retrieval strategy, benchmark, deployment setting, or theoretical framing.
Identify representative papers for each phase and explain why they represent that phase.
Separate "well-supported trend" from "possible emerging signal." Emerging signals need at least 2 papers or a clear recent change in framing.
End with open questions and next searches.

Deliverable

Return:

Search command(s), with token omitted.
Timeline table.
3-5 trend phases.
Representative papers per phase.
Emerging directions and weak signals.
Next search-papers queries.

Files

SKILL.md and 1 other file in agent-skill/sciatlas-trend-report of zjunlp/SciAtlas.

SKILL.md
agents/openai.yaml

Open the folder on GitHubat commit e8873a9

Compare with similar skills

Sciatlas Trend Report next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Sciatlas Trend Report compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Sciatlas Trend Report this skillzjunlp/SciAtlas	160	—	~965	Automated safety check: Pass	MIT	10 days ago
Logseq Review Workflow Evallogseq/logseq	45k	—	~1k	Automated safety check: Pass	AGPL-3.0	today
Baoyu URL To Markdownsdyckjq-lab/llm-wiki-skill	2.5k	2 repos	~3.2k	Automated safety check: Pass	None	2 mo ago
Obsidian CLIAtmosphere/atmosphere	3.8k	13 repos	~795	Automated safety check: Pass	Apache-2.0	yesterday
Esm Cjs Risk Scanlogseq/logseq	45k	—	~3.3k	Automated safety check: Pass	AGPL-3.0	today
Knowledge Searchdataelement/bisheng	12k	—	~1.1k	Automated safety check: Pass	Apache-2.0	today

Similar skills

Logseq Review Workflow Eval
logseq/logseq
Compare two revisions of the Logseq logseq-review-workflow skill by running the same review prompt against isolated before and after skill snapshots, collecting both outputs, and producing a…
45k GitHub stars~1k tokensUpdated today
Knowledge ManagementAuto-check passed
Baoyu URL To Markdown
sdyckjq-lab/llm-wiki-skill
Fetch any URL and convert to markdown using Chrome CDP. An agent skill from sdyckjq-lab/llm-wiki-skill.
2.5k GitHub starsUsed in 2 repos~3.2k tokens
Knowledge ManagementAuto-check passed
Obsidian CLI
Atmosphere/atmosphere
Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more.
3.8k GitHub starsUsed in 13 repos~795 tokens
Knowledge ManagementAuto-check passed
Esm Cjs Risk Scan
logseq/logseq
Scan Logseq ClojureScript Node/Electron targets for npm module loading risks, especially ESM-only packages that may fail when loaded through js/require or shadow-cljs require-based shims.
45k GitHub stars~3.3k tokensUpdated today
Knowledge ManagementAuto-check passed
Knowledge Search
dataelement/bisheng
Search the user's knowledge bases and knowledge spaces (企业知识库检索).
12k GitHub stars~1.1k tokensUpdated today
Knowledge ManagementAuto-check passed
Capture Conversation
outline/outline
Save the current conversation, a decision, or a set of notes as a document in an Outline collection; use when the user wants to keep what was discussed in their knowledge base.
41k GitHub stars~474 tokensUpdated today
Knowledge ManagementAuto-check passed

More from zjunlp/SciAtlas

Sciatlas Idea Evaluate
zjunlp/SciAtlas
Use only the current SciAtlas automated review workflow (reviewpipeline) to take a novice user from zero setup to a final automated review of a research idea or paper, including setup, registration…
160 GitHub stars~2.2k tokensUpdated 10 days ago
Auto-check: notes
Sciatlas Idea Generate
zjunlp/SciAtlas
Use only the current SciAtlas multi-step idea-generation workflow (sciatlasideagen) to take a novice user from zero setup to final literature-grounded research idea seeds, including setup…
160 GitHub stars~1.7k tokensUpdated 10 days ago
Auto-check: notes
Sciatlas Idea Grounding
zjunlp/SciAtlas
Use only SciAtlas search-papers to take a novice user from zero setup to final prior-art grounding for a research idea, including setup, registration guidance, configuration, retrieval, artifact…
160 GitHub stars~1.1k tokensUpdated 10 days ago
Auto-check passed
Sciatlas Literature Review
zjunlp/SciAtlas
Use only the current SciAtlas literature-review workflow (literaturereviewpipeline) to take a novice user from zero setup to a final evidence-grounded survey outline, paper map, or literature…
160 GitHub stars~1.7k tokensUpdated 10 days ago
Auto-check: notes
Sciatlas Quick Paper Search
zjunlp/SciAtlas
Use only SciAtlas search-papers to take a novice user from zero setup to a final small evidence-backed paper search result, including setup, registration guidance, configuration, retrieval, artifact…
160 GitHub stars~1.3k tokensUpdated 10 days ago
Auto-check passed
Sciatlas Researcher Review
zjunlp/SciAtlas
Use only SciAtlas search-papers to take a novice user from zero setup to a final evidence-grounded researcher profile from retrieved papers, including setup, registration guidance, configuration…
160 GitHub stars~1.1k tokensUpdated 10 days ago
Auto-check passed

Questions about Sciatlas Trend Report

What does Sciatlas Trend Report do?

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…. Sciatlas Trend Report is an agent skill from zjunlp/SciAtlas. 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.

When should I use Sciatlas Trend Report?

Sciatlas Trend Report fits situations like: the user asks for topic history; field evolution; representative papers over time; emerging directions.

How do I install Sciatlas Trend Report in Claude Code?

Run `npx skills add zjunlp/SciAtlas --skill sciatlas-trend-report -a claude-code`. Or copy the skill folder (agent-skill/sciatlas-trend-report in zjunlp/SciAtlas) into .claude/skills/sciatlas-trend-report in your project. Claude Code loads it when a task matches its description.

How do I install Sciatlas Trend Report in Codex?

Run `npx skills add zjunlp/SciAtlas --skill sciatlas-trend-report -a codex`. Or copy the skill folder (agent-skill/sciatlas-trend-report in zjunlp/SciAtlas) into .agents/skills/sciatlas-trend-report in your project. Codex loads it when a task matches its description.

Can I use Sciatlas Trend Report in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add zjunlp/SciAtlas --skill sciatlas-trend-report -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sciatlas-trend-report, .gemini/skills/sciatlas-trend-report, .github/skills/sciatlas-trend-report and .opencode/skills/sciatlas-trend-report in your project.

What does Sciatlas Trend Report need to run?

Going by SKILL.md and its folder, Sciatlas Trend Report needs the command-line tools its instructions call (python) and credentials named SCIATLAS_API_KEY. Our summary lists: Python 3; A credential in SCIATLAS_API_KEY.

Does Sciatlas Trend Report access the network?

SKILL.md names 1 domain. In commands or code: sciatlas.openkg.cn; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Sciatlas Trend Report safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Sciatlas Trend Report use?

Sciatlas Trend Report is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Sciatlas Trend Report use?

About 965 tokens (SKILL.md is roughly 3.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Sciatlas Trend Report?

Skills that share tags, products or a category with Sciatlas Trend Report: Logseq Review Workflow Eval (logseq/logseq, 45k stars), Baoyu URL To Markdown (sdyckjq-lab/llm-wiki-skill, 2.5k stars), Obsidian CLI (Atmosphere/atmosphere, 3.8k stars) and Esm Cjs Risk Scan (logseq/logseq, 45k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Sciatlas Trend Report?

zjunlp (a GitHub organization) maintains it in zjunlp/SciAtlas, which has 160 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on September 30, 2026.

Source: zjunlp/SciAtlas on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Sciatlas Trend Report

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

SciAtlas Trend Report

Operating Contract

Zero-Start Bootstrap

Search Plan

Reading Artifacts

Trend Analysis Method

Deliverable

Files

Compare with similar skills

Similar skills

More from zjunlp/SciAtlas

Related

Questions about Sciatlas Trend Report