raman-marketplace

Academic research assistant for literature reviews, paper analysis, and scholarly writing. Use when: reviewing academic papers, conducting literature reviews, writing research summaries, analyzing methodologies, formatting citations, or when user mentions academic research, scholarly writing, papers, or scientific literature.

Adversarial review of mathematical proofs, theorems, and formal arguments. Use when asked to review a proof, check a paper's correctness, verify a theorem, find bugs in mathematical reasoning, audit a derivation, or stress-test a formal argument. Implements iterative self-correction from Woodruff et al. (2026) and the Generator-Verifier-Reviser pattern from Aletheia (Feng et al., 2026).

Read, update, and promote claim statuses through the controlled vocabulary. Includes the project.yaml patch protocol and the conjectures.md update procedure.

Systematically test mathematical conjectures by searching for counterexamples, verifying small cases, and constructing proofs or refutations. Use when Raman proposes a conjecture, when a paper claims an unproven bound, when testing whether a theorem generalizes, or when asked to "find a counterexample," "test this conjecture," "verify this bound," or "check if this holds." Implements the simulation and counterexample search techniques from Woodruff et al. (2026) and the neuro-symbolic verification loop from Aletheia (Feng et al., 2026).

Generate research ideas by finding cross-disciplinary connections, retrieving obscure theorems from distant fields, and identifying analogies between different mathematical domains. Use when Raman asks for new research directions, when ingesting a paper that might connect to other fields, when looking for "bridges" between topics, or when asked to "find connections," "what other fields use this technique," or "cross-pollinate." Implements the cross-pollination techniques from Woodruff et al. (2026, Section 2.2, 4.x) and AI Behavioral Science's framework for studying AI-human strategic interactions (Jackson et al., 2025).

Classify each prose claim before writing to paper/paper.md. Enforce the controlled vocabulary and reject illegal proof language.

Extract, classify, and integrate PDF papers from the project inbox/ folder into the literature pipeline. Use this skill whenever PDFs are present in inbox/, when a user says "I dropped some papers in the inbox", or before any literature or ideation pass that should incorporate locally stored papers.

Append a well-formed run summary to logs/agent-history.md after every agent pass. Shared by all agents.

Pick a target publication venue, define the venue-specific publication bar, and route loop-backs after proof, experiment, or verifier passes.

Locate the active project, validate workspace state, and load required artifacts before any command executes.