agentleFS
papersflow-aipapersflow-ai/papersflow-skills/skills/deepscan-monitor/SKILL.md

deepscan-monitor

Skill4 starsChanged 8 months agoMITView on GitHub

Run and monitor PapersFlow DeepScan jobs. Use when the user wants long-running research progress, intermediate findings, final reports, or plotting from a completed run.

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 6 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the user wants Claude to manage a longer-running PapersFlow research workflow instead of a single search call.

    line 8
  2. Very specific:

    Use run_deepscan to start the job.

    line 12
  3. Very specific:

    Use summarize_evidence when the user wants a cross-report summary from stored DeepScan history.

    line 23
  4. Very specific:

    Use run_python_plot only after you have stable report data worth plotting.

    line 24
  5. Distinctive:

    Do not imply the MCP server will push completion notifications into Claude automatically.

    line 28
  6. Very specific:

    Prefer get_deepscan_live_snapshot over get_deepscan_status when the user wants richer live information.

    line 30
  7. Distinctive:

    If a report is not ready yet, say that clearly and keep the next action obvious.

    line 31
  8. Distinctive:

    When a run is still active, summarize:

    line 35
  9. Distinctive:

    Keep updates brief unless the user asks for more detail.

    line 44
  10. Very specific:

    Use run_python_plot only for meaningful visualizations after you have stable report outputs, for example:

    line 48
  11. Distinctive:

    Do not generate plots for sparse or obviously low-quality data without saying so.

    line 55

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

DeepScan Monitor

Use this skill when the user wants Claude to manage a longer-running PapersFlow research workflow instead of a single search call.

Workflow

  1. Use run_deepscan to start the job.
  2. Immediately tell the user that the run is asynchronous.
  3. Poll with get_deepscan_live_snapshot for the best live view of:
    • progress
    • status message
    • checkpoint state
    • top papers
    • partial summary
    • key findings
  4. Fall back to get_deepscan_status if the user only wants lightweight progress checks.
  5. Once finalReportAvailable is true or the run is completed, call get_deepscan_report.
  6. Use summarize_evidence when the user wants a cross-report summary from stored DeepScan history.
  7. Use run_python_plot only after you have stable report data worth plotting.

Important Behavior

  • Do not imply the MCP server will push completion notifications into Claude automatically.
  • Poll deliberately and explain that the run is being checked.
  • Prefer get_deepscan_live_snapshot over get_deepscan_status when the user wants richer live information.
  • If a report is not ready yet, say that clearly and keep the next action obvious.

Progress Update Style

When a run is still active, summarize:

  • current status
  • progress percentage
  • current stage or status message
  • any checkpoint question
  • notable live papers
  • key findings if available

Keep updates brief unless the user asks for more detail.

Plotting Guidance

Use run_python_plot only for meaningful visualizations after you have stable report outputs, for example:

  • papers by year
  • citation distribution
  • venue distribution
  • grouped comparison across a small number of finished runs

Do not generate plots for sparse or obviously low-quality data without saying so.

Examples

  • User asks: "Run a DeepScan on evaluation benchmarks for agentic retrieval systems and keep me posted."
  • User asks: "Check how my DeepScan is progressing and tell me the key findings so far."
  • User asks: "The run is finished, summarize the final report and plot papers by year."
  • User asks: "Summarize the evidence from my recent DeepScan reports on protein structure prediction."

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.