Every page linked below is one self-contained HTML file. An agent wrote a few hundred lines of content and joined them to Hunt & Hackett's report kit. Open them, read their source, and ask your own agent for the next one.
Six of the eight tell one story: an intrusion at a freight company, and what followed. The same facts become a written report, a deck, a service review, a network review, a board brief and a budget proposal, because each reader needs something different from them.
Incident report
For a customer's CISO, after an intrusion. Narrative layout, light scheme; opens on a cover and a byline.
Scroll through "The path": the diagram stays beside the text and shows the hop you are reading. Then the whole incident on one line, drawn to scale, with the intruder above it and the response below.
Published data story
For customers and the press, read on a screen. Analytical layout, dark scheme; opens on the figure.
It opens on the chart that is the finding. Below it: the same decline in four sectors on one scale, a heatmap of tactics by sector, and a thousand alerts narrowed to nine.
Debrief for a meeting
The same incident, for the management team. Presentation layout, dark scheme; opens on a title screen.
Press Play on the path, or use the arrow keys to move between screens. One statement gets a screen to itself.
Quarterly service review
For a customer who tracks the same measures every quarter. Analytical layout, light scheme; opens on key figures and a list of facts.
The one report that opens on numbers, because it is about them. Find the heatmap of alerts by hour and weekday.
Network and data-flow review
For the head of infrastructure. Analytical layout, light scheme; opens on the diagram.
The diagram is the front page. Point at a system to trace what feeds it and what it feeds; the three red routes are the finding.
Decision brief
For a board with five minutes. Analytical layout, light scheme; opens on findings in words.
Three findings in words where a strip of numbers would have been filler. Short on purpose.
Budget proposal
For an executive committee, in a bright room. Presentation layout, light scheme; opens on a cover as the title screen.
A light deck behind a navy title screen. The scatter names only the three measures being proposed.
Research note
For engineers who will check the claims. Narrative layout, light scheme; opens on a cover and a byline.
A call path with a three-step walkthrough, the calls and their results in a code block, and a table of what held and what did not.
Fonts, charts and data are inside it. It opens offline, makes no network requests, and can be emailed as it is.
Narrow the window, or open the PDF beside any example: the same file, laid out again.
Figures draw in once; dots show direction; a reader who asks for reduced motion gets the final state.
The content sits at the top of the file with a short guide. "Source" under each example is that content.
Every link goes to the place in an example where the part is used.
| To show | The kit draws | See it in |
|---|---|---|
| Change over time | BH.line | threat landscape, service review |
| Size or ranking | BH.bar | threat landscape, service review, investment proposal |
| Before and after | BH.dot | service review, network review, board brief, investment proposal |
| How two measures relate | BH.scatter | threat landscape, investment proposal |
| What happened when, to scale | BH.timeline | incident report, incident debrief |
| A value for every pair of two groupings | BH.heatmap | threat landscape, service review |
| How systems connect, what flows where | BH.flow | incident report, incident debrief, network review, research note |
| Volumes between stages | BH.sankey | threat landscape |
| A trend beside a number | BH.spark | service review |
| A share of a whole | BH.waffle | network review |
| A form made for one report | BH.plot | incident report |
| Part | What it is for | See it in |
|---|---|---|
bh-cover | The header as a navy title band | incident report, investment proposal, research note |
bh-findings | Conclusions in words, numbered | incident report, incident debrief, network review, board brief, investment proposal |
bh-keyfigures | Measures with their comparisons | incident report, incident debrief, service review |
bh-step | Text that drives the diagram beside it | incident report |
bh-split | Text and one tall figure side by side | incident report, incident debrief |
bh-band | One section set apart on a tint | threat landscape, investment proposal |
bh-statement | One sentence set large | threat landscape, incident debrief, investment proposal |
bh-code | Commands and log lines, as written | incident report, research note |
bh-terms | Terms and their meanings | incident report |
bh-table | Exact values, with inline bars and status | incident report, service review, network review, research note |
bh-timeline | Dated events | incident report, service review, investment proposal |
bh-compare | Options side by side | service review, board brief, investment proposal, research note |
bh-callout | The one decision or recommendation | incident report, incident debrief, service review, board brief, investment proposal, research note |
bh-aside | A note beside the text | incident report, threat landscape, service review, network review, research note |
bh-pair | Two figures side by side | service review |
bh-quote | A quotation | research note |
With the skill installed, a request like these is enough. The agent states the reader and the takeaway, writes the content, joins it to the kit, runs the checker, looks at the screenshots, and hands over one file.
Incident report
"Here are the responder's notes and three log extracts for IR-2026-031. Write the incident report for the customer's CISO, and take the reader through the path one hop at a time."
Published data story
"From cases.csv, write this quarter's threat landscape. The story is how fast intruders now act. Dark scheme; it will be read online."
Debrief for a meeting
"Turn IR-2026-031 into a deck for Tuesday's management meeting. One idea per screen, and end on the decision we need."
Quarterly service review
"Here are the Q3 exports from the detection platform. Write Meridian Freight's quarterly service review. Be straight about the warehouse network."
Network and data-flow review
"From firewall-rules.csv and flows-september.csv, show which systems can reach the warehouse network and which routes skip the jump host."
Decision brief
"Summarise the perimeter review for the board in one page. They need the three findings and a recommendation, not the method."
Budget proposal
"Make the case for the three security investments for 2027 to the executive committee. Light scheme: the boardroom has windows."
Research note
"Write up part 1 of the lpacCom post as a research note for reviewers. Separate what the authors observed from what they only state."
# Install the skill for any agent that reads Agent Skills
npx skills add cozybear-dev/beautiful-html