Skip to content
Back to skills

Hayba Dialogue Subtitle Review

ASecurity

Use when checking one voiced dialogue beat for subtitle timing, legibility, safe layout, and audible playback.

  • 13 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added October 4, 2026
ai-agentsgo

Works with

  • cli

Security analysis

A100/100

Scanned October 4, 2026

npx -y skills add zajalist/hayba --skill hayba-dialogue-subtitle-review --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Hayba Dialogue Subtitle Review?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Hayba Dialogue Subtitle Review
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/zajalist-hayba-dialogue-subtitle-review/badge)](https://www.skillsdirectory.com/skills/zajalist-hayba-dialogue-subtitle-review)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: hayba-dialogue-subtitle-review
description: Use when checking one voiced dialogue beat for subtitle timing, legibility, safe layout, and audible playback.
metadata:
  category: narrative
  tags: dialogue, subtitles, timing, audio
---

# Review one voiced dialogue beat

## When to use

Use for a specific line or exchange with known voice asset, speaker, language, and intended duration. Record the subtitle text, reading-speed target, viewport sizes, and the moment the line should begin and end. Project dialogue and localization systems vary; identify the actual owner before editing.

## Tool routing

- Inspect the sound with audio_asset_inspect and the subtitle widget with ui_get_widget_info. Measure the actual and longest expected line with ui_measure_text, then use ui_layout_snapshot, ui_render_widget_to_png, and ui_validate for clipping, safe areas, and contrast. Fix a confirmed layout problem with ui_set_slot_layout or ui_set_text_style, then re-render and revalidate.
- Check editor_get_state, start editor_start_pie only when a dialogue trigger exists, and observe live text with editor_pie_widget_tree and sound presence with audio_active_sounds. Capture the start, middle, and end through editor_pie_screenshot, polling each requested file. Stop with editor_stop_pie after this workflow's session.
- If the project has no typed dialogue or subtitle timing authoring path, make that edit in its own Unreal system and use this workflow for verification. Do not use 2D audio preview to claim spatial dialogue placement.

## Evidence

Report text, language, voice asset, observed display interval, measured layout, validation findings, sound presence, and any timing mismatch. Active-sound presence does not prove lip sync, audibility, or exact subtitle synchronization; these need listened and viewed playback.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.