Maintain an OKF paper wiki under `paper-wiki/` or another user-named wiki root, including optional Chinese mirror notes under `papers_zh/`. Use when asked to add arXiv or research-paper URLs, capture non-paper sources such as blog posts, docs, or talks, update or translate paper notes, maintain paper/topic/concept/source indexes, automatically create or update topic summary pages for important new themes, maintain concept entity pages for methods, datasets, benchmarks, metrics, terms, or tools, link papers to research projects, normalize paper metadata, track reading status, compare papers, generate required `viz.html` visualizations, or validate the paper wiki.
Audit, position, and communicate research value without outrunning the evidence. Use when users need audience-specific buy-in from advisors, collaborators, reviewers, talk audiences, or the research community; want to pitch or promote an idea, paper, result, codebase, or demo; plan research PR; or need to detect and repair overclaiming. Do not use for generic proofreading, summarization, or formatting.
Generate or lint a compact top-level FILETREE.md navigation map. Use when repository structure changes or FILETREE.md needs creation, regeneration, or validation.
Map scattered ideas into a human-approved DAG of verifiable states, then drive fresh agents through it edge by edge. Use when the user has a destination or idea fragments but lacks the domain knowledge to identify or sequence the route; when revising a map bundle; when compiling approved edges into launch prompts; or when recording execution evidence, deviations, and human verification.
Prompt-contract authoring for frontier reasoning and coding agents. Use when the user wants a new implementation prompt, a phased agent task, a copy-ready prompt, or an evidence-based upgrade of an existing prompt that should work across capable model providers.
Two-stage academic rebuttal assistant. Given the paper abstract, reviewer comments, scores, confidences, and venue constraints, first diagnose the underlying concerns, assess whether rebuttal is worth the limited author time, and produce a prioritized experiment-and-analysis plan. After the author provides completed results, produce an evidence-grounded rebuttal, revision plan, or resubmission plan. Never fabricate results, reviewer intent, citations, or manuscript locations.
Use when selecting, auditing, or justifying experimental baselines for a research idea, paper draft, task, benchmark, or experiment plan. Finds classic methods, recent SOTA, direct competitors, strong simple baselines, ablation baselines, resource-matched comparisons, and reviewer-expected missing baselines, but only admits baselines with non-empty, accessible GitHub repositories that appear reproducible. Records strong papers without usable open-source code as excluded candidates rather than selected baselines.
A protocol framework for long-horizon autonomous tasks. Targets three empirically-observed failure modes — cognitive loops, stalling, runtime fragility — by prescribing state management, stall detection, and watchdog mechanisms. Validated on multiple task types including paper writing (4 ICLR-format surveys, in-framework self-rating 8.0-8.6/10).