Research Report

Rules:

• generate the image with real commands such as python3, bash, or a project script
• save the image next to the report file
• reference it with a relative path like ./chart.png
• use meaningful filenames and meaningful alt text
• place the image near the paragraph it supports

Report Structure

The structure should fit the topic. Typical sections:

• title
• executive summary
• core findings
• analysis / implications
• conclusion or recommendations

Use one H1 only. Use H2 and H3 for actual structure, not decoration.

Citation Rules

Use citations whenever the report depends on researched facts.

• place citations inline, immediately after the claim they support
• use natural anchor text such as the publication or source name
• only cite URLs actually present in tool outputs
• never fabricate URLs
• do not add a bibliography unless the user explicitly asks for one

Example:

Recent research shows significant AI advances ([Nature](https://...)) and sustained enterprise adoption ([McKinsey](https://...)).

Writing Principles

• lead with conclusions, then support them with evidence
• analyze rather than merely summarize
• explain trade-offs, uncertainty, and why the information matters
• match depth to the request: concise asks get concise reports; deep dives get substantial structure
• calibrate vocabulary to the user's sophistication

Quality Checklist

• Report saved as a .md file
• Major claims are cited when research was required
• Tables are used where comparison is easier than prose
• Charts or images are embedded only when they add value
• Conclusions synthesize the evidence instead of repeating it
• File is shown to the user with show