Academic
Academic writing, research, citations
market-data
by JoelLewis
"Market data management: real-time vs delayed feeds, Level 1/2/3 data, data vendors, consolidated tape, market data licensing, distribution, and infrastructure."
lit-review
by pedrohcgs
Structured literature search + synthesis with citation extraction, thematic clustering, and gap identification. Use when user says "find papers on X", "do a lit review", "what's the literature on...", "summarize what we know about...", "where's the gap in this field", "review recent work on Y". Produces a written review with BibTeX-ready citations. Uses WebSearch/WebFetch for recent work.
credible-claims
by pedrohcgs
Research-brief + claim-record discipline for delegated or AI-assisted research work. Use when starting any substantive research task or long autonomous run (write the brief first), and when reporting results that will support a claim in a paper or decision (produce the claim record). Keeps faster execution from being confused with credible evidence.
research-ideation
by pedrohcgs
Generate structured research questions, testable hypotheses, and candidate empirical strategies from a topic, phenomenon, or dataset description. Use when user says "give me research ideas on X", "brainstorm questions about Y", "what could I study with this data?", "I'm looking for a paper idea on...", "generate hypotheses for...". One-shot generation, not multi-turn. For idea-refinement use /interview-me.
verify-claims
by pedrohcgs
Run Chain-of-Verification (CoVe) on a draft or a block of text with factual claims. Spawns the claim-verifier agent in a forked (fresh) context so it never sees the draft — then reports which claims are supported, contradicted, or unverifiable. Use when user says "verify these citations", "check the claims in X", "did I hallucinate anything", "fact-check this draft", "run CoVe on this", or after any text generation that asserts facts about papers, datasets, or numerical results. NOT for style/grammar review (use /proofread) or substance review (use /review-paper).
submission-disclosures
by pedrohcgs
Generate the submission-time disclosure block for a manuscript — the AI-use disclosure statement matched to the target journal's policy, CRediT author-contribution roles, conflict-of-interest statement, and data-availability statement. Use when the user says "AI disclosure", "disclosure statement", "do I need to disclose Claude", "CRediT roles", "conflict of interest statement", "data availability statement", or is preparing a submission package. NOT statistical-disclosure screening of restricted-data outputs — that is /disclosure-check.
literature-review
by IncarnaMind
Writes a literature review across the User's Documents on the Question's topic, synthesised by theme rather than one Document after another, showing where the Documents agree and disagree and what they leave out, with every claim cited. Use when the User asks for a literature review, a review of related work, a state-of-the-art overview or a synthesis of several Documents.
summarise-document
by IncarnaMind
Writes a structured summary of one Document, or of each Document in the Question's Search scope, with sections that suit the kind of Document (a paper's claims, method and limitations; an agreement's parties, term and obligations) and each point with a Citation. Use when the User asks to summarise, digest or give an overview of a paper, report, contract or other Document.
preregister
by pedrohcgs
Draft a structured preregistration document (OSF, AsPredicted, or AEA RCT Registry style) from a research spec or free-form study description. Output is a Markdown file with hypotheses, design, sampling plan, analysis plan, exclusions, and inference criteria — annotated with MUST / SHOULD / MAY clarity flags. Use when user says "preregister", "draft a preregistration", "OSF preregistration", "AsPredicted", "AEA RCT registry", "PAP", "preanalysis plan", or before launching an experiment / data collection / analysis on data the analyst has not yet seen. NOT a registry submission tool — produces a document the user uploads to OSF / AsPredicted / AEA themselves.
validate-bib
by pedrohcgs
Validate bibliography entries against citations in all lecture files. Structural checks (missing/unused entries, malformed fields) by default; --semantic adds citation-drift detection, DOI verification, and style-consistency checks.
interview-me
by pedrohcgs
Interactive interview that formalizes a fuzzy research idea into a structured spec (RQ, hypotheses, identification, data needs, empirical strategy). Use when user says "interview me", "help me think through this idea", "I have a half-baked idea", "formalize this into a project", "walk me through framing a study". Multi-turn Q&A; saves spec to disk. NOT for lit review (/lit-review) or ideation from scratch (/research-ideation).
mind-to-report
by IncarnaMind
Turns the User's Mind, meaning the Notes, Questions and earlier Answers above the Question, into a structured report draft with a title, a summary, sections and a conclusion, keeping their Citations and inventing no sources. Use when the User asks to write up, draft a report, compile or turn their notes or this Mind into a document.
humanize
by pedrohcgs
Read-only audit of .tex, .qmd, or .md text for AI-voice tells — boilerplate transitions ("Moreover", "Furthermore", "It is important to note that"), AI-cliché lexicon ("delve", "navigate the complexities", "tapestry", "robust framework"), em-dash overuse, symmetric paragraph shapes, tricolon abuse, hedging stacking, "not only X but also Y" frames, and formulaic openers. Produces a report; does NOT rewrite. Use when user says "humanize", "does this sound like AI?", "check for AI tells", "de-AI this draft", "remove AI voice", "audit my prose for sycophancy", or before journal submission / posting a working paper.
research-proposal
by luwill
Generate academic research proposals for PhD applications. Use when user asks to "write a research proposal", "create PhD proposal", "generate research plan", "撰写研究计划", "写博士申请", "doctoral proposal", or mentions specific research topics for PhD application. Supports STEM, humanities, and social sciences with field-specific adaptations. Follows Nature Reviews-style academic writing conventions. Supports both English and Chinese output based on user preference.
prompt-improver
by severity1
This skill enriches vague prompts with targeted research and clarification before execution. Should be used when a prompt is determined to be vague and requires systematic research, question generation, and execution guidance.
grant-proposal
by poemswe
You must use this when drafting grant proposals, refining research aims, or aligning projects with agency priorities.
paper2code
by issol14
연구 논문(PDF/arXiv URL)을 분석하여 실행 가능한 코드로 변환합니다. 논문 복제, 알고리즘 구현, 연구 재현 요청 시 자동으로 활성화됩니다. "이 논문 구현해줘", "paper2code", "논문 코드로 변환" 등의 요청에 반응합니다.
experiment-design
by lingzhi227
Design experiment plans with progressive stages — initial implementation, baseline tuning, creative research, and ablation studies. Plan baselines, datasets, hyperparameter sweeps, and evaluation metrics. Use when planning experiments for a research paper.
research-planning
by lingzhi227
Design research plans and paper architectures. Given a research topic or idea, generate structured plans with methodology outlines, paper structure, dependency-ordered task lists, UML diagrams, and experiment designs. Use when starting a new research project or paper.
github-research
by lingzhi227
Explore and analyze GitHub repositories related to a research topic. Reads deep-research output, discovers repos from multiple sources, deeply analyzes code, and produces integration blueprints.
math-reasoning
by lingzhi227
Formal mathematical reasoning for research papers — derive equations, write proofs, formalize problem settings, select statistical tests, and generate LaTeX math notation. Use when the user needs mathematical derivations, theorem proofs, notation tables, or statistical analysis formalization.
algorithm-design
by lingzhi227
Design algorithms with LaTeX pseudocode and UML diagrams. Generate algorithmic environments, Mermaid class/sequence diagrams, and ensure consistency between pseudocode and implementation. Use when formalizing methods for a paper.
paper-to-code
by lingzhi227
Convert an ML research paper into a complete, runnable code repository. 3-stage pipeline from Paper2Code — Planning (UML + dependency graph) → Analysis (per-file logic) → Coding (dependency-ordered generation). Use for reproducing paper methods.
citation-management
by lingzhi227
Manage BibTeX citations for LaTeX papers. Harvest missing citations from a draft using Semantic Scholar, validate cite keys against .bib files, deduplicate entries, and format bibliography. Use when working with references, BibTeX, or citations.