Results for “paper”

Create or enrich a pursuit capture brief from USASpending bulk data, optional SAM live intel, and optional LLM narrative. Use when opening a recompete workspace, scaffolding admin paperwork, or when the user asks for a one-page pursuit snapshot with citations.

Use when designing or auditing experiments for an ACL paper, covering tuned LLM baselines, multi-dataset and multilingual evaluation, statistical significance and variance, human evaluation with agreement reporting, contamination and prompt-sensitivity controls, ablations, and error-analysis expectations in NLP reviewing.

Download, split, and deeply read academic PDFs. Use when asked to read, review, or summarize an academic paper. Splits PDFs into 4-page chunks, reads them in small batches, and produces structured reading notes — avoiding context window crashes and shallow comprehension.

Run a pre-mortem risk analysis on a PRD or launch plan, categorizing risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifying by urgency and creating action plans.

Systematically evaluate scholarly work using the ScholarEval framework, providing structured assessment across research quality dimensions including problem formulation, methodology, analysis, and writing with quantitative scoring and actionable feedback.

Monitor Hacker News, Reddit, and arXiv for AI agent developments and trending topics. Use when the user wants a summary of recent AI agent news, needs to search for specific research papers, or wants to set up automated news digests in heartbeats.

Use to choose the PNAS submission track — Direct Submission (standard, editor-assigned, peer reviewed) vs Contributed Submission (an NAS member communicates their own paper). Covers eligibility, the editor/member role, the discontinued and legacy tracks, and how to pick. Unique to PNAS.

Use when a research implementation plan exists in docs/superpapers/plans/ and the user is ready to execute it — collecting data, running analysis, producing outputs, writing the paper. Orchestrates task execution with replication-driven verification and two-stage review at phase boundaries.

Use when planning a SOSP campaign across the annual cycle — back-scheduling from the spring abstract and paper deadlines, running the summer response and July notification, stacking the August camera-ready with artifact evaluation, and retargeting rejections across the SOSP/OSDI/EuroSys circuit.

Call a DeepSeek-backed OpenCode agent as a separate critique, writing, or revision agent from Codex. Use when Codex needs to delegate adversarial research critique, novelty skepticism, method review, manuscript prose, LaTeX section drafting, academic text revision, or paper-writing feedback loops to DeepSeek.

Perform an exhaustive, multi-pass proofread and copy-edit of an applied-microeconomics manuscript to top-economics-journal standards (AER, QJE, Econometrica, ReStud), checking prose, equations, table notes, footnotes, and citations for avoidable errors. Use before submitting or circulating an empirical economics paper.

Connects AI assistants to the Hugging Face Hub via MCP server tools to search models, datasets, Spaces, and papers, retrieve repo details and documentation, run compute jobs, and use Gradio Spaces as AI tools.

Use when auditing an ACL submission before an ACL Rolling Review cycle deadline, covering long/short paper page budgets, the mandatory Limitations section, Responsible NLP checklist, anonymized PDFs and supplements, preprint declarations, dual-submission rules, resubmission linking, and ARR desk-reject triggers on OpenReview.

Master the AI tools that accelerate research and information gathering. From market research to academic analysis, find insights faster and make better decisions. Use when "research, find information, academic papers, market research, competitive intelligence, fact check, research, information, analysis, academic, market-research" mentioned.

Use when starting a new research project, exploring a research idea, deciding whether a question is viable, or before touching code or data for a new paper. Runs a research-focused brainstorm that clarifies research question, identification strategy, data feasibility, and contribution before any implementation.

Use when planning a COLT (Conference on Learning Theory) submission calendar backward from the single AoE paper deadline — proof-completion and verification milestones, writing and appendix-assembly passes, CMT logistics, the rebuttal window, decision aftermath, and PMLR camera-ready with conference presentation in early summer.

Use when planning a CVPR submission campaign end to end, covering the November abstract/paper/supplement deadline chain, coauthor reviewer-duty scheduling, the January rebuttal sprint, February decisions, camera-ready and June conference logistics, and the resubmission ladder across ICCV, ECCV, and the next CVPR.

Use when auditing an ESEC/FSE research-track submission for HotCRP readiness, covering the mandatory paper-registration step, the ACM Primary Article Template page budget, double-anonymous "heavy" anonymity, the open-science Data Availability statement, PACMSE publication, and desk-reject triage before the AoE cutoff.

Use when planning or managing a full OSDI cycle — the December title-registration and submission deadlines on HotCRP, the silent no-rebuttal review window, March notification, the May artifact deadline, June shepherded final papers, and the July conference — including rejection retargeting to SOSP or NSDI.

