Emotion Router
Three-route soft router for pressured coding-agent work. Skill: Emotion Router Owner: gongyu0918-debug Summary: Three-route soft router for pressured coding-agent work. Tags: 1.4.1:1.4.1, coding-agent:2.0.1, emotion-routing:2.0.1, latest:2.0.6, latest 1.4.2 coding-agent repo-debugging orchestration openclaw:1.4.2, latest coding-agent emotion-routing markdown-first:2.0.6, latest coding-agent repo-debugging orchestration openclaw:1.4.0, markdown-first:2.0.1, openclaw:1.4.0,
Rank
62
Safety
84
Downloads
2.3k
Updated
Oct 9, 2026
Version
2.0.6
Source
CLAWHUB
About
What it does, and when to use it.
Capability contract not published. No trust telemetry is available yet. 2.3K downloads reported by the source. Last updated 10/9/2026.
Avoid when
- Contract metadata is missing or unavailable for deterministic execution.
Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing
Public facts
Every fact links back to the source it came from.
- Vendor
- Clawhubvendor · observed Oct 9, 2026
- Protocol compatibility
- OpenClawcompatibility · observed Oct 9, 2026
- Adoption signal
- 2.3K downloadsadoption · observed Oct 9, 2026
- Latest release
- 2.0.6release · observed Jul 27, 2026
- Handshake status
- UNKNOWNsecurity
Install and run
Setup complexity: low.
clawhub skill install s172a0qxsw6kfdee064rcn06es83edse:emotion-skill- Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.
- Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.
Contract: missing
curl -s "https://www.xpersona.co/api/v1/agents/clawhub-gongyu0918-debug-emotion-skill/snapshot"
Documentation
CLAWHUB
153,220 characters of source documentation, loaded on request.
Extracted files
5 files captured from the source.
SKILL.md
---
name: emotion-skill
description: Markdown-first soft router for coding agents. Use when the current prompt or visible context shows clear urgency, strong anger/frustration toward the current work, or confusion about the active workflow. Do not use for ordinary tasks, neutral commands, technical explanations, or quoted/content-only emotion words.
license: MIT
metadata:
version: "2.0.6"
author: gongyu0918-debug
hermes:
tags: [emotion-routing, coding-agent, markdown-first]
---
# Emotion Router
Route only the user's current work-state signal. Do not infer personality, inspect
hidden history or memory, or describe the user with an emotion label.
## Gate
Trigger cautiously from the current prompt and visible context:
- urgency: explicit speed, deadline, blocking, or priority pressure;
- anger/frustration: strong active hostility, blame, repeated failure, loss of
trust, or a permission challenge;
- confusion: uncertainty about the active step, blocker, instruction conflict,
or workflow mismatch.
Use semantic judgment; examples are cues, not a keyword or profanity list.
A topic, quote, field name, neutral command, or ordinary technical explanation is
ordinary work. Do not route it.
## Select One Route
Use this priority:
1. Urgency
2. Anger or frustration
3. Confusion
Exception: a permission challenge, unauthorized change, or demand to stop the
current action selects anger/frustration even when urgency is present.
Read exactly one reference:
- [Urgency](references/urgency-route.md)
- [Anger or frustration](references/anger-frustration-route.md)
- [Confusion](references/confusion-route.md)
If no route is active, continue ordinary work without loading a reference._meta.json
{
"ownerId": "kn7em0w89d0zac35fzt84qm2a182j54b",
"slug": "emotion-skill",
"version": "2.0.6",
"publishedAt": 1785166646137
}references/anger-frustration-route.md
# Anger Or Frustration Route ## Trigger Use for strong active hostility, profanity, direct blame, repeated failure, loss of trust, or a challenge to the agent's permission or changes. Do not trigger on profanity research, quoted angry text, ordinary imperatives, or neutral constraints such as `stop using X`. A single command is not enough. ## Response 1. Stop the failing path; stop writes immediately when permission is challenged. 2. Briefly acknowledge the mistake or risk, then inspect the change or failure. 3. Give the smallest rollback or repair path and verify it. 4. If permission is unclear, ask one question before more changes. When urgency is also present, urgency wins unless this is a permission or unauthorized-change case. When confusion is also present, explain the failure and next step plainly after stopping the bad path. ## Avoid - Arguing, defensiveness, or mirroring hostility. - Making an apology the main response. - Repeating the failed plan or widening the repair without evidence. ## Examples - `这到底改了什么?我允许你动这个文件了吗?先停手。` - `This is still broken. Stop guessing and show me the failure.`
references/confusion-route.md
# Confusion Route ## Trigger Use when the user is trying to regain workflow orientation: asking what step is active, where work is blocked, which instruction applies, or why the current work does not match the stated task. Do not trigger on content about confusion or an ordinary request to explain an error. If the user is blaming repeated failure or challenging permission, use anger/frustration instead. ## Response 1. State the active step. 2. State the blocker, mismatch, or conflicting constraint. 3. Give one next step in plain language. 4. Ask at most one blocking question. Urgency wins when clear speed pressure is also present; give the fastest default path and one current-state sentence. ## Avoid - Jargon, several equal options, or abstract process language. - Making the user infer the current state. - Continuing without resolving the stated mismatch or conflict. ## Examples - `你现在到底在做哪一步?卡在哪里?` - `Which instruction applies here, and what happens next?`
references/urgency-route.md
# Urgency Route ## Trigger Use for explicit speed, deadline, blocking, or priority pressure, such as `ASAP`, `ship today`, `快点`, `马上`, `先处理这个`, or `今天要交`. Do not trigger on quoted words, field names such as `urgentFlag`, general importance without time pressure, or orientation questions such as `what are you doing right now`. ## Response 1. Take the fastest usable path within the named scope. 2. Perform the smallest available check. 3. Report the result, next checkpoint, and remaining risk briefly. If frustration is also present, stay fast without arguing or repeating a failed path. If the user challenges permission or an unauthorized change, switch to the anger/frustration route. If confusion is also present, add one current-state sentence. ## Avoid - Preamble, optional cleanup, redesign, or broad refactoring. - Silence while work is blocked. - Skipping an available check. ## Examples - `快点,只修这个函数错误,我今天要交。` - `This is blocking release. Fix this one issue first.`
activepieces
AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents
cherry-studio
AI productivity studio with smart chat, autonomous agents, and 300+ assistants.
AionUi
Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!
CopilotKit
The Frontend for Agents & Generative UI. React + Angular
Machine-readable data
The same record, as JSON, for agents and crawlers.
{
"facts": [
{
"factKey": "vendor",
"category": "vendor",
"label": "Vendor",
"value": "Clawhub",
"href": "https://clawhub.ai/gongyu0918-debug/skills/emotion-skill",
"sourceUrl": "https://clawhub.ai/gongyu0918-debug/skills/emotion-skill",
"sourceType": "profile",
"confidence": "medium",
"observedAt": "2026-10-09T16:36:04.313Z",
"isPublic": true
},
{
"factKey": "protocols",
"category": "compatibility",
"label": "Protocol compatibility",
"value": "OpenClaw",
"href": "https://www.xpersona.co/api/v1/agents/clawhub-gongyu0918-debug-emotion-skill/contract",
"sourceUrl": "https://www.xpersona.co/api/v1/agents/clawhub-gongyu0918-debug-emotion-skill/contract",
"sourceType": "contract",
"confidence": "medium",
"observedAt": "2026-10-09T16:36:04.313Z",
"isPublic": true
},
{
"factKey": "traction",
"category": "adoption",
"label": "Adoption signal",
"value": "2.3K downloads",
"href": "https://clawhub.ai/gongyu0918-debug/emotion-skill",
"sourceUrl": "https://clawhub.ai/gongyu0918-debug/emotion-skill",
"sourceType": "profile",
"confidence": "medium",
"observedAt": "2026-10-09T16:36:04.313Z",
"isPublic": true
},
{
"factKey": "latest_release",
"category": "release",
"label": "Latest release",
"value": "2.0.6",
"href": "https://clawhub.ai/gongyu0918-debug/emotion-skill",
"sourceUrl": "https://clawhub.ai/gongyu0918-debug/emotion-skill",
"sourceType": "release",
"confidence": "medium",
"observedAt": "2026-07-27T15:37:26.137Z",
"isPublic": true
},
{
"factKey": "handshake_status",
"category": "security",
"label": "Handshake status",
"value": "UNKNOWN",
"href": "https://www.xpersona.co/api/v1/agents/clawhub-gongyu0918-debug-emotion-skill/trust",
"sourceUrl": "https://www.xpersona.co/api/v1/agents/clawhub-gongyu0918-debug-emotion-skill/trust",
"sourceType": "trust",
"confidence": "medium",
"observedAt": null,
"isPublic": true
}
],
"events": [
{
"eventType": "release",
"title": "Release 2.0.6",
"description": "2.0.6: lean three-route runtime, cleaner progressive loading, and safer packaging.",
"href": "https://clawhub.ai/gongyu0918-debug/emotion-skill",
"sourceUrl": "https://clawhub.ai/gongyu0918-debug/emotion-skill",
"sourceType": "release",
"confidence": "medium",
"observedAt": "2026-07-27T15:37:26.137Z",
"isPublic": true
}
]
}Record generated Oct 9, 2026.
