mikubaka88/ccfa-skills

ccf-literature-monitor

Scan recent arXiv/OpenReview papers, venue feeds, labs, and competitors for overlap.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/mikubaka88/ccfa-skills --skill ccf-literature-monitor

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

CCF Literature Monitor

Family File Contract

Before file work, reuse canonical paths and one task/artifact working directory; default to project-root ccfa-workfiles/<purpose>/<artifact-id>/. Update in place, preserve inputs, and use UTF-8 with Chinese-text checks. Apply artifact-contracts.md for naming, ownership, and task-created cleanup; handoffs inherit these paths.

Collaboration Contract

Before specialist execution, read and apply ccf-humanization first, then ccf-common. At every handoff, reuse their applicable active rules or refresh missing/changed ones. Both preflights are required even without prose; detailed editing, experiment, and maintenance modes run only when relevant.

Integrate necessary specialist contributions under one owner; reuse valid prerequisites and verify affected results. Follow the cooperation routes without duplicate reports.

Core Rule

Monitor arXiv, OpenReview, conference and journal feeds, original technical reports, project pages, labs, and named competitors for relevant new work. For novelty watch, inspect overlap; for trend scouting, also identify new observations, changed assumptions, and useful mechanisms. Report findings factually. Do not exaggerate novelty threats, dismiss real overlap, or infer priority from weak evidence. Provide actionable overlap 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. Keep an inspiration or conflicting observation distinct from a novelty threat; its relevance does not require a high overlap score.
  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.

Reuse stable paper IDs and versioned source evidence from the existing topic report; fetch targeted metadata before full text. Check updates within the actual requested window even when older content is cached. Optional expansion into extra topics follows Common's extended_search preference and never replaces the required current scan.

  1. Resolve a concrete evidence gap needed for the current deliverable through its owner and integrate the result. Complete requested downstream work; offer unrelated follow-up only when useful. RESEARCH and FOLLOW-UP describe findings, not automatic instructions to start retrieval, scoring, redesign, or rewriting.

Output Contract

Honor the user's requested shape and brevity. A short update gives the time range, source basis, new or changed findings, and their relevant consequence. An internal contribution returns those findings to its owner without a standalone report. Full monitoring reports use references/report-template.md as the single canonical structure; keep only relevant handoff signals and keep routine self-checks internal. Preserve actual coverage limits without repeating a disclaimer for every paper.

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.

同じリポジトリから

関連する Skills

すべての Skills
mikubaka88
コミュニティ

ccf-common

Required shared preflight for every CCFA skill after ccf-humanization: apply routing, scope, prerequisites, evidence rules, handoffs, and artifact contracts. Also maintain and audit these shared rules. Research deliverables remain with their specialist owners.

1時間の導入数
12
GitHub Stars
3363
更新日
10月31日
mikubaka88
コミュニティ

ccf-experiment-designer

Design and interpret CCF experiments: datasets, baselines, metrics, ablations, run requirements, observed feedback, and result-table contents. Use for 设计实验, 消融, benchmark planning, 实验结果分析, and research evidence design. Research engineer owns code implementation, reproduction, and training diagnostics; orchestrator coordinates campaigns.

1時間の導入数
11
GitHub Stars
3363
更新日
10月31日
mikubaka88
コミュニティ

ccf-humanization

Required first preflight before every CCFA skill, including research, review, retrieval, experiments, visuals, and maintenance. Keep reasoning and communication direct, remove empty defensive framing, and preserve evidence and uncertainty. Also use for 去防御性 and 论文人性化. Apply prose edits only within the authorized task; specialist skills retain ownership.

1時間の導入数
11
GitHub Stars
3363
更新日
10月31日
mikubaka88
コミュニティ

ccf-idea-optimizer

Develop and optimize rough CCF research ideas into problems, insights, mechanisms, and evidence plans. Use for 优化idea, 具象化idea, 找方向, 方向探索, and rescue routes when development is the requested deliverable. Judging whether an idea is worthwhile, novel, or coherent belongs to ccf-idea-reviewer even without scores; manuscript edits belong to ccf-paper-writer.

1時間の導入数
11
GitHub Stars
3363
更新日
10月31日