Research Reports Your Agent Writes Need Sources Before Sentences

A developer published an MIT-licensed agent skill, deep-research-framework, that enforces source tiering, question definition and an uncertainty statement before a coding agent writes a research report. The workflow requires core conclusions to rest on at least two independent sources, bars tertiary sources from supporting core conclusions, and downgrades unsupported findings to explicitly marked single-source claims. It is one of five SKILL.md files in the agent-skills-en pack, installed by copying the folder into an agent's skills directory.

Ask a coding agent for a research report and you usually get fluent prose first and evidence later — if at all. A single forum post becomes "research shows." A number from 2023 is presented as the current state. Twenty sources are listed at the end, and you still cannot tell what the author actually believes. The failure is structural, not stylistic: the writing started before the question was defined and before the sources were tiered. So I wrote the workflow down as a skill, and the skill's first claim is blunt: the quality floor of research is set by its sources, not its prose. The workflow starts with one sentence stating what the report must answer, plus at most three sub-questions. Starting before the question is clear guarantees the research will sprawl — the agent collects whatever it finds first and the report's shape is decided by search order instead of by the question. Sources are tiered before searching, so you don't believe whatever you find first: That last line is a hard rule in the skill: no tertiary source supports a core conclusion. A forum thread can point a direction, never serve as evidence. Key conclusions need two or more independent sources. Two sources quoting the same origin don't count as independent — that is the trap that makes a single press release look like a consensus. If no second source exists, the conclusion is downgraded to a "single-source claim" and marked as such, instead of being quietly upgraded by confident wording. Related rules: Only after those three steps does writing start, and the structure is fixed: The skill also insists on ordering inside the author's head: state "what you don't know" before "what you know" — honest uncertainty beats pretty certainty. And mark speculation as speculation: use "may", "likely", "unverified" — never dress speculation up with "clearly" or "it is well known". The report outline template from the skill: Research Report: <Topic example outline Core conclusions 3–5 lines : … 1. Sub-question one - Conclusion: … - Evidence: … source: primary/secondary, as of … - Evidence: … second independent source 2. Sub-question two … Uncertainty statement - Not found: … - Single-source claims: … one source only, pending verification - Invalidation conditions: if … changes, conclusion X in this report needs reassessment. The skill lists its own failure modes explicitly: That last one is why the uncertainty statement is a required closing section rather than a footnote. A report whose unknowns are explicit can be trusted where it does claim something; a report that hides them cannot be trusted anywhere. This is one of five free, MIT-licensed skills in a small pack I maintain — the others cover commit messages, code review, meeting minutes, and technical proofreading. Each one is a single SKILL.md file: copy the folder into your agent's skills directory and it applies the workflow without being re-explained every session. Repo: https://github.com/alapha888/agent-skills-en https://github.com/alapha888/agent-skills-en — the research skill is under skills/deep-research-framework/ , including the full workflow and anti-pattern list. If your work has house rules of its own — sources you always trust or never cite — fork the file and add them to the tiering step. The structure is the stable part; the source list is yours.