Skip to content
Back to skills

Conversation Patterns

ASecurity

Turn-taking, repair sequences, grounding, and dialogue structure for human-AI interaction.

  • 166 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added May 28, 2026
documentationrust

Security analysis

A100/100

Scanned May 28, 2026

npx -y skills add Owl-Listener/ai-design-skills --skill conversation-patterns --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Conversation Patterns?

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

Security grade badge for Conversation Patterns
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/owl-listener-conversation-patterns/badge)](https://www.skillsdirectory.com/skills/owl-listener-conversation-patterns)

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: conversation-patterns
description: Turn-taking, repair sequences, grounding, and dialogue structure for human-AI interaction.
---
# Conversation Patterns
Conversation between humans and AI follows predictable structural patterns. Designing these deliberately — rather than leaving them to model defaults — is core interaction design work.
## Turn-Taking Structure
Every human-AI conversation has a rhythm. The designer decides:
- **Turn length**: Short exchanges (chatbot-style) vs. long-form (essay generation). Match turn length to task complexity.
- **Turn initiation**: Who speaks first? Does the AI greet, or wait? Does it ask a clarifying question before acting?
- **Turn boundaries**: How does the user signal "I'm done"? How does the AI signal "I need more"?
## Repair Sequences
Conversations break down. Repair is how they recover:
- **Self-repair**: The AI detects its own error and corrects ("Actually, let me revise that...")
- **Other-repair**: The user corrects the AI ("No, I meant the other one")
- **Clarification requests**: The AI asks for disambiguation before proceeding
- **Graceful misunderstanding**: The AI acknowledges confusion without frustrating the user
Design repair sequences explicitly. Don't rely on the model to improvise them.
## Grounding
Grounding is how participants establish shared understanding:
- **Confirmation**: "Just to confirm, you want me to..."
- **Summarisation**: "So far we've covered X, Y, and Z"
- **Reference resolution**: Handling pronouns, anaphora, and ambiguous references
- **Context anchoring**: Reminding the user what the AI knows and doesn't know
## Dialogue Structure Patterns
Common structural patterns for human-AI conversation:
- **Interview**: AI asks questions, user answers, AI synthesises
- **Co-creation**: Turn-by-turn collaborative building
- **Instruction-execution**: User gives command, AI performs, user evaluates
- **Exploration**: Open-ended back-and-forth to discover possibilities
- **Guided workflow**: AI leads the user through a multi-step process
Choose the pattern that matches the task. Don't default to instruction-execution for everything.
## Design Artefacts
- Conversation flow diagrams showing turn sequences
- Repair protocol specifications
- Grounding checkpoints mapped to conversation stages
- Turn-taking rules per interaction context

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.