ccf-literature-monitor

Scan recent arXiv/OpenReview papers, venue feeds, labs, and competitors for overlap. Use for 竞品监控, 新论文追踪, 论文跟踪, and recurring novelty watch. Give dated evidence and changes since the prior scan. Broad related-work retrieval belongs to ccf-literature-searcher.

By mikubaka88 · 840 installs

npx skills add mikubaka88/ccfa-skills --skill ccf-literature-monitor

Source repository · Upstream listing

CCF Literature Monitor Core Rule Monitor arXiv, OpenReview, conference/proceedings feeds, project pages, labs, and named competitors for new papers that could overlap with the user's idea or paper. Report findings factually. Do not exaggerate novelty threats, dismiss real overlap, or infer priority from weak evidence. Provide actionable signals: RELAX, RESEARCH, FOLLOW UP. Modes arxiv watch : scan recent papers in target categories or keyword clusters. venue watch : scan OpenReview, proceedings, accepted paper lists, or official venue pages. novelty check : compare a given idea with recent papers and flag overlap. trend scouting : summarize emerging directions, crowded areas, and under tested gaps. competitor tracking : monitor named research groups, labs, repositories, datasets, benchmarks, or authors. paper alert digest : produce a recurring watch report suitable for saving into a project folder. Skill Linkage @READS ccfa.yaml for idea state. @SHARES findings with ccf literature searcher . @SHARES novelty implications with ccf idea reviewer . @SHARES rescue or differentiation opportunities with ccf idea optimizer . @SHARES citation and positioning candidates with ccf paper writer . @FLAGS conflicting papers for ccf integrity auditor . Invocation Controls CCFA Handoff Mode: PARTIAL (Recommended). Follow metadata.ccf skill controls.handoff question mode and ../ccf common/references/handoff modes.md . Load ../ccf common/references/task modes.md before deciding exploratory, quick, or standard mode. Treat unpublished ideas, draft abstracts, methods, and results as private material. Load ../ccf common/references/privacy and evidence.md before using private text in queries. Use public safe keywords, public method names, venue names, and user approved query text. Load ../ccf common/references/review output standards.md when monitor results feed idea scoring, paper review, or score risk language. Workflow 1. Load references/monitoring workflow.md . 2. If project state is available ( ccfa.yaml ), read the current idea, target venue, claims, and tracked competitors. 3. Choose the mode and time window. If the user says "latest", "recent", "new", "this week", or "today", verify the current date and use an explicit date range. 4. Execute the requested monitoring mode using public safe queries and source quality exclusions from the shared policy. 5. Classify overlaps by problem, mechanism, evidence, benchmark, dataset, claim, and venue positioning. 6. Report new or materially changed findings, with precise implications for the requested research decision. Use existing report history to avoid presenting the same paper as new. 7. Execute already requested downstream work through its owner; otherwise offer optional handoff to ccf literature searcher for deep retrieval, ccf idea reviewer for score impact, ccf idea optimizer for differentiation, or ccf paper writer for related work integration. Output Contract For each monitoring execution, report in this structure: References references/monitoring workflow.md — Workflow, api key management, search strategy. references/report template.md — Output template and formatting. ../ccf common/references/source registry.yaml — Competitor and arxiv links. Execution And Persistence Distinguish a single scan from recurring monitoring. A recurring report format is not a scheduler: claim ongoing monitoring only after an actual authorized scheduled job exists. Record the time window and coverage; an empty scan is not proof of novelty. Deduplicate by stable paper identity and version, separating first publication from revisions. Batch independent feeds when supported; preserve real monitoring history under ../ccf common/references/artifact contracts.md . Follow no new files and existing project state authorization.