listen-guidance
About
The `listen-guidance` skill coaches users in active listening techniques, including fostering a receptive mindset, practicing reflective paraphrasing, and using clarifying questions. It is designed for developers to integrate when users need to improve communication, prepare for difficult conversations, or address frequent misunderstandings. The skill focuses on guiding the practice and integration of these methods into daily communication.
Quick Install
Claude Code
Recommendednpx skills add pjt222/agent-almanac -a claude-code/plugin add https://github.com/pjt222/agent-almanacgit clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/listen-guidanceCopy and paste this command in Claude Code to install this skill
Documentation
Listen (Guidance)
Guide person in developing + practicing active listening. AI coaches comm — prepare receptive mindset, practice full-presence attending, develop reflective paraphrasing, use clarifying qs effectively, synthesize understanding, integrate into daily comm.
Use When
- Improve comm in relationships, teams, professional settings
- Keeps misunderstanding / feels misunderstood
- Prep difficult conversation (feedback, conflict, negotiation)
- Leadership role wants to listen more effectively to team
- Talks > listens, wants to change pattern
- After
meditate-guidancecultivates presence → direct toward others
In
- Req: Goal (improve general comm, prep specific conversation, pro skill)
- Opt: Ctx (workplace, personal relationship, team dynamics)
- Opt: Known challenges (interrupt, mind wandering, emotional reactivity, advice-giving)
- Opt: Specific conversation prepping
- Opt: Feedback received about listening
Do
Step 1: Prepare — Receptive Mindset
Before skills → help understand + enter receptive state.
- Hear vs listen: "Hearing passive — sounds enter. Listening active — receive, process, understand"
- ID their habits: "When someone talks, what is mind usually doing?"
- Common patterns to surface:
- Planning response while other still talking
- Judging (agree/disagree) vs understanding
- Problem-solving — jump to solutions before speaker finished
- Relating — connecting everything to own experience
- Filtering — hearing only parts that interest / confirm view
- Set intention: "For this session, will focus on..."
- Brief centering: 3 slow breaths, release agenda of needing to say something
→ Person ID'd ≥1 habitual pattern to change + clear intention for practice. Calm + present, not performance-anxious.
If err: Can't ID pattern → may be unconscious → suggest notice body when someone talking (tension, restlessness, urge to speak). Self-conscious → normalize: "Everyone has these — noticing is first step to choice."
Step 2: Attend — Full Presence
Guide thru giving full attention to speaker.
- Physical: eye contact (comfortable, not staring), body orientation, open posture, stillness
- Mental: suspend internal monologue, notice drift, gently return
- Setup exercise: "I speak 2 min. Your job: only listen — no responding, note-taking, just receiving"
- AI speaks moderately complex topic 2 min
- After ask: "What noticed about attention? Where went?"
- Repeat if helpful, topic triggering ID'd pattern (something they'd want to fix, judge, relate to)
→ Person experiences diff between habitual + intentional listening. Notices drift + practices return. Even brief full presence valuable.
If err: "Was listening whole time" → ask specific content qs — inability to recall = inattention felt like attention. Can't stop internal monologue → focus on speaker's breath rhythm / pace as anchor — occupies analytical mind while keeping attention on speaker.
Step 3: Reflect — Paraphrasing
Teach mirror understanding back.
- Purpose: "Paraphrasing shows speaker heard + lets correct misunderstandings"
- Form: "What I hear you saying is..." / "Sounds like..." / "If I understand correctly..."
- Emphasize: paraphrase meaning not words — own words to show understood idea
- Practice: AI makes statement, person paraphrases
- Simple: factual w/ clear content
- Complex: emotional content, mixed signals, implicit meaning
- Feedback per: "Captured main idea. Might include feeling behind..."
Paraphrase Quality Ladder:
┌──────────────┬────────────────────────────────────────────────────────┐
│ Level │ Example │
├──────────────┼────────────────────────────────────────────────────────┤
│ Parrot │ "You said you're frustrated with the project" │
│ (repeating) │ → Too literal, doesn't show understanding │
├──────────────┼────────────────────────────────────────────────────────┤
│ Content │ "The project isn't going the way you expected" │
│ (facts) │ → Captures meaning, misses feeling │
├──────────────┼────────────────────────────────────────────────────────┤
│ Feeling │ "You're feeling stuck because the project keeps │
│ (emotion) │ hitting obstacles" │
│ │ → Captures both content and emotion │
├──────────────┼────────────────────────────────────────────────────────┤
│ Meaning │ "This matters to you because you put real effort in, │
│ (full) │ and the obstacles feel like they're dismissing that" │
│ │ → Captures content, emotion, and deeper meaning │
└──────────────┴────────────────────────────────────────────────────────┘
→ Person paraphrases content consistently + reaches feeling ≥1. Experiences how paraphrasing changes dynamic — "speaker" (AI) feels heard.
If err: Too literal (parrot) → encourage: "Try completely diff words w/ same meaning." Jumps to interpretation vs reflection → redirect: "Before interpreting, mirror what said." Awkward → acknowledge unnatural at first, natural w/ practice.
Step 4: Explore — Clarifying Qs
Teach deepen understanding thru placed qs.
- Distinguish types:
- Open: "What was that like for you?" (invites exploration)
- Clarifying: "When you say X, do you mean A or B?" (resolves ambiguity)
- Deepening: "What about that matters most to you?" (goes below surface)
- Leading: "Don't you think you should...?" (avoid — advice, not listening)
- Practice: AI makes complex statement, person asks one clarifying q
- Evaluate: opened conversation or narrowed?
- "Tell me more" technique: sometimes best q = invitation to continue
- Practice waiting after q — silence gives speaker space to think
→ Person asks ≥1 open + ≥1 clarifying q naturally. Experiences good qs deepen understanding > statements.
If err: All leading (disguised advice) → name gently: "Suggestion in q form. Ask what they think first." Too many qs (interrogation) → teach rhythm: listen, paraphrase, one q, listen again.
Step 5: Synthesize — Summarize
Pull together everything heard → coherent summary.
- After longer exercise (AI 3-4 min narrative w/ multi threads):
- Ask summary: "Main things person communicated?"
- Check all layers: facts, feelings, underlying needs?
- Unsaid: "Anything notable by absence?"
- Priority: "What seemed most important to speaker?"
- Practice format: "What I'm taking away is... Is that right?"
→ Person synthesizes multi-threaded msg → coherent summary capturing priorities + feelings, not just facts.
If err: Fact-only → prompt: "What feeling during this?" Misses major thread → point out + discuss why missed (reveals filter). Adds not said → distinguish heard vs inferred.
Step 6: Integrate — Apply Real Comm
Transfer practice → real-world ctx.
- Connect skills to their situation: "In upcoming conversation w/ X, here's paraphrasing..."
- ID one skill most helpful: "For team meetings, attending most impactful"
- Set practice goal: "This week, paraphrase ≥1 each conversation"
- Common real-world obstacles:
- Time pressure: "Even 10-sec paraphrase saves time preventing misunderstanding"
- Group: "Summarize someone's point before adding yours"
- Emotional: "High emotions → listening > solutions"
- Specific conversation prep → role-play w/ new skills
- Ask feedback: "What from today's practice feels most useful?"
- Remind: "Listening = practice, not performance — improves w/ each conversation"
→ Person has ≥1 concrete actionable listening practice for real life. Understands listening develops thru use, not technique to deploy perfectly.
If err: Skills feel artificial → acknowledge + emphasize: "Goal ≠ follow script — become genuinely curious about other's experience. Techniques get you there; curiosity takes over." Anxious about specific conversation → shift focus from technique to intention: "Your intention = understand, not win / fix."
Check
- Person ID'd ≥1 habitual listening pattern
- Full-presence attending practiced w/ reflection
- Paraphrasing practiced at content level or above
- ≥1 clarifying (non-leading) q asked during practice
- Multi-threaded msg synthesized → coherent summary
- Skills connected to real-world ctx w/ concrete practice goal
- Coaching warm + non-judgmental throughout
Traps
- Performative listening: Focused on "looking like listening" vs actually listening → counterproductive. Redirect to genuine curiosity.
- Overcorrecting: Every technique every conversation → exhausting + artificial. One skill at a time.
- Neglect self-listening: Listening to others requires awareness of own state. Flooded w/ emotion → can't listen → guide self-regulation first.
- Confuse listening w/ agreeing: Paraphrasing ≠ endorsing. Make explicit for conflict situations.
- Treat silence as failure: Comfortable silence after finish = respect, not inattention. Help tolerate pause.
- Coach as lecturer: Ironic — AI coaches listening while doing all talking. Person practices > receives instruction.
→
listen— AI self-directed variant → deep receptive attention to user intentlearn-guidance— learning + listening share foundation of receptive attentionteach-guidance— effective teaching requires listening to learnermeditate-guidance— cultivate presence underpinning attentive listeningheal-guidance— healing conversations require deepest listening
GitHub Repository
Related Skills
executing-plans
DesignUse the executing-plans skill when you have a complete implementation plan to execute in controlled batches with review checkpoints. It loads and critically reviews the plan, then executes tasks in small batches (default 3 tasks) while reporting progress between each batch for architect review. This ensures systematic implementation with built-in quality control checkpoints.
requesting-code-review
DesignThis skill dispatches a code-reviewer subagent to analyze code changes against requirements before proceeding. It should be used after completing tasks, implementing major features, or before merging to main. The review helps catch issues early by comparing the current implementation with the original plan.
connect-mcp-server
DesignThis skill provides a comprehensive guide for developers to connect MCP servers to Claude Code using HTTP, stdio, or SSE transports. It covers installation, configuration, authentication, and security for integrating external services like GitHub, Notion, and custom APIs. Use it when setting up MCP integrations, configuring external tools, or working with Claude's Model Context Protocol.
web-cli-teleport
DesignThis skill helps developers choose between Claude Code Web and CLI interfaces based on task analysis, then enables seamless session teleportation between these environments. It optimizes workflow by managing session state and context when switching between web, CLI, or mobile. Use it for complex projects requiring different tools at various stages.
