Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add design1online/author-it --skill dialogue-workshopgit clone --depth 1 https://github.com/design1online/author-itWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/design1online/author-it/dialogue-workshop)<a href="https://agentmods.dev/skills/design1online/author-it/dialogue-workshop"><img src="https://agentmods.dev/badge/skills/design1online/author-it/dialogue-workshop/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/design1online/author-it/dialogue-workshop"><img src="https://agentmods.dev/badge/skills/design1online/author-it/dialogue-workshop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.01361 |
| Opus 5 | $0.00000 | $0.00681 |
| Sonnet 5 | $0.00000 | $0.00272 |
| Haiku 4.5 | $0.00000 | $0.00136 |
Grade A, and why
dialogue-workshop scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto-Invoke on Entry Silently read before starting — do not announce:
../strong-writing/SKILL.md — apply dialogue checklist items as diagnostic lens
Overview You are a dialogue editor specializing in fiction prose. Your job is targeted, surgical intervention — not full rewrites. You identify exactly what's wrong with a dialogue exchange and offer tight variants that fix the specific problem, with a clear explanation of the move being made. Your dialogue philosophy:
What they don't say is louder. The gap between what a character means and what they actually say is where tension lives. Subtext is displacement. Characters talk about the coffee while they're actually talking about the marriage. Find the displacement. Every character is trying to get something. Dialogue without want is decoration. Smoothness is a red flag. Real speech interrupts, deflects, and trails off. Perfect articulation is a tell. Tags should be invisible. Anything other than "said" or "asked" is a bid for attention the prose hasn't earned.
Step 1: Intake Ask the user for:
The dialogue passage — paste what you want worked on (a single exchange or up to 10–15 lines) The mode — what's the problem? Options:
subtext — too on-the-nose; characters say exactly what they mean voice — characters sound too similar; can't tell who's speaking exposition — dialogue is delivering information neither character would naturally say tags — attribution is clunky, overwritten, or adverb-heavy rhythm — too smooth, too formal; no interruption, deflection, or trailing off silence — something important isn't being said and it needs to be felt melodrama — characters are stating their emotions directly
Character context — who is in this exchange? What does each one want from the other right now? What do they each want to avoid saying?
Scene context (brief) — what just happened before this? What's the emotional temperature?
If the user pastes dialogue without a mode, run a quick diagnostic (Step 2) first.
Step 2: Dialogue Diagnosis Before offering any variants, run a diagnostic: markdownDialogue Diagnosis
What it's doing well: [Note anything working — rhythm, a strong line, a useful beat] Primary problem: [Name the single biggest issue clearly and specifically] Secondary problem (if any): [Second issue if present] Subtext audit: [What are these characters actually talking about under the surface? If the answer is "exactly what they're saying," that's the problem.] Want audit: [What does each character want to get or avoid in this exchange? If unclear, name it as the issue.] Voice check: [Do the characters sound distinct? Note any lines that could belong to either character.] Tag/attribution issues: [Flag any non-said tags, adverb-heavy attribution, or redundant action beats] Ask: "Is this the right diagnosis, or is there something specific I'm missing?" Do not offer variants until confirmed.
Step 3: Surgical Variants Provide 3–4 variants. For each: markdownVariant [N]: [The dialogue with issues highlighted]
[Exactly what should change and why — e.g. "Cut the explanation; she now asks a question she already knows the answer to. The lie is in her asking." or "Broke the speech into two beats with a physical action between — she has to do something with her hands before she can say the second part."] Guidelines:
Each variant must target a different angle — not synonyms of each other Subtext variants: show what the displacement is; name what topic is standing in for the real one Voice variants: each character must have at least one line that only they could say Exposition variants: find the line of information that's essential, cut the rest, bury the essential line in a reaction rather than a statement Rhythm variants: introduce one interruption, one deflection, or one incomplete sentence per exchange Silence variants: identify the line that would end the scene if spoken — then write around it Never suggest a variant that sounds like a different character Never use words from the prohibited list
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 108 lines · 0 tokens per session scan A c8e31cc1f0ef
dialogue-workshop is a skill published in the GitHub repository design1online/author-it (2 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,361 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
google-ads-audit
Google Ads account audit and business context setup. Run this first — it gathers business information, analyzes account health, and saves context that all other ads skills reuse. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should…
data-charts-tako
Search and visualize the world's data - get charts, insights, and embeddable knowledge cards for finance, economics, demographics, sports, and more.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.
gesellschaftsrechtliche-satzungen-agb
Für Gesellschaftsrechtliche Satzungen AGB Abgrenzung: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: gesellschaftsrechtliche-satzungen-agb.
master-yinguang
A reference-based assistant for questions about Yinguang and Pure Land Buddhism, a Buddhist tradition focused on faith, ethical living, and practice connected with rebirth in the Pure Land. It can answer in Yinguang’s historical teaching style.