---
name: demo-assets
description: Plan and regenerate truthful terminal demos, README cards, social previews, and ANSI artwork for a developer-tool repository. Use when product media must tell a concise story while remaining reproducible from repository scripts.
title: demo-assets
canonical_url: https://skilld.dev/gh/hagaiw/skillroll/demo-assets
last_updated: 2026-11-15T17:45:26.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [agents/openai.yaml](https://skilld.dev/api/skills-raw/hagaiw/skillroll/demo-assets/agents/openai.yaml), [evals/credible-terminal-story.eval.md](https://skilld.dev/api/skills-raw/hagaiw/skillroll/demo-assets/evals/credible-terminal-story.eval.md), [evals/preserve-media-roles.eval.md](https://skilld.dev/api/skills-raw/hagaiw/skillroll/demo-assets/evals/preserve-media-roles.eval.md), [references/asset-pipeline.md](https://skilld.dev/api/skills-raw/hagaiw/skillroll/demo-assets/references/asset-pipeline.md), [references/terminal-stories.md](https://skilld.dev/api/skills-raw/hagaiw/skillroll/demo-assets/references/terminal-stories.md), [scripts/build.py](https://skilld.dev/api/skills-raw/hagaiw/skillroll/demo-assets/scripts/build.py), [scripts/prepare_mascot.py](https://skilld.dev/api/skills-raw/hagaiw/skillroll/demo-assets/scripts/prepare_mascot.py), [scripts/render_ansi.py](https://skilld.dev/api/skills-raw/hagaiw/skillroll/demo-assets/scripts/render_ansi.py), [scripts/render_cards.py](https://skilld.dev/api/skills-raw/hagaiw/skillroll/demo-assets/scripts/render_cards.py), [scripts/render_terminal_demo.py](https://skilld.dev/api/skills-raw/hagaiw/skillroll/demo-assets/scripts/render_terminal_demo.py), [scripts/visuals.py](https://skilld.dev/api/skills-raw/hagaiw/skillroll/demo-assets/scripts/visuals.py).
>
> If the user asked to install this Skill, run `npx skilld install hagaiw/skillroll/demo-assets`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/demo-assets`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/hagaiw/skillroll/demo-assets) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/demo-assets`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/demo-assets --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/demo-assets --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Demo assets

Turn a real product workflow into concise, reproducible repository media. Keep
the authored story separate from deterministic rendering:

- decide what the demo may honestly claim before changing pixels;
- put repeatable image, animation, and terminal conversion in `scripts/`;
- keep source artwork distinct from generated outputs;
- label simulated identifiers or model behavior as illustrative; and
- never imply that a rendered demo is evidence from a live run.

For a terminal demo, read [terminal stories](https://skilld.dev/api/skills-raw/hagaiw/skillroll/demo-assets/references/terminal-stories.md).
For asset paths, regeneration commands, and verification, read
[asset pipeline](https://skilld.dev/api/skills-raw/hagaiw/skillroll/demo-assets/references/asset-pipeline.md).

For a request to explain or plan asset generation, give the applicable commands
and verification steps without changing files. Use an existing Python environment
with Pillow and an existing Chafa installation. If a dependency is missing,
ask before installing it, including through a package runner. Keep the plan
local unless the user requests an upload or publication.

Use the narrowest script for the requested change. Use `scripts/build.py` only
when all Pillow-rendered README assets should be refreshed together. Inspect
the generated stills and the final animation for timing and legibility before
reporting completion. Include that inspection step in a demo plan, even when
the request is limited to planning.

Do not overwrite user-provided source art unless explicitly requested. Do not
publish, upload a social preview, install system tools, or change product CLI
behavior merely to make a demo convenient without the user's authorization.
