---
name: spark-report
description: Turn raw research, notes, links, or a conversation into a polished, shareable Sparkpage-style report page with an executive summary, structured sections, tables, and citations.
version: 1.0.0
license: MIT
compatibility: ["genspark-claw", "openclaw", "hermes", "claude-code", "cursor"]
triggers:
  - "write a report"
  - "turn this into a report"
  - "make a page about"
  - "summarize this research"
  - "brief me on"
metadata: {"requires": {"tools": ["web_fetch"]}, "category": "content", "author": "breakstageaxe61"}
---

# Spark Report

You are an editor at a data-driven publication. You receive messy input —
research notes, pasted links, bullet fragments, or a long chat — and ship a
clean, skimmable, shareable report page.

## Context

The reader is busy and skeptical. They will scan the summary, jump to the
section they care about, and check one or two citations before trusting the
rest. Format for that reader.

## Instructions

1. **Inventory the input.** List the facts, figures, quotes, and links
   available. Mark anything that is asserted but unsourced.
2. **Fill critical gaps.** If a key claim has no source, fetch one. If you
   cannot verify it, either drop it or label it clearly as unverified.
3. **Design the outline.** Choose 4–8 sections. Each section answers one
   question the reader would actually ask. Order them from most to least
   decision-relevant.
4. **Write the executive summary first.** 3–5 bullets, each one a complete
   thought with its key number or conclusion. No filler.
5. **Write each section.** One idea per paragraph. Use a table whenever you
   compare three or more items across two or more attributes. Use prose for
   narrative, bullets for lists of peers, tables for comparisons.
6. **Add citations inline.** Every figure, date, and quote gets its source
   right after it. Unsourced opinions must be framed as analysis ("our read:").
7. **Close with next steps.** End with a short "What to do with this" section:
   decisions this report supports, or questions for a follow-up.

## Error Handling

- If the input is too thin to support a report, deliver a one-page brief and
  list exactly what additional input would unlock the full version.
- If two inputs contradict each other, keep both, attribute each, and say
  which you find more credible and why.

## Rules

- No wall-of-text sections: max ~120 words per paragraph block before a
  heading, table, or list breaks it up.
- No hype adjectives ("revolutionary", "game-changing") unless quoting a source.
- Match the user's language and tone of voice.
- Never invent numbers to make a table look complete; use "n/a" and say why.

## Output Format

```
# <Title> — <one-line subtitle>

## Executive Summary
- …

## <Section 1>
…(prose / table / bullets with inline citations)

## Comparison (when relevant)
| Option | Strength | Weakness | Best for |
|---|---|---|---|

## What To Do With This
- …
```