How do I install the Research Documentation skill?

Run npx skillmds@latest add konradcinkusz/research-documentation in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Research Documentation safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Research Documentation?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Research Documentation free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Research Documentation?

konradcinkusz (@konradcinkusz) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Research Documentation by konradcinkusz

Name: Research Documentation
Author: konradcinkusz

Research Documentation

Use when a repository produces measurements, benchmarks or experiments that need writing up as research rather than as a guide, or when any document in it has to be authored in LaTeX and compiled to PDF. What counts as research and what does not, the docs/research layout, the shape of a study document, the evidence rules (every number traceable, reproduction stated as a command, validate the instrument before trusting its readings, negative results get written up), when a study graduates to a LaTeX paper or a Beamer deck, how a non-study document borrows the house style without claiming to be research, how Mermaid diagrams reach a PDF from a single source, how a second language edition is published, and the shape of the GitHub Actions workflow that builds any of them. Bundled assets: the study template, the paper template and the Beamer theme.

konradcinkusz Updated Sep 17, 2026

File contents

Scientific research documentation

Read references/00-RESEARCH-DOCUMENTATION.md before applying any of this. That file is the standard; everything below it is a summary to help you decide whether this skill applies and to check your work afterwards.

Reference-architecture principles: P14.

Bundled templates: assets/TEMPLATE.md, assets/PAPER-TEMPLATE.tex, assets/BEAMER-THEME.sty.

What this standard covers

What counts as research (and what doesn't)
Where research lives in a repository
The shape of a study
The evidence rules
From study to paper (LaTeX)
Presenting work as slides (Beamer)
Documents that borrow the house style without being studies
Diagrams in a PDF
Publishing a document in more than one language
Building the PDF in CI
Relationship to the rest of the standards
Worked example

What counts as research (and what doesn't)

A study asks a question whose answer wasn't known before the work was done, and answers it with evidence: measurements, verified computations, reproducible experiments, or systematic analysis of committed code. Examples: benchmarking an algorithm against its theoretical complexity, verifying an implementation against independently derived expected values, characterizing a system's behavior under a sweep of inputs, root-causing a discrepancy between a model's specification and its implementation.

Not research, and living elsewhere:

Theory/background material — teaching a reader established results (textbook algorithms, probability rules). That is a theory doc (docs/THEORY.md in bayesian-inference is the worked example) and a study cites it rather than repeating it.
Design decisions — those go in the decisions log (docs/architecture/05-DECISIONS.md pattern).
Gap analysis / roadmap — docs/architecture/ per the constitution.

Generated from docs/research/00-RESEARCH-DOCUMENTATION.md by scripts/build-marketplace.mjs. Do not edit this file: change the source document, or its entry in catalog/marketplace.catalog.json, and re-run the generator.

---name: research-documentationdescription: Use when a repository produces measurements, benchmarks or experiments that need writing up as research rather than as a guide, or when any document in it has to be authored in LaTeX and compiled to PDF. What counts as research and what does not, the docs/research layout, the shape of a study document, the evidence rules (every number traceable, reproduction stated as a command, validate the instrument before trusting its readings, negative results get written up), when a study graduates to a LaTeX paper or a Beamer deck, how a non-study document borrows the house style without claiming to be research, how Mermaid diagrams reach a PDF from a single source, how a second language edition is published, and the shape of the GitHub Actions workflow that builds any of them. Bundled assets: the study template, the paper template and the Beamer theme.---# Scientific research documentation**Read [`references/00-RESEARCH-DOCUMENTATION.md`](references/00-RESEARCH-DOCUMENTATION.md) before applying any of this.**That file is the standard; everything below it is a summary to help you decidewhether this skill applies and to check your work afterwards.Reference-architecture principles: P14.Bundled templates: [`assets/TEMPLATE.md`](assets/TEMPLATE.md), [`assets/PAPER-TEMPLATE.tex`](assets/PAPER-TEMPLATE.tex), [`assets/BEAMER-THEME.sty`](assets/BEAMER-THEME.sty).## What this standard covers- What counts as research (and what doesn't)- Where research lives in a repository- The shape of a study- The evidence rules- From study to paper (LaTeX)- Presenting work as slides (Beamer)- Documents that borrow the house style without being studies- Diagrams in a PDF- Publishing a document in more than one language- Building the PDF in CI- Relationship to the rest of the standards- Worked example## What counts as research (and what doesn't)A **study** asks a question whose answer wasn't known before the work wasdone, and answers it with evidence: measurements, verified computations,reproducible experiments, or systematic analysis of committed code. Examples:benchmarking an algorithm against its theoretical complexity, verifying animplementation against independently derived expected values, characterizinga system's behavior under a sweep of inputs, root-causing a discrepancybetween a model's specification and its implementation.Not research, and living elsewhere:- **Theory/background material** — teaching a reader established results (textbook algorithms, probability rules). That is a theory doc (`docs/THEORY.md` in `bayesian-inference` is the worked example) and a study *cites* it rather than repeating it.- **Design decisions** — those go in the decisions log (`docs/architecture/05-DECISIONS.md` pattern).- **Gap analysis / roadmap** — `docs/architecture/` per the constitution.---Generated from [`docs/research/00-RESEARCH-DOCUMENTATION.md`](https://github.com/konradcinkusz/architecture-standards/blob/main/docs/research/00-RESEARCH-DOCUMENTATION.md) by `scripts/build-marketplace.mjs`. Do not edit this file: change the source document, or its entry in `catalog/marketplace.catalog.json`, and re-run the generator.

Frequently asked questions