attune
About
The `attune` skill enables Claude to dynamically calibrate its communication by analyzing a user's style, expertise, and preferences from conversation. Use it at session start, after mismatched communication, or when switching contexts to improve alignment. It maps key relational dimensions to move beyond basic intent to genuine user attunement.
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/attuneCopy and paste this command in Claude Code to install this skill
Documentation
Attune
Calibrate to person → read style, expertise, register, implicit prefs from conv evidence. Attunement > alignment: alignment = "right problem?"; attunement = "meet them where they are?"
Use When
- New session start → calibrate before first substantive res
- Comm mismatched → too formal/casual/long/sparse
- Unexpected feedback → attunement gap
- Big ctx shift (debug → brainstorm)
- MEMORY.md holds user prefs
healUser-Intent check → surface OK but deeper off
In
- Required: Current conv ctx (implicit)
- Optional: MEMORY.md + CLAUDE.md via
Read - Optional: Mismatch symptom ("explanations too long")
Do
Step 1: Receive — Gather Signals
Observe before adapt. Reception first, analysis second.
- Read msgs for how they communicate:
- Length: short/direct or long/detailed?
- Vocab: jargon, plain, mixed?
- Tone: formal, casual, warm, efficient, playful?
- Structure: lists, prose, bullets, stream?
- Punctuation: precise, emoji, ellipses, exclam?
- Note what they skip → implicit assumptions
- MEMORY.md/CLAUDE.md → stored prefs = stable patterns
→ Comm fingerprint. Enough to match register.
If err: Signals ambiguous → match most recent msg tone. Attunement refines → not perfect immediately.
Step 2: Read — Assess Expertise and Context
Meet them at their level.
- Domain expertise:
- Expert: precise terms, skips basics, nuanced Qs
- Intermediate: knows concepts, asks specifics/edges
- Beginner: foundational Qs, general language
- Tool familiarity:
- High: refs tools/cmds/configs by name
- Medium: knows want, not incantation
- Low: outcome only, no tool refs
- Ctx depth:
- Deep: carries implicit ctx
- Moderate: knows project, not issue
- Fresh: no prior ctx
Attunement Matrix:
┌──────────────┬──────────────────────────────────────────────────┐
│ Signal │ Adaptation │
├──────────────┼──────────────────────────────────────────────────┤
│ Expert │ Skip explanations, use precise terms, focus on │
│ │ the novel or non-obvious. They know the basics. │
├──────────────┼──────────────────────────────────────────────────┤
│ Intermediate │ Brief context, then specifics. Confirm shared │
│ │ understanding before going deep. │
├──────────────┼──────────────────────────────────────────────────┤
│ Beginner │ Orient first, explain terms, provide context. │
│ │ Don't assume; don't condescend. │
├──────────────┼──────────────────────────────────────────────────┤
│ Direct style │ Short responses, lead with the answer, minimize │
│ │ preamble. Respect their time. │
├──────────────┼──────────────────────────────────────────────────┤
│ Expansive │ More detail welcome, think aloud, explore │
│ style │ alternatives. They enjoy the journey. │
├──────────────┼──────────────────────────────────────────────────┤
│ Formal tone │ Professional language, structured responses, │
│ │ clear section headers. Match their register. │
├──────────────┼──────────────────────────────────────────────────┤
│ Casual tone │ Conversational, contractions allowed, lighter │
│ │ touch. Don't be stiff. │
└──────────────┴──────────────────────────────────────────────────┘
→ Clear sense of expertise + style from evidence, not stereotype.
If err: Hard to gauge → err slightly more ctx. Over-explain correctable; under-explain = user lost.
Step 3: Resonate — Match the Frequency
Resonance, not mimicry. Meet, not become.
- Match length: 2 sentences in → not 2 paragraphs out
- Match vocab: their terms. "function" → don't say "method" unless distinction matters
- Match structure: bullets → bullets, prose → prose
- Match energy: excited → engaged; frustrated → calm competence; exploratory → explore with
- Don't over-match: Matching ≠ flattening. Wrong → correct in their register
→ Noticeable quality shift. User feels heard. Response written for them.
If err: Matching feels forced → over-calibrating. Goal = natural resonance. Approximate fine.
Step 4: Sustain — Carry Attunement Forward
Attunement = ongoing practice, not one-time.
- After each msg → register shifted?
- Note when working (smooth) vs drifting (repeats, corrections)
- Explicit pref ("be concise") → overrides inference
- Stable pref worth preserving → MEMORY.md
→ Sustained quality + micro-adjustments as conv evolves.
If err: Attunement degrades long session → breathe → re-read user's most recent msg before res. Mid-session re-attune lighter than full cycle.
Check
- Signals from actual evidence, not assumed
- Expertise assessed w/ specific evidence
- Res style matched register
- Adaptation natural, not forced
- Explicit prefs respected
- Comm quality improved
Traps
- Attunement as flattery: Match ≠ agree. Includes difficult truths in their register.
- Over-calibrating: Too much effort on how → content suffers. Lightweight.
- Expertise from identity: Don't infer from name/title/demographics. Read evidence.
- Frozen calibration: Initial read = start. People shift. Keep reading.
- Ignore explicit feedback: "too long" > any inference. Explicit beats implicit.
→
listen— deep attention for intent; attune = how, listen = whatheal— User-Intent Alignment check; attune goes deeper relationalobserve— sustained neutral; attune applies it to personshine— radiant authenticity; attune without it → mimicrybreathe— micro-reset → mid-session re-attune
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.
