Use when asked to turn a QA or capture flow into a reusable static shell script so it can be re-run without an agent — generate a repo-native `.sh` that launches, seeds, and captures screenshots/video deterministically. Triggers on "정적 스크립트로 만들어줘", "sh 파일로", "에이전트 없이 재실행", "capture script 생성".
Installs into .claude/skills of the current project.
Are you the author of Scriptify?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/testbeagle-scriptify)
---
name: scriptify
description: Use when asked to turn a QA or capture flow into a reusable static shell script so it can be re-run without an agent — generate a repo-native `.sh` that launches, seeds, and captures screenshots/video deterministically. Triggers on "정적 스크립트로 만들어줘", "sh 파일로", "에이전트 없이 재실행", "capture script 생성".
---
# scriptify
Freeze a flow the agent already worked out into a committed, repo-native `.sh` runner, so the maintainer can re-run it with no agent and no token cost. This is the mechanism the other skills call in their "offer a runner" step.
## Phase 0 — Discover (reuse preflight, read-only)
Run/reuse `../preflight/SKILL.md` to get the exact launch, seed, and capture commands and the output location. A runner must be a recording of a **verified** flow — either one a prior approved bugsweep/a11ysweep/perfsweep run already executed, or one this skill verifies after the gate (Phase 3). Do not run the flow during discovery.
## Phase 1 — Plan + approval gate (MANDATORY)
Present what the script will do (targets, steps, output path, where the file lands) and whether verifying it will execute the flow, then stop per the shared gate in `../beagle-shared/approval-gate.md` (if that file is missing, still stop and wait for the user's explicit approval).
## Phase 2 — Emit
Generate the script per `../beagle-shared/emit-runner.md`:
- Reuse the repo's existing script style/location if it has one; else portable bash (`set -euo pipefail`, env-parameterized, idempotent, reads bundle id/package from build output, echoes every artifact path).
- Carry the hard rules into the script so they survive without the agent: Android `am start -n` (never `monkey`), uninstall only within the approved data-reset scope (`install -r` for upgrade flows); iOS verify `BUILD SUCCEEDED` in the log.
- Write it to the repo's `scripts/` (or wherever its current scripts live), `chmod +x`.
## Phase 3 — Verify, then hand over
Run the emitted script twice from a fresh seeded state and confirm it produces the expected artifacts. A runner you didn't run is unverified — say so; don't claim it works. Then offer the script + a one-line usage note; let the maintainer commit it (don't auto-commit).
