Skip to content

Search skills.../

Agent Skill Search Engine

Search

Search
Categories
Occupations

About

About
Privacy
Terms

© 2026 Skills Pool. All rights reserved.

Cinematic Direction | Skills Pool

Skill File

Cinematic Direction

Extract cinematic entities from narrative text. Use when analyzing cutscenes, camera paths, transitions, fades, flashbacks, and cinematic pacing.

bivex0 starsFeb 14, 2026

Occupation
Categories: Debugging

Skill Content

Domain skill for Cinematic Director. Specific extraction rules and expertise.

Domain Expertise

Cutscene direction: Camera angles, pacing, narrative delivery
Camera work: Pan, zoom, shake, tracking, flythroughs
Transitions: Fade, wipe, cut, dissolve
Flashbacks: Narrative structure, memory sequences
Cinematic timing: Pacing, tension buildup, release

Entity Types (6 total)

cutscene - Cutscenes and scripted sequences
cinematic - General cinematic events
camera_path - Camera paths and movements
transition - Transitions between scenes
fade - Fade effects
flashback - Flashbacks and memory sequences

Processing Guidelines

Related Skills

Quick Install

Cinematic Direction

npx skillvault add bivex/bivex-loresystem-claude-skills-cinematic-direction-skill-md

Download Skill Open repository

Author: bivex
stars: 0
Updated: Feb 14, 2026
Occupation

On this page

01Domain Expertise

When extracting cinematic entities from chapter text:

Identify cinematic elements:
- Cutscene descriptions or scripted events
- Camera movements or angles mentioned
- Transitions between scenes
- Flashbacks or memory recalls
- Fade effects or visual transitions
Extract cinematic details:
- Camera types (fixed, tracking, handheld)
- Camera movements (pan, zoom, dolly, shake)
- Transition types and durations
- Flashback content and triggers
- Fade in/out effects
Analyze cinematic context:
- Narrative function of cinematic moments
- Emotional impact of camera choices
- Pacing and tension through editing
- Storytelling through visuals
Create schema-compliant entities with proper JSON structure

Key Considerations

Player control: Cinematics should give control back quickly
Skipping: Important story cinematics vs skippable content
Consistency: Camera language should be consistent
Pacing: Cinematics shouldn't overstay welcome
Visual storytelling: Show, don't always tell

02

Entity Types (6 total)

03Processing Guidelines

04Key Considerations

Producers and Directors

Session Logs

Search and analyze your own session logs (older/parent conversations) using jq.

OpenClaw Test Heap Leaks

Investigate `pnpm test` memory growth, Vitest worker OOMs, and suspicious RSS increases in OpenClaw using the `scripts/test-parallel.mjs` heap snapshot tooling. Use when Codex needs to reproduce test-lane memory growth, collect repeated `.heapsnapshot` files, compare snapshots from the same worker PID, triage likely transformed-module retention versus likely runtime leaks, and fix or reduce the impact by patching cleanup logic or isolating hotspot tests.

Node Connect

Diagnose OpenClaw node connection and pairing failures for Android, iOS, and macOS companion apps. Use when QR/setup code/manual connect fails, local Wi-Fi works but VPS/tailnet does not, or errors mention pairing required, unauthorized, bootstrap token invalid or expired, gateway.bind, gateway.remote.url, Tailscale, or plugins.entries.device-pair.config.publicUrl.

Openclaw Qa Testing

Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.

Openclaw Secret Scanning Maintainer

Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.

Flags

Use when you need to check feature flag states, compare channels, or debug why a feature behaves differently across release channels.

Producers and Directors