AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Demo Story Packager

skill-45ck-skill-harness-demo-story-packager · by 45ck

Package completed demo-machine runs, browser capture artifacts, or evidence-backed product demos into source-linked handoff bundles. Use when Codex needs to organize `.demo.yaml`, `events.json`, `quality.json`, screenshots, storyboard outputs, rendered videos, review prompts, or release-ready demo assets without losing provenance.

↗ Website ↗ Repository
— No reviews yet
0 installs
12 views
0.0% view→install

Install

$ agentstack add skill-45ck-skill-harness-demo-story-packager

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Demo Story Packager? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Demo Story Packager

Overview

Use this skill to turn a captured demo into a reviewable and reusable package. Keep the durable source first and treat video, posters, frame strips, and HTML as generated outputs.

Inputs

  • .demo.yaml or equivalent source flow
  • events.json, verification.json, quality.json, environment.json
  • rendered output.mp4 and raw video.webm
  • analyzer outputs such as review-bundle.json, review-prompt.md, video.shots.json, segment.evidence.json, layout-safety.report.json, and segment-storyboard/
  • screenshots, Playwright traces, or manual QA reports when they are part of the evidence

Workflow

  1. Identify the canonical source: usually .demo.yaml, QA flow JSON, or a source artifact under docs/artifacts/source/.
  2. Inventory generated media and evidence. Do not infer pass/fail claims from video alone.
  3. Separate draft assets from approved assets. Keep generated assets out of git unless the repo intentionally promotes them.
  4. Write a handoff summary with audience, source path, run directory, evidence files, known quality findings, and next action.
  5. If a review surface is needed, use demo-review-surface and record it in docs/artifacts/artifacts.manifest.json when the target repo has a manifest.
  6. Before handoff, run available checks such as demo-machine analyze, demo-machine doctor, node scripts/check-artifact-manifest.mjs, or node scripts/check-artifact-html-policy.mjs.

Output Contract

Name these paths when available:

  • source spec or QA flow
  • run directory
  • rendered media
  • evidence files
  • generated review surface
  • approval or promotion destination
  • commands already run

Guardrails

  • Do not treat generated video as canonical evidence without source files.
  • Do not include secrets, tokens, private browser data, or customer records in shareable media.
  • Prefer local-first artifacts. Do not upload media to third-party services unless the user explicitly asks.
  • If the source and media disagree, mark the package stale and regenerate from source.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

  • Author: 45ck
  • Source: 45ck/skill-harness
  • License: MIT
  • Homepage: https://github.com/45ck/skill-harness/releases/tag/v0.1.0

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Web & Browser