Skip to content

Guide · Agent skill

Incident Retro Learning Deck agent skill: install and use

Updated · written with AI from the project's own documentation and checked against our catalogue data

The Incident Retro Learning Deck is an agent skill, a set of instructions and template files that an AI agent such as Claude loads when you ask for a matching task. This one guides the agent to build a single-file HTML slide deck in a specific cream-and-blue style, based on the knowledge-arch-blueprint template from the html-ppt master skill. This guide explains what the skill does, how to install it, how to phrase requests so it triggers, and what to check before presenting the deck.

Incident Retro Learning Decknexu-io/open-design · Apache-2.0

Quick start

  1. 1Get the files. Download the skill ZIP from this page and unzip it. Confirm you also have the html-ppt master skill files at design-templates/html-ppt.
  2. 2Install the skill. Place the skill in ~/.claude/skills/ or a project's .claude/skills/ folder, or upload the ZIP under Settings → Capabilities → Skills in the Claude apps.
  3. 3Gather your inputs. Collect the audience, decision target, source materials, deadline and must-keep numbers for the retro.
  4. 4Make the request. Ask for an HTML deck for engineering, SRE and leadership, naming the decision you need from them.
  5. 5Set up the template. Copy the knowledge-arch-blueprint index.html and style.css, then choose Recipe A or Recipe B so the shared assets load.
  6. 6Check speaker notes. Confirm presenter notes sit inside notes elements and not in visible slide text.
  7. 7Open and test. Open the resulting HTML file in a web browser and check that slides navigate correctly.

What the skill makes the agent do

The skill is a pointer to a presentation template rather than a general incident-analysis tool. Its SKILL.md is written around an example retrospective about a daemon-restart data bug, covering the root cause, the fix and the systemic follow-ups. The intended result is a decision-oriented product management deck for engineering, SRE and leadership audiences.

The skill keeps the visual identity of the knowledge-arch-blueprint template. It also explains how to copy the template files so the deck still works outside the original repository, and how to keep speaker notes out of the visible slide text.

  • Produces a single-file HTML slide deck in the knowledge-arch-blueprint style
  • Follows the authoring rules of the html-ppt master skill
  • Keeps speaker notes in notes elements that do not appear on the slides

Install the Incident Retro Learning Deck skill

Download the skill ZIP from this page and unzip it. You can then place the skill folder in one of two locations: your personal skills folder at ~/.claude/skills/, or a project-level .claude/skills/ folder inside a specific project. Alternatively, in the Claude apps, open Settings → Capabilities → Skills and upload the ZIP there.

The skill depends on the html-ppt master skill files at design-templates/html-ppt. Check that those files are available before you start, because the skill points to them for its authoring rules and template folders.

  • Personal install: ~/.claude/skills/
  • Project install: .claude/skills/ inside the project folder
  • Claude apps: Settings → Capabilities → Skills, then upload the ZIP
  • Prerequisite: the html-ppt master skill files in design-templates/html-ppt

Trigger the skill with a natural request

You do not need special syntax. Describe a post-incident review deck and mention the audience. The skill's example prompt asks for a decision-grade product management deck for engineering, SRE and leadership, so requests with those terms match the skill most closely. Trigger keywords listed for the skill include html deck, html slides, product, roadmap, architecture and product-management.

Before building, the example prompt asks the agent to request only missing essentials: audience, decision target, source-of-truth materials, deadline and must-keep numbers. Have these ready so the agent can move on quickly.

  • Example request: Create an incident retro deck as an HTML slide deck for engineering, SRE and leadership, with the decision we need from them.
  • Also useful: html slides for a post-incident review, using the knowledge-arch-blueprint look.
  • Expect the agent to ask for the audience, decision target, source materials, deadline and any numbers that must stay exact.

What the agent produces

Based on the example prompt, the output covers a slide plan, written slides, a visual direction, a speaker-ready structure, and a critic pass. The critic pass checks the deck against a rubric: whether cross-functional reviewers can agree on the next irreversible step.

Use the output as a draft. The skill only describes an example and gives no analysis method beyond its prompt text, so the agent does not analyse your real incident data. You need to supply the timeline, root cause and follow-ups yourself.

  • Slide plan and written slides
  • Visual direction in the template's style
  • Speaker-ready structure with notes
  • Critic pass against a decision rubric

Make the deck work outside the original repository

The template's index.html links shared CSS and JavaScript using parent-relative paths. Once you copy index.html into a project, those links break, the deck does not activate and slide navigation stops working. Choose one of two recipes for each project.

Recipe A copies fonts.css, base.css, animations/animations.css and runtime.js into a project-local assets/ folder and rewrites the four links to local paths. Recipe B inlines the contents of those files into the HTML as style and script blocks, which gives you one self-contained index.html. Do not ship the upstream ../../../assets/ paths in a project.

  • Copy index.html and style.css from templates/full-decks/knowledge-arch-blueprint/
  • Keep the tpl-knowledge-arch-blueprint body class
  • Recipe A: local assets folder with rewritten paths
  • Recipe B: inline everything into one file
<aside class="notes">Presenter-only notes go here.</aside>

Keep speaker notes out of visible slide text

Put presenter notes inside an aside or div element with the class notes. Text placed there is for the presenter and is not meant to appear as slide content. The skill's rule is that presenter-only text never goes on the slide itself.

To change the look, you can swap in any of the 36 themes from the themes folder through the theme link element. The template's keyboard runtime lets you cycle themes with the T key.

  • Notes go in a notes element, not in slide text
  • Themes live in design-templates/html-ppt/assets/themes/
  • Swap themes via the element with id theme-link

What people use it for

  • Presenting a post-incident review of a data bug to engineering and SRE teams
  • Briefing leadership on the decision needed after an outage, with a consistent visual style
  • Turning a written retrospective into a slide deck with speaker notes for the presenter
  • Creating a roadmap or architecture review deck that follows the same cream-and-blue look

Frequently asked questions

Is the Incident Retro Learning Deck skill free to use?

The directory lists this entry under the Apache-2.0 licence. The SKILL.md credits the underlying visual system and runtime to an upstream MIT-licensed project, lewislulu/html-ppt-skill, and asks you to keep its LICENSE file in place when redistributing.

What do I need to run this skill?

You need the html-ppt master skill files at design-templates/html-ppt, because this skill depends on them. You also need a web browser to open the finished HTML deck. The skill runs no scripts and uses no network access.

Where do I install an agent skill?

Put the unzipped skill in ~/.claude/skills/ for personal use or in .claude/skills/ inside a project. In the Claude apps, you can instead upload the ZIP under Settings → Capabilities → Skills.

Why does my HTML deck show no slides or navigation after I copy it?

The template links shared files with parent-relative paths that break once index.html is moved. Copy base.css, fonts.css, animations.css and runtime.js locally and rewrite the links, or inline the files into one HTML file.

Can the skill analyse my real incident data?

No. The SKILL.md describes an example retrospective and gives no analysis method beyond its prompt text. You need to supply the timeline, root cause and follow-ups yourself.

Is there an alternative if I want a different visual style?

Yes. The skill points to one specific template, so the master html-ppt skill is a better starting point if you want a different style. You can also swap in any of the 36 themes in the themes folder.

New agent skills, repos and AI tools — every week

The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.

Our verdict

This skill suits teams that want a consistent HTML slide deck for a post-incident review, especially when presenting to mixed engineering, SRE and leadership audiences. It is not a fit if you need a different visual style, or if you expect the agent to analyse real incident data, in which case start from the html-ppt master skill and supply your own analysis.

Download the skill