npc-showcase-clips

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites: none for the install itself: no account, no API key, no paid service, and nothing else to install first. For using the skill afterwards as described, SKILL.md names no account, no API key and no paid service either: you need a game or mod integration that can stage a scripted NPC exchange, hold the gameplay camera, write or pin a reply, pick an action and render both voices before the clip rolls; the GTA V example tools SKILL.md points to (not installed) run locally on Windows with ffmpeg for screen and audio capture and Deno for the cutting script. Never put a key in a file: this skill names none. Install "npc-showcase-clips" for me. It is a single SKILL.md playbook for recording short clips of NPC conversations that look like real gameplay, ready to post: script an exchange at a chosen place and time, hold the gameplay camera still behind the player, render both lines before the clip rolls so they play back to back, keep only the game's own HUD and subtitles on screen, and cut 5-10 s clips in 16:9 (and 9:16) using timeline markers, re-taking any clip that runs long instead of cutting words. Repository: https://github.com/christos-antono/NPCTalk (the skill is the .agents/skills/npc-showcase-clips/ folder at the pinned commit: SKILL.md only; the identical .claude/skills/ copy and the root skills/ copy are duplicates, not the source of this listing, and the rest of the NPCTalk repo is not installed) Pinned version: install the code at commit 59635ceb8ee010599c3caf9d9d1ee1aa114af91d exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/christos-antono/NPCTalk into a temporary folder, check out commit 59635ceb8ee010599c3caf9d9d1ee1aa114af91d, and copy the .agents/skills/npc-showcase-clips/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-19: [FINGERPRINTS] - SKILL.md: SHA-256 e7814d4c757df59772cf8c9af6304a56cbbd4aed690e915f7fba8fce2d34cd6f If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full and tell me in plain words: what the skill does when used, which services it connects to, whether it reads or sends any personal information or keys, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds one file only: SKILL.md (4,193 bytes). There is no code, no script, no reference file and no dependency list in the folder: the skill is instructions for scripting, staging, recording, syncing and cutting a short NPC clip. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit. SKILL.md names no remote service, no host, no API key and no telemetry at all, at install time or at use time. That is a disclosure, not a step to run during this install: any voice rendering or LLM reply writing a clip relies on belongs to the game or mod setup you already provide, outside this skill folder and not installed here. - At use time, the work SKILL.md describes is local: a scripted exchange (clip name; at: a named spot or "x, y, z, heading"; time: hour of day; a: who speaks first, the player, a character or a ped model with a voice; b: the partner; line: the first line; reply: an instruction the LLM writes live, or say: a pinned approved line, for example with [shouting]; do: an action name or none), including NPC-only clips where the player is hidden and two NPCs talk. - To look like gameplay: every frame, set the follow camera's view mode and its heading and pitch relative to the player and disable look input (fixed is fine, cinematic cameras read as a trailer); frame the partner in front and a little to the side (2 m forward, 1 m right), raycast around the spot and turn away from walls, kiosks and doorways; snap to pavement and raycast down for the ground (awnings and roofs fool height lookups); keep the screen clean, the game's HUD and subtitles on and nothing of the mod on screen, and suppress phone calls and help text during a take; render first, then roll: write the reply, pick the action and render both voices before the clip starts, then play them back to back. - Recording, sync and cutting in the GTA V example SKILL.md points to (examples/gta-v/mod/DirectorClips.cs, examples/gta-v/tools/shoot.ps1 and examples/gta-v/tools/edit.ts, none of them part of this skill and none installed): shoot.ps1 brings the game to the front, reloads the mod, records the screen (ffmpeg ddagrab) and the PC's audio (WASAPI loopback) as separate files, starts the script and restarts capture if focus is lost; each capture segment starts with a white flash and a 1 kHz beep logged with a timestamp, and the mod logs clip_start/clip_end and every line's audio_on/audio_off to a timeline; edit.ts --clips <take> makes one MP4 per clip, from 0.2 s before clip_start until the last word or action, cropped to the game window, 1920 wide and loudness-normalised, caps clips at 10 s and reports any line that would be cut off instead of cutting it. Do not run any of that during this install. - Re-take, do not cut words: a clip that runs long gets re-shot (new renders come out different lengths) or its line tightened by a few words; pin approved replies with say:/do: so a re-take keeps the joke. Before sending a clip anywhere, look first: a contact sheet of one frame per clip (ffmpeg -ss 5 ... tile=5x4) catches a hidden partner or a wall in the shot in seconds. Gotchas SKILL.md lists: Windows Smart App Control refusing a new DLL after a reload (Code Integrity event 3077, test-load a new build first and keep the last one that loaded), another process holding the log file open so a take has no video start in its log, and a phone call or help text landing mid-clip. And its closing rule: voices in clips are clones, so before posting a clip anywhere the human decides, and say it is AI. 3. When I say "yes, install", install it as a skill: copy the whole npc-showcase-clips folder into the agent's skills directory, in a folder named "npc-showcase-clips", keeping its file (SKILL.md). Do not use the repo's plugin, marketplace or npx routes: those install the whole NPCTalk plugin or all of its skills, not this single skill alone. 4. Verify with no network calls: frontmatter valid, file in place. 5. Report what was installed, where, and what I still need to do myself (for example: provide the game or mod integration, any characters, voices, LLM and lines myself; provide ffmpeg, Deno, PowerShell and a running game myself only if I want to follow the GTA V example tools; provide any clip script myself; using the skill is a separate step that only starts when I ask for it, no clip is recorded or posted during this install, and the decision to post a clip, with the AI-voice disclosure SKILL.md requires, is mine alone). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.