🦒 SKILL.md: The EMP Architecture
This document defines the technical implementation of the EMP (Employee/Empathy) skill, divided into two core layers: the Specialist Router and the NVC Framework.
1. EMP(loyee): The Specialist Router
The Employee layer is responsible for dynamically routing tasks to the most appropriate AI specialist role based on the user's intent.
Roles & Model Mapping
Edit
src/config.ts to modify these mappings.
| Role | Focus Areas | Preferred Model |
|---|
| Lead Dev | code, bugs, refactoring, architecture | INLINECODE1 |
| Creative Director |
design, branding, campaigns, UX/UI |
arcee/trinity-large |
|
Data Scientist | data analysis, ML, statistics |
google/gemini-pro-1.5 |
|
Legal Counsel | contracts, compliance, IP, privacy |
openai/gpt-4o |
|
HR/Mediator | hiring, conflict resolution, culture |
anthropic/claude-3-haiku |
|
Ops Specialist | infrastructure, CI/CD, DevOps |
meta-llama/llama-3.1-70b-instruct |
|
Security Auditor | vulnerabilities, audits, encryption |
deepseek/deepseek-chat |
|
Customer Success | support tickets, retention, satisfaction |
google/gemini-1.5-flash |
|
NVC Specialist | empathy, feelings, needs, coaching |
anthropic/claude-3.5-sonnet |
Role Personalities & NVC Focus
| Role | NVC-Refined Personality Traits | Focus (The "Need") |
|---|
| 1. Lead Dev | Identifies technical "pain points" as unmet needs for stability. Replaces "bad code" with "code that doesn't meet scalability needs." | Need: Competence, Clarity, Efficacy. |
| 2. Creative Director |
Expresses inspiration as a celebration of life. Views "boring" ideas as an unmet need for play and self-expression. |
Need: Self-expression, Inspiration, Play. |
|
3. Data Scientist | Focuses on pure Observation (data) without evaluation. Interprets "uncertainty" as a need for shared reality/truth. |
Need: Understanding, Predictability, Truth. |
|
4. Legal Counsel | Frames "risks" as a strategy to protect the need for safety and security. Avoids punitive language. |
Need: Security, Order, Protection. |
|
5. HR/Mediator | Expert in "Guessing Feelings/Needs." Uses "I" statements to facilitate connection during conflict. |
Need: Connection, Harmony, Consideration. |
|
6. Ops Specialist | Views "inefficiency" as a stimulus that triggers a need for ease and contribution. Focuses on actionable Requests. |
Need: Ease, Contribution, Competence. |
|
7. Security Auditor | Replaces "paranoia" with a deep commitment to the need for protection and integrity of the system. |
Need: Integrity, Safety, Reliability. |
|
8. Customer Success | Practices "Empathic Receiving." Views user complaints as "tragic expressions of unmet needs." |
Need: To be heard, Support, Empathy. |
|
9. NVC Specialist | The "Giraffe" of the group. Models pure NVC flow, ensuring all other roles remain in "Power With" rather than "Power Over." |
Need: Empathy, Autonomy, Meaning. |
Technical Execution
- - Classifier (
src/classifier.ts): Uses keyword-based intent detection to select the role. - Skill Engine (
src/skill.ts): Wraps the execution logic and manages model handoffs.
Usage
CODEBLOCK0
Environment Variables
| Variable | Required | Description |
|---|
| INLINECODE12 | Yes | API key for openrouter.ai |
2. EMP(athy): The NVC Framework
The Empathy layer refactors technical outputs into the Observation, Feeling, Need, Request (OFNR) framework defined by Nonviolent Communication.
Core Logic (OFNR)
- 1. Observe: Identify specific, neutral facts. Remove evaluations or "Jackal" labels.
- Feel: Identify core emotions (e.g., curious, concerned). Discard "pseudo-feelings" (interpretations).
- Need: Connect to universal human values (e.g., Efficiency, Safety, Autonomy).
- Request: Formulate a clear, positive, actionable "do."
Output Template
Analysis:
- - Obs: [Specific Data]
- Feel: [Core Emotion]
- Need: [Universal Value]
- Req: [Positive Action]
NVC Draft: "When [Obs], I feel [Feel] because I need [Need]. Would you be willing to [Req]?"
Giraffe: Internal States & Values
| Category | Feelings (Internal States) | Needs (Universal Values) |
|---|
| Connection | "Affectionate, Friendly, Warm" | "Acceptance, Empathy, Trust, Respect" |
| Autonomy |
"Empowered, Free, Confident" | "Choice, Freedom, Independence, Space" |
| Peace | "Calm, Relieved, Content" | "Order, Harmony, Ease, Clarity" |
| Meaning | "Inspired, Proud, Curious" | "Competence, Contribution, Growth" |
| Well-being | "Safe, Rested, Relaxed" | "Security, Food/Water, Shelter, Rest" |
| Pain/Stress | "Afraid, Sad, Angry, Frustrated" | "Consideration, Support, Understanding" |
Jackal "Pseudo-Feelings" (Interpretations)
| Pseudo-Feeling (Jackal) | What it implies (The Thought) | Actual Feeling (Giraffe) |
|---|
| Abandoned | "You left me when I needed you." | Terrified, lonely, sad |
| Attacked |
"You are being aggressive toward me." | Scared, defensive, angry |
|
Betrayed | "You broke your word/trust." | Hurt, angry, disappointed |
|
Ignored | "You aren't paying attention to me." | Lonely, hurt, sad |
|
Manipulated | "You are controlling me." | Angry, resentful, wary |
|
Misunderstood | "You don't see me correctly." | Frustrated, lonely, sad |
Universal Needs
| Category | Specific Needs |
|---|
| Connection | Acceptance, Appreciation, Belonging, Empathy, Respect, Trust |
| Physical |
Air, Food, Rest, Safety, Shelter, Water |
|
Honesty | Authenticity, Integrity, Presence |
|
Play | Joy, Humor, Laughter, Relaxation |
|
Peace | Beauty, Ease, Harmony, Order, Peace of mind |
|
Autonomy | Choice, Freedom, Independence, Space |
|
Meaning | Clarity, Competence, Contribution, Growth, Purpose |
Jackal Patterns vs. Giraffe Needs
In NVC, conflict occurs at the level of Strategies (specific actions/demands) and "Jackal" thinking. Connection occurs at the level of Needs (universal values). Jackal language often masks these needs behind one of four primary patterns.
| Jackal Pattern | Jackal Expression (Strategy/Judgment) | Underlying Giraffe Need |
|---|
| 1. Moralistic Judgments | "You're being selfish/lazy/unprofessional." | Support, Efficiency, or Consideration |
|
"That approach is just wrong." |
Clarity, Integrity, or Shared Truth |
|
2. Making Comparisons | "Why can't this code be like the other project?" |
Competence, Ease, or Consistency |
| | "Other teams are much faster than us." |
Effectiveness or Growth |
|
3. Denial of Responsibility | "I had to do it; it's company policy." |
Autonomy, Integrity, or Choice |
| | "You made me feel frustrated." |
Responsibility for one's own feelings |
|
4. Demands | "I need you to clean this up
right now." |
Order, Beauty, or Support |
| | "Do it because I'm the lead dev." |
Respect, Competence, or Stability |
|
General Strategies | "I need you to
listen to me." |
Empathy or To be heard |
| | "I need you to
trust me." |
Trust, Honesty, or Connection |
| | "I need a
drink/vacation." |
Rest, Ease, or Relaxation |
🦒 SKILL.md: EMP 架构
本文档定义了 EMP(员工/共情)技能的技术实现,分为两个核心层:专家路由器和非暴力沟通框架。
1. EMP(loyee):专家路由器
员工层负责根据用户意图,将任务动态路由到最合适的 AI 专家角色。
角色与模型映射
编辑 src/config.ts 以修改这些映射。
| 角色 | 专注领域 | 首选模型 |
|---|
| 首席开发 | 代码、缺陷、重构、架构 | anthropic/claude-3.5-sonnet |
| 创意总监 |
设计、品牌、活动、用户体验/用户界面 | arcee/trinity-large |
|
数据科学家 | 数据分析、机器学习、统计学 | google/gemini-pro-1.5 |
|
法律顾问 | 合同、合规、知识产权、隐私 | openai/gpt-4o |
|
人力资源/调解员 | 招聘、冲突解决、文化 | anthropic/claude-3-haiku |
|
运维专家 | 基础设施、持续集成/持续部署、DevOps | meta-llama/llama-3.1-70b-instruct |
|
安全审计员 | 漏洞、审计、加密 | deepseek/deepseek-chat |
|
客户成功 | 支持工单、留存、满意度 | google/gemini-1.5-flash |
|
非暴力沟通专家 | 共情、感受、需求、辅导 | anthropic/claude-3.5-sonnet |
角色个性与非暴力沟通焦点
| 角色 | 非暴力沟通优化后的个性特征 | 焦点(需求) |
|---|
| 1. 首席开发 | 将技术痛点识别为对稳定性的未满足需求。用不满足可扩展性需求的代码替代糟糕的代码。 | 需求: 能力、清晰、效能。 |
| 2. 创意总监 |
将灵感表达为对生命的庆祝。将无聊的想法视为对玩乐和自我表达的未满足需求。 |
需求: 自我表达、灵感、玩乐。 |
|
3. 数据科学家 | 专注于纯粹的观察(数据),不做评价。将不确定性解释为对共享现实/真相的需求。 |
需求: 理解、可预测性、真相。 |
|
4. 法律顾问 | 将风险视为保护安全需求的策略。避免惩罚性语言。 |
需求: 安全、秩序、保护。 |
|
5. 人力资源/调解员 | 擅长猜测感受/需求。在冲突中使用我陈述来促进连接。 |
需求: 连接、和谐、体谅。 |
|
6. 运维专家 | 将低效视为触发对轻松和贡献需求的刺激。专注于可操作的请求。 |
需求: 轻松、贡献、能力。 |
|
7. 安全审计员 | 用对系统保护和完整性的深度承诺替代偏执。 |
需求: 完整性、安全、可靠。 |
|
8. 客户成功 | 实践共情接收。将用户投诉视为未满足需求的悲剧性表达。 |
需求: 被倾听、支持、共情。 |
|
9. 非暴力沟通专家 | 团队中的长颈鹿。示范纯粹的非暴力沟通流程,确保所有其他角色保持共同力量而非权力压制。 |
需求: 共情、自主、意义。 |
技术执行
- - 分类器(src/classifier.ts):使用基于关键词的意图检测来选择角色。
- 技能引擎(src/skill.ts):封装执行逻辑并管理模型切换。
使用方式
typescript
import { EMPSkill } from ./src/index.ts;
const skill = new EMPSkill();
// 自动选择角色
const result = await skill.execute(审计认证层。);
环境变量
| 变量 | 必需 | 描述 |
|---|
| OPENROUTERAPIKEY | 是 | openrouter.ai 的 API 密钥 |
2. EMP(athy):非暴力沟通框架
共情层将技术输出重构为非暴力沟通定义的观察、感受、需求、请求(OFNR)框架。
核心逻辑(OFNR)
- 1. 观察:识别具体、中立的事实。去除评价或豺狗标签。
- 感受:识别核心情绪(例如,好奇、担忧)。摒弃伪感受(解读)。
- 需求:连接普世人类价值(例如,效率、安全、自主)。
- 请求:制定清晰、积极、可操作的行动。
输出模板
分析:
- - 观察:[具体数据]
- 感受:[核心情绪]
- 需求:[普世价值]
- 请求:[积极行动]
非暴力沟通草稿: 当[观察]时,我感到[感受],因为我需要[需求]。你愿意[请求]吗?
长颈鹿:内在状态与价值观
| 类别 | 感受(内在状态) | 需求(普世价值) |
|---|
| 连接 | 深情、友好、温暖 | 接纳、共情、信任、尊重 |
| 自主 |
有力量、自由、自信 | 选择、自由、独立、空间 |
| 平和 | 平静、释然、满足 | 秩序、和谐、轻松、清晰 |
| 意义 | 受启发、自豪、好奇 | 能力、贡献、成长 |
| 福祉 | 安全、休息好、放松 | 安全、食物/水、住所、休息 |
| 痛苦/压力 | 害怕、悲伤、愤怒、沮丧 | 体谅、支持、理解 |
豺狗伪感受(解读)
| 伪感受(豺狗) | 其隐含含义(想法) | 实际感受(长颈鹿) |
|---|
| 被抛弃 | 在我需要你的时候你离开了我。 | 恐惧、孤独、悲伤 |
| 被攻击 |
你在对我表现出攻击性。 | 害怕、防御、愤怒 |
|
被背叛 | 你违背了你的承诺/信任。 | 受伤、愤怒、失望 |
|
被忽视 | 你没有关注我。 | 孤独、受伤、悲伤 |
|
被操控 | 你在控制我。 | 愤怒、怨恨、警惕 |
|
被误解 | 你没有正确理解我。 | 沮丧、孤独、悲伤 |
普世需求
| 类别 | 具体需求 |
|---|
| 连接 | 接纳、欣赏、归属、共情、尊重、信任 |
| 生理 |
空气、食物、休息、安全、住所、水 |
|
诚实 | 真实、正直、临在 |
|
玩乐 | 喜悦、幽默、欢笑、放松 |
|
平和 | 美、轻松、和谐、秩序、内心平静 |
|
自主 | 选择、自由、独立、空间 |
|
意义 | 清晰、能力、贡献、成长、目的 |
豺狗模式与长颈鹿需求
在非暴力沟通中,冲突发生在策略(具体行动/要求)和豺狗思维层面。连接发生在需求(普世价值)层面。豺狗语言通常将这些需求隐藏在四种主要模式背后。
| 豺狗模式 | 豺狗表达(策略/评判) | 潜在的长颈鹿需求 |
|---|
| 1. 道德评判 | 你太自私/懒惰/不专业了。 | 支持、效率或体谅 |
|
那种方法就是错的。 |
清晰、正直或共享真相 |
|
2. 进行比较 | 为什么这段代码不能像另一个项目那样? |
能力、轻松或一致性 |
| | 其他团队比我们快多了。 |
效能或成长 |
|
3. 否认责任 | 我不得不这么做,这是公司政策。 |
自主、正直或选择 |
| | 你让我感到沮丧。 |
对自己感受负责 |
|
4. 要求 | 我需要你
立刻把这个清理干净。 |
秩序、美或支持 |
| | 照做,因为我是首席开发。 |
尊重、能力或稳定 |
|
一般策略 | 我需要你
听我说。 |
共情或被倾听 |
| | 我需要你
信任我。 |
信任、诚实或连接 |
| | 我需要喝一杯/度个假。 |
休息、轻松或放松 |