demo-pipeline

demo-pipeline is a skill for Claude Code from JuanMarchetto/agent-skills. It costs 65 tokens per session (3,808 once invoked), scanned C, original, MIT.

An automated tool for recording walkthrough videos and screenshots of mobile and web apps from a written script.

In plain words
What is it for?
Use it to record login and navigation demos, highlight app features, and produce screenshots, video, and QA results.
Why use it?
It removes the manual work of planning each step, controlling app state, recording the flow, and assembling a quality report.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: positional $N argument.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is screenshots: ./screenshots/.

Part of the demo-pipeline plugin — 1 skill shipped together

Good fit Use it to record login and navigation demos, highlight app features, and produce screenshots, video, and QA results.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/JuanMarchetto/agent-skills
agentmods
npx agentmods add skills/juanmarchetto/agent-skills/demo-pipeline

Made for: Claude Code.

Or install demo-pipeline, the plugin that ships this one along with the rest of its 1 skill.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for demo-pipeline

README.md
[![agentmods](https://agentmods.dev/badge/skills/juanmarchetto/agent-skills/demo-pipeline/github.svg)](https://agentmods.dev/skills/juanmarchetto/agent-skills/demo-pipeline)
Your own site
<a href="https://agentmods.dev/skills/juanmarchetto/agent-skills/demo-pipeline"><img src="https://agentmods.dev/badge/skills/juanmarchetto/agent-skills/demo-pipeline/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for demo-pipeline

Your own site · 80×15
<a href="https://agentmods.dev/skills/juanmarchetto/agent-skills/demo-pipeline"><img src="https://agentmods.dev/badge/skills/juanmarchetto/agent-skills/demo-pipeline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 65 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,808 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00065 $0.03808
Opus 5 $0.00032 $0.01904
Sonnet 5 $0.00013 $0.00762
Haiku 4.5 $0.00006 $0.00381

Measured 13d ago against content hash 9b85f95c1932, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade C, and why

demo-pipeline scanned grade C with 2 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 13d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Downloads and executes remote codehighSupply chain

curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.

- **Maestro not installed**: Provide install command: `curl -Ls "https://get.maestro.mobile.dev" | bash`

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -s -o /dev/null -w "%{http_code}" http://localhost:8081 2>/dev/null
skills/demo-pipeline/SKILL.md · 425 lines

How it starts

The opening of the file, as written. The whole thing — 425 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Demo Pipeline

Record polished app demos from a natural language script. Works with Expo mobile (Maestro) and web apps (webreel/Playwright).

Pipeline: DISCOVER → DETECT → STATE SETUP → PARSE → EXECUTE → COMPILE

Quick Start

User says: "record demo — show the login, navigate to rewards, highlight featured items, end on profile"

You:

  1. Discover all screens, states, and flows via static analysis
  2. Detect the project type and running state
  3. Set up demo state injection (if demo_mode is enabled)
  4. Generate a unified YAML script from the description
  5. Present YAML for user approval
  6. Execute with the right tool (Maestro or webreel)
  7. Collect screenshots, video, and generate report

Phase 0: DISCOVER — Flow & State Analysis

Analyze the codebase to map all screens, states, flows, and native dependencies.

Step 1: Discover screens

Read the file-based routing structure:

find src/app -name "*.tsx" -not -name "_layout.tsx" -not -name "+not-found.tsx" | sort

For each screen file, extract the route path from its filesystem location.

Step 2: Identify states per screen

For each screen file, search for UI conditionals that reveal possible states:

grep -n "loading\|isLogged\|isEmpty\|error\|balance.*>\|\.length.*==.*0" src/app/**/*.tsx

Common patterns to look for:

  • {loading ? <Skeleton/> : ...}loading state
  • {isLoggedIn && ...} or {user ? ... : ...}guest vs logged-in
  • {items.length === 0 ? <EmptyState/> : ...}empty state
  • {balance > 0 ? ... : ...}empty-balance vs has-balance
  • {error ? <Error/> : ...}error state

Step 3: Map navigation flows

Search for navigation calls to build a flow graph:

grep -rn "router\.push\|router\.replace\|href=" src/app/ src/components/

Group into named flows (e.g., "Full reward claim": home → rewards → [id] → scan → confirmation).

Step 4: Identify native dependencies

Search for native module usage per screen:

grep -rn "expo-camera\|CameraView\|useMobileWallet\|SeedVault\|Linking\|expo-local-authentication" src/

Read the full file on GitHub · 425 lines

Files

What ships with it

9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 13d ago First seen · 425 lines · 65 tokens per session scan C 9b85f95c1932

Subscribe to this mod's changes

demo-pipeline is a skill published in the GitHub repository JuanMarchetto/agent-skills (5 stars, last pushed 5mo ago), licensed MIT. It adds 65 tokens to every session and 3,808 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories