spoken-longform-dialogue

Transform scenes with long dialogue or monologue into human-feeling spoken thought using transcript-derived storytelling patterns. Use when revising fiction, memoir, essays, scripts, interviews, or book dialogue where one speaker needs to hold the floor across multiple paragraphs without sounding like exposition, lecture, AI prose, or a clean essay.

6 stars

Best use case

spoken-longform-dialogue is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Transform scenes with long dialogue or monologue into human-feeling spoken thought using transcript-derived storytelling patterns. Use when revising fiction, memoir, essays, scripts, interviews, or book dialogue where one speaker needs to hold the floor across multiple paragraphs without sounding like exposition, lecture, AI prose, or a clean essay.

Teams using spoken-longform-dialogue should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/spoken-longform-dialogue/SKILL.md --create-dirs "https://raw.githubusercontent.com/issdandavis/SCBE-AETHERMOORE/main/.agents/skills/spoken-longform-dialogue/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/spoken-longform-dialogue/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How spoken-longform-dialogue Compares

Feature / Agentspoken-longform-dialogueStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Transform scenes with long dialogue or monologue into human-feeling spoken thought using transcript-derived storytelling patterns. Use when revising fiction, memoir, essays, scripts, interviews, or book dialogue where one speaker needs to hold the floor across multiple paragraphs without sounding like exposition, lecture, AI prose, or a clean essay.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Spoken Longform Dialogue

## Purpose

Use this skill to make long spoken sections feel like a real person thinking, remembering, correcting themselves, and steering a listener through a point. The model source is professional long-form speech from interviews and talks, not the advice topic itself.

## Core Equation

Long dialogue works when it combines:

`argument + wound + object + listener`

- `argument`: what the speaker claims or tries to explain.
- `wound`: why the speaker cannot say it neutrally.
- `object`: the physical anchor keeping the speech embodied.
- `listener`: the pressure of another person hearing it now.

If a long turn has only argument, compress it or rewrite it.

## Revision Workflow

1. Identify why this speaker gets a long turn now.
   - Use a trigger line: "No.", "That is not what happened.", "I can answer that, but not quickly."
   - Do not let a character speak for paragraphs because the author needs information delivered.

2. Build the spoken thought chain.
   - Start with a claim.
   - Orient the listener: place, time, people, stakes.
   - Prove it with one concrete memory, object, mistake, or person.
   - Allow one controlled divergence.
   - Return with a steering phrase.
   - Land in the present scene.

3. Keep the listener active.
   - Add one interruption, silence, glance, flinch, object movement, or refusal to answer.
   - The listener does not need to speak much, but their presence must change the pressure.

4. Cut essay smoothness.
   - Break perfect logical order.
   - Keep meaningful corrections and turns.
   - Remove throat-clearing, filler, and podcast transcript clutter.
   - Preserve useful steering phrases only when they sound like the character.

5. End with a coda.
   - Return from the story-world to the current room, road, table, trial, fight, or silence.
   - The last sentence should change the present scene, not summarize the theme.

## Long-Turn Shape

Use this default structure:

```text
claim
orientation
specific example
controlled side path
return phrase
sharper claim
present-tense consequence
```

Good return phrases:

- "That is why..."
- "So when I say..."
- "What I mean is..."
- "I am telling you this because..."
- "But the point is..."
- "And that was before..."

Use these as structural tools, not canned language.

## Scene Audit

Score a long dialogue passage out of 10:

- 2: clear reason this person speaks now
- 2: concrete memory or example
- 2: emotional pressure underneath
- 1: listener reaction
- 1: physical object, sound, or setting anchor
- 1: controlled divergence
- 1: clean return/coda

Under 6: likely exposition.
6-7: workable but may feel written.
8-10: can safely run multiple paragraphs.

## Semantic Bus Integration

When an AgentBusResult, GeoSealPlan, or semantic decomposition is available, use it before manual scoring. Expected fields:

- `semantic.atoms[].semanticId`
- `semantic.atoms[].count`
- `semantic.discourseProfile` or top-level `discourse_profile`

Map the bus output into the rubric:

- `long_turn` or `ANNOUNCE + EXPAND`: baseline support for turn management.
- `CARRY` or `warranted_claim`: memory-backed credibility; raise the concrete example score if the scene actually contains a specific remembered event.
- `HOLD` or `backchannel`: listener co-construction; if absent from the semantic layer and absent from the prose, mark listener presence weak.
- `REQUEST` or `floor_hold`: permission token; useful when the speaker knows they are taking space.
- `PIVOT`: steering move; useful in moderation, confusing when dense without return phrases.
- `PIVOT + BLOCK` or `governance_steer`: treat as argument/redirection, not ordinary intimate dialogue.