Use when planning a VLDB project on the PVLDB rolling calendar, covering month-picking strategy, the volume-to-conference mapping and acceptance cutoff, budgeting a possible three-month revision, coordinating author caps across a group, and backward planning from the 25th-abstract / 1st-paper rhythm.

Use when planning a UIST cycle end to end — the late-March abstract and paper deadlines, the ten-week build-freeze before video production, the rebuttal window, conditional acceptance, the July camera-ready, adjunct-track parallel lanes, and the November conference — with owners and risk buffers.

Use when designing or auditing the evaluation of an ASE (IEEE/ACM Automated Software Engineering) paper, covering real subject systems, fair runnable tool baselines, task-matched effectiveness metrics, ablations that isolate a learned component, oracle and correctness validation, contamination-aware LLM handling, and provenance for mining.

any input (code, docs, papers, images) → knowledge graph → clustered communities → HTML + JSON + audit report. Use when user asks any question about a codebase, project content, architecture, or file relationships — especially if graphify-out/ exists. Provides persistent graph with god nodes, community detection, and BFS/DFS query tools.

Full research pipeline: Workflow 1 (idea discovery) → implementation → Workflow 2 (auto review loop). Goes from a broad research direction all the way to a submission-ready paper. Use when user says "全流程", "full pipeline", "从找idea到投稿", "end-to-end research", or wants the complete autonomous research lifecycle.

Use when auditing a KDD submission for readiness in either cycle, covering Research vs ADS track declaration, OpenReview profile completeness for all authors, the ACM sigconf 8-content-page budget, double-blind checks, in-paper artifact references, resubmission declarations, and desk-reject triggers specific to ACM SIGKDD.

Use when planning an NSDI campaign across the spring and fall deadlines — sequencing abstract and paper gates, notification waits, one-shot revision windows, artifact evaluation, and the May symposium — so a networked-systems project always knows which of the two yearly gates it is really building toward.

Use when auditing a CAV (Computer Aided Verification) submission for portal readiness, covering the four submission categories (Regular / Short Tool / Short Application / Industrial Experience & Case Studies), the LNCS page limits, the per-category anonymization matrix, the artifact-intent declaration, and desk-reject triage before the AoE paper deadline.

Use when planning a CIKM project calendar across the May abstract/paper gates, June short-track gates, August notification and camera-ready, and the November conference, including the post-submission phase now live in the 2026 cycle, multi-track coordination, and fallback planning toward CIKM 2027 or sibling venues.

Use when planning an EDBT project timeline across the multiple-cycle rolling model — choosing a submission cycle, backward-planning through the author-feedback phase and the in-cycle revise-and-resubmit window, and handling the cycle-to-conference roll — for a database-systems paper published open access on OpenProceedings.

Use when planning an ICRA submission calendar end to end — the September paper deadline, the two video-attachment windows, winter review silence, late-January notification, March camera-ready, and the May/June conference — or when interleaving a fallback RA-L or IROS plan around the single annual ICRA shot.

Turns a one-line topic into a finished Vox-style paper-collage explainer or ad video, automating script, collage keyframes, motion, voice-over, music, and captions via the Atlas Cloud API and local ffmpeg.

Search the bioRxiv preprint server and retrieve paper metadata or download PDFs via its API. Use when finding life sciences preprints by keywords, authors, DOI, date ranges, or categories, or when conducting a biology literature review of not-yet-peer-reviewed work. Part of the AlterLab Academic Skills suite.

Use when experiments complete to judge what claims the results support, what they don't, and what evidence is still missing. Codex MCP evaluates results against intended claims and routes to next action (pivot, supplement, or confirm). Use after experiments finish — before writing the paper or running ablations.

规划、撰写、重构、润色、压缩、扩写、收口和审校中文医学文本，并为持续项目建立写作主控索引、内容型总纲、全文一致性账本、章节任务书、证据账本、决策记录和最终交付物清单。支持 Grant（医学基金标书、项目申请、研究目标、任务分解、技术路线、进度与甘特图、项目管理、风险分析、创新性、预期效益、研究基础和可行性论证）与 Journal（毕业论文、期刊论文、综述、病例报告、指南解读和学术报告），自动识别或联合调用全文建构、局部构篇、语言精修、结构审计、语言审计及项目收口。

Use when planning a KDD project calendar across the venue's two submission cycles per year, including cycle choice, abstract-then-paper deadline pairs a week apart, rebuttal capacity planning, the Resubmit-to-next-cycle loop, ADS evidence lead times, and ACM e-rights/TAPS camera-ready scheduling for SIGKDD.

Use when planning a CoRL submission cycle end to end — the late-May abstract and paper deadlines, the summer review window, first-round rejection risk, the August one-page rebuttal and discussion period, autumn decisions, the October PMLR camera-ready, and the November conference — including what to do between milestones.