Create showcase artifacts with ak:show-off

Use ak:show-off to turn a prompt or Markdown brief into a polished, self-contained HTML showcase with cited content and optional section images. The workflow persists screenshot, publication, and language preferences, creates a durable plan, and can publish externally, so resolve those controls before the mission content is analyzed.

Choose ak:show-off for a presentation artifact

Use ak:show-off when

• You need a scrollable demo, visual presentation, or social-ready showcase.
• The work benefits from two to six designed sections with a strong hero.
• You want responsive 16:9, 9:16, and 1:1 section captures.
• You need bilingual Vietnamese and English output or a single supported language.

Choose another workflow when

• You need a reusable application or product surface rather than a showcase.
• You only need prose or a standard document without HTML presentation design.
• The material contains credentials, private data, or content that cannot be researched, rendered, or published safely.
• You cannot approve a plan artifact. Plan creation is a hard prerequisite.

Resolve preferences and prerequisites

The user-level defaults are consequential:

Preferences are stored at $AGENTKIT_HOME/show-off/preferences.json, falling back to ~/.agentkit/show-off/preferences.json. SHOW_OFF_PREFS_PATH can override the file for tests or a one-off advanced setup.

Before you start:

• Complete Onboarding, and confirm Engineer Kit plus its inherited design and project-management Skills are installed.
• Have Node.js 18 or newer available.
• For local capture, provide Puppeteer and a usable Chrome or Chromium binary; Sharp is used when available to compress oversized images.
• Decide whether internet research, public publication, and screenshot capture are allowed for this mission.
• Exclude secrets and confirm rights to publish the supplied content and assets.

Request a bounded showcase

State the mission, audience, evidence standard, publication boundary, screenshot choice, and language. Add “for this run only” when an override must not persist.

/ak:show-off "Create an English-only launch demo from release-notes.md. Local only, no screenshots, for this run only. Cite every external claim and open the final HTML for review."

/ak:show-off "Create an English-only launch demo from release-notes.md. Local only, no screenshots, for this run only. Cite every external claim and open the final HTML for review."

$ak:show-off "Create an English-only launch demo from release-notes.md. Local only, no screenshots, for this run only. Cite every external claim and open the final HTML for review."

Without the one-run qualifier, an explicit preference change is saved immediately. The latest explicit instruction overrides stored state.

Understand what happens during a run

1. The Skill resolves workflow control. Before reading the mission, it loads persisted preferences and applies explicit overrides.
2. It creates durable planning state. ak:project-management creates a dated directory under plans/, registers the applicable request-analysis, content, HTML, review, capture, and publish tasks, and records arguments and preferences.
3. It researches the mission. The workflow searches the internet for support and fact-checking, then writes cited section content to assets/showoff/<mission-name>/content.md.
4. It optionally publishes the document. When publication remains enabled, agentwiki organizes or creates a destination and publishes the content.
5. It designs the showcase. ak:frontend-design creates a self-contained HTML presentation with two to six sections, responsive composition, theme controls, citations, and Vietnamese-capable fonts when needed.
6. It captures enabled outputs. The local script launches Puppeteer, waits for network idle, fonts, images, CSS backgrounds, layout frames, and the settle delay, then captures each section at every selected ratio.
7. It uses a conditional remote fallback. Only when publication is enabled, local capture fails, rws exists, and RWEB_API_KEY is set, the workflow may capture the public page through ReviewWeb.
8. It publishes and opens the result. When enabled, it updates the static site; in every flow it opens the local HTML or reports why that was impossible.
9. It reconciles the plan. Each task is updated as it starts, completes, or is intentionally skipped.

With two to six sections and the three default ratios, capture can create six to eighteen high-resolution images. Each readiness signal is bounded by the default 15-second render timeout, plus a default 1.5-second settle delay per readiness pass; remote assets and animations can extend the overall run.

Keep publication and capture under explicit control

• Internet research sends search queries and receives external content. Do not include private mission data in those queries.
• agentwiki mutates an external content destination. Publication may expose the content and make the HTML reachable publicly.
• ReviewWeb sends the public URL to an external screenshot provider and requires RWEB_API_KEY. The key stays in the environment and must never appear in a command or generated HTML.
• Local Puppeteer starts browser processes, may load remote page assets, and writes image files. Stop failed or orphaned browser processes.
• Preference writes, plan files, content Markdown, HTML, and images are durable disk effects. Review paths and size before keeping them.
• The workflow does not authorize authentication work, database access, source deployment, commits, pushes, or handling sensitive data.

Verify the result

A complete run should give you:

• A plan with the resolved preferences and accurate task status.
• Cited content.md organized into the chosen sections.
• A self-contained HTML artifact with a strong hero, system/light/dark theme control, responsive layout, and correct language treatment.
• When enabled, images named by ratio and section under assets/showoff/<mission-name>/images/.
• Capture JSON listing successful files, sizes, compression state, and any error.
• A local review path and, only when explicitly approved, the public destination.

Verify at 16:9, 9:16, and 1:1; check that content is not clipped, Vietnamese diacritics render, controls are keyboard-visible, reduced motion is respected, citations resolve, and no credential or private text appears in artifacts. The package includes preference-helper tests runnable with Node; no test is defined for generated design quality or external publication.

Troubleshoot or continue

Know the current limits

• The default workflow assumes web search, bilingual output, screenshots, and publication; use explicit opt-outs for a smaller or private run.
• Capture requires local browser dependencies or an eligible published remote fallback.
• The license field points to LICENSE.txt, but that file is absent from both exact packages. Confirm distribution terms before redistributing Skill assets.
• The current stable and beta packages contain identical ak:show-off, preference, capture, and preference-test files.