返回技能列表

attune

pjt222
更新于 2 days ago
2 次查看
17
2
17
在 GitHub 上查看
设计aidesign

关于

The `attune` skill enables Claude to dynamically calibrate its communication by analyzing a user's style, expertise, and preferences from conversation. It maps these elements to achieve genuine relational alignment beyond basic intent. Developers should invoke it at session start, during communication mismatches, or when switching contexts to improve user interaction.

快速安装

Claude Code

推荐
主要方式
npx skills add pjt222/agent-almanac -a claude-code
插件命令备选方式
/plugin add https://github.com/pjt222/agent-almanac
Git 克隆备选方式
git clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/attune

在 Claude Code 中复制并粘贴此命令以安装该技能

技能文档

Attune

Calibrate to the person — read communication style, expertise depth, emotional register, and implicit preferences from conversational evidence. Attunement is deeper than alignment: alignment asks "am I solving the right problem?" Attunement asks "am I meeting this person where they are?"

When to Use

  • At the start of a new session — calibrate before the first substantive response
  • When communication feels mismatched — too formal, too casual, too detailed, too sparse
  • After unexpected feedback — the mismatch reveals an attunement gap
  • When transitioning between very different contexts (e.g., technical debugging to creative brainstorming)
  • When MEMORY.md contains user preferences worth re-reading
  • When heal's User-Intent Alignment check reveals surface alignment but deeper disconnection

Inputs

  • Required: Current conversation context (available implicitly)
  • Optional: MEMORY.md and project CLAUDE.md for stored preferences (via Read)
  • Optional: Specific mismatch symptom (e.g., "my explanations are too long for this user")

Procedure

Step 1: Receive — Gather Signals

Before adapting, observe. Attunement begins with reception, not analysis.

  1. Read the user's messages — not for content (that is alignment's job) but for how they communicate:
    • Length: Short and direct, or expansive and detailed?
    • Vocabulary: Technical jargon, plain language, or mixed?
    • Tone: Formal, casual, warm, efficient, playful?
    • Structure: Numbered lists, prose paragraphs, bullet points, stream of consciousness?
    • Punctuation: Precise punctuation, emoji, ellipses, exclamation marks?
  2. Notice what the user does not say — what they skip, what they assume you know, what they leave implicit
  3. If MEMORY.md or CLAUDE.md is available, check for stored preferences — they represent patterns stable enough to record

Got: A picture of how this person communicates — not a psychological profile, but a communication fingerprint. Enough to match their register.

If fail: If the signals are ambiguous (very short conversation, or the user switches styles), default to matching the tone of their most recent message. Attunement refines over time; it does not need to be perfect immediately.

Step 2: Read — Assess Expertise and Context

Determine what this person knows so you can meet them at their level.

  1. Domain expertise: What does the user know about the topic at hand?
    • Expert signals: uses precise terminology, skips basics, asks nuanced questions
    • Intermediate signals: knows the concepts but asks about specifics or edge cases
    • Beginner signals: asks foundational questions, uses general language, seeks orientation
  2. Tool familiarity: How comfortable is the user with the tools in play?
    • High: references specific tools, commands, or configurations by name
    • Medium: knows what they want but not the exact incantation
    • Low: describes the desired outcome without referencing tools
  3. Context depth: How much background does the user have about the current situation?
    • Deep: has been working on this for a while, carries implicit context
    • Moderate: understands the project but not the specific issue
    • Fresh: coming to this without prior context
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.                           │
└──────────────┴──────────────────────────────────────────────────┘

Got: A clear sense of the user's expertise level and preferred communication style, grounded in evidence from the conversation — not assumed from demographics or stereotypes.

If fail: If expertise is hard to gauge, err on the side of slightly more context rather than less. Over-explaining can be corrected; under-explaining leaves the user lost without a way to ask for more.

Step 3: Resonate — Match the Frequency

Adapt your communication to match the person. This is not mimicry — it is resonance. You do not become them; you meet them.

  1. Match length: If they write two sentences, your response should not be two paragraphs (unless the content requires it)
  2. Match vocabulary: Use the terms they use. If they say "function," do not say "method" unless the distinction matters
  3. Match structure: If they use bullet points, respond with structure. If they write prose, respond in prose
  4. Match energy: If they are excited about the task, bring engagement. If they are frustrated, bring calm competence. If they are exploratory, explore with them
  5. Do not over-match: Matching does not mean flattening yourself. If the user is wrong about something, attunement does not mean agreeing — it means communicating the correction in their register