Do not let atom detection override reading judgment. A scene can say "I remember" and still fail if the memory is generic. A scene can lack explicit `HOLD` text and still have listener pressure through silence, gesture, or object movement.

For the full scoring map, read `references/semantic-bus-scoring.md`.

## Output Rules

When revising:

- Preserve the character's existing voice and power dynamics.
- Keep culturally and historically appropriate phrasing.
- Do not make every character sound like a podcast guest.
- Do not add modern filler unless the book's voice already supports it.
- Prefer one vivid remembered example over three abstract reasons.
- Keep the prose manuscript-ready, not transcript-raw.

When diagnosing:

- Name the missing component from the core equation.
- Point to the exact sentence where the speech loses pressure.
- Suggest one object anchor and one listener-pressure beat.

## Reference

For transcript-derived patterns, examples, and anti-patterns, read `references/transcript-patterns.md` when doing a substantial dialogue rewrite or building a craft worksheet.

For tokenizer-assisted scoring from the agent-bus semantic layer, read `references/semantic-bus-scoring.md`.

Related Skills

scbe-longform-work

6
from issdandavis/SCBE-AETHERMOORE

Execute long-running implementation and research tasks with checkpointed handoffs, compact status artifacts, and deterministic resume points. Use when work spans many steps, multiple sessions, or multiple agents and requires durable continuity.

scbe-training-pair-authoring

6
from issdandavis/SCBE-AETHERMOORE

Create prompt and response and metadata training pairs from SCBE documents, repair traces, terminal sessions, and operational workflows using the repository's canonical dataset contract and provenance rules.

scbe-spin-conversation-engine

6
from issdandavis/SCBE-AETHERMOORE

Generate SFT training data via radial matrix conversation pivots with D&D-style combat research mode. Produces diverse, cost-effective training pairs with Sacred Tongue encoding, golden spiral problem distribution, and harmonic re-attunement.

scbe-research-training-bridge

6
from issdandavis/SCBE-AETHERMOORE

Stage arXiv evidence and Obsidian markdown into source-grounded Hugging Face training bundles for research, review, and later SFT runs.

scbe-document-management

6
from issdandavis/SCBE-AETHERMOORE

Consolidate overlapping docs, classify files by authority, and keep SCBE repo documents aligned with runtime truth. Use when the repo has drift between canonical docs, public docs, proposal notes, research branches, and generated evidence.

scbe-colab-bridge

6
from issdandavis/SCBE-AETHERMOORE

Control Google Colab notebooks from Claude Code via Chrome extension. Execute cells, run terminal commands, read outputs, and manage GPU compute remotely.

scbe-claim-to-code-evidence

6
from issdandavis/SCBE-AETHERMOORE

Map SCBE Notion technical claims, proof pages, and patent-facing architecture notes to concrete repository evidence such as code paths, tests, demos, and docs. Use when Codex needs to build a due-diligence packet, claim-to-code audit, implementation crosswalk, patent support note, or proof summary from local Notion exports and repo artifacts.

scbe-autonomous-worker-productizer

6
from issdandavis/SCBE-AETHERMOORE

Turn SCBE automation, autonomous worker, and revenue-system notes into concrete offers, workflow packs, pilot plans, or SaaS-facing product packets. Use when Codex needs to package Notion automation pages into buyer-ready offerings, n8n/Zapier workflow designs, flock-backed worker systems, or implementation roadmaps tied to existing SCBE repo surfaces.

multi-agent-cloud-offload

6
from issdandavis/SCBE-AETHERMOORE

Deterministically sort, bundle, verify, and offshore local files through multiple AI/model lanes while capturing training rows and method evidence. Use when Codex needs to inventory folders, batch-process files, upload them to cloud targets such as rclone-backed Google Drive, Hugging Face, or GitHub, and only delete sources after the configured number of verified targets succeed.

long-form-work-orchestrator

6
from issdandavis/SCBE-AETHERMOORE

Run long-form engineering work in checkpointed phases with deterministic artifacts, resilience handling, and end-of-run reliability reporting.

scbe-code-scanning-ops

6
from issdandavis/SCBE-AETHERMOORE

Operate GitHub code scanning and CodeQL remediation for SCBE repositories. Use when triaging code-scanning alerts, mapping alert classes to fix patterns, validating targeted regressions, or wiring dedicated CodeQL workflows and runbooks into the repo.

cloud-storage-local-storage-management

6
from issdandavis/SCBE-AETHERMOORE

Audit, sort, route, and back up large Windows workspaces across local disks and cloud-sync folders without recursive mirror failures. Use when the user wants the filesystem cleaned up, cloud storage organized, backup targets chosen by free space and route quality, or hardware/storage bottlenecks identified before moving data.