EMP

EMP Skill for OpenClaw – empathetic, role-based task routing

Security Scan

The skill's code and SKILL.md largely match the described purpose (an OpenRouter-backed, empathy-aware role router), but there are metadata inconsistencies and installation/persistence actions (copying SOUL.md / SKILL.md into ~/.openclaw) that the registry listing did not advertise — you should review installation steps and the OpenRouter usage before installing.

Purpose & Capability

The name/description (empathetic role-based routing) align with the included source: classifier, router, NVC wrapper and an OpenRouter HTTP client. Requested runtime artifact 'node' and the code's use of OPENROUTER_API_KEY are consistent with the stated purpose. Minor inconsistency: the registry metadata reported 'Required env vars: none' but SKILL.md and the code require OPENROUTER_API_KEY.

Instruction Scope

SKILL.md and package.json include instructions that copy SOUL.md and SKILL.md into ~/.openclaw/workspace (persistent write to the user's home workspace). The runtime instructions and code only access the OpenRouter API (via OPENROUTER_API_KEY) and do not read other system secrets, which is fine, but the implicit install step that writes files to the user's workspace is scope‑expanding and not declared in the registry.

Install Mechanism

The registry listed 'No install spec — instruction-only', yet SKILL.md metadata and package.json provide install actions (npm module '.' and a cp shell command). There are no downloads from external URLs and dependencies are empty, so code installation risk is low; however the presence of an undocumented shell cp step that will write files to ~/.openclaw is a mismatch to the registry claim and worth reviewing before running any install commands.

Credentials

The skill requires a single API key (OPENROUTER_API_KEY) which is appropriate for calling OpenRouter. However, the registry listing omitted declaring required env vars while SKILL.md and the code require that key — this mismatch could cause surprise (silent failures or unintended attempts to call OpenRouter). No other credentials or unrelated secrets are requested.

Persistence & Privilege

The skill is not set to always:true and does not modify other skills. It does, however, include install steps that copy files into ~/.openclaw/workspace (SOUL.md and SKILL.md), producing persistent content in the user's OpenClaw workspace. This is a legitimate behavior for a skill but should be disclosed and confirmed before installation.

What to consider before installing

Before installing: (1) Be aware the skill will send your prompts to openrouter.ai using OPENROUTER_API_KEY — only use a dedicated API key and understand data/retention and billing implications. (2) The registry metadata omitted the required OPENROUTER_API_KEY and install instructions that copy SOUL.md/SKILL.md into ~/.openclaw/workspace; verify and permit these file writes (or inspect the files first). (3) Review the package.json install scripts and SKILL.md metadata; don't run any install/copy commands you don't trust — consider installing in a sandbox or container. (4) If you need higher assurance, audit the included source locally (it is small and readable) and test without granting elevated credentials. If you want, I can produce a short checklist of commands to safely inspect and sandbox the skill before running any install steps.

🦒 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	anthropic/claude-3.5-sonnet
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

import { EMPSkill } from "./src/index.ts";
const skill = new EMPSkill();

// Auto-selected role
const result = await skill.execute("Audit the auth layer.");

Environment Variables

Variable	Required	Description
OPENROUTER_API_KEY	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.
2. Feel: Identify core emotions (e.g., curious, concerned). Discard "pseudo-feelings" (interpretations).
3. Need: Connect to universal human values (e.g., Efficiency, Safety, Autonomy).
4. 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

---