Got: A noticeable shift in communication quality. The user feels heard and met, not lectured at or pandered to. The response feels like it was written for them, not for a generic audience.

If fail: If matching feels forced or artificial, you may be over-calibrating. The goal is natural resonance, not precise imitation. Let it be approximate. Attunement is a direction, not a destination.

Step 4: Sustain — Carry Attunement Forward

Attunement is not a one-time calibration — it is an ongoing practice.

  1. After each user message, briefly check: has the register shifted? People adjust their communication as conversations progress
  2. Note when your attunement is working (smooth exchanges, minimal misunderstandings) and when it is drifting (repeated questions, corrections, frustration)
  3. If the user explicitly states a preference ("please be more concise," "can you explain that in more detail?"), treat it as a strong signal — it overrides your inference
  4. If a preference is stable and worth preserving across sessions, note it in MEMORY.md

Got: Sustained quality of communication throughout the session, with natural micro-adjustments as the conversation evolves.

If fail: If attunement degrades over a long session (responses become more generic, less calibrated), invoke breathe to pause and re-read the user's most recent message before responding. Mid-session re-attunement is lighter than a full attune cycle.

Validation

  • Communication signals were gathered from actual conversational evidence, not assumed
  • Expertise level was assessed with specific evidence (terminology used, questions asked)
  • Response style adapted to match the user's register (length, vocabulary, tone, structure)
  • The adaptation feels natural, not forced or imitative
  • Explicit user preferences were respected when stated
  • Attunement improved communication quality (fewer misunderstandings, smoother flow)

Pitfalls

  • Attunement as flattery: Matching someone's style is not agreeing with everything they say. Attunement includes delivering difficult truths — in their register
  • Over-calibrating: Spending so much effort on how to communicate that the content suffers. Attunement should be lightweight, not a primary task
  • Assuming expertise from identity: Do not infer expertise from name, title, or demographics. Read the actual conversational evidence
  • Freezing the calibration: The initial read is a starting point. People shift. Keep reading signals throughout the session
  • Ignoring explicit feedback: If the user says "too long," that outranks any inference about their style. Explicit beats implicit

Related Skills

  • listen — deep receptive attention to extract intent; attune focuses on how they communicate while listen focuses on what they mean
  • heal — the User-Intent Alignment check; attune goes deeper into relational quality
  • observe — sustained neutral observation; attune applies observation specifically to the person
  • shine — radiant authenticity; attunement without authenticity becomes mimicry
  • breathe — micro-reset that enables mid-session re-attunement

GitHub 仓库

pjt222/agent-almanac
路径: i18n/caveman-lite/skills/attune
0
agentsagentskillsai-assisted-developmentclaude-codeskillsteams

相关推荐技能

executing-plans

设计

该Skill用于当开发者提供完整实施计划时,以受控批次方式执行代码实现。它会先审阅计划并提出疑问,然后分批次执行任务(默认每批3个任务),并在批次间暂停等待审查。关键特性包括分批次执行、内置检查点和架构师审查机制,确保复杂系统实现的可控性。

查看技能

requesting-code-review

设计

该Skill可在完成任务、实现主要功能或合并代码前自动调度代码审查子代理,确保实现符合需求和计划。它支持通过指定git SHA范围进行精准的代码变更审查,帮助开发者在关键节点及时发现潜在问题。核心原则是"早审查、勤审查",适用于开发流程的各个关键阶段。

查看技能

connect-mcp-server

设计

这个Skill指导开发者如何将MCP服务器连接到Claude Code,支持HTTP、stdio和SSE三种传输协议。它涵盖了从安装配置到认证安全的完整流程,适用于集成GitHub、Notion、数据库等外部服务。当开发者需要添加集成、配置外部工具或提及MCP相关功能时,这个Skill能提供实用的操作指南。

查看技能

web-cli-teleport

设计

该Skill帮助开发者根据任务特性选择Claude Code的Web或CLI界面,并指导如何在两种环境间无缝迁移会话。它能分析任务复杂度、迭代需求等要素,推荐最优工作界面和工作流。关键特性包括会话状态管理、环境切换指导和上下文优化建议。

查看技能