Individual skill

conversation-patterns

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

claude-plugin/model-interaction-design/skills/conversation-patterns/SKILL.md

Read pinned source

Source commit f41b650435b62dec6d5b1dc3598ac4679f8b7ae7

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
203
Repository last updated
Jun 9, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt
# 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
Back to top