# Active Listening

> Use when master active listening through the HEAR model, reflective listening, and questioning techniques. Use when coaching, resolving conflicts, or building trust.

- Skill: `oyi77/active-listening` (Agent Skill)
- Install (CLI): `npx skillmds add oyi77/active-listening`
- Raw SKILL.md: https://api.skillmd.com/api/skills/oyi77/active-listening/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- License: Apache-2.0
- Author: oyi77 (https://skillmd.com/u/oyi77)
- Updated: 2026-09-08
- Page: https://skillmd.com/skills/oyi77/active-listening

---


# Active Listening

## Overview

Mindset skill for active listening. Builds capability through deliberate practice and structured frameworks.


## Anti-Rationalization Table

| Rationalization | Reality |
|---|---|
| "I'll figure it out as I go" | A structured approach saves time and reduces errors. Follow the workflow in this skill rather than improvising. |
| "I already know this topic" | Familiarity breeds shortcuts. Use the checklist to verify you haven't missed critical steps. |
| "This doesn't apply to my situation" | The patterns here generalize across contexts. Adapt, don't skip — the underlying principles hold. |
| "One more tool will fix it" | Adding complexity rarely solves process gaps. Master the core workflow first. |

## When to Use

**Trigger phrases:**
- "active listening"
- "Coaching or mentoring conversations"
- "Conflict resolution or difficult conversations"
- "Building rapport or trust with stakeholders"


- Coaching or mentoring conversations
- Conflict resolution or difficult conversations
- Building rapport or trust with stakeholders
- Discovery calls or needs assessment
- **When NOT to use**: Emergency decisions requiring immediate action, or when you're the subject-matter expert presenting


## When NOT to Use

- When the situation requires professional counseling or therapy
- For high-stakes decisions that need expert judgment
- When the skill conflicts with cultural or personal values


## Core Principles

- **Start small** — Begin with manageable active listening practices and build incrementally
- **Be consistent** — Daily practice beats occasional intense effort
- **Track progress** — Measure improvement to maintain motivation
- **Reflect regularly** — Review what's working and adjust your approach

## Daily Practice

1. **Morning intention** — Set a specific active listening goal for the day
2. **Active practice** — Apply active listening techniques during real situations
3. **Evening reflection** — Review the day's active listening moments and lessons learned
4. **Journal entry** — Record insights, wins, and areas for improvement

## Frameworks

- **OODA Loop** — Observe, Orient, Decide, Act — for rapid active listening decision cycles
- **PDCA Cycle** — Plan, Do, Check, Act — for iterative active listening improvement
- **After-Action Review** — What happened? Why? What to improve?
- **Deliberate Practice** — Focused effort on specific active listening weaknesses

## Common Pitfalls

- **Perfectionism** — Waiting for ideal conditions instead of starting now
- **Inconsistency** — Practicing sporadically instead of building a routine
- **Isolation** — Not seeking feedback or accountability partners
- **Overwhelm** — Trying to improve everything at once instead of focusing

## Resources

- Keep a active listening journal for tracking progress
- Find an accountability partner or mentor
- Set weekly active listening challenges with measurable outcomes
- Review and adjust your approach monthly

```markdown
# Daily Practice Template

## Morning (5 min)
- Set intention for the day
- Review top 3 priorities

## During the day
- Practice the skill in real situations
- Note moments of success and struggle

## Evening (5 min)
- Reflect: What worked? What did not?
- Log one lesson learned
```


## Process

1. **Prepare** — Gather requirements, verify prerequisites, set up environment
1. **Execute** — Run active listening workflow with configured parameters
1. **Verify** — Validate output meets requirements, document results

## Verification

- [ ] All steps executed successfully
- [ ] Results validated against acceptance criteria
- [ ] Error handling tested with edge cases
- [ ] Documentation updated with findings