research-doc-conventions

Applies house style conventions to research documents in the research/ directory.

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/dperussina/function2agent --skill research-doc-conventions-dperussina
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: research-doc-conventions
Source: https://github.com/dperussina/function2agent/tree/main/.cursor/skills/research-doc-conventions
Command: npx skills add https://github.com/dperussina/function2agent --skill research-doc-conventions-dperussina

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Research documents in a shared repository drift in structure and quality over time. This Skill enforces a consistent house style for research/ documents so every new or edited document follows the same skeleton, sourcing rules, and confidence-annotation habits. ## Core Features & Use Cases - Required document skeleton: Enforces a dated header, TL;DR box of claims, anchor-linked table of contents, numbered sections, and mandatory closing sections (Relevance to function2agent, unverified claims, Sources). - Sourcing and confidence rules: Requires inline links at the point of each claim, arXiv citation format, grouped Sources sections, inline confidence annotations, and a "claims I found poorly supported" subsection. - Density and voice standards: Prescribes tables for comparisons, Mermaid diagrams, good/bad example pairs, and first-person voice reserved for judgment calls. - Use Case: When writing a new research/07-agent-memory.md document summarizing external findings, apply this Skill to produce a document that matches the established format, including the TL;DR box ending with a "For function2agent" item and an honest unverified-claims section. ## Quick Start Write a new research document on the topic I provide following the research/ house style conventions.

Frequently Asked Questions about research-doc-conventions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a research document that matches this repository's house style?▼

Follow the required skeleton: dated header, TL;DR box of 6-8 bolded claims, anchor-linked table of contents, numbered sections, then Relevance to function2agent, unverified claims, and Sources sections. Every non-obvious claim needs an inline link at the point of the claim.

What belongs in the TL;DR section of a research document?▼

A blockquoted numbered list of 6-8 items where each item is a claim, not a topic: a bolded lead clause followed by the supporting evidence and an inline link. The last item is conventionally the "For function2agent" product implication.

Should I edit existing research documents to match the conventions?▼

No. The conventions explicitly prohibit editing existing research documents to conform, since several may be actively in progress. Apply the style only to documents you are authoring.

How are sources and citations formatted in these research documents?▼

Cite arXiv papers by ID and title with inline links at the point of each claim, quote primary sources verbatim in blockquotes when wording is load-bearing, and group the final Sources section by document section rather than one flat list.

What goes in the unverified section of a research document?▼

List claims sourced only to unreplicated preprints, fast-moving version numbers with verification dates, engineering opinions held without controlled studies, self-contradictory documentation, and any author inferences explicitly labeled as inferences.