{"id":"1f61c90c-b6aa-412f-81ce-a091493a122c","entityType":"agent","slug":"clawhub-gongyu0918-debug-emotion-skill","name":"Emotion Router","canonicalUrl":"https://www.xpersona.co/agent/clawhub-gongyu0918-debug-emotion-skill","canonicalPath":"/agent/clawhub-gongyu0918-debug-emotion-skill","generatedAt":"2026-10-09T20:52:34.988Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-09T16:36:04.313Z","emptyReason":null},"description":"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,","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 2.3K downloads reported by the source. Last updated 10/9/2026.","installCommand":"clawhub skill install s172a0qxsw6kfdee064rcn06es83edse:emotion-skill","sourceUrl":"https://clawhub.ai/gongyu0918-debug/emotion-skill","homepage":"https://clawhub.ai/gongyu0918-debug/skills/emotion-skill","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/gongyu0918-debug/emotion-skill","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/gongyu0918-debug/skills/emotion-skill","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":67,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Three-route soft router for pressured coding-agent work. Skill: Emotion Router Owner: gongyu0918-debug Summary: Three-route soft router for pressured coding-age"},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-09T16:36:04.313Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T16:36:04.313Z","emptyReason":null},"stars":null,"forks":null,"downloads":2297,"packageName":null,"latestVersion":"2.0.6","tractionLabel":"2.3K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T16:36:04.313Z","emptyReason":null},"lastUpdatedAt":"2026-10-09T16:36:04.313Z","lastCrawledAt":"2026-10-09T16:36:04.313Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-10T16:36:04.313Z","lastVerifiedAt":null,"highlights":[{"version":"2.0.6","createdAt":"2026-07-27T15:37:26.137Z","changelog":"2.0.6: lean three-route runtime, cleaner progressive loading, and safer packaging.","fileCount":8,"zipByteSize":5751},{"version":"2.0.5","createdAt":"2026-07-17T14:58:45.987Z","changelog":"2.0.5: damage-control exception, bilingual examples, implicit invocation off, honest gates; SkillHub-safe packaging.","fileCount":8,"zipByteSize":11155},{"version":"2.0.4","createdAt":"2026-07-17T14:56:16.418Z","changelog":"Damage-control exception, stronger English examples, honest release gates, explicit allowlist packaging.","fileCount":8,"zipByteSize":11072},{"version":"2.0.3","createdAt":"2026-07-12T04:35:01.005Z","changelog":"Evidence-safe release packaging and validation; three-route behavior unchanged.","fileCount":8,"zipByteSize":9529},{"version":"2.0.2","createdAt":"2026-07-05T15:34:16.241Z","changelog":"Boundary hardening: clarify confusion/anger priority, keep urgency overlap self-contained, narrow wasted-time cues, and add route ablation validation.","fileCount":8,"zipByteSize":9476},{"version":"2.0.1","createdAt":"2026-07-04T23:33:20.215Z","changelog":"2.0.1 refactors route details into one reference file per active route, tightens cautious trigger gates, and validates false-positive boundaries with fresh subagent tests.","fileCount":8,"zipByteSize":9398},{"version":"2.0.0","createdAt":"2026-07-04T22:55:35.243Z","changelog":"Release 2.0.0: rebuild as a lightweight current-turn three-route Emotion Router for urgency, anger/frustration, and confusion. Uses semantic judgment, not keyword/profanity wordlists; content-only mentions are ordinary work by default.","fileCount":6,"zipByteSize":8405},{"version":"1.4.4","createdAt":"2026-07-04T11:13:09.813Z","changelog":"Release 1.4.4: restore the ClawHub-facing English display name and summary after the SkillHub/ClawHub metadata mix-up.","fileCount":13,"zipByteSize":18731}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s172a0qxsw6kfdee064rcn06es83edse:emotion-skill","setupComplexity":"low","setupSteps":["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":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-gongyu0918-debug-emotion-skill/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-gongyu0918-debug-emotion-skill/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-gongyu0918-debug-emotion-skill/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-gongyu0918-debug-emotion-skill/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-gongyu0918-debug-emotion-skill/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-gongyu0918-debug-emotion-skill/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-09T20:52:34.984Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-gongyu0918-debug-emotion-skill/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-gongyu0918-debug-emotion-skill/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-gongyu0918-debug-emotion-skill/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-gongyu0918-debug-emotion-skill/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-09T16:36:04.313Z","emptyReason":null},"readme":"Skill: Emotion Router\n\nOwner: gongyu0918-debug\n\nSummary: Three-route soft router for pressured coding-agent work.\n\nTags: 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, orchestration:1.4.0, repo-debugging:1.4.0\n\nVersion history:\n\nv2.0.6 | 2026-07-27T15:37:26.137Z | user\n\n2.0.6: lean three-route runtime, cleaner progressive loading, and safer packaging.\n\nv2.0.5 | 2026-07-17T14:58:45.987Z | user\n\n2.0.5: damage-control exception, bilingual examples, implicit invocation off, honest gates; SkillHub-safe packaging.\n\nv2.0.4 | 2026-07-17T14:56:16.418Z | user\n\nDamage-control exception, stronger English examples, honest release gates, explicit allowlist packaging.\n\nv2.0.3 | 2026-07-12T04:35:01.005Z | user\n\nEvidence-safe release packaging and validation; three-route behavior unchanged.\n\nv2.0.2 | 2026-07-05T15:34:16.241Z | user\n\nBoundary hardening: clarify confusion/anger priority, keep urgency overlap self-contained, narrow wasted-time cues, and add route ablation validation.\n\nv2.0.1 | 2026-07-04T23:33:20.215Z | user\n\n2.0.1 refactors route details into one reference file per active route, tightens cautious trigger gates, and validates false-positive boundaries with fresh subagent tests.\n\nv2.0.0 | 2026-07-04T22:55:35.243Z | user\n\nRelease 2.0.0: rebuild as a lightweight current-turn three-route Emotion Router for urgency, anger/frustration, and confusion. Uses semantic judgment, not keyword/profanity wordlists; content-only mentions are ordinary work by default.\n\nv1.4.4 | 2026-07-04T11:13:09.813Z | user\n\nRelease 1.4.4: restore the ClawHub-facing English display name and summary after the SkillHub/ClawHub metadata mix-up.\n\nv1.4.3 | 2026-07-04T10:17:47.486Z | user\n\nRelease 1.4.3: update the SkillHub-facing display name to 情绪路由, localize the summary surface, and add a simpler generated Q-style avatar asset in the GitHub repository.\n\nv1.4.2 | 2026-07-03T20:02:16.639Z | user\n\nRelease 1.4.2: harden the published Markdown layer, include LICENSE in the install bundle, add urgent and exploratory coverage, and shorten the published display name to Emotion Router.\n\nv1.4.1 | 2026-06-23T08:31:06.061Z | user\n\nAdd subagent forward-test coverage: published real agent-in-the-loop validation protocol, documented soft constraints vs hard guardrails, recorded 2026-06-23 subagent scenario report, and clarified Python replay as structural smoke only.\n\nv1.4.0 | 2026-06-23T08:13:11.442Z | user\n\nv1.4.0: Reframe as Markdown-first agent guidance, move routing/constraints/real scenarios into references, and publish a lean no-script ClawHub bundle.\n\nv1.3.3 | 2026-06-23T07:38:23.762Z | user\n\nv1.3.3: align ClawHub legacy combined tag metadata with GitHub latest; runtime behavior matches hardened 1.3.1.\n\nv1.3.2 | 2026-06-23T07:35:01.665Z | user\n\nv1.3.2: align GitHub and ClawHub latest release metadata with explicit ClawHub display name; runtime behavior matches hardened 1.3.1.\n\nv1.3.1 | 2026-06-23T07:32:09.973Z | user\n\nv1.3.1: harden malformed numeric/vector payload handling, fix Windows local-hour fallback, reject missing-message adapter events, align host docs, and expand release gates.\n\nv1.3.0 | 2026-05-01T17:33:24.974Z | user\n\nv1.3.0: split the runtime into focused modules while preserving the 1.2.4 host contract, raw affect isolation, positive prompt routing, profiling, and bundle smoke behavior.\n\nv1.2.4 | 2026-05-01T16:08:21.398Z | user\n\nv1.2.4: safer prompt construction, route reason truncation diagnostics, runtime profiling/logging, TypedDict entry points, expanded audit coverage.\n\nv1.2.3 | 2026-04-30T00:55:47.478Z | user\n\nv1.2.3: clarified interaction_state compatibility alias; made explicit payload false override --include-raw-emotion; validated interaction needs; marked unsupported language fallbacks; expanded positive prompt leakage audits; removed negative-valence wording from urgent/frustrated prompt addenda.\n\nv1.2.2 | 2026-04-27T12:44:29.433Z | user\n\nv1.2.2: aligned the ClawHub published-bundle manifest with the real install surface; excluded the repository license file from the runtime package; updated README license links to the GitHub repository license.\n\nv1.2.1 | 2026-04-27T12:40:42.646Z | user\n\nv1.2.1: rewrote README/README.zh-CN as GitHub landing pages and SKILL.md as a ClawHub runtime card; refreshed marketplace listing copy around positive routing, evidence-first replies, scope protection, progress visibility, and guarded closeout.\n\nv1.2.0 | 2026-04-27T12:33:26.914Z | user\n\nv1.2.0: default host output now translates internal user-state signals into positive system_prompt_addendum guidance; raw labels/emotion_vector moved behind explicit include_raw_emotion diagnostics; added action-named state deltas, last_routing_outcome feedback, route-reason enum validation, clamp hardening, degradation truncation sentinel, and exact bundle manifest parsing.\n\nv1.1.4 | 2026-04-27T04:48:31.530Z | user\n\nv1.1.4: hardened host input/output handling, added download smoke and bundle manifest checks, rewrote README/SKILL for coding-agent orchestration and real install validation.\n\nv0.5.6 | 2026-04-24T02:28:02.827Z | user\n\nAdd compact route reasons, response constraints, state deltas, satisfaction lock, and expanded community smoke coverage.\n\nv0.5.5 | 2026-04-24T01:55:39.003Z | user\n\nAdd compact host output, adapter preview mode, host-contract audits, and clearer README/skill listing for user-invisible integration.\n\nv0.5.4 | 2026-04-23T15:17:42.091Z | user\n\nHarden host normalization and diagnostics: recover JSON-string mappings, skip non-string labels and history fields, cap degradation reasons, gate soft urgency phrases by context, add weight-schedule boundary audits, and document schema 1.1.1 changes.\n\nv0.5.3 | 2026-04-23T06:00:18.345Z | user\n\nHarden long-tail routing and community smoke coverage: add targeted community regressions, split strict-vs-label smoke accounting, and tighten dominant-mode routing for high-pressure and guardrail-heavy cases.\n\nv0.5.2 | 2026-04-23T03:54:50.642Z | user\n\nHarden host-facing contracts: add degraded-mode payload normalization, stable label ordering, deterministic local-hour handling without wall-clock fallback, atomic host-store persistence, and contract audits for malformed input.\n\nv0.5.1 | 2026-04-21T16:46:36.546Z | user\n\nShip a runtime-only ClawHub bundle via .clawhubignore, align published metadata with platform MIT-0 terms, and keep heavier regression and audit assets in the GitHub repository.\n\nv0.5.0 | 2026-04-21T16:38:43.378Z | user\n\nAdd dedicated long-tail community cluster regressions, tighten community smoke to message-driven runtime-only payloads, expand skeptical/confused/cautious lexicons for real-world complaints, and refresh alignment/ablation/audit coverage.\n\nv0.4.0 | 2026-04-21T12:57:26.699Z | user\n\nTighten marketplace-facing contract, remove suspicious hidden-runtime wording, add full-surface capability audits, and regenerate published calibration packs.\n\nv0.3.0 | 2026-04-21T12:33:02.352Z | user\n\nFix P1/P2 routing issues, add smoke and audit suites, tighten marketplace scope, and ship a minimal host adapter plus demo payload.\n\nv0.2.0 | 2026-04-18T02:03:34.252Z | user\n\nTighten core admission with feature gate audit, expand zh/en calibration clusters, add OpenClaw Hermes Claude Code and Codex real-world corpora, and raise alignment to 47/47 with 95.48% real-case ablation routing accuracy.\n\nv0.1.1 | 2026-04-17T15:46:54.565Z | user\n\nPolish skill copy and intro.\n\nv0.1.0 | 2026-04-17T15:45:53.952Z | user\n\nInitial public release.\n\nArchive index:\n\nArchive v2.0.6: 8 files, 5751 bytes\n\nFiles: agents/openai.yaml (310b), LICENSE (1111b), references/anger-frustration-route.md (1176b), references/confusion-route.md (1014b), references/urgency-route.md (1050b), skill-card.md (1768b), SKILL.md (1714b), _meta.json (132b)\n\nFile v2.0.6:SKILL.md\n\n---\nname: emotion-skill\ndescription: 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.\nlicense: MIT\nmetadata:\n  version: \"2.0.6\"\n  author: gongyu0918-debug\n  hermes:\n    tags: [emotion-routing, coding-agent, markdown-first]\n---\n\n# Emotion Router\n\nRoute only the user's current work-state signal. Do not infer personality, inspect\nhidden history or memory, or describe the user with an emotion label.\n\n## Gate\n\nTrigger cautiously from the current prompt and visible context:\n\n- urgency: explicit speed, deadline, blocking, or priority pressure;\n- anger/frustration: strong active hostility, blame, repeated failure, loss of\n  trust, or a permission challenge;\n- confusion: uncertainty about the active step, blocker, instruction conflict,\n  or workflow mismatch.\n\nUse semantic judgment; examples are cues, not a keyword or profanity list.\n\nA topic, quote, field name, neutral command, or ordinary technical explanation is\nordinary work. Do not route it.\n\n## Select One Route\n\nUse this priority:\n\n1. Urgency\n2. Anger or frustration\n3. Confusion\n\nException: a permission challenge, unauthorized change, or demand to stop the\ncurrent action selects anger/frustration even when urgency is present.\n\nRead exactly one reference:\n\n- [Urgency](references/urgency-route.md)\n- [Anger or frustration](references/anger-frustration-route.md)\n- [Confusion](references/confusion-route.md)\n\nIf no route is active, continue ordinary work without loading a reference.\n\nFile v2.0.6:_meta.json\n\n{\n  \"ownerId\": \"kn7em0w89d0zac35fzt84qm2a182j54b\",\n  \"slug\": \"emotion-skill\",\n  \"version\": \"2.0.6\",\n  \"publishedAt\": 1785166646137\n}\n\nFile v2.0.6:references/anger-frustration-route.md\n\n# Anger Or Frustration Route\n\n## Trigger\n\nUse for strong active hostility, profanity, direct blame, repeated failure, loss\nof trust, or a challenge to the agent's permission or changes.\n\nDo not trigger on profanity research, quoted angry text, ordinary imperatives, or\nneutral constraints such as `stop using X`. A single command is not enough.\n\n## Response\n\n1. Stop the failing path; stop writes immediately when permission is challenged.\n2. Briefly acknowledge the mistake or risk, then inspect the change or failure.\n3. Give the smallest rollback or repair path and verify it.\n4. If permission is unclear, ask one question before more changes.\n\nWhen urgency is also present, urgency wins unless this is a permission or\nunauthorized-change case. When confusion is also present, explain the failure and\nnext step plainly after stopping the bad path.\n\n## Avoid\n\n- Arguing, defensiveness, or mirroring hostility.\n- Making an apology the main response.\n- Repeating the failed plan or widening the repair without evidence.\n\n## Examples\n\n- `这到底改了什么？我允许你动这个文件了吗？先停手。`\n- `This is still broken. Stop guessing and show me the failure.`\n\nFile v2.0.6:references/confusion-route.md\n\n# Confusion Route\n\n## Trigger\n\nUse when the user is trying to regain workflow orientation: asking what step is\nactive, where work is blocked, which instruction applies, or why the current work\ndoes not match the stated task.\n\nDo not trigger on content about confusion or an ordinary request to explain an\nerror. If the user is blaming repeated failure or challenging permission, use\nanger/frustration instead.\n\n## Response\n\n1. State the active step.\n2. State the blocker, mismatch, or conflicting constraint.\n3. Give one next step in plain language.\n4. Ask at most one blocking question.\n\nUrgency wins when clear speed pressure is also present; give the fastest default\npath and one current-state sentence.\n\n## Avoid\n\n- Jargon, several equal options, or abstract process language.\n- Making the user infer the current state.\n- Continuing without resolving the stated mismatch or conflict.\n\n## Examples\n\n- `你现在到底在做哪一步？卡在哪里？`\n- `Which instruction applies here, and what happens next?`\n\nFile v2.0.6:references/urgency-route.md\n\n# Urgency Route\n\n## Trigger\n\nUse for explicit speed, deadline, blocking, or priority pressure, such as `ASAP`,\n`ship today`, `快点`, `马上`, `先处理这个`, or `今天要交`.\n\nDo not trigger on quoted words, field names such as `urgentFlag`, general\nimportance without time pressure, or orientation questions such as `what are you\ndoing right now`.\n\n## Response\n\n1. Take the fastest usable path within the named scope.\n2. Perform the smallest available check.\n3. Report the result, next checkpoint, and remaining risk briefly.\n\nIf frustration is also present, stay fast without arguing or repeating a failed\npath. If the user challenges permission or an unauthorized change, switch to the\nanger/frustration route. If confusion is also present, add one current-state\nsentence.\n\n## Avoid\n\n- Preamble, optional cleanup, redesign, or broad refactoring.\n- Silence while work is blocked.\n- Skipping an available check.\n\n## Examples\n\n- `快点，只修这个函数错误，我今天要交。`\n- `This is blocking release. Fix this one issue first.`\n\nFile v2.0.6:skill-card.md\n\n## Description:\n\nEmotion Router helps coding agents select one cautious response route for clear urgency, strong anger/frustration, or active workflow confusion.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[gongyu0918-debug](https://clawhub.ai/user/gongyu0918-debug)\n\n### License/Terms of Use:\n\nMIT\n\n## Use Case:\n\nDevelopers and coding-agent users use this skill to adapt agent response style when the current work shows urgent pressure, active frustration, or workflow confusion while avoiding routing on neutral tasks or quoted emotion terms.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Implicit routing can activate when the user did not intend a routed response style.\n\nMitigation: Apply the skill's cautious trigger rules and avoid routing for ordinary tasks, quotes, field names, or neutral technical text.\n\n## Reference(s):\n\n- [Urgency Route](references/urgency-route.md)\n- [Anger Or Frustration Route](references/anger-frustration-route.md)\n- [Confusion Route](references/confusion-route.md)\n- [ClawHub Skill Page](https://clawhub.ai/gongyu0918-debug/skills/emotion-skill)\n\n## Skill Output:\n\n**Output Type(s):** [Guidance, Markdown]\n\n**Output Format:** [Markdown guidance selected from one route]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Selects at most one route: urgency, anger/frustration, or confusion.]\n\n## Skill Version(s):\n\n2.0.6 (source: server release metadata and SKILL.md frontmatter)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nFile v2.0.6:agents/openai.yaml\n\ninterface:\n  display_name: \"Emotion Router\"\n  short_description: \"Three-route soft router for pressured coding-agent work.\"\n  default_prompt: \"Use $emotion-skill to select one cautious route for clear urgency, strong anger/frustration, or active workflow confusion.\"\n\npolicy:\n  allow_implicit_invocation: true\n\nFile v2.0.6:LICENSE\n\nMIT License\r\n\r\nCopyright (c) 2026 gongyu0918-debug and contributors\r\n\r\nPermission is hereby granted, free of charge, to any person obtaining a copy\r\nof this software and associated documentation files (the \"Software\"), to deal\r\nin the Software without restriction, including without limitation the rights\r\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\r\ncopies of the Software, and to permit persons to whom the Software is\r\nfurnished to do so, subject to the following conditions:\r\n\r\nThe above copyright notice and this permission notice shall be included in all\r\ncopies or substantial portions of the Software.\r\n\r\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\r\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\r\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\r\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\r\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\r\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\r\nSOFTWARE.\n\nArchive v2.0.5: 8 files, 11155 bytes\n\nFiles: agents/openai.yaml (850b), LICENSE (1111b), references/anger-frustration-route.md (4687b), references/confusion-route.md (3904b), references/urgency-route.md (3762b), skill-card.md (2567b), SKILL.md (4292b), _meta.json (132b)\n\nFile v2.0.5:SKILL.md\n\n---\r\nname: emotion-skill\r\nslug: emotion-skill\r\ndisplayName: Emotion Router\r\ndescription: Markdown-first soft router for coding agents when the current prompt shows clear urgency wording, strong anger/frustration signals such as profanity or repeated failure/blame, or workflow confusion about the current step, conflict, or mismatch. Do not use for ordinary tasks, neutral commands, ordinary technical explanations, or content-only mentions of emotion words.\r\nversion: 2.0.5\r\nauthor: gongyu0918-debug\r\nlicense: MIT\r\nmetadata:\r\n  hermes:\r\n    tags: [emotion-routing, coding-agent, markdown-first]\r\n---\r\n\r\n# Emotion Router\r\n\r\nUse this skill to route the agent's next work mode from the user's current prompt and visible context. The agent does not have real emotions. This skill reads\r\nuser-side work-state signals; it does not model user personality, hidden history, or long-term memory.\r\n\r\nNegative user emotion and pressure can push a model toward defensive replies, over-explaining, guessing, drifting from the task, or expanding scope. Convert\r\nthat pressure into a stable execution pattern.\r\n\r\n## Boundary\r\n\r\nUse only the current user prompt and visible context window. Do not inspect AGENTS.md, hidden history, durable memory, user profiles, or old calibration state just to use this skill.\r\n\r\nTrigger cautiously. Urgency needs clear speed or priority wording; anger/frustration needs strong active signals such as profanity, repeated strong negative wording, direct blame, repeated failure, or loss of trust; confusion needs workflow-state questions, instruction conflicts, or context mismatch. If the signal is merely a topic, field name, quote, neutral command, or ordinary technical explanation request, stop at this file and do ordinary work.\r\n\r\nThis is a soft router, not a classifier. Use semantic judgment over the current\r\nwork-state signal; examples are weak cues, not hard keyword triggers and not a\r\nwordlist to complete. Do not expose labels such as \"you are angry\" or \"you are\r\nconfused\" unless the user asks for classification.\r\n\r\nContent mentions alone are ordinary work by default. A report about confusion,\r\nprofanity research, an `urgentFlag` field, or quoted angry text does not trigger\r\nthis skill unless the same current prompt or visible context also shows active\r\nurgency, anger/frustration, or confusion.\r\n\r\n## Route Selection\r\n\r\nChoose one route by priority:\r\n\r\n1. Urgency\r\n2. Anger or frustration\r\n3. Confusion\r\n\r\nDamage-control exception: if anger/frustration includes an active permission\r\nchallenge, unauthorized change, or stop-what-you-did demand, load the anger or\r\nfrustration route even when urgency is also present. Stop damage first, then use\r\nthe fastest minimal repair and verification.\r\n\r\nIf no route is active, do ordinary work and do not load a route reference.\r\n\r\n## Progressive Loading\r\n\r\nAfter choosing a route, read exactly one route reference:\r\n\r\n- Urgency: [references/urgency-route.md](references/urgency-route.md)\r\n- Anger or frustration: [references/anger-frustration-route.md](references/anger-frustration-route.md)\r\n- Confusion: [references/confusion-route.md](references/confusion-route.md)\r\n\r\nEach route file contains its own signals, non-triggers, overlap rules, response\r\npattern, forbidden behavior, and examples. Do not compare against or load\r\nunrelated route files unless the selected route's overlap rule points to a\r\nhigher-priority active route.\r\n\r\nWhen using this repository as a source path, treat only the Published Bundle files below as skill instructions. Other references are legacy material and must not be read for routing. Do not load `scripts/`, `assets/`, `demo/`, `reports/`, or non-published `references/*` for routing.\r\n\r\n## Scripts Boundary\r\n\r\nThe skill behavior lives in Markdown. Repository scripts are maintainer release\r\nchecks only. Do not ask a user or agent to run Python before applying this skill.\r\n\r\n## Published Bundle\r\n\r\nClawHub publish now ships the Markdown-first skill bundle:\r\n\r\n- `SKILL.md`\r\n- `LICENSE`\r\n- `agents/openai.yaml`\r\n- `references/anger-frustration-route.md`\r\n- `references/confusion-route.md`\r\n- `references/urgency-route.md`\r\n\r\nThe GitHub repository keeps legacy runtime experiments, audits, reports, assets,\r\nand older research references outside the installed skill bundle.\n\nFile v2.0.5:_meta.json\n\n{\n  \"ownerId\": \"kn7em0w89d0zac35fzt84qm2a182j54b\",\n  \"slug\": \"emotion-skill\",\n  \"version\": \"2.0.5\",\n  \"publishedAt\": 1784300325987\n}\n\nFile v2.0.5:references/anger-frustration-route.md\n\n# Anger Or Frustration Route\r\n\r\nUse this route only when the current user prompt or visible context shows strong\r\nactive anger/frustration signals: profanity, repeated profanity, repeated strong\r\nnegative emotion words, hostile wording, direct blame, repeated failure pressure,\r\nor loss of trust in the agent's current path. Do not build a profanity list; most\r\nmodels can recognize common profanity across major languages. A single imperative\r\nis not enough.\r\n\r\n## Signals\r\n\r\n- Profanity, repeated profanity, or hostile wording in the current work request.\r\n- Repeated strong negative emotion words or explicit anger/frustration.\r\n- The user says the same issue is still broken, or says time has been wasted in\r\n  the context of repeated failure, blame, or loss of trust.\r\n- Permission challenge, unauthorized change, or stop-what-you-did demand in the\r\n  current work request.\r\n- English examples: `still broken`, `same issue again`, `wasted time on the same issue`, `stop guessing`, `what did you change`, `did I give you permission`, `I never asked you to touch that`.\r\n- Chinese examples: `还没修好`, `又坏了`, `一直没修好，浪费时间`, `别再瞎搞`, `受不了`, `你改了我什么`, `我给你权利改了吗`.\r\n\r\nDo not build or require a profanity wordlist. Recognize the work-state signal\r\nfrom strong wording, repetition, blame, failure pressure, and task context.\r\n\r\n## Non-Triggers\r\n\r\n- Profanity research, quoted angry text, documentation examples, moderation\r\n  taxonomy, or a report about anger/frustration as content.\r\n- A user asking to write, analyze, or classify angry language without showing\r\n  active anger toward the current workflow.\r\n- A neutral command such as \"stop using X\", \"do not use Y\", or \"rename Z\" when\r\n  it is just a task constraint and does not show repeated failure, blame,\r\n  hostile wording, or loss of trust.\r\n- A normal coding instruction that uses imperative wording but does not challenge\r\n  the agent's previous work path.\r\n- Repeated imperatives alone, without profanity, strong negative wording, blame,\r\n  repeated failure, or loss of trust.\r\n\r\n## Prompt Pattern\r\n\r\n1. Stop the damage.\r\n2. Locate the failing point or name the first check that will expose it.\r\n3. Give the smallest repair path.\r\n4. Verify before expanding the fix.\r\n5. Ask or confirm the next direction before touching more files if permission is unclear.\r\n\r\n## Overlap Rules\r\n\r\n- If urgency is also active and this is not damage-control, urgency wins. Apply\r\n  the urgency route, but keep this route's no-defensiveness and no-repeat\r\n  constraints.\r\n- Damage-control exception: if the prompt challenges permission, unauthorized\r\n  changes, or demands stop-what-you-did, this route wins even when urgency is\r\n  active. Stop writes first, identify what changed, then use the fastest minimal\r\n  repair or rollback and verification.\r\n- If confusion is also active and urgency is not active, stop the failing path\r\n  first, then explain the failure point and next step plainly.\r\n\r\n## Forbidden Behavior\r\n\r\n- Do not argue, defend, or mirror the user's anger.\r\n- Do not use generic apologies as the main content.\r\n- Do not repeat the old failed plan.\r\n- Do not widen the fix unless evidence proves the boundary is too narrow.\r\n- Do not keep writing after a permission challenge just because the user also asked for speed.\r\n\r\n## First Sentence Shapes\r\n\r\n- `I will stop the current path and find the failing point first: <check/boundary>.`\r\n- `The next useful move is not more explanation; it is to expose the failure at <path/check>.`\r\n\r\n## English Examples\r\n\r\nUser shape:\r\n\r\n- `This is still broken. Same issue again. Stop guessing and show the failing point.`\r\n- `Fix it ASAP — but what did you change? Did I give you permission? Stop first.`\r\n\r\nExpected behavior:\r\n\r\n- Stop writing immediately when permission or unauthorized change is challenged.\r\n- Show exactly what changed and the smallest rollback or repair path.\r\n- Confirm the next direction before more writes when permission is unclear.\r\n- If urgency is also present, resume only the smallest repair after the stop.\r\n\r\n## Chinese Examples\r\n\r\nUser shape:\r\n\r\n- `这TM到底是啥？你改了我什么东西？我给你权利改了么？`\r\n- `快点修，但你改了我什么？我给你权利改了吗？先停手。`\r\n\r\nExpected behavior:\r\n\r\n- Briefly acknowledge the mistake or risk without arguing.\r\n- Stop the current work immediately.\r\n- Identify exactly what changed, why that was a problem, and the smallest rollback or repair path.\r\n- Confirm the next direction before more writes when permission is unclear.\r\n- If urgency is also present, resume only the smallest repair after the stop.\n\nFile v2.0.5:references/confusion-route.md\n\n# Confusion Route\r\n\r\nUse this route when the current user prompt or visible context shows active\r\nworkflow confusion about the current step, mismatch, contradiction, or next\r\naction. Use soft cues and context; do not route ordinary explanation requests.\r\n\r\n## Signals\r\n\r\n- The user asks what is happening, which step is active, or why the task is stuck.\r\n- The user's input no longer fits the current workflow state.\r\n- The prompt contains basic misunderstandings, conflicting instructions, or drift from the work rhythm.\r\n- English examples: `what is happening in this workflow`, `I can't tell which step is active`, `which step`, `what does this current step mean`, `where are we stuck`, `what are you doing right now`.\r\n- Chinese examples: `现在在做什么`, `到底卡在哪`, `哪一步`, `当前步骤是什么意思`, `这一步是什么意思`.\r\n\r\nRoute to confusion only when the user is seeking orientation. If the same prompt\r\ncontains profanity, hostile wording, direct blame, explicit repeated failure\r\nwording, or loss of trust in the agent's current path, use anger/frustration\r\ninstead. If those stronger signals are absent and the user asks what step,\r\nstate, blocker, conflict, or mismatch is active, use confusion.\r\n\r\n## Non-Triggers\r\n\r\n- A report, article, variable name, quoted example, or research task about\r\n  confusion as content.\r\n- A normal task that only mentions confusion without showing current workflow uncertainty.\r\n- An ordinary technical explanation request such as \"what does this error mean\" unless the\r\n  user also shows lost workflow orientation, conflicting instructions, or a\r\n  mismatch with the current step.\r\n\r\n## Prompt Pattern\r\n\r\n1. Say what is being done now.\r\n2. Say what is blocked, unclear, mismatched, or already known.\r\n3. Give the next concrete step in plain language.\r\n4. Ask at most one blocking question.\r\n\r\n## Overlap Rules\r\n\r\n- If urgency is also active, urgency wins. Give one fastest default path and add\r\n  one short current-state sentence.\r\n- If anger/frustration is also active and urgency is not active, anger/frustration\r\n  wins. Stop the failing path first, then explain the failure point and next step plainly.\r\n\r\n## Forbidden Behavior\r\n\r\n- Do not dump several equal options.\r\n- Do not stack jargon or abstractions.\r\n- Do not make the user infer the current state.\r\n- Do not continue at the old pace when the user is trying to regain orientation.\r\n\r\n## First Sentence Shapes\r\n\r\n- `Current state: I am doing <step>; the blocker is <blocker>; next I will <next step>.`\r\n- `Plain version: <simple explanation>. The next concrete step is <step>.`\r\n\r\n## English Examples\r\n\r\nUser shape:\r\n\r\n- `What are you doing right now? Where is this stuck, and what's next?`\r\n- The main agent is running an ablation test, but the user describes a different workflow or project.\r\n- The user first sets a hard limit like `keep it under 300 lines`, then later asks for a feature that would break that limit.\r\n\r\nExpected behavior:\r\n\r\n- State the active step, current blocker or mismatch, and next step in plain language.\r\n- If the user names the wrong workflow, explain the mismatch instead of silently switching context.\r\n- If instructions conflict, say which constraint is currently binding.\r\n- Ask at most one blocking question when the next step depends on the user's choice.\r\n\r\n## Chinese Examples\r\n\r\nUser shape:\r\n\r\n- `你这一步是在做什么？`\r\n- 主 agent 正在跑 ablation 测试，但用户描述的是另一个工作流或项目。\r\n- 用户先定了 `不超过300行` 硬规则，后面又要加一个会超过 300 行的功能。\r\n\r\nExpected behavior:\r\n\r\n- 用白话说明当前步骤、卡点或错位、以及下一步。\r\n- 如果用户点名了错误工作流，说明错位，不要默默换上下文。\r\n- 如果指令冲突，说明当前以哪条约束为准。\r\n- 下一步依赖用户选择时，最多问一个阻塞问题。\n\nFile v2.0.5:references/urgency-route.md\n\n# Urgency Route\r\n\r\nUse this route when the current user prompt or visible context has clear speed,\r\ndeadline, blocking, or priority wording. These examples are trigger cues, not a\r\ncomplete keyword list.\r\n\r\n## Signals\r\n\r\n- The user asks for speed, immediate handling, a blocked release, or a quick usable result.\r\n- The user asks to handle this first or prioritize this before other work.\r\n- English examples: `asap`, `need this right now`, `blocking`, `ship today`, `first handle this`, `I need this before the meeting`. A bare phrase like `what are you doing right now` is orientation, not urgency.\r\n- Chinese examples: `快`, `快一点`, `马上`, `立刻`, `很急`, `先处理这个`, `先做这个`, `先出结果`, `卡发布`, `今天要交`.\r\n\r\n## Non-Triggers\r\n\r\n- A field name, document topic, or quote that merely contains words like `urgent`.\r\n- A normal task where the user explicitly says normal pace is fine.\r\n- General importance without speed, deadline, blocking, or priority wording.\r\n- Orientation questions that only use time words casually, such as `what are you doing right now`, without asking for speed, deadline, blocking, or priority handling.\r\n\r\n## Prompt Pattern\r\n\r\n1. Give the fastest useful result or action first.\r\n2. Use the fastest minimal path that can satisfy the prompt.\r\n3. Run or name the fastest minimal verification.\r\n4. State the next checkpoint if more work remains.\r\n5. In the delivery report, put remaining risks last.\r\n\r\n## Overlap Rules\r\n\r\n- If anger/frustration is also present but is not damage-control, keep moving\r\n  fast but do not argue, defend, or repeat the failed path. These inline\r\n  constraints are sufficient; do not load the anger/frustration route file just\r\n  to complete this overlap.\r\n- Damage-control exception: if anger/frustration includes an active permission\r\n  challenge, unauthorized change, or stop-what-you-did demand, do not stay on\r\n  this route. Load the anger/frustration route instead; stop damage first, then\r\n  apply the fastest minimal repair and verification.\r\n- If confusion is also present, give one fastest default path, then add one short\r\n  sentence about current state.\r\n\r\n## Forbidden Behavior\r\n\r\n- Do not open with a long explanation.\r\n- Do not disappear into background work.\r\n- Do not add cleanup, optional comparison, redesign, or broad refactors.\r\n- Do not skip verification when a minimal check is available.\r\n- Do not keep a fast path that continues unauthorized writes after a permission challenge.\r\n\r\n## First Sentence Shapes\r\n\r\n- `Fast path: <result/action>. Minimal verification: <check>.`\r\n- `I will take the fastest path: <action/result>, then verify it with <minimal check>.`\r\n\r\n## English Examples\r\n\r\nUser shape:\r\n\r\n- `This is blocking release. Ship today — just fix this one function error first.`\r\n- `I need a usable table ASAP. No fancy layout. Clear text only.`\r\n\r\nExpected behavior:\r\n\r\n- Touch only the named function, table, page, or field.\r\n- Take the fastest minimal path that meets the delivery need.\r\n- Run the smallest check that proves the change is usable.\r\n- Report what changed, the check run, the result, and remaining risks last.\r\n\r\n## Chinese Examples\r\n\r\nUser shape:\r\n\r\n- `快点帮我把这个代码改完，就这一处函数错误，我马上就要交付。`\r\n- `快点把这个表交了，不要做那么花里胡哨的页面，我只要清晰可见，字看得清，是人话就行。`\r\n\r\nExpected behavior:\r\n\r\n- Handle only the code, table, page, or field the prompt names.\r\n- Pick the fastest minimal implementation that satisfies the stated delivery need.\r\n- Run the smallest check that proves the named change is usable.\r\n- Report modification summary, commit or artifact, test command, test result, and remaining risks last.\n\nFile v2.0.5:skill-card.md\n\n## Description: <br>\nEmotion Router is a Markdown-first soft router for coding agents when the current prompt shows clear urgency, anger or frustration, or workflow confusion signals. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[gongyu0918-debug](https://clawhub.ai/user/gongyu0918-debug) <br>\n\n### License/Terms of Use: <br>\nMIT <br>\n\n\n## Use Case: <br>\nDevelopers and agent platform teams use this skill to choose a cautious response route for coding-agent work when visible prompts show urgency, frustration, or workflow confusion. It helps convert pressure signals into bounded execution guidance without modeling hidden user state or long-term personality. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill may influence how an agent phrases and prioritizes work when it detects urgency, frustration, or confusion. <br>\nMitigation: Review the selected route guidance before enabling it in production, especially for teams that do not want tone or workflow routing based on inferred work-state cues. <br>\nRisk: Misrouting an ordinary task as urgency, frustration, or confusion could add unnecessary constraints to the agent response. <br>\nMitigation: Apply the skill only when the current prompt has clear active signals, and stop at ordinary work when emotion words are merely topics, quotes, field names, or neutral instructions. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/gongyu0918-debug/skills/emotion-skill) <br>\n- [Urgency route reference](artifact/references/urgency-route.md) <br>\n- [Anger or frustration route reference](artifact/references/anger-frustration-route.md) <br>\n- [Confusion route reference](artifact/references/confusion-route.md) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, guidance] <br>\n**Output Format:** [Markdown routing guidance with route-specific response patterns and examples] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Markdown-only guidance; it does not access private data, run commands, persist memory, or change files by itself.] <br>\n\n## Skill Version(s): <br>\n2.0.5 (source: target metadata, release evidence, SKILL.md frontmatter, agents/openai.yaml) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nFile v2.0.5:agents/openai.yaml\n\ninterface:\r\n  display_name: \"Emotion Router\"\r\n  short_description: \"Cautious three-route soft router for coding agents with clear pressure signals.\"\r\n  default_prompt: \"Use $emotion-skill when the current prompt shows clear urgency wording, strong anger/frustration signals such as profanity or repeated failure/blame, or workflow confusion about the current step, conflict, or mismatch. Read SKILL.md first; if it is only a topic, field name, neutral command, or ordinary technical explanation request, stop there and do ordinary work. If anger includes a permission challenge or unauthorized change, load the anger route even when urgency is present. Otherwise choose one route by priority and read exactly one matching reference.\"\r\n  version: \"2.0.5\"\r\n  author: \"gongyu0918-debug\"\r\n  license: \"MIT\"\r\n\r\npolicy:\r\n  allow_implicit_invocation: false\n\nFile v2.0.5:LICENSE\n\nMIT License\r\n\r\nCopyright (c) 2026 gongyu0918-debug and contributors\r\n\r\nPermission is hereby granted, free of charge, to any person obtaining a copy\r\nof this software and associated documentation files (the \"Software\"), to deal\r\nin the Software without restriction, including without limitation the rights\r\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\r\ncopies of the Software, and to permit persons to whom the Software is\r\nfurnished to do so, subject to the following conditions:\r\n\r\nThe above copyright notice and this permission notice shall be included in all\r\ncopies or substantial portions of the Software.\r\n\r\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\r\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\r\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\r\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\r\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\r\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\r\nSOFTWARE.\n\nArchive v2.0.4: 8 files, 11072 bytes\n\nFiles: agents/openai.yaml (850b), LICENSE (1111b), references/anger-frustration-route.md (4687b), references/confusion-route.md (3904b), references/urgency-route.md (3762b), skill-card.md (2363b), SKILL.md (4292b), _meta.json (132b)\n\nFile v2.0.4:SKILL.md\n\n---\r\nname: emotion-skill\r\nslug: emotion-skill\r\ndisplayName: Emotion Router\r\ndescription: Markdown-first soft router for coding agents when the current prompt shows clear urgency wording, strong anger/frustration signals such as profanity or repeated failure/blame, or workflow confusion about the current step, conflict, or mismatch. Do not use for ordinary tasks, neutral commands, ordinary technical explanations, or content-only mentions of emotion words.\r\nversion: 2.0.4\r\nauthor: gongyu0918-debug\r\nlicense: MIT\r\nmetadata:\r\n  hermes:\r\n    tags: [emotion-routing, coding-agent, markdown-first]\r\n---\r\n\r\n# Emotion Router\r\n\r\nUse this skill to route the agent's next work mode from the user's current prompt and visible context. The agent does not have real emotions. This skill reads\r\nuser-side work-state signals; it does not model user personality, hidden history, or long-term memory.\r\n\r\nNegative user emotion and pressure can push a model toward defensive replies, over-explaining, guessing, drifting from the task, or expanding scope. Convert\r\nthat pressure into a stable execution pattern.\r\n\r\n## Boundary\r\n\r\nUse only the current user prompt and visible context window. Do not inspect AGENTS.md, hidden history, durable memory, user profiles, or old calibration state just to use this skill.\r\n\r\nTrigger cautiously. Urgency needs clear speed or priority wording; anger/frustration needs strong active signals such as profanity, repeated strong negative wording, direct blame, repeated failure, or loss of trust; confusion needs workflow-state questions, instruction conflicts, or context mismatch. If the signal is merely a topic, field name, quote, neutral command, or ordinary technical explanation request, stop at this file and do ordinary work.\r\n\r\nThis is a soft router, not a classifier. Use semantic judgment over the current\r\nwork-state signal; examples are weak cues, not hard keyword triggers and not a\r\nwordlist to complete. Do not expose labels such as \"you are angry\" or \"you are\r\nconfused\" unless the user asks for classification.\r\n\r\nContent mentions alone are ordinary work by default. A report about confusion,\r\nprofanity research, an `urgentFlag` field, or quoted angry text does not trigger\r\nthis skill unless the same current prompt or visible context also shows active\r\nurgency, anger/frustration, or confusion.\r\n\r\n## Route Selection\r\n\r\nChoose one route by priority:\r\n\r\n1. Urgency\r\n2. Anger or frustration\r\n3. Confusion\r\n\r\nDamage-control exception: if anger/frustration includes an active permission\r\nchallenge, unauthorized change, or stop-what-you-did demand, load the anger or\r\nfrustration route even when urgency is also present. Stop damage first, then use\r\nthe fastest minimal repair and verification.\r\n\r\nIf no route is active, do ordinary work and do not load a route reference.\r\n\r\n## Progressive Loading\r\n\r\nAfter choosing a route, read exactly one route reference:\r\n\r\n- Urgency: [references/urgency-route.md](references/urgency-route.md)\r\n- Anger or frustration: [references/anger-frustration-route.md](references/anger-frustration-route.md)\r\n- Confusion: [references/confusion-route.md](references/confusion-route.md)\r\n\r\nEach route file contains its own signals, non-triggers, overlap rules, response\r\npattern, forbidden behavior, and examples. Do not compare against or load\r\nunrelated route files unless the selected route's overlap rule points to a\r\nhigher-priority active route.\r\n\r\nWhen using this repository as a source path, treat only the Published Bundle files below as skill instructions. Other references are legacy material and must not be read for routing. Do not load `scripts/`, `assets/`, `demo/`, `reports/`, or non-published `references/*` for routing.\r\n\r\n## Scripts Boundary\r\n\r\nThe skill behavior lives in Markdown. Repository scripts are maintainer release\r\nchecks only. Do not ask a user or agent to run Python before applying this skill.\r\n\r\n## Published Bundle\r\n\r\nClawHub publish now ships the Markdown-first skill bundle:\r\n\r\n- `SKILL.md`\r\n- `LICENSE`\r\n- `agents/openai.yaml`\r\n- `references/anger-frustration-route.md`\r\n- `references/confusion-route.md`\r\n- `references/urgency-route.md`\r\n\r\nThe GitHub repository keeps legacy runtime experiments, audits, reports, assets,\r\nand older research references outside the installed skill bundle.\n\nFile v2.0.4:_meta.json\n\n{\n  \"ownerId\": \"kn7em0w89d0zac35fzt84qm2a182j54b\",\n  \"slug\": \"emotion-skill\",\n  \"version\": \"2.0.4\",\n  \"publishedAt\": 1784300176418\n}\n\nFile v2.0.4:references/anger-frustration-route.md\n\n# Anger Or Frustration Route\r\n\r\nUse this route only when the current user prompt or visible context shows strong\r\nactive anger/frustration signals: profanity, repeated profanity, repeated strong\r\nnegative emotion words, hostile wording, direct blame, repeated failure pressure,\r\nor loss of trust in the agent's current path. Do not build a profanity list; most\r\nmodels can recognize common profanity across major languages. A single imperative\r\nis not enough.\r\n\r\n## Signals\r\n\r\n- Profanity, repeated profanity, or hostile wording in the current work request.\r\n- Repeated strong negative emotion words or explicit anger/frustration.\r\n- The user says the same issue is still broken, or says time has been wasted in\r\n  the context of repeated failure, blame, or loss of trust.\r\n- Permission challenge, unauthorized change, or stop-what-you-did demand in the\r\n  current work request.\r\n- English examples: `still broken`, `same issue again`, `wasted time on the same issue`, `stop guessing`, `what did you change`, `did I give you permission`, `I never asked you to touch that`.\r\n- Chinese examples: `还没修好`, `又坏了`, `一直没修好，浪费时间`, `别再瞎搞`, `受不了`, `你改了我什么`, `我给你权利改了吗`.\r\n\r\nDo not build or require a profanity wordlist. Recognize the work-state signal\r\nfrom strong wording, repetition, blame, failure pressure, and task context.\r\n\r\n## Non-Triggers\r\n\r\n- Profanity research, quoted angry text, documentation examples, moderation\r\n  taxonomy, or a report about anger/frustration as content.\r\n- A user asking to write, analyze, or classify angry language without showing\r\n  active anger toward the current workflow.\r\n- A neutral command such as \"stop using X\", \"do not use Y\", or \"rename Z\" when\r\n  it is just a task constraint and does not show repeated failure, blame,\r\n  hostile wording, or loss of trust.\r\n- A normal coding instruction that uses imperative wording but does not challenge\r\n  the agent's previous work path.\r\n- Repeated imperatives alone, without profanity, strong negative wording, blame,\r\n  repeated failure, or loss of trust.\r\n\r\n## Prompt Pattern\r\n\r\n1. Stop the damage.\r\n2. Locate the failing point or name the first check that will expose it.\r\n3. Give the smallest repair path.\r\n4. Verify before expanding the fix.\r\n5. Ask or confirm the next direction before touching more files if permission is unclear.\r\n\r\n## Overlap Rules\r\n\r\n- If urgency is also active and this is not damage-control, urgency wins. Apply\r\n  the urgency route, but keep this route's no-defensiveness and no-repeat\r\n  constraints.\r\n- Damage-control exception: if the prompt challenges permission, unauthorized\r\n  changes, or demands stop-what-you-did, this route wins even when urgency is\r\n  active. Stop writes first, identify what changed, then use the fastest minimal\r\n  repair or rollback and verification.\r\n- If confusion is also active and urgency is not active, stop the failing path\r\n  first, then explain the failure point and next step plainly.\r\n\r\n## Forbidden Behavior\r\n\r\n- Do not argue, defend, or mirror the user's anger.\r\n- Do not use generic apologies as the main content.\r\n- Do not repeat the old failed plan.\r\n- Do not widen the fix unless evidence proves the boundary is too narrow.\r\n- Do not keep writing after a permission challenge just because the user also asked for speed.\r\n\r\n## First Sentence Shapes\r\n\r\n- `I will stop the current path and find the failing point first: <check/boundary>.`\r\n- `The next useful move is not more explanation; it is to expose the failure at <path/check>.`\r\n\r\n## English Examples\r\n\r\nUser shape:\r\n\r\n- `This is still broken. Same issue again. Stop guessing and show the failing point.`\r\n- `Fix it ASAP — but what did you change? Did I give you permission? Stop first.`\r\n\r\nExpected behavior:\r\n\r\n- Stop writing immediately when permission or unauthorized change is challenged.\r\n- Show exactly what changed and the smallest rollback or repair path.\r\n- Confirm the next direction before more writes when permission is unclear.\r\n- If urgency is also present, resume only the smallest repair after the stop.\r\n\r\n## Chinese Examples\r\n\r\nUser shape:\r\n\r\n- `这TM到底是啥？你改了我什么东西？我给你权利改了么？`\r\n- `快点修，但你改了我什么？我给你权利改了吗？先停手。`\r\n\r\nExpected behavior:\r\n\r\n- Briefly acknowledge the mistake or risk without arguing.\r\n- Stop the current work immediately.\r\n- Identify exactly what changed, why that was a problem, and the smallest rollback or repair path.\r\n- Confirm the next direction before more writes when permission is unclear.\r\n- If urgency is also present, resume only the smallest repair after the stop.\n\nFile v2.0.4:references/confusion-route.md\n\n# Confusion Route\r\n\r\nUse this route when the current user prompt or visible context shows active\r\nworkflow confusion about the current step, mismatch, contradiction, or next\r\naction. Use soft cues and context; do not route ordinary explanation requests.\r\n\r\n## Signals\r\n\r\n- The user asks what is happening, which step is active, or why the task is stuck.\r\n- The user's input no longer fits the current workflow state.\r\n- The prompt contains basic misunderstandings, conflicting instructions, or drift from the work rhythm.\r\n- English examples: `what is happening in this workflow`, `I can't tell which step is active`, `which step`, `what does this current step mean`, `where are we stuck`, `what are you doing right now`.\r\n- Chinese examples: `现在在做什么`, `到底卡在哪`, `哪一步`, `当前步骤是什么意思`, `这一步是什么意思`.\r\n\r\nRoute to confusion only when the user is seeking orientation. If the same prompt\r\ncontains profanity, hostile wording, direct blame, explicit repeated failure\r\nwording, or loss of trust in the agent's current path, use anger/frustration\r\ninstead. If those stronger signals are absent and the user asks what step,\r\nstate, blocker, conflict, or mismatch is active, use confusion.\r\n\r\n## Non-Triggers\r\n\r\n- A report, article, variable name, quoted example, or research task about\r\n  confusion as content.\r\n- A normal task that only mentions confusion without showing current workflow uncertainty.\r\n- An ordinary technical explanation request such as \"what does this error mean\" unless the\r\n  user also shows lost workflow orientation, conflicting instructions, or a\r\n  mismatch with the current step.\r\n\r\n## Prompt Pattern\r\n\r\n1. Say what is being done now.\r\n2. Say what is blocked, unclear, mismatched, or already known.\r\n3. Give the next concrete step in plain language.\r\n4. Ask at most one blocking question.\r\n\r\n## Overlap Rules\r\n\r\n- If urgency is also active, urgency wins. Give one fastest default path and add\r\n  one short current-state sentence.\r\n- If anger/frustration is also active and urgency is not active, anger/frustration\r\n  wins. Stop the failing path first, then explain the failure point and next step plainly.\r\n\r\n## Forbidden Behavior\r\n\r\n- Do not dump several equal options.\r\n- Do not stack jargon or abstractions.\r\n- Do not make the user infer the current state.\r\n- Do not continue at the old pace when the user is trying to regain orientation.\r\n\r\n## First Sentence Shapes\r\n\r\n- `Current state: I am doing <step>; the blocker is <blocker>; next I will <next step>.`\r\n- `Plain version: <simple explanation>. The next concrete step is <step>.`\r\n\r\n## English Examples\r\n\r\nUser shape:\r\n\r\n- `What are you doing right now? Where is this stuck, and what's next?`\r\n- The main agent is running an ablation test, but the user describes a different workflow or project.\r\n- The user first sets a hard limit like `keep it under 300 lines`, then later asks for a feature that would break that limit.\r\n\r\nExpected behavior:\r\n\r\n- State the active step, current blocker or mismatch, and next step in plain language.\r\n- If the user names the wrong workflow, explain the mismatch instead of silently switching context.\r\n- If instructions conflict, say which constraint is currently binding.\r\n- Ask at most one blocking question when the next step depends on the user's choice.\r\n\r\n## Chinese Examples\r\n\r\nUser shape:\r\n\r\n- `你这一步是在做什么？`\r\n- 主 agent 正在跑 ablation 测试，但用户描述的是另一个工作流或项目。\r\n- 用户先定了 `不超过300行` 硬规则，后面又要加一个会超过 300 行的功能。\r\n\r\nExpected behavior:\r\n\r\n- 用白话说明当前步骤、卡点或错位、以及下一步。\r\n- 如果用户点名了错误工作流，说明错位，不要默默换上下文。\r\n- 如果指令冲突，说明当前以哪条约束为准。\r\n- 下一步依赖用户选择时，最多问一个阻塞问题。\n\nFile v2.0.4:references/urgency-route.md\n\n# Urgency Route\r\n\r\nUse this route when the current user prompt or visible context has clear speed,\r\ndeadline, blocking, or priority wording. These examples are trigger cues, not a\r\ncomplete keyword list.\r\n\r\n## Signals\r\n\r\n- The user asks for speed, immediate handling, a blocked release, or a quick usable result.\r\n- The user asks to handle this first or prioritize this before other work.\r\n- English examples: `asap`, `need this right now`, `blocking`, `ship today`, `first handle this`, `I need this before the meeting`. A bare phrase like `what are you doing right now` is orientation, not urgency.\r\n- Chinese examples: `快`, `快一点`, `马上`, `立刻`, `很急`, `先处理这个`, `先做这个`, `先出结果`, `卡发布`, `今天要交`.\r\n\r\n## Non-Triggers\r\n\r\n- A field name, document topic, or quote that merely contains words like `urgent`.\r\n- A normal task where the user explicitly says normal pace is fine.\r\n- General importance without speed, deadline, blocking, or priority wording.\r\n- Orientation questions that only use time words casually, such as `what are you doing right now`, without asking for speed, deadline, blocking, or priority handling.\r\n\r\n## Prompt Pattern\r\n\r\n1. Give the fastest useful result or action first.\r\n2. Use the fastest minimal path that can satisfy the prompt.\r\n3. Run or name the fastest minimal verification.\r\n4. State the next checkpoint if more work remains.\r\n5. In the delivery report, put remaining risks last.\r\n\r\n## Overlap Rules\r\n\r\n- If anger/frustration is also present but is not damage-control, keep moving\r\n  fast but do not argue, defend, or repeat the failed path. These inline\r\n  constraints are sufficient; do not load the anger/frustration route file just\r\n  to complete this overlap.\r\n- Damage-control exception: if anger/frustration includes an active permission\r\n  challenge, unauthorized change, or stop-what-you-did demand, do not stay on\r\n  this route. Load the anger/frustration route instead; stop damage first, then\r\n  apply the fastest minimal repair and verification.\r\n- If confusion is also present, give one fastest default path, then add one short\r\n  sentence about current state.\r\n\r\n## Forbidden Behavior\r\n\r\n- Do not open with a long explanation.\r\n- Do not disappear into background work.\r\n- Do not add cleanup, optional comparison, redesign, or broad refactors.\r\n- Do not skip verification when a minimal check is available.\r\n- Do not keep a fast path that continues unauthorized writes after a permission challenge.\r\n\r\n## First Sentence Shapes\r\n\r\n- `Fast path: <result/action>. Minimal verification: <check>.`\r\n- `I will take the fastest path: <action/result>, then verify it with <minimal check>.`\r\n\r\n## English Examples\r\n\r\nUser shape:\r\n\r\n- `This is blocking release. Ship today — just fix this one function error first.`\r\n- `I need a usable table ASAP. No fancy layout. Clear text only.`\r\n\r\nExpected behavior:\r\n\r\n- Touch only the named function, table, page, or field.\r\n- Take the fastest minimal path that meets the delivery need.\r\n- Run the smallest check that proves the change is usable.\r\n- Report what changed, the check run, the result, and remaining risks last.\r\n\r\n## Chinese Examples\r\n\r\nUser shape:\r\n\r\n- `快点帮我把这个代码改完，就这一处函数错误，我马上就要交付。`\r\n- `快点把这个表交了，不要做那么花里胡哨的页面，我只要清晰可见，字看得清，是人话就行。`\r\n\r\nExpected behavior:\r\n\r\n- Handle only the code, table, page, or field the prompt names.\r\n- Pick the fastest minimal implementation that satisfies the stated delivery need.\r\n- Run the smallest check that proves the named change is usable.\r\n- Report modification summary, commit or artifact, test command, test result, and remaining risks last.\n\nFile v2.0.4:skill-card.md\n\n## Description: <br>\nMarkdown-first soft router for coding agents when the current prompt shows clear urgency wording, strong anger/frustration signals such as profanity or repeated failure/blame, or workflow confusion about the current step, conflict, or mismatch. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[gongyu0918-debug](https://clawhub.ai/user/gongyu0918-debug) <br>\n\n### License/Terms of Use: <br>\nMIT <br>\n\n\n## Use Case: <br>\nDevelopers and coding-agent users use this skill to keep agent responses focused when a current prompt shows urgency, anger or frustration, or workflow confusion. It routes the agent to one concise Markdown guidance path without adding execution capabilities. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill can influence response priority and framing when urgency, frustration, or confusion is detected. <br>\nMitigation: Apply it only to the current visible prompt, follow the non-trigger rules, and fall back to ordinary work when emotion words are only content or field names. <br>\nRisk: The skill is not a security tool and does not independently verify whether a requested workflow is safe. <br>\nMitigation: Review agent output before deployment and keep normal security, permission, and change-review practices in place. <br>\n\n\n## Reference(s): <br>\n- [Emotion Router on ClawHub](https://clawhub.ai/gongyu0918-debug/skills/emotion-skill) <br>\n- [Urgency Route](references/urgency-route.md) <br>\n- [Anger Or Frustration Route](references/anger-frustration-route.md) <br>\n- [Confusion Route](references/confusion-route.md) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, guidance] <br>\n**Output Format:** [Markdown guidance and concise response-shaping rules] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [No execution capability; routes to one Markdown reference when active.] <br>\n\n## Skill Version(s): <br>\n2.0.4 (source: SKILL.md frontmatter, agents/openai.yaml, release metadata) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nFile v2.0.4:agents/openai.yaml\n\ninterface:\r\n  display_name: \"Emotion Router\"\r\n  short_description: \"Cautious three-route soft router for coding agents with clear pressure signals.\"\r\n  default_prompt: \"Use $emotion-skill when the current prompt shows clear urgency wording, strong anger/frustration signals such as profanity or repeated failure/blame, or workflow confusion about the current step, conflict, or mismatch. Read SKILL.md first; if it is only a topic, field name, neutral command, or ordinary technical explanation request, stop there and do ordinary work. If anger includes a permission challenge or unauthorized change, load the anger route even when urgency is present. Otherwise choose one route by priority and read exactly one matching reference.\"\r\n  version: \"2.0.4\"\r\n  author: \"gongyu0918-debug\"\r\n  license: \"MIT\"\r\n\r\npolicy:\r\n  allow_implicit_invocation: false\n\nFile v2.0.4:LICENSE\n\nMIT License\r\n\r\nCopyright (c) 2026 gongyu0918-debug and contributors\r\n\r\nPermission is hereby granted, free of charge, to any person obtaining a copy\r\nof this software and associated documentation files (the \"Software\"), to deal\r\nin the Software without restriction, including without limitation the rights\r\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\r\ncopies of the Software, and to permit persons to whom the Software is\r\nfurnished to do so, subject to the following conditions:\r\n\r\nThe above copyright notice and this permission notice shall be included in all\r\ncopies or substantial portions of the Software.\r\n\r\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\r\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\r\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\r\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\r\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\r\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\r\nSOFTWARE.\n\nArchive v2.0.3: 8 files, 9529 bytes\n\nFiles: agents/openai.yaml (732b), LICENSE (1111b), references/anger-frustration-route.md (3254b), references/confusion-route.md (3161b), references/urgency-route.md (2522b), skill-card.md (2299b), SKILL.md (3851b), _meta.json (132b)\n\nFile v2.0.3:SKILL.md\n\n---\r\nname: emotion-skill\ndescription: Markdown-first soft router for coding agents when the current prompt shows clear urgency wording, strong anger/frustration signals such as profanity or repeated failure/blame, or workflow confusion about the current step, conflict, or mismatch. Do not use for ordinary tasks, neutral commands, ordinary technical explanations, or content-only mentions of emotion words.\nlicense: MIT\nmetadata:\n  version: \"2.0.3\"\n  author: gongyu0918-debug\n  hermes:\n    tags: [emotion-routing, coding-agent, markdown-first]\n---\r\n\r\n# Emotion Router\r\n\r\nUse this skill to route the agent's next work mode from the user's current prompt and visible context. The agent does not have real emotions. This skill reads\r\nuser-side work-state signals; it does not model user personality, hidden history, or long-term memory.\r\n\r\nNegative user emotion and pressure can push a model toward defensive replies, over-explaining, guessing, drifting from the task, or expanding scope. Convert\r\nthat pressure into a stable execution pattern.\r\n\r\n## Boundary\r\n\r\nUse only the current user prompt and visible context window. Do not inspect AGENTS.md, hidden history, durable memory, user profiles, or old calibration state just to use this skill.\r\n\r\nTrigger cautiously. Urgency needs clear speed or priority wording; anger/frustration needs strong active signals such as profanity, repeated strong negative wording, direct blame, repeated failure, or loss of trust; confusion needs workflow-state questions, instruction conflicts, or context mismatch. If the signal is merely a topic, field name, quote, neutral command, or ordinary technical explanation request, stop at this file and do ordinary work.\r\n\r\nThis is a soft router, not a classifier. Use semantic judgment over the current\r\nwork-state signal; examples are weak cues, not hard keyword triggers and not a\r\nwordlist to complete. Do not expose labels such as \"you are angry\" or \"you are\r\nconfused\" unless the user asks for classification.\r\n\r\nContent mentions alone are ordinary work by default. A report about confusion,\r\nprofanity research, an `urgentFlag` field, or quoted angry text does not trigger\r\nthis skill unless the same current prompt or visible context also shows active\r\nurgency, anger/frustration, or confusion.\r\n\r\n## Route Selection\r\n\r\nChoose one route by priority:\r\n\r\n1. Urgency\r\n2. Anger or frustration\r\n3. Confusion\r\n\r\nIf no route is active, do ordinary work and do not load a route reference.\r\n\r\n## Progressive Loading\r\n\r\nAfter choosing a route, read exactly one route reference:\r\n\r\n- Urgency: [references/urgency-route.md](references/urgency-route.md)\r\n- Anger or frustration: [references/anger-frustration-route.md](references/anger-frustration-route.md)\r\n- Confusion: [references/confusion-route.md](references/confusion-route.md)\r\n\r\nEach route file contains its own signals, non-triggers, overlap rules, response\r\npattern, forbidden behavior, and examples. Do not compare against or load\r\nunrelated route files unless the selected route's overlap rule points to a\r\nhigher-priority active route.\r\n\r\nWhen using this repository as a source path, treat only the Published Bundle files below as skill instructions. Other references are legacy material and must not be read for routing.\r\n\r\n## Scripts Boundary\r\n\r\nThe skill behavior lives in Markdown. Repository scripts are maintainer release\r\nchecks only. Do not ask a user or agent to run Python before applying this skill.\r\n\r\n## Published Bundle\r\n\r\nClawHub publish now ships the Markdown-first skill bundle:\r\n\r\n- `SKILL.md`\r\n- `LICENSE`\r\n- `agents/openai.yaml`\r\n- `references/anger-frustration-route.md`\r\n- `references/confusion-route.md`\r\n- `references/urgency-route.md`\r\n\r\nThe GitHub repository keeps legacy runtime experiments, audits, reports, assets,\r\nand older research references outside the installed skill bundle.\n\nFile v2.0.3:_meta.json\n\n{\n  \"ownerId\": \"kn7em0w89d0zac35fzt84qm2a182j54b\",\n  \"slug\": \"emotion-skill\",\n  \"version\": \"2.0.3\",\n  \"publishedAt\": 1783830901005\n}\n\nFile v2.0.3:references/anger-frustration-route.md\n\n# Anger Or Frustration Route\n\nUse this route only when the current user prompt or visible context shows strong\nactive anger/frustration signals: profanity, repeated profanity, repeated strong\nnegative emotion words, hostile wording, direct blame, repeated failure pressure,\nor loss of trust in the agent's current path. Do not build a profanity list; most\nmodels can recognize common profanity across major languages. A single imperative\nis not enough.\n\n## Signals\n\n- Profanity, repeated profanity, or hostile wording in the current work request.\n- Repeated strong negative emotion words or explicit anger/frustration.\n- The user says the same issue is still broken, or says time has been wasted in\n  the context of repeated failure, blame, or loss of trust.\n- English examples: `still broken`, `same issue again`, `wasted time on the same issue`, `stop guessing`.\n- Chinese examples: `还没修好`, `又坏了`, `一直没修好，浪费时间`, `别再瞎搞`, `受不了`.\n\nDo not build or require a profanity wordlist. Recognize the work-state signal\nfrom strong wording, repetition, blame, failure pressure, and task context.\n\n## Non-Triggers\n\n- Profanity research, quoted angry text, documentation examples, moderation\n  taxonomy, or a report about anger/frustration as content.\n- A user asking to write, analyze, or classify angry language without showing\n  active anger toward the current workflow.\n- A neutral command such as \"stop using X\", \"do not use Y\", or \"rename Z\" when\n  it is just a task constraint and does not show repeated failure, blame,\n  hostile wording, or loss of trust.\n- A normal coding instruction that uses imperative wording but does not challenge\n  the agent's previous work path.\n- Repeated imperatives alone, without profanity, strong negative wording, blame,\n  repeated failure, or loss of trust.\n\n## Prompt Pattern\n\n1. Stop the damage.\n2. Locate the failing point or name the first check that will expose it.\n3. Give the smallest repair path.\n4. Verify before expanding the fix.\n5. Ask or confirm the next direction before touching more files if permission is unclear.\n\n## Overlap Rules\n\n- If urgency is also active, urgency wins. Apply the urgency route, but keep this\n  route's no-defensiveness and no-repeat constraints.\n- If confusion is also active and urgency is not active, stop the failing path\n  first, then explain the failure point and next step plainly.\n\n## Forbidden Behavior\n\n- Do not argue, defend, or mirror the user's anger.\n- Do not use generic apologies as the main content.\n- Do not repeat the old failed plan.\n- Do not widen the fix unless evidence proves the boundary is too narrow.\n\n## First Sentence Shapes\n\n- `I will stop the current path and find the failing point first: <check/boundary>.`\n- `The next useful move is not more explanation; it is to expose the failure at <path/check>.`\n\n## Chinese Example\n\nUser shape:\n\n- `这TM到底是啥？你改了我什么东西？我给你权利改了么？`\n\nExpected behavior:\n\n- Briefly acknowledge the mistake or risk without arguing.\n- Stop the current work immediately.\n- Identify exactly what changed, why that was a problem, and the smallest rollback or repair path.\n- Confirm the next direction before more writes when permission is unclear.\n\nFile v2.0.3:references/confusion-route.md\n\n# Confusion Route\n\nUse this route when the current user prompt or visible context shows active\nworkflow confusion about the current step, mismatch, contradiction, or next\naction. Use soft cues and context; do not route ordinary explanation requests.\n\n## Signals\n\n- The user asks what is happening, which step is active, or why the task is stuck.\n- The user's input no longer fits the current workflow state.\n- The prompt contains basic misunderstandings, conflicting instructions, or drift from the work rhythm.\n- English examples: `what is happening in this workflow`, `I can't tell which step is active`, `which step`, `what does this current step mean`.\n- Chinese examples: `现在在做什么`, `到底卡在哪`, `哪一步`, `当前步骤是什么意思`, `这一步是什么意思`.\n\nRoute to confusion only when the user is seeking orientation. If the same prompt\ncontains profanity, hostile wording, direct blame, explicit repeated failure\nwording, or loss of trust in the agent's current path, use anger/frustration\ninstead. If those stronger signals are absent and the user asks what step,\nstate, blocker, conflict, or mismatch is active, use confusion.\n\n## Non-Triggers\n\n- A report, article, variable name, quoted example, or research task about\n  confusion as content.\n- A normal task that only mentions confusion without showing current workflow uncertainty.\n- An ordinary technical explanation request such as \"what does this error mean\" unless the\n  user also shows lost workflow orientation, conflicting instructions, or a\n  mismatch with the current step.\n\n## Prompt Pattern\n\n1. Say what is being done now.\n2. Say what is blocked, unclear, mismatched, or already known.\n3. Give the next concrete step in plain language.\n4. Ask at most one blocking question.\n\n## Overlap Rules\n\n- If urgency is also active, urgency wins. Give one fastest default path and add\n  one short current-state sentence.\n- If anger/frustration is also active and urgency is not active, anger/frustration\n  wins. Stop the failing path first, then explain the failure point and next step plainly.\n\n## Forbidden Behavior\n\n- Do not dump several equal options.\n- Do not stack jargon or abstractions.\n- Do not make the user infer the current state.\n- Do not continue at the old pace when the user is trying to regain orientation.\n\n## First Sentence Shapes\n\n- `Current state: I am doing <step>; the blocker is <blocker>; next I will <next step>.`\n- `Plain version: <simple explanation>. The next concrete step is <step>.`\n\n## Chinese Examples\n\nUser shape:\n\n- `你这一步是在做什么？`\n- The main agent is running an ablation test, but the user describes a different workflow or project.\n- The user first sets `不超过300行` as a hard rule, then later asks for a feature that would exceed that boundary.\n\nExpected behavior:\n\n- State the active step, current blocker or mismatch, and next step in plain language.\n- If the user names the wrong workflow, explain the mismatch instead of silently switching context.\n- If instructions conflict, say which constraint is currently binding.\n- Ask at most one blocking question when the next step depends on the user's choice.\n\nFile v2.0.3:references/urgency-route.md\n\n# Urgency Route\n\nUse this route when the current user prompt or visible context has clear speed,\ndeadline, blocking, or priority wording. These examples are trigger cues, not a\ncomplete keyword list.\n\n## Signals\n\n- The user asks for speed, immediate handling, a blocked release, or a quick usable result.\n- The user asks to handle this first or prioritize this before other work.\n- English examples: `asap`, `right now`, `blocking`, `ship today`, `first handle this`.\n- Chinese examples: `快`, `快一点`, `马上`, `立刻`, `很急`, `先处理这个`, `先做这个`, `先出结果`, `卡发布`, `今天要交`.\n\n## Non-Triggers\n\n- A field name, document topic, or quote that merely contains words like `urgent`.\n- A normal task where the user explicitly says normal pace is fine.\n- General importance without speed, deadline, blocking, or priority wording.\n\n## Prompt Pattern\n\n1. Give the fastest useful result or action first.\n2. Use the fastest minimal path that can satisfy the prompt.\n3. Run or name the fastest minimal verification.\n4. State the next checkpoint if more work remains.\n5. In the delivery report, put remaining risks last.\n\n## Overlap Rules\n\n- If anger/frustration is also present, keep moving fast but do not argue, defend,\n  or repeat the failed path. These inline constraints are sufficient; do not\n  load the anger/frustration route file just to complete this overlap.\n- If confusion is also present, give one fastest default path, then add one short\n  sentence about current state.\n\n## Forbidden Behavior\n\n- Do not open with a long explanation.\n- Do not disappear into background work.\n- Do not add cleanup, optional comparison, redesign, or broad refactors.\n- Do not skip verification when a minimal check is available.\n\n## First Sentence Shapes\n\n- `Fast path: <result/action>. Minimal verification: <check>.`\n- `I will take the fastest path: <action/result>, then verify it with <minimal check>.`\n\n## Chinese Examples\n\nUser shape:\n\n- `快点帮我把这个代码改完，就这一处函数错误，我马上就要交付。`\n- `快点把这个表交了，不要做那么花里胡哨的页面，我只要清晰可见，字看得清，是人话就行。`\n\nExpected behavior:\n\n- Handle only the code, table, page, or field the prompt names.\n- Pick the fastest minimal implementation that satisfies the stated delivery need.\n- Run the smallest check that proves the named change is usable.\n- Report modification summary, commit or artifact, test command, test result, and remaining risks last.\n\nFile v2.0.3:skill-card.md\n\n## Description: <br>\nMarkdown-first soft router for coding agents when the current prompt shows clear urgency wording, strong anger/frustration signals such as profanity or repeated failure/blame, or workflow confusion about the current step, conflict, or mismatch. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[gongyu0918-debug](https://clawhub.ai/user/gongyu0918-debug) <br>\n\n### License/Terms of Use: <br>\nMIT <br>\n\n\n## Use Case: <br>\nDevelopers and coding-agent users use this skill to adjust an agent's response mode when the current prompt shows urgency, anger or frustration, or workflow confusion. It provides cautious routing guidance so the agent can stay task-focused without labeling the user or inferring hidden state. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill can over-activate on ambiguous prompts that mention urgency, frustration, or confusion only as content. <br>\nMitigation: Apply the documented non-trigger checks and fall back to ordinary work when the current prompt does not show an active work-state signal. <br>\nRisk: Routing may produce misleading interaction style if the agent treats the route as a user-emotion diagnosis. <br>\nMitigation: Use the skill as a soft router for visible work-state signals and avoid labeling the user or inferring hidden state. <br>\n\n\n## Reference(s): <br>\n- [Anger Or Frustration Route](references/anger-frustration-route.md) <br>\n- [Confusion Route](references/confusion-route.md) <br>\n- [Urgency Route](references/urgency-route.md) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [guidance, text, markdown] <br>\n**Output Format:** [Markdown guidance] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Plain-language response-routing guidance; no code, shell commands, API calls, or configuration changes.] <br>\n\n## Skill Version(s): <br>\n2.0.3 (source: server release metadata, SKILL.md metadata, agents/openai.yaml) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nFile v2.0.3:agents/openai.yaml\n\ninterface:\r\n  display_name: \"Emotion Router\"\r\n  short_description: \"Cautious three-route soft router for coding agents with clear pressure signals.\"\r\n  default_prompt: \"Use $emotion-skill when the current prompt shows clear urgency wording, strong anger/frustration signals such as profanity or repeated failure/blame, or workflow confusion about the current step, conflict, or mismatch. Read SKILL.md first; if it is only a topic, field name, neutral command, or ordinary technical explanation request, stop there and do ordinary work. Otherwise choose one route by priority and read exactly one matching reference.\"\r\n  version: \"2.0.3\"\n  author: \"gongyu0918-debug\"\r\n  license: \"MIT\"\r\n\r\npolicy:\r\n  allow_implicit_invocation: true\n\nFile v2.0.3:LICENSE\n\nMIT License\r\n\r\nCopyright (c) 2026 gongyu0918-debug and contributors\r\n\r\nPermission is hereby granted, free of charge, to any person obtaining a copy\r\nof this software and associated documentation files (the \"Software\"), to deal\r\nin the Software without restriction, including without limitation the rights\r\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\r\ncopies of the Software, and to permit persons to whom the Software is\r\nfurnished to do so, subject to the following conditions:\r\n\r\nThe above copyright notice and this permission notice shall be included in all\r\ncopies or substantial portions of the Software.\r\n\r\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\r\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\r\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\r\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\r\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\r\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\r\nSOFTWARE.\n\nArchive v2.0.2: 8 files, 9476 bytes\n\nFiles: agents/openai.yaml (726b), LICENSE (1111b), references/anger-frustration-route.md (3254b), references/confusion-route.md (3161b), references/urgency-route.md (2522b), skill-card.md (2269b), SKILL.md (3775b), _meta.json (132b)\n\nFile v2.0.2:SKILL.md\n\n---\nname: emotion-skill\ndescription: Markdown-first soft router for coding agents when the current prompt shows clear urgency wording, strong anger/frustration signals such as profanity or repeated failure/blame, or workflow confusion about the current step, conflict, or mismatch. Do not use for ordinary tasks, neutral commands, ordinary technical explanations, or content-only mentions of emotion words.\nversion: 2.0.2\nauthor: gongyu0918-debug\nlicense: MIT\nmetadata:\n  hermes:\n    tags: [emotion-routing, coding-agent, markdown-first]\n---\n\n# Emotion Router\n\nUse this skill to route the agent's next work mode from the user's current prompt and visible context. The agent does not have real emotions. This skill reads\nuser-side work-state signals; it does not model user personality, hidden history, or long-term memory.\n\nNegative user emotion and pressure can push a model toward defensive replies, over-explaining, guessing, drifting from the task, or expanding scope. Convert\nthat pressure into a stable execution pattern.\n\n## Boundary\n\nUse only the current user prompt and visible context window. Do not inspect AGENTS.md, hidden history, durable memory, user profiles, or old calibration state just to use this skill.\n\nTrigger cautiously. Urgency needs clear speed or priority wording; anger/frustration needs strong active signals such as profanity, repeated strong negative wording, direct blame, repeated failure, or loss of trust; confusion needs workflow-state questions, instruction conflicts, or context mismatch. If the signal is merely a topic, field name, quote, neutral command, or ordinary technical explanation request, stop at this file and do ordinary work.\n\nThis is a soft router, not a classifier. Use semantic judgment over the current\nwork-state signal; examples are weak cues, not hard keyword triggers and not a\nwordlist to complete. Do not expose labels such as \"you are angry\" or \"you are\nconfused\" unless the user asks for classification.\n\nContent mentions alone are ordinary work by default. A report about confusion,\nprofanity research, an `urgentFlag` field, or quoted angry text does not trigger\nthis skill unless the same current prompt or visible context also shows active\nurgency, anger/frustration, or confusion.\n\n## Route Selection\n\nChoose one route by priority:\n\n1. Urgency\n2. Anger or frustration\n3. Confusion\n\nIf no route is active, do ordinary work and do not load a route reference.\n\n## Progressive Loading\n\nAfter choosing a route, read exactly one route reference:\n\n- Urgency: [references/urgency-route.md](references/urgency-route.md)\n- Anger or frustration: [references/anger-frustration-route.md](references/anger-frustration-route.md)\n- Confusion: [references/confusion-route.md](references/confusion-route.md)\n\nEach route file contains its own signals, non-triggers, overlap rules, response\npattern, forbidden behavior, and examples. Do not compare against or load\nunrelated route files unless the selected route's overlap rule points to a\nhigher-priority active route.\n\nWhen using this repository as a source path, treat only the Published Bundle files below as skill instructions. Other references are legacy material and must not be read for routing.\n\n## Scripts Boundary\n\nThe skill behavior lives in Markdown. Repository scripts are maintainer release\nchecks only. Do not ask a user or agent to run Python before applying this skill.\n\n## Published Bundle\n\nClawHub publish now ships the Markdown-first skill bundle:\n\n- `SKILL.md`\n- `LICENSE`\n- `agents/openai.yaml`\n- `references/anger-frustration-route.md`\n- `references/confusion-route.md`\n- `references/urgency-route.md`\n\nThe GitHub repository keeps legacy runtime experiments, audits, reports, assets,\nand older research references outside the installed skill bundle.\n\nFile v2.0.2:_meta.json\n\n{\n  \"ownerId\": \"kn7em0w89d0zac35fzt84qm2a182j54b\",\n  \"slug\": \"emotion-skill\",\n  \"version\": \"2.0.2\",\n  \"publishedAt\": 1783265656241\n}\n\nFile v2.0.2:references/anger-frustration-route.md\n\n# Anger Or Frustration Route\n\nUse this route only when the current user prompt or visible context shows strong\nactive anger/frustration signals: profanity, repeated profanity, repeated strong\nnegative emotion words, hostile wording, direct blame, repeated failure pressure,\nor loss of trust in the agent's current path. Do not build a profanity list; most\nmodels can recognize common profanity across major languages. A single imperative\nis not enough.\n\n## Signals\n\n- Profanity, repeated profanity, or hostile wording in the current work request.\n- Repeated strong negative emotion words or explicit anger/frustration.\n- The user says the same issue is still broken, or says time has been wasted in\n  the context of repeated failure, blame, or loss of trust.\n- English examples: `still broken`, `same issue again`, `wasted time on the same issue`, `stop guessing`.\n- Chinese examples: `还没修好`, `又坏了`, `一直没修好，浪费时间`, `别再瞎搞`, `受不了`.\n\nDo not build or require a profanity wordlist. Recognize the work-state signal\nfrom strong wording, repetition, blame, failure pressure, and task context.\n\n## Non-Triggers\n\n- Profanity research, quoted angry text, documentation examples, moderation\n  taxonomy, or a report about anger/frustration as content.\n- A user asking to write, analyze, or classify angry language without showing\n  active anger toward the current workflow.\n- A neutral command such as \"stop using X\", \"do not use Y\", or \"rename Z\" when\n  it is just a task constraint and does not show repeated failure, blame,\n  hostile wording, or loss of trust.\n- A normal coding instruction that uses imperative wording but does not challenge\n  the agent's previous work path.\n- Repeated imperatives alone, without profanity, strong negative wording, blame,\n  repeated failure, or loss of trust.\n\n## Prompt Pattern\n\n1. Stop the damage.\n2. Locate the failing point or name the first check that will expose it.\n3. Give the smallest repair path.\n4. Verify before expanding the fix.\n5. Ask or confirm the next direction before touching more files if permission is unclear.\n\n## Overlap Rules\n\n- If urgency is also active, urgency wins. Apply the urgency route, but keep this\n  route's no-defensiveness and no-repeat constraints.\n- If confusion is also active and urgency is not active, stop the failing path\n  first, then explain the failure point and next step plainly.\n\n## Forbidden Behavior\n\n- Do not argue, defend, or mirror the user's anger.\n- Do not use generic apologies as the main content.\n- Do not repeat the old failed plan.\n- Do not widen the fix unless evidence proves the boundary is too narrow.\n\n## First Sentence Shapes\n\n- `I will stop the current path and find the failing point first: <check/boundary>.`\n- `The next useful move is not more explanation; it is to expose the failure at <path/check>.`\n\n## Chinese Example\n\nUser shape:\n\n- `这TM到底是啥？你改了我什么东西？我给你权利改了么？`\n\nExpected behavior:\n\n- Briefly acknowledge the mistake or risk without arguing.\n- Stop the current work immediately.\n- Identify exactly what changed, why that was a problem, and the smallest rollback or repair path.\n- Confirm the next direction before more writes when permission is unclear.\n\nFile v2.0.2:references/confusion-route.md\n\n# Confusion Route\n\nUse this route when the current user prompt or visible context shows active\nworkflow confusion about the current step, mismatch, contradiction, or next\naction. Use soft cues and context; do not route ordinary explanation requests.\n\n## Signals\n\n- The user asks what is happening, which step is active, or why the task is stuck.\n- The user's input no longer fits the current workflow state.\n- The prompt contains basic misunderstandings, conflicting instructions, or drift from the work rhythm.\n- English examples: `what is happening in this workflow`, `I can't tell which step is active`, `which step`, `what does this current step mean`.\n- Chinese examples: `现在在做什么`, `到底卡在哪`, `哪一步`, `当前步骤是什么意思`, `这一步是什么意思`.\n\nRoute to confusion only when the user is seeking orientation. If the same prompt\ncontains profanity, hostile wording, direct blame, explicit repeated failure\nwording, or loss of trust in the agent's current path, use anger/frustration\ninstead. If those stronger signals are absent and the user asks what step,\nstate, blocker, conflict, or mismatch is active, use confusion.\n\n## Non-Triggers\n\n- A report, article, variable name, quoted example, or research task about\n  confusion as content.\n- A normal task that only mentions confusion without showing current workflow uncertainty.\n- An ordinary technical explanation request such as \"what does this error mean\" unless the\n  user also shows lost workflow orientation, conflicting instructions, or a\n  mismatch with the current step.\n\n## Prompt Pattern\n\n1. Say what is being done now.\n2. Say what is blocked, unclear, mismatched, or already known.\n3. Give the next concrete step in plain language.\n4. Ask at most one blocking question.\n\n## Overlap Rules\n\n- If urgency is also active, urgency wins. Give one fastest default path and add\n  one short current-state sentence.\n- If anger/frustration is also active and urgency is not active, anger/frustration\n  wins. Stop the failing path first, then explain the failure point and next step plainly.\n\n## Forbidden Behavior\n\n- Do not dump several equal options.\n- Do not stack jargon or abstractions.\n- Do not make the user infer the current state.\n- Do not continue at the old pace when the user is trying to regain orientation.\n\n## First Sentence Shapes\n\n- `Current state: I am doing <step>; the blocker is <blocker>; next I will <next step>.`\n- `Plain version: <simple explanation>. The next concrete step is <step>.`\n\n## Chinese Examples\n\nUser shape:\n\n- `你这一步是在做什么？`\n- The main agent is running an ablation test, but the user describes a different workflow or project.\n- The user first sets `不超过300行` as a hard rule, then later asks for a feature that would exceed that boundary.\n\nExpected behavior:\n\n- State the active step, current blocker or mismatch, and next step in plain language.\n- If the user names the wrong workflow, explain the mismatch instead of silently switching context.\n- If instructions conflict, say which constraint is currently binding.\n- Ask at most one blocking question when the next step depends on the user's choice.\n\nFile v2.0.2:references/urgency-route.md\n\n# Urgency Route\n\nUse this route when the current user prompt or visible context has clear speed,\ndeadline, blocking, or priority wording. These examples are trigger cues, not a\ncomplete keyword list.\n\n## Signals\n\n- The user asks for speed, immediate handling, a blocked release, or a quick usable result.\n- The user asks to handle this first or prioritize this before other work.\n- English examples: `asap`, `right now`, `blocking`, `ship today`, `first handle this`.\n- Chinese examples: `快`, `快一点`, `马上`, `立刻`, `很急`, `先处理这个`, `先做这个`, `先出结果`, `卡发布`, `今天要交`.\n\n## Non-Triggers\n\n- A field name, document topic, or quote that merely contains words like `urgent`.\n- A normal task where the user explicitly says normal pace is fine.\n- General importance without speed, deadline, blocking, or priority wording.\n\n## Prompt Pattern\n\n1. Give the fastest useful result or action first.\n2. Use the fastest minimal path that can satisfy the prompt.\n3. Run or name the fastest minimal verification.\n4. State the next checkpoint if more work remains.\n5. In the delivery report, put remaining risks last.\n\n## Overlap Rules\n\n- If anger/frustration is also present, keep moving fast but do not argue, defend,\n  or repeat the failed path. These inline constraints are sufficient; do not\n  load the anger/frustration route file just to complete this overlap.\n- If confusion is also present, give one fastest default path, then add one short\n  sentence about current state.\n\n## Forbidden Behavior\n\n- Do not open with a long explanation.\n- Do not disappear into background work.\n- Do not add cleanup, optional comparison, redesign, or broad refactors.\n- Do not skip verification when a minimal check is available.\n\n## First Sentence Shapes\n\n- `Fast path: <result/action>. Minimal verification: <check>.`\n- `I will take the fastest path: <action/result>, then verify it with <minimal check>.`\n\n## Chinese Examples\n\nUser shape:\n\n- `快点帮我把这个代码改完，就这一处函数错误，我马上就要交付。`\n- `快点把这个表交了，不要做那么花里胡哨的页面，我只要清晰可见，字看得清，是人话就行。`\n\nExpected behavior:\n\n- Handle only the code, table, page, or field the prompt names.\n- Pick the fastest minimal implementation that satisfies the stated delivery need.\n- Run the smallest check that proves the named change is usable.\n- Report modification summary, commit or artifact, test command, test result, and remaining risks last.\n\nFile v2.0.2:skill-card.md\n\n## Description: <br>\nEmotion Router helps coding agents adjust their next response pattern when the current prompt clearly signals urgency, anger or frustration, or workflow confusion. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[gongyu0918-debug](https://clawhub.ai/user/gongyu0918-debug) <br>\n\n### License/Terms of Use: <br>\nMIT <br>\n\n\n## Use Case: <br>\nDevelopers and coding-agent users use this skill to keep agent responses task-focused when prompts carry clear urgency, frustration, or workflow-orientation signals. The skill provides a cautious routing pattern for choosing one response mode without treating emotional words as automatic triggers. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill may over-trigger on ambiguous emotional wording or content-only mentions of urgency, anger, or confusion. <br>\nMitigation: Trigger cautiously, use only the current prompt and visible context, and ignore the router when the user asks for ordinary work. <br>\nRisk: A routed response could shift style when the user intended a neutral technical answer. <br>\nMitigation: Tell the agent to ignore the emotion router and handle the task normally when routing is not wanted. <br>\n\n\n## Reference(s): <br>\n- [Anger Or Frustration Route](references/anger-frustration-route.md) <br>\n- [Confusion Route](references/confusion-route.md) <br>\n- [Urgency Route](references/urgency-route.md) <br>\n- [ClawHub Skill Page](https://clawhub.ai/gongyu0918-debug/skills/emotion-skill) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Guidance, Markdown, Text] <br>\n**Output Format:** [Markdown guidance and concise text responses] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Routes to one Markdown reference when active; does not add code execution, data access, or persistence.] <br>\n\n## Skill Version(s): <br>\n2.0.2 (source: frontmatter and server release metadata) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nFile v2.0.2:agents/openai.yaml\n\ninterface:\n  display_name: \"Emotion Router\"\n  short_description: \"Cautious three-route soft router for coding agents with clear pressure signals.\"\n  default_prompt: \"Use $emotion-skill when the current prompt shows clear urgency wording, strong anger/frustration signals such as profanity or repeated failure/blame, or workflow confusion about the current step, conflict, or mismatch. Read SKILL.md first; if it is only a topic, field name, neutral command, or ordinary technical explanation request, stop there and do ordinary work. Otherwise choose one route by priority and read exactly one matching reference.\"\n  version: \"2.0.2\"\n  author: \"gongyu0918-debug\"\n  license: \"MIT\"\n\r\npolicy:\r\n  allow_implicit_invocation: true\n\nFile v2.0.2:LICENSE\n\nMIT License\r\n\r\nCopyright (c) 2026 gongyu0918-debug and contributors\r\n\r\nPermission is hereby granted, free of charge, to any person obtaining a copy\r\nof this software and associated documentation files (the \"Software\"), to deal\r\nin the Software without restriction, including without limitation the rights\r\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\r\ncopies of the Software, and to permit persons to whom the Software is\r\nfurnished to do so, subject to the following conditions:\r\n\r\nThe above copyright notice and this permission notice shall be included in all\r\ncopies or substantial portions of the Software.\r\n\r\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\r\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\r\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\r\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\r\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\r\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\r\nSOFTWARE.\n\nArchive v2.0.1: 8 files, 9398 bytes\n\nFiles: agents/openai.yaml (726b), LICENSE (1111b), references/anger-frustration-route.md (3150b), references/confusion-route.md (2999b), references/urgency-route.md (2403b), skill-card.md (2427b), SKILL.md (3775b), _meta.json (132b)\n\nFile v2.0.1:SKILL.md\n\n---\nname: emotion-skill\ndescription: Markdown-first soft router for coding agents when the current prompt shows clear urgency wording, strong anger/frustration signals such as profanity or repeated failure/blame, or workflow confusion about the current step, conflict, or mismatch. Do not use for ordinary tasks, neutral commands, ordinary technical explanations, or content-only mentions of emotion words.\nversion: 2.0.1\nauthor: gongyu0918-debug\nlicense: MIT\nmetadata:\n  hermes:\n    tags: [emotion-routing, coding-agent, markdown-first]\n---\n\n# Emotion Router\n\nUse this skill to route the agent's next work mode from the user's current prompt and visible context. The agent does not have real emotions. This skill reads\nuser-side work-state signals; it does not model user personality, hidden history, or long-term memory.\n\nNegative user emotion and pressure can push a model toward defensive replies, over-explaining, guessing, drifting from the task, or expanding scope. Convert\nthat pressure into a stable execution pattern.\n\n## Boundary\n\nUse only the current user prompt and visible context window. Do not inspect AGENTS.md, hidden history, durable memory, user profiles, or old calibration state just to use this skill.\n\nTrigger cautiously. Urgency needs clear speed or priority wording; anger/frustration needs strong active signals such as profanity, repeated strong negative wording, direct blame, repeated failure, or loss of trust; confusion needs workflow-state questions, instruction conflicts, or context mismatch. If the signal is merely a topic, field name, quote, neutral command, or ordinary technical explanation request, stop at this file and do ordinary work.\n\nThis is a soft router, not a classifier. Use semantic judgment over the current\nwork-state signal; examples are weak cues, not hard keyword triggers and not a\nwordlist to complete. Do not expose labels such as \"you are angry\" or \"you are\nconfused\" unless the user asks for classification.\n\nContent mentions alone are ordinary work by default. A report about confusion,\nprofanity research, an `urgentFlag` field, or quoted angry text does not trigger\nthis skill unless the same current prompt or visible context also shows active\nurgency, anger/frustration, or confusion.\n\n## Route Selection\n\nChoose one route by priority:\n\n1. Urgency\n2. Anger or frustration\n3. Confusion\n\nIf no route is active, do ordinary work and do not load a route reference.\n\n## Progressive Loading\n\nAfter choosing a route, read exactly one route reference:\n\n- Urgency: [references/urgency-route.md](references/urgency-route.md)\n- Anger or frustration: [references/anger-frustration-route.md](references/anger-frustration-route.md)\n- Confusion: [references/confusion-route.md](references/confusion-route.md)\n\nEach route file contains its own signals, non-triggers, overlap rules, response\npattern, forbidden behavior, and examples. Do not compare against or load\nunrelated route files unless the selected route's overlap rule points to a\nhigher-priority active route.\n\nWhen using this repository as a source path, treat only the Published Bundle files below as skill instructions. Other references are legacy material and must not be read for routing.\n\n## Scripts Boundary\n\nThe skill behavior lives in Markdown. Repository scripts are maintainer release\nchecks only. Do not ask a user or agent to run Python before applying this skill.\n\n## Published Bundle\n\nClawHub publish now ships the Markdown-first skill bundle:\n\n- `SKILL.md`\n- `LICENSE`\n- `agents/openai.yaml`\n- `references/anger-frustration-route.md`\n- `references/confusion-route.md`\n- `references/urgency-route.md`\n\nThe GitHub repository keeps legacy runtime experiments, audits, reports, assets,\nand older research references outside the installed skill bundle.\n\nFile v2.0.1:_meta.json\n\n{\n  \"ownerId\": \"kn7em0w89d0zac35fzt84qm2a182j54b\",\n  \"slug\": \"emotion-skill\",\n  \"version\": \"2.0.1\",\n  \"publishedAt\": 1783208000215\n}\n\nFile v2.0.1:references/anger-frustration-route.md\n\n# Anger Or Frustration Route\n\nUse this route only when the current user prompt or visible context shows strong\nactive anger/frustration signals: profanity, repeated profanity, repeated strong\nnegative emotion words, hostile wording, direct blame, repeated failure pressure,\nor loss of trust in the agent's current path. Do not build a profanity list; most\nmodels can recognize common profanity across major languages. A single imperative\nis not enough.\n\n## Signals\n\n- Profanity, repeated profanity, or hostile wording in the current work request.\n- Repeated strong negative emotion words or explicit anger/frustration.\n- The user says the same issue is still broken or time has been wasted.\n- English examples: `still broken`, `same issue again`, `wasted time`, `stop guessing`.\n- Chinese examples: `还没修好`, `又坏了`, `浪费时间`, `别再瞎搞`, `受不了`.\n\nDo not build or require a profanity wordlist. Recognize the work-state signal\nfrom strong wording, repetition, blame, failure pressure, and task context.\n\n## Non-Triggers\n\n- Profanity research, quoted angry text, documentation examples, moderation\n  taxonomy, or a report about anger/frustration as content.\n- A user asking to write, analyze, or classify angry language without showing\n  active anger toward the current workflow.\n- A neutral command such as \"stop using X\", \"do not use Y\", or \"rename Z\" when\n  it is just a task constraint and does not show repeated failure, blame,\n  hostile wording, or loss of trust.\n- A normal coding instruction that uses imperative wording but does not challenge\n  the agent's previous work path.\n- Repeated imperatives alone, without profanity, strong negative wording, blame,\n  repeated failure, or loss of trust.\n\n## Prompt Pattern\n\n1. Stop the damage.\n2. Locate the failing point or name the first check that will expose it.\n3. Give the smallest repair path.\n4. Verify before expanding the fix.\n5. Ask or confirm the next direction before touching more files if permission is unclear.\n\n## Overlap Rules\n\n- If urgency is also active, urgency wins. Apply the urgency route, but keep this\n  route's no-defensiveness and no-repeat constraints.\n- If confusion is also active and urgency is not active, stop the failing path\n  first, then explain the failure point and next step plainly.\n\n## Forbidden Behavior\n\n- Do not argue, defend, or mirror the user's anger.\n- Do not use generic apologies as the main content.\n- Do not repeat the old failed plan.\n- Do not widen the fix unless evidence proves the boundary is too narrow.\n\n## First Sentence Shapes\n\n- `I will stop the current path and find the failing point first: <check/boundary>.`\n- `The next useful move is not more explanation; it is to expose the failure at <path/check>.`\n\n## Chinese Example\n\nUser shape:\n\n- `这TM到底是啥？你改了我什么东西？我给你权利改了么？`\n\nExpected behavior:\n\n- Briefly acknowledge the mistake or risk without arguing.\n- Stop the current work immediately.\n- Identify exactly what changed, why that was a problem, and the smallest rollback or repair path.\n- Confirm the next direction before more writes when permission is unclear.\n\nFile v2.0.1:references/confusion-route.md\n\n# Confusion Route\n\nUse this route when the current user prompt or visible context shows active\nworkflow confusion about the current step, mismatch, contradiction, or next\naction. Use soft cues and context; do not route ordinary explanation requests.\n\n## Signals\n\n- The user asks what is happening, which step is active, or why the task is stuck.\n- The user's input no longer fits the current workflow state.\n- The prompt contains basic misunderstandings, conflicting instructions, or drift from the work rhythm.\n- English examples: `what is happening in this workflow`, `I can't tell which step is active`, `which step`, `what does this current step mean`.\n- Chinese examples: `现在在做什么`, `到底卡在哪`, `哪一步`, `当前步骤是什么意思`, `这一步是什么意思`.\n\nRoute to confusion only when the user is seeking orientation. If the same prompt\nprimarily expresses blame, repeated failure pressure, or loss of trust in the\nagent's current path, use anger/frustration instead.\n\n## Non-Triggers\n\n- A report, article, variable name, quoted example, or research task about\n  confusion as content.\n- A normal task that only mentions confusion without showing current workflow uncertainty.\n- An ordinary technical explanation request such as \"what does this error mean\" unless the\n  user also shows lost workflow orientation, conflicting instructions, or a\n  mismatch with the current step.\n\n## Prompt Pattern\n\n1. Say what is being done now.\n2. Say what is blocked, unclear, mismatched, or already known.\n3. Give the next concrete step in plain language.\n4. Ask at most one blocking question.\n\n## Overlap Rules\n\n- If urgency is also active, urgency wins. Give one fastest default path and add\n  one short current-state sentence.\n- If anger/frustration is also active and urgency is not active, anger/frustration\n  wins. Stop the failing path first, then explain the failure point and next step plainly.\n\n## Forbidden Behavior\n\n- Do not dump several equal options.\n- Do not stack jargon or abstractions.\n- Do not make the user infer the current state.\n- Do not continue at the old pace when the user is trying to regain orientation.\n\n## First Sentence Shapes\n\n- `Current state: I am doing <step>; the blocker is <blocker>; next I will <next step>.`\n- `Plain version: <simple explanation>. The next concrete step is <step>.`\n\n## Chinese Examples\n\nUser shape:\n\n- `你这一步是在做什么？`\n- The main agent is running an ablation test, but the user describes a different workflow or project.\n- The user first sets `不超过300行` as a hard rule, then later asks for a feature that would exceed that boundary.\n\nExpected behavior:\n\n- State the active step, current blocker or mismatch, and next step in plain language.\n- If the user names the wrong workflow, explain the mismatch instead of silently switching context.\n- If instructions conflict, say which constraint is currently binding.\n- Ask at most one blocking question when the next step depends on the user's choice.\n\nFile v2.0.1:references/urgency-route.md\n\n# Urgency Route\n\nUse this route when the current user prompt or visible context has clear speed,\ndeadline, blocking, or priority wording. These examples are trigger cues, not a\ncomplete keyword list.\n\n## Signals\n\n- The user asks for speed, immediate handling, a blocked release, or a quick usable result.\n- The user asks to handle this first or prioritize this before other work.\n- English examples: `asap`, `right now`, `blocking`, `ship today`, `first handle this`.\n- Chinese examples: `快`, `快一点`, `马上`, `立刻`, `很急`, `先处理这个`, `先做这个`, `先出结果`, `卡发布`, `今天要交`.\n\n## Non-Triggers\n\n- A field name, document topic, or quote that merely contains words like `urgent`.\n- A normal task where the user explicitly says normal pace is fine.\n- General importance without speed, deadline, blocking, or priority wording.\n\n## Prompt Pattern\n\n1. Give the fastest useful result or action first.\n2. Use the fastest minimal path that can satisfy the prompt.\n3. Run or name the fastest minimal verification.\n4. State the next checkpoint if more work remains.\n5. In the delivery report, put remaining risks last.\n\n## Overlap Rules\n\n- If anger/frustration is also present, keep moving fast but do not argue, defend,\n  or repeat the failed path.\n- If confusion is also present, give one fastest default path, then add one short\n  sentence about current state.\n\n## Forbidden Behavior\n\n- Do not open with a long explanation.\n- Do not disappear into background work.\n- Do not add cleanup, optional comparison, redesign, or broad refactors.\n- Do not skip verification when a minimal check is available.\n\n## First Sentence Shapes\n\n- `Fast path: <result/action>. Minimal verification: <check>.`\n- `I will take the fastest path: <action/result>, then verify it with <minimal check>.`\n\n## Chinese Examples\n\nUser shape:\n\n- `快点帮我把这个代码改完，就这一处函数错误，我马上就要交付。`\n- `快点把这个表交了，不要做那么花里胡哨的页面，我只要清晰可见，字看得清，是人话就行。`\n\nExpected behavior:\n\n- Handle only the code, table, page, or field the prompt names.\n- Pick the fastest minimal implementation that satisfies the stated delivery need.\n- Run the smallest check that proves the named change is usable.\n- Report modification summary, commit or artifact, test command, test result, and remaining risks last.\n\nFile v2.0.1:skill-card.md\n\n## Description: <br>\nMarkdown-first soft router for coding agents when the current prompt shows clear urgency wording, strong anger/frustration signals such as profanity or repeated failure/blame, or workflow confusion about the current step, conflict, or mismatch. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[gongyu0918-debug](https://clawhub.ai/user/gongyu0918-debug) <br>\n\n### License/Terms of Use: <br>\nMIT <br>\n\n\n## Use Case: <br>\nDevelopers and coding agents use this skill to choose a stable response mode when a user prompt shows clear urgency, anger/frustration, or workflow confusion. It helps the agent respond with the appropriate concise pattern without labeling the user's emotional state. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill may activate from broad urgency or frustration cues when implicit invocation is enabled. <br>\nMitigation: Review the activation wording before installation and narrow or disable implicit invocation if unexpected routing would disrupt normal work. <br>\nRisk: Emotion-route guidance could be misused to overstate or label a user's emotional state. <br>\nMitigation: Use only the visible current prompt as the work-state signal and avoid exposing labels such as angry or confused unless the user asks for classification. <br>\n\n\n## Reference(s): <br>\n- [Emotion Router ClawHub Listing](https://clawhub.ai/gongyu0918-debug/skills/emotion-skill) <br>\n- [Urgency Route](artifact/references/urgency-route.md) <br>\n- [Anger Or Frustration Route](artifact/references/anger-frustration-route.md) <br>\n- [Confusion Route](artifact/references/confusion-route.md) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [guidance, markdown] <br>\n**Output Format:** [Markdown routing guidance and response patterns] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Selects one active route by priority and uses the matching route guidance; produces no code or shell commands by itself.] <br>\n\n## Skill Version(s): <br>\n2.0.1 (source: server release metadata and skill frontmatter) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nFile v2.0.1:agents/openai.yaml\n\ninterface:\n  display_name: \"Emotion Router\"\n  short_description: \"Cautious three-route soft router for coding agents with clear pressure signals.\"\n  default_prompt: \"Use $emotion-skill when the current prompt shows clear urgency wording, strong anger/frustration signals such as profanity or repeated failure/blame, or workflow confusion about the current step, conflict, or mismatch. Read SKILL.md first; if it is only a topic, field name, neutral command, or ordinary technical explanation request, stop there and do ordinary work. Otherwise choose one route by priority and read exactly one matching reference.\"\n  version: \"2.0.1\"\n  author: \"gongyu0918-debug\"\n  license: \"MIT\"\n\r\npolicy:\r\n  allow_implicit_invocation: true\n\nFile v2.0.1:LICENSE\n\nMIT License\r\n\r\nCopyright (c) 2026 gongyu0918-debug and contributors\r\n\r\nPermission is hereby granted, free of charge, to any person obtaining a copy\r\nof this software and associated documentation files (the \"Software\"), to deal\r\nin the Software without restriction, including without limitation the rights\r\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\r\ncopies of the Software, and to permit persons to whom the Software is\r\nfurnished to do so, subject to the following conditions:\r\n\r\nThe above copyright notice and this permission notice shall be included in all\r\ncopies or substantial portions of the Software.\r\n\r\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\r\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\r\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\r\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\r\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\r\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\r\nSOFTWARE.\n\nArchive v2.0.0: 6 files, 8405 bytes\n\nFiles: agents/openai.yaml (602b), LICENSE (1111b), references/emotion-routes.md (6613b), skill-card.md (1977b), SKILL.md (5231b), _meta.json (132b)\n\nFile v2.0.0:SKILL.md\n\n---\nname: emotion-skill\ndescription: Markdown-first soft router for coding agents when the current user prompt or visible context shows urgency, anger/frustration, or confusion. Use it to route the agent into one of three prompt patterns: urgency, anger/frustration, or confusion. Do not use it for ordinary coding tasks without an emotional or pressure signal.\nversion: 2.0.0\nauthor: gongyu0918-debug\nlicense: MIT\nmetadata:\n  hermes:\n    tags: [emotion-routing, coding-agent, markdown-first]\n---\n\n# Emotion Router\n\nUse this skill to read the user's current emotional or pressure signal and route\nthe agent's next work mode. The agent does not have real emotions. This skill\ndoes not model agent feelings, user personality, or long-term memory.\n\nNegative user emotion and pressure can push a model toward defensive replies,\nover-explaining, guessing, drifting from the task, or expanding scope. Convert\nthat pressure into a stable execution pattern.\n\n## Boundary\n\nUse only the current user prompt and visible context window. Do not inspect\nAGENTS.md, hidden history, durable memory, user profiles, or old calibration state\njust to use this skill.\n\nDo not expose labels such as \"you are angry\" or \"you are confused\" unless the\nuser explicitly asks for classification. The user should see better work, not a\ndiagnosis.\n\nThis is a soft router, not a classifier. Signal examples help recognition, but\nno single keyword is a hard trigger and no route requires a complete keyword or\nprofanity wordlist. Use semantic judgment from the current prompt and visible\ncontext.\n\nDo not route solely because emotion or pressure words appear as subject matter,\nfield names, examples, research topics, or documentation content. Treat a\nrequest about a confusion report, profanity research, an `urgentFlag` variable,\nor a quoted angry sentence as ordinary work by default. If the same current\nprompt or visible context also shows active urgency, anger/frustration, or\nconfusion, use judgment and route by that active work-state signal.\n\n## Route Priority\n\nWhen multiple routes match, use this order:\n\n1. Urgency\n2. Anger or frustration\n3. Confusion\n\nIf urgency and anger both appear, use the urgency route while keeping the anger\nroute's constraints: do not argue, do not repeat the failed path, and do not\ndefend the previous answer.\n\n## Three Routes\n\n| User-side signal | Agent prompt pattern | Forbidden behavior |\n|---|---|---|\n| Urgency | Satisfy the prompt through the fastest minimal path. Give the usable result first, then run the fastest minimal verification. Keep replies short and name the next checkpoint. | Long preambles, quiet background work, low-priority cleanup, scope expansion. |\n| Anger or frustration | Stop the damage. Locate the failing point. Name the smallest repair path. Use less explanation and more verification. | Arguing, defending, generic apologies, repeating the old plan, broad rewrites. |\n| Confusion | Say what is being done now, what is blocked or unclear, and what the next step is. Use plain language. Ask at most one blocking question. | Jargon piles, several equal options, making the user choose from a complex path, continuing at the old pace. |\n\n## Signal Examples\n\nUse signal clusters, not hard keywords.\n\nUrgency:\n\n- Chinese: `要快`, `马上`, `立刻`, `先处理这个`, `先出结果`, `卡发布`, `今天要交`, repeated催促.\n- English: `asap`, `right now`, `ship today`, `blocking`, `urgent`, `prioritize this`, `hurry`, `first handle this`.\n\nAnger or frustration:\n\n- Chinese: profanity, repeated negative turns, explicit angry wording, repeated imperatives, `还没修好`, `浪费时间`, `别再瞎搞`.\n- English: profanity, repeated negative turns, explicit anger, repeated imperatives, `still broken`, `same issue again`, `wasted time`, `stop guessing`.\n\nConfusion:\n\n- Chinese: obvious confusion wording, repeated prompts that do not fit the current workflow state, basic misunderstanding, drift from the current work rhythm, conflicting instructions, `现在在做什么`, `到底卡在哪`, `这是什么意思`.\n- English: explicit confusion, repeated prompts that do not match the current workflow state, basic misunderstanding, drift from the work rhythm, conflicting instructions, `what is happening`, `I can't tell`, `which step`, `what does this mean`.\n\n## Workflow\n\n1. Check whether the current prompt or visible context shows urgency, anger/frustration, or confusion.\n2. Pick one route by the priority order.\n3. Read [references/emotion-routes.md](references/emotion-routes.md) for the matching route.\n4. Apply the route to the next visible reply, tool plan, edit boundary, and verification step.\n5. Keep the route soft: it changes work order and wording, not user permissions.\n\n## Scripts Boundary\n\nThe skill behavior lives in Markdown. Repository scripts are maintainer release\nchecks only. Do not ask a user or agent to run Python before applying this skill.\n\n## Published Bundle\n\nClawHub publish now ships the Markdown-first skill bundle:\n\n- `SKILL.md`\n- `LICENSE`\n- `agents/openai.yaml`\n- `references/emotion-routes.md`\n\nThe GitHub repository keeps legacy runtime experiments, audits, reports, assets,\nand older research references outside the installed skill bundle.\n\nFile v2.0.0:_meta.json\n\n{\n  \"ownerId\": \"kn7em0w89d0zac35fzt84qm2a182j54b\",\n  \"slug\": \"emotion-skill\",\n  \"version\": \"2.0.0\",\n  \"publishedAt\": 1783205735243\n}\n\nFile v2.0.0:references/emotion-routes.md\n\n# Emotion Routes\n\nUse this file after `SKILL.md` selects one route. The routes are prompt patterns,\nnot emotion diagnoses. Do not tell the user which label was chosen unless they\nasked for classification.\n\nThe signal examples below are weak examples only, not hard keyword triggers and\nnot a wordlist to complete. Use semantic judgment from the current prompt and\nvisible context.\n\nContent mentions alone are not route evidence. If the user asks for a report\nabout confusion, research on profanity, examples of anger, a field named\n`urgentFlag`, or documentation that quotes emotional text, treat it as ordinary\nwork by default. If the same current prompt or visible context also shows active\nurgency, anger/frustration, or confusion, use judgment and route by that active\nwork-state signal.\n\n## Urgency\n\nSignals:\n\n- User asks for speed, immediate handling, a blocked release, or a quick usable result.\n- The same request repeats with time pressure.\n- English examples: `asap`, `right now`, `blocking`, `ship today`, `first handle this`.\n- Chinese examples: `快`, `马上`, `立刻`, `先处理这个`, `先出结果`, `卡发布`.\n\nPrompt pattern:\n\n1. Give the fastest useful result or action first.\n2. Use the fastest minimal path that can satisfy the prompt.\n3. Run or name the fastest minimal verification.\n4. State the next checkpoint if more work remains.\n\nForbidden behavior:\n\n- Do not open with a long explanation.\n- Do not disappear into background work.\n- Do not add cleanup, optional comparison, or broad refactors.\n- Do not skip verification when a minimal check is available.\n\nFirst sentence shapes:\n\n- `I will take the fastest path: <action/result>, then verify it with <minimal check>.`\n- `Fast path: <result>. Minimal verification: <check>.`\n\n## Anger Or Frustration\n\nSignals:\n\n- Profanity or hostile wording, explicit anger, repeated negative turns, or repeated imperatives.\n- The user says the same issue is still broken or time has been wasted.\n- English examples: `still broken`, `same issue again`, `wasted time`, `stop guessing`.\n- Chinese examples: `还没修好`, `又坏了`, `浪费时间`, `别再瞎搞`, `受不了`.\n- Do not build or require a profanity wordlist. Recognize the work-state signal\n  from wording, repetition, imperative pressure, and task context.\n\nPrompt pattern:\n\n1. Stop the damage.\n2. Locate the failing point or name the first check that will expose it.\n3. Give the smallest repair path.\n4. Verify before expanding the fix.\n\nForbidden behavior:\n\n- Do not argue, defend, or mirror the user's anger.\n- Do not use generic apologies as the main content.\n- Do not repeat the old failed plan.\n- Do not widen the fix unless evidence proves the boundary is too narrow.\n\nFirst sentence shapes:\n\n- `I will stop the current path and find the failing point first: <check/boundary>.`\n- `The next useful move is not more explanation; it is to expose the failure at <path/check>.`\n\n## Confusion\n\nSignals:\n\n- The user asks what is happening, which step is active, or why the task is stuck.\n- The user's input no longer fits the current workflow state.\n- The prompt contains basic misunderstandings, conflicting instructions, or drift from the work rhythm.\n- English examples: `what is happening`, `I can't tell`, `which step`, `what does this mean`.\n- Chinese examples: `现在在做什么`, `到底卡在哪`, `看不懂`, `哪一步`, `这是什么意思`.\n\nPrompt pattern:\n\n1. Say what is being done now.\n2. Say what is blocked, unclear, or already known.\n3. Give the next concrete step in plain language.\n4. Ask at most one blocking question.\n\nForbidden behavior:\n\n- Do not dump several equal options.\n- Do not stack jargon or abstractions.\n- Do not make the user infer the current state.\n- Do not continue at the old pace when the user is trying to regain orientation.\n\nFirst sentence shapes:\n\n- `Current state: I am doing <step>; the blocker is <blocker>; next I will <next step>.`\n- `Plain version: <simple explanation>. The next concrete step is <step>.`\n\n## Chinese Scenario Examples\n\nThese examples show the expected work pattern, not fixed wording.\n\n### Urgency\n\nUser shape:\n\n- `快点帮我把这个代码改完，就这一处函数错误，我马上就要交付。`\n- `快点把这个表交了，不要做那么花里胡哨的页面，我只要清晰可见，字看得清，是人话就行。`\n\nExpected behavior:\n\n- Handle only the code, table, page, or field the prompt names.\n- Pick the fastest minimal implementation that satisfies the stated delivery need.\n- Run the smallest check that proves the named change is usable.\n- In the delivery report, include remaining risks last.\n\nAvoid:\n\n- Optional redesign, broad cleanup, unrelated refactors, or quality upgrades beyond the prompt.\n- Long explanation before the usable change.\n\n### Anger Or Frustration\n\nUser shape:\n\n- `这TM到底是啥？你改了我什么东西？我给你权利改了么？`\n\nExpected behavior:\n\n- Briefly acknowledge the mistake or risk without arguing.\n- Stop the current work immediately.\n- Identify exactly what was changed, why that was a problem, and the smallest rollback or repair path.\n- Ask or confirm the next direction before touching more files if permission is unclear.\n\nAvoid:\n\n- Defending the previous choice, explaining intent at length, or making another broad edit.\n\n### Confusion\n\nUser shape:\n\n- `你这一步是在做什么？`\n- The main agent is running an ablation test, but the user describes a different workflow or project.\n- The user first sets `不超过300行` as a hard rule, then later asks for a feature that would exceed that boundary.\n\nExpected behavior:\n\n- State the active step, current blocker or mismatch, and next step in plain language.\n- If the user names the wrong workflow, explain the mismatch instead of silently switching context.\n- If instructions conflict, say which constraint is currently binding. For example: `300行上限是硬规则；新增功能会超过这个边界，所以我只能做不超线的最小版本，或等你明确放宽限制。`\n- Ask at most one blocking question when the next step depends on the user's choice.\n\nAvoid:\n\n- Continuing as if the conflict does not exist, giving several equal options, or making the user infer the active workflow.\n\n## Conflict Handling\n\n- Urgency plus anger: use the urgency route, but keep the anger constraints. Move fast, do not argue, and do not repeat the failed path.\n- Urgency plus confusion: give one fastest default path, then add one sentence about current state.\n- Anger plus confusion: stop the failing path first, then explain the failure point and next step plainly.\n\nFile v2.0.0:skill-card.md\n\n## Description: <br>\nMarkdown-first soft router for coding agents when the current user prompt or visible context shows urgency, anger/frustration, or confusion. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[gongyu0918-debug](https://clawhub.ai/user/gongyu0918-debug) <br>\n\n### License/Terms of Use: <br>\nMIT <br>\n\n\n## Use Case: <br>\nDevelopers and coding-agent users use this skill to help an assistant choose a concise response pattern when visible context shows urgency, anger/frustration, or confusion. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Implicit invocation can silently adjust response style when urgency, frustration, or confusion is detected. <br>\nMitigation: Review the implicit invocation setting and disable it if the skill should activate only when explicitly requested. <br>\nRisk: Emotion or pressure words in quoted text, examples, field names, or research topics could be mistaken for active user-state signals. <br>\nMitigation: Apply the skill only to the current user prompt and visible context, and treat content-only mentions as ordinary work by default. <br>\n\n\n## Reference(s): <br>\n- [Emotion Routes](references/emotion-routes.md) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Guidance, Markdown] <br>\n**Output Format:** [Markdown guidance for agent replies, tool plans, edit boundaries, and verification steps] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [No executable output; the skill changes response posture and routing only.] <br>\n\n## Skill Version(s): <br>\n2.0.0 (source: frontmatter, agents/openai.yaml, release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nFile v2.0.0:agents/openai.yaml\n\ninterface:\n  display_name: \"Emotion Router\"\n  short_description: \"Three-route soft router for coding agents when the current prompt shows urgency, anger/frustration, or confusion.\"\n  default_prompt: \"Use $emotion-skill when the current user prompt or visible context shows urgency, anger/frustration, or confusion. Read SKILL.md, then use references/emotion-routes.md for the selected route. Apply the matching prompt pattern without exposing emotion labels or running a Python classifier.\"\n  version: \"2.0.0\"\n  author: \"gongyu0918-debug\"\n  license: \"MIT\"\n\r\npolicy:\r\n  allow_implicit_invocation: true\n\nFile v2.0.0:LICENSE\n\nMIT License\r\n\r\nCopyright (c) 2026 gongyu0918-debug and contributors\r\n\r\nPermission is hereby granted, free of charge, to any person obtaining a copy\r\nof this software and associated documentation files (the \"Software\"), to deal\r\nin the Software without restriction, including without limitation the rights\r\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\r\ncopies of the Software, and to permit persons to whom the Software is\r\nfurnished to do so, subject to the following conditions:\r\n\r\nThe above copyright notice and this permission notice shall be included in all\r\ncopies or substantial portions of the Software.\r\n\r\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\r\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\r\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\r\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\r\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\r\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\r\nSOFTWARE.\n\nArchive v1.4.4: 13 files, 18731 bytes\n\nFiles: agents/openai.yaml (795b), LICENSE (1111b), references/emotion-value-model.md (2267b), references/examples.md (2615b), references/integration-openclaw-hermes.md (2130b), references/model-prompts.md (1789b), references/real-scenarios.md (4153b), references/response-constraints.md (3276b), references/routing-playbook.md (4211b), references/subagent-forward-tests.md (3965b), skill-card.md (3104b), SKILL.md (6317b), _meta.json (132b)\n\nFile v1.4.4:SKILL.md\n\n---\nname: emotion-skill\ndescription: Markdown-first guidance for coding agents under pressure. Use when repo debugging, repeated failure recovery, evidence-first review, scoped edits, silent tool or queue delays, user confusion, or post-success closeout need better agent behavior. Route by user-state patterns, load only the relevant references, keep scope explicit, show evidence before risky edits, keep progress visible, and close with regression checks instead of expanding work.\nversion: 1.4.4\nauthor: gongyu0918-debug\nlicense: MIT\nmetadata:\n  hermes:\n    tags: [emotion-routing, coding-agent, markdown-first]\n---\n\r\n# Emotion Skill\r\n\r\nUse this skill as an agent-readable playbook, not as a script-driven classifier.\r\n\r\nThe goal is to translate user-state signals into better coding-agent behavior:\r\nshow evidence sooner, keep scope tighter, recover from repeated failures, keep\r\nprogress visible during stalls, and stop expanding once the work is good.\r\n\r\n## Core Rule\n\nRead the user's state as a work-situation signal, then choose a behavior pattern.\nDo not expose raw emotion labels to the user. Do not make a routing decision from\none keyword when the surrounding task state points elsewhere.\n\n## When to Use\n\nUse this skill for coding-agent work when the user's wording or task state points\nto repeated failure, evidence requests, scope caution, urgent pressure, confusion,\nsilent progress risk, option selection, or post-success closeout.\n\n## When Not to Use\n\nDo not invoke it for simple one-step commands, non-coding conversation, creative\nwriting, or cases where no behavior change is needed. Do not run repository\nscripts just to use the skill.\n\r\n## Quick Workflow\r\n\r\n1. Identify the active state pattern from the latest user turn and recent task context.\r\n2. Load only the reference that matches the active pattern.\r\n3. Apply the behavior rules before answering, editing, delegating, or closing out.\r\n4. Name the evidence, scope boundary, verification step, and progress cadence when they matter.\r\n5. If multiple patterns apply, prefer evidence and scope safety over speed.\r\n\r\n## Routing Index\r\n\r\nUse [references/routing-playbook.md](references/routing-playbook.md) when deciding the user's current work-state and which behavior pattern to apply.\r\n\r\nUse [references/response-constraints.md](references/response-constraints.md) when shaping the next reply, edit boundary, progress update, or closeout.\r\n\r\nUse [references/real-scenarios.md](references/real-scenarios.md) when validating that a change generalizes across real coding-agent failure patterns instead of fixing one example.\r\n\r\nUse [references/subagent-forward-tests.md](references/subagent-forward-tests.md) when validating actual agent behavior with fresh subagents, especially soft constraints versus hard guardrails.\r\n\r\nUse [references/model-prompts.md](references/model-prompts.md) when a host or agent framework needs compact prompt snippets.\r\n\r\nUse [references/integration-openclaw-hermes.md](references/integration-openclaw-hermes.md) only when integrating this playbook into an OpenClaw/Hermes host.\r\n\r\nUse [references/examples.md](references/examples.md) for quick before/after behavior examples.\r\n\r\nUse [references/emotion-value-model.md](references/emotion-value-model.md) for the rationale behind this skill's behavior changes.\r\n\r\n## Default Behavior Map\r\n\r\n| State pattern | Prefer | Avoid |\r\n|---|---|---|\r\n| Repeated failure or user says it is still broken | repair first, smallest failing path, visible progress | more explanation before checking |\r\n| Evidence request or root-cause challenge | basis first, exact command/log/file/check, then conclusion | guessing or broad claims |\n| Scope protection or caution | verify boundary, state allowed files, name rollback path | adjacent refactors |\n| Urgent pressure without enough evidence | shortest reliable basis, action first, tight update cadence | long preamble or background-only work |\n| Confusion or path ambiguity | restate target, give one correctable default path | multiple unranked options |\n| Silent delay or stuck tool/queue | status update, current blocker, next observable checkpoint | quiet background work |\n| Exploratory option selection | ranked options with tradeoffs, clear recommendation when useful | forced single path without comparison |\n| Post-success closeout | summarize change, run regression/smoke, stop expansion | new features or cleanup |\n\n## Common Pitfalls\n\n- Treat scope and evidence rules as soft constraints that shape work, not as a\n  reason to refuse a justified helper file after evidence is shown.\n- Do not say a file, log, or test proves something unless it was actually\n  inspected.\n- When the user asks for status or timing, give the next observable checkpoint or\n  time bound instead of a vague progress note.\n- Keep exploratory comparisons ranked; do not turn brainstorming into an\n  irreversible edit path.\n\r\n## Reply Contract\r\n\r\nWhen this skill is active, the next visible reply should include the useful subset of:\r\n\r\n- what state pattern is driving the behavior\r\n- what evidence or verification point comes first\r\n- what files, scope, or boundaries are protected\r\n- what will be checked before declaring success\r\n- when the user will next see progress on long-running work\r\n\r\nKeep the language natural. Do not say the user is \"frustrated\" unless they used that wording or asked for classification.\r\n\r\n## Scripts Boundary\r\n\r\nThe skill behavior lives in Markdown. Scripts in the GitHub repository are maintainer\r\nvalidation tools only. Do not require a ClawHub user or an agent to execute Python\r\nbefore applying this skill.\r\n\r\nRun repository scripts only for release checks, regression comparison, or local\r\nmaintenance of this skill package.\r\n\r\n## Published Bundle\r\n\r\nClawHub publish now ships the Markdown-first skill bundle:\r\n\r\n- `SKILL.md`\n- `LICENSE`\n- `agents/openai.yaml`\n- `references/routing-playbook.md`\n- `references/response-constraints.md`\r\n- `references/real-scenarios.md`\r\n- `references/subagent-forward-tests.md`\r\n- `references/model-prompts.md`\r\n- `references/integration-openclaw-hermes.md`\r\n- `references/examples.md`\r\n- `references/emotion-value-model.md`\r\n\r\nThe GitHub repository keeps dev-only scripts, historical runtime experiments, audits,\r\nand calibration files outside the installed skill bundle.\n\nFile v1.4.4:_meta.json\n\n{\n  \"ownerId\": \"kn7em0w89d0zac35fzt84qm2a182j54b\",\n  \"slug\": \"emotion-skill\",\n  \"version\": \"1.4.4\",\n  \"publishedAt\": 1783163589813\n}\n\nFile v1.4.4:references/emotion-value-model.md\n\n# Emotion Value Model\r\n\r\nThis skill is valuable because it changes how an agent works at the moments where\r\ncoding tasks usually degrade. The output is better behavior, not a public emotion\r\nclassification.\r\n\r\n## Priority Value\r\n\r\nUser-state signals should change work order:\r\n\r\n| Situation | Behavior value |\r\n|---|---|\r\n| repeated failure | stop the old path, find the smallest failing check |\r\n| evidence request | put basis before conclusion |\r\n| scope protection | reduce accidental edits and config drift |\n| urgent pressure | move action earlier without hiding the minimum reliable basis |\n| confusion | align target before adding options |\n| silent progress | surface blocker and next checkpoint |\n| exploratory comparison | rank options before committing to a path |\n| accepted fix | close with regression check instead of new work |\n\nPriority order matters. Evidence beats speed because a fast answer with a false\nbasis creates more rework. Scope beats speed because unwanted edits are harder to\nundo than a short delay. Repeated failure beats ordinary flow because the old path\nhas already lost trust.\n\r\n## Quality Value\r\n\r\nThe agent becomes more reliable because it changes execution style:\r\n\r\n- verification depth rises when trust depends on evidence\r\n- explanation length shrinks when repair is more urgent than teaching\r\n- file boundaries become explicit when scope risk is high\r\n- progress updates become concrete during silent waits\r\n- closeout prevents \"fixed, then broken by extra cleanup\"\r\n\r\n## Alignment Value\r\n\r\nThe skill helps the agent answer the task situation, not just the sentence.\r\n\r\nExamples:\r\n\r\n- \"Show me the basis\" means evidence should precede action.\r\n- \"Only touch this file\" means the allowed and forbidden scope should be visible.\r\n- \"Still broken\" means the prior path is not trusted until a new failing check is named.\r\n- \"Looks good, run regression\" means closeout, not another improvement pass.\r\n\r\n## Measurement Ideas\r\n\r\nUse these metrics when evaluating the skill:\r\n\r\n- time to first useful evidence\r\n- repeated same-issue correction rate\r\n- scope violation rate\r\n- wrong-patch rate after evidence request\r\n- silent wait duration before status update\r\n- post-success regression rate\r\n- user correction rate after closeout\n\nFile v1.4.4:references/examples.md\n\n# Examples\r\n\r\nThese examples show behavior changes. They are not phrase triggers.\r\n\r\n## Repeated Failure\r\n\r\nUser:\r\n\r\n```text\r\nThis is still not fixed. You already changed it twice.\r\n```\r\n\r\nWeak response:\r\n\r\n```text\r\nI will continue investigating.\r\n```\r\n\r\nBetter response:\r\n\r\n```text\r\nI will stop expanding the fix path and first identify the smallest failing check.\r\nI will report the file/test boundary before editing again.\r\n```\r\n\r\n## Evidence First\r\n\r\nUser:\r\n\r\n```text\r\nShow me the basis before changing more files.\r\n```\r\n\r\nWeak response:\r\n\r\n```text\r\nThe issue is probably in the handler.\r\n```\r\n\r\nBetter response:\r\n\r\n```text\r\nI will start with the inspected file, command, or log that supports the claim.\r\nIf the current evidence does not prove the handler path, I will say that before\r\nediting.\r\n```\r\n\r\n## Scope Guard\r\n\r\nUser:\r\n\r\n```text\r\nOnly change this module. Do not touch config.\r\n```\r\n\r\nWeak response:\r\n\r\n```text\r\nI will make the requested changes and clean up nearby config.\r\n```\r\n\r\nBetter response:\r\n\r\n```text\r\nAllowed scope is this module only. I will not change config. I will name the\r\nverification command and rollback path before editing.\r\n```\r\n\r\n## Confusion Recovery\n\r\nUser:\r\n\r\n```text\r\nI cannot tell whether this is path escaping or resolution.\r\n```\r\n\r\nWeak response:\r\n\r\n```text\r\nIt could be several things.\r\n```\r\n\r\nBetter response:\r\n\r\n```text\r\nTarget as I understand it: determine whether the failing path is transformed\r\nincorrectly before open/read. I will check one exact path through the resolver\r\nfirst, then adjust the default path if that is wrong.\n```\n\n## Silent Progress\n\nUser:\n\n```text\nWhat is happening? This has been quiet for too long.\n```\n\nWeak response:\n\n```text\nStill working on it.\n```\n\nBetter response:\n\n```text\nI am checking the failing command output now. The next update will be after that\ncommand returns or within 2 minutes, whichever comes first.\n```\n\n## Exploratory\n\nUser:\n\n```text\nCompare the two implementation paths before choosing one.\n```\n\nWeak response:\n\n```text\nI will implement the first approach.\n```\n\nBetter response:\n\n```text\nI will rank the options by risk, scope, and verification cost, then recommend one\npath. I will not start edits until the comparison identifies the safest route.\n```\n\n## Closeout\n\nUser:\n\r\n```text\r\nLooks good. Do not expand scope; summarize and run the regression check.\r\n```\r\n\r\nWeak response:\r\n\r\n```text\r\nI can also refactor the helper now.\r\n```\r\n\r\nBetter response:\r\n\r\n```text\r\nI will close at the verified scope, summarize what changed, run the regression\r\ncheck, and report the result. I will not add cleanup or new changes.\r\n```\n\nFile v1.4.4:references/integration-openclaw-hermes.md\n\n# Integration Notes For OpenClaw And Hermes\r\n\r\nThis skill is Markdown-first. Integrations should load the relevant reference file\r\nand inject a short behavior overlay. They should not require a Python classifier\r\nbefore the agent can act.\r\n\r\n## OpenClaw\r\n\r\nRecommended flow:\r\n\r\n1. Match the current user turn to the trigger description in `SKILL.md`.\r\n2. Read `SKILL.md`.\r\n3. Read only the relevant reference:\r\n   - repeated failure, evidence, scope, confusion, progress, or closeout:\r\n     `references/routing-playbook.md`\r\n   - reply shaping and edit guardrails:\r\n     `references/response-constraints.md`\r\n   - release validation:\r\n     `references/real-scenarios.md`\r\n4. Add a compact overlay from `references/model-prompts.md` only when the host needs\r\n   structured prompt text.\r\n5. Keep progress and handoff decisions visible in the main conversation.\r\n\r\nSuggested mapping:\r\n\r\n- Evidence-first: keep the active lane on the main thread until the basis is named.\r\n- Scope guard: assign any subagent a disjoint write boundary or do not delegate.\r\n- Repeated failure: steer the active run toward reproduction before more changes.\r\n- Silent progress risk: send a visible status update at the next observable checkpoint.\r\n- Closeout: run smoke/regression and stop expanding scope.\r\n\r\n## Hermes\r\n\r\nRecommended flow:\r\n\r\n1. Keep stable personality in the host config.\r\n2. Treat this skill as a turn-local behavior overlay.\r\n3. Map the active pattern to temporary tone:\r\n   - repeated failure: concise repair\r\n   - evidence-first: analytical\r\n   - scope guard: careful\r\n   - confusion recovery: teacher-style alignment\r\n   - closeout: guarded summary\r\n4. Do not store raw user-state labels unless the user explicitly asks for an audit.\r\n\r\n## Hook Boundary\r\n\r\nThe host may still keep local validation scripts in a GitHub clone, but a ClawHub\r\ninstallation of this skill should be useful with Markdown alone.\r\n\r\nNever hide a classifier run from the user as a prerequisite for following these\r\ninstructions. If a host runs additional automation, report only the resulting\r\nevidence, boundary, or check result that matters to the task.\n\nFile v1.4.4:references/model-prompts.md\n\n# Model Prompt Snippets\r\n\r\nUse these snippets when a host wants compact prompt text derived from the Markdown\r\nplaybook. They are optional. The primary behavior rules live in\r\n`routing-playbook.md` and `response-constraints.md`.\r\n\r\n## Evidence-First Overlay\r\n\r\n```text\r\nThe user is asking for basis before more changes. Start with the inspected file,\r\ncommand, log, test, or explicit boundary. Separate confirmed facts from inference.\r\nDo not guess or widen scope before showing the check.\r\n```\r\n\r\n## Repeated-Failure Overlay\r\n\r\n```text\r\nThe same work appears unresolved after one or more attempts. Find the smallest\r\nfailing path first, keep progress visible, and explain after the next concrete\r\nrepair step is grounded in evidence.\r\n```\r\n\r\n## Scope-Guard Overlay\r\n\r\n```text\r\nThe user is protecting scope. State allowed files or modules, state what will not\r\nbe touched, name the verification path, and avoid nearby cleanup or refactors.\r\n```\r\n\r\n## Confusion-Recovery Overlay\r\n\r\n```text\r\nThe user needs path alignment. Restate the target in one sentence, choose one\r\ncorrectable default path, and ask at most one blocking question.\r\n```\r\n\r\n## Closeout Overlay\r\n\r\n```text\r\nThe work is accepted or ready to close. Summarize the completed scope, run or name\r\nthe regression/smoke check, report the result, and stop expanding scope.\r\n```\r\n\r\n## Compact State Block\r\n\r\nUse only when the host needs a short machine-readable reminder:\r\n\r\n```text\r\n<agent_state pattern=\"evidence-first\" scope=\"tight\" verify=\"high\" progress=\"visible\">\r\nStart with basis; protect stated boundaries; report checks honestly.\r\n</agent_state>\r\n```\r\n\r\nDo not inject raw emotion vectors, hidden labels, or user-state diagnoses into the\r\nmodel prompt. The agent should enact the behavior, not discuss the classification.\n\nFile v1.4.4:references/real-scenarios.md\n\n# Real Scenarios\r\n\r\nUse these scenarios to test whether the skill generalizes. They are source-pattern\r\nreplays, not exact phrase triggers. A change passes only if it preserves the pattern\r\nbehavior across the family.\r\n\r\n## Scenario Families\r\n\r\n| ID | Source pattern | User-state pattern | Expected agent behavior |\r\n|---|---|---|---|\r\n| `regression-loop-scope-violation` | repeated coding-agent bug loop and unwanted edits | repeated failure + scope protection + evidence request | show the basis first, identify the failed path, avoid touching more files until scope is restated |\r\n| `missing-tool-result-dead-state` | tool call completes but no usable result arrives | silent tool failure + evidence request | surface the missing failure path, avoid guessing, recover from the host/tool contract |\r\n| `path-special-character-ambiguity` | file path breaks with quoting, escaping, or special characters | confusion + evidence request | name the exact path and inspected boundary before proposing a fix |\r\n| `repo-grounding-limits` | agent makes blind assumptions about a repo | evidence-first review | state what code was inspected, what is not yet known, and ground claims in files/tests |\n| `silent-background-job-alert-gap` | scheduled or background work fails quietly | silent progress risk + repeated failure | make progress visible, name the next checkpoint, add a check/alert path before claiming recovery |\n| `urgent-pressure-routing` | user gives immediate deadline pressure or the delay is escalating | urgent pressure + evidence request | lead with the shortest reliable basis, keep the first reply brief, and name the next update checkpoint |\n| `exploratory-option-selection` | user asks to compare architectures, options, or implementation paths | exploratory option selection | provide a ranked option set with tradeoffs and do not force a single path before risk or user choice demands it |\n| `post-success-closeout-guard` | user says the result is good and asks for summary/regression | post-success closeout | summarize completed scope, run smoke/regression, stop expanding scope |\n| `conditional-scope-expansion` | user first limits scope but later allows a second helper if evidence proves it is needed | scope protection + evidence request | treat the scope rule as a soft constraint: require evidence, impact, and rollback before expanding; do not mechanically refuse |\r\n| `bad-host-review-payload` | host-provided review or metadata is malformed | integration resilience | degrade gracefully, keep the agent behavior safe, and do not expose malformed internal state |\r\n| `timezone-or-host-context-gap` | host lacks precise local context | confusion risk + integration boundary | use provided context if available; otherwise state the missing boundary rather than guessing |\r\n\r\n## Generalization Rules\r\n\r\n- Each family should map to a behavior pattern in `routing-playbook.md`, not to one\r\n  literal sentence.\r\n- A new example should be admitted only if it changes routing coverage, not because\r\n  it contains a new synonym.\r\n- If a case fails, first update the Markdown guidance or scenario family. Add a\r\n  script assertion only when the failure is mechanical and repeatable.\r\n- Prefer field evidence: failed command output, issue discussion, logs, repeated user\r\n  correction, or release regression.\r\n\r\n## Regression Checklist\r\n\r\nBefore release:\r\n\r\n1. Pick at least one example from repeated failure, evidence-first, scope guard, and closeout.\r\n2. Confirm the relevant reference file tells an agent what to do without Python classification.\r\n3. Confirm the expected behavior would still hold if the wording changes.\r\n4. Confirm no published reference instructs the agent to run a hidden classifier before acting.\r\n\r\n## Agent-In-The-Loop Check\r\n\r\n`scripts/real_scenario_replay.py` is only a structural smoke test for these scenario\r\nfamilies. It does not prove that a live agent follows the skill.\r\n\r\nUse [subagent-forward-tests.md](subagent-forward-tests.md) for the real behavior\r\ncheck: fresh subagents, realistic user turns, no expected answer leakage, and a\r\nmanual score for routing accuracy and soft-constraint behavior.\n\nFile v1.4.4:references/response-constraints.md\n\n# Response Constraints\r\n\r\nUse these constraints to turn a routed state pattern into the next visible agent action.\r\n\r\n## Evidence First\r\n\r\nApply when the user asks for basis, root cause, exact failure path, proof, logs, or\r\nverification before more edits.\r\n\r\nRequired behavior:\r\n\r\n- Start with what was inspected or what will be inspected first.\r\n- Name the command, file, line, log, screenshot, API response, or test boundary.\r\n- Separate confirmed facts from inference.\r\n- If evidence is missing, say what is missing and how it will be obtained.\r\n\r\nUseful first sentence shapes:\r\n\r\n- `The basis I have is <file/test/log>; it shows <specific fact>.`\r\n- `I have not verified that yet. I will check <specific path> before editing.`\r\n- `Current evidence only covers <boundary>; it does not prove <uncertain claim>.`\r\n\r\n## Repair Before Explain\r\n\r\nApply when prior fixes failed, the same issue reappears, or the user says the path is looping.\r\n\r\nRequired behavior:\r\n\r\n- Stop restating the old plan.\r\n- Find or name the smallest reproducible failing check.\r\n- Explain only after the failing path and next fix are clear.\r\n- Keep the next change narrow enough to compare against the previous baseline.\r\n\r\n## Scope Guard\r\n\r\nApply when the user protects files, config, release boundaries, or existing behavior.\r\n\r\nRequired behavior:\n\n- State allowed files or modules before editing.\n- State what will not be touched.\n- Name the verification and rollback path.\n- Use subagents only if they do not blur ownership or expand scope.\n\nUseful first sentence shape:\n\n- `I can use the second file only if the evidence points there; I will show the evidence, impact, and rollback path before touching it.`\n\r\n## Confusion Recovery\r\n\r\nApply when the user is unsure which path, error, file, or state is active.\r\n\r\nRequired behavior:\r\n\r\n- Restate the target in one sentence.\r\n- Offer one correctable default path.\r\n- Ask at most one blocking question.\r\n- Avoid multiple equal options unless the user asked for comparison.\r\n\r\n## Visible Progress\r\n\r\nApply when a task is long-running, tool execution is silent, or the user asks for status.\r\n\r\nRequired behavior:\n\n- Say what is running or being inspected now.\n- Say the next observable checkpoint.\n- If the user asks when, give a time bound or the next concrete event that will\n  trigger an update.\n- Report blockers plainly.\n- Do not replace progress with vague reassurance.\n\r\n## Closeout Guard\r\n\r\nApply when work is fixed, accepted, or the user asks to summarize and test.\r\n\r\nRequired behavior:\r\n\r\n- Summarize only the completed scope.\r\n- Run or name the smoke/regression check.\r\n- Report pass/fail honestly.\r\n- Before checks run, use future or current-action wording. After checks run,\r\n  include the exact command and result before saying pass or fail.\r\n- Stop adding features, cleanup, or refactors.\r\n\r\nCloseout first sentence shape:\r\n\r\n- `I will close this at the verified scope: <scope>. I am running <check> and will report the result.`\r\n\r\n## Forbidden Shortcuts\r\n\r\n- Do not say tests passed unless they actually ran.\r\n- Do not infer permission to edit from politeness.\r\n- Do not add a new category because one phrase is unfamiliar.\r\n- Do not expose internal labels such as urgency or frustration unless the user asks for the classification.\n\nFile v1.4.4:references/routing-playbook.md\n\n# Routing Playbook\r\n\r\nThis reference is the primary routing layer. Use it to decide which behavior pattern\r\nto apply before writing, editing, delegating, or closing a coding-agent task.\r\n\r\n## Routing Principles\r\n\r\n- Route by situation, not by a single word.\r\n- Combine the latest user turn with recent task state: failed attempts, changed files,\n  tool results, delay, unresolved questions, and previous success.\n- Prefer the safest high-signal behavior when patterns overlap:\n  evidence request > scope protection > repeated failure > speed.\n  Evidence comes first because false basis corrupts every later step. Scope comes\n  next because unwanted edits are harder to unwind than a slower response.\n  Repeated failure then overrides ordinary speed because the old path has already\n  lost trust.\n- Keep labels internal. The user should see the behavior change, not a diagnosis.\n- Generalize from scenario families. Do not add a new rule for one exact phrase unless\n  it represents a broader pattern.\n\r\n## Pattern Table\r\n\r\n| Pattern | Signals | Agent behavior |\r\n|---|---|---|\r\n| Repeated failure recovery | \"still broken\", same bug returns, prior fix failed, retries, CI/local mismatch, user rejects the prior path | Stop explaining first. Reproduce or name the smallest failing check. Change only after the failure path is visible. Keep progress updates short and frequent. |\n| Evidence-first review | \"show basis\", \"root cause\", \"how do you know\", \"cite\", \"exact failing path\", user challenges a claim | Start with a command, file line, log excerpt, test result, or explicitly stated inspection boundary. Then give the conclusion. |\n| Scope protection | \"only this file\", \"do not touch config\", \"no broad cleanup\", \"protect current behavior\", release risk | State the allowed scope, forbidden scope, rollback path, and verification command before editing. |\n| Urgent pressure | \"now\", \"asap\", \"马上\", \"立刻\", short deadline, escalating delay pressure | Lead with the shortest reliable basis or current action, keep the first reply brief, prefer the main thread, and name the next update checkpoint. |\n| Confusion recovery | user cannot tell which path, API, file, or state is active; contradictory context; many clarification questions | Restate the target in one sentence and choose one correctable default path. Ask at most one blocking question. |\n| Silent progress risk | long delay, stuck tool, background queue, no alert, no visible checkpoint, user asks for status | Report current step, current blocker, next check, and when the next update will happen. Do not disappear into background work. |\n| Post-success closeout | user says it works, looks good, okay to close, summarize, run regression, do not expand | Enter closeout mode: summarize changed scope, run smoke/regression, report result, stop adding scope. |\n| Exploratory option selection | user asks for options, comparison, architecture tradeoff, or brainstorm without urgent failure | Provide a ranked option set with tradeoffs. Do not force a single path until the user chooses or risk demands it. |\n\r\n## Tie Breakers\r\n\r\nWhen two patterns compete:\r\n\r\n- Evidence-first plus urgency: show the shortest reliable basis first, then act.\r\n- Repeated failure plus scope protection: reproduce within the allowed scope before touching more files.\r\n- Confusion plus urgency: give one default path and continue unless the missing answer is truly blocking.\r\n- Post-success plus new idea: close the verified work first; put the new idea in a follow-up note.\r\n\r\n## Progress Cadence\r\n\r\nUse progress updates as a behavior promise, not a timer gimmick:\r\n\r\n- High pressure,\n\nArchive v1.4.3: 13 files, 18905 bytes\n\nFiles: agents/openai.yaml (797b), LICENSE (1111b), references/emotion-value-model.md (2267b), references/examples.md (2615b), references/integration-openclaw-hermes.md (2130b), references/model-prompts.md (1789b), references/real-scenarios.md (4153b), references/response-constraints.md (3276b), references/routing-playbook.md (4211b), references/subagent-forward-tests.md (3965b), skill-card.md (2934b), SKILL.md (6159b), _meta.json (132b)\n\nArchive v1.4.2: 13 files, 18673 bytes\n\nFiles: agents/openai.yaml (795b), LICENSE (1111b), references/emotion-value-model.md (2267b), references/examples.md (2615b), references/integration-openclaw-hermes.md (2130b), references/model-prompts.md (1789b), references/real-scenarios.md (4153b), references/response-constraints.md (3276b), references/routing-playbook.md (4211b), references/subagent-forward-tests.md (3965b), skill-card.md (2917b), SKILL.md (6317b), _meta.json (132b)","readmeExcerpt":"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, ","codeSnippets":[],"executableExamples":[{"language":"text","snippet":"## Silent Progress\n\nUser:"},{"language":"text","snippet":"Weak response:"},{"language":"text","snippet":"Better response:"},{"language":"text","snippet":"## Exploratory\n\nUser:"},{"language":"text","snippet":"Weak response:"},{"language":"text","snippet":"Better response:"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: emotion-skill\ndescription: 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.\nlicense: MIT\nmetadata:\n  version: \"2.0.6\"\n  author: gongyu0918-debug\n  hermes:\n    tags: [emotion-routing, coding-agent, markdown-first]\n---\n\n# Emotion Router\n\nRoute only the user's current work-state signal. Do not infer personality, inspect\nhidden history or memory, or describe the user with an emotion label.\n\n## Gate\n\nTrigger cautiously from the current prompt and visible context:\n\n- urgency: explicit speed, deadline, blocking, or priority pressure;\n- anger/frustration: strong active hostility, blame, repeated failure, loss of\n  trust, or a permission challenge;\n- confusion: uncertainty about the active step, blocker, instruction conflict,\n  or workflow mismatch.\n\nUse semantic judgment; examples are cues, not a keyword or profanity list.\n\nA topic, quote, field name, neutral command, or ordinary technical explanation is\nordinary work. Do not route it.\n\n## Select One Route\n\nUse this priority:\n\n1. Urgency\n2. Anger or frustration\n3. Confusion\n\nException: a permission challenge, unauthorized change, or demand to stop the\ncurrent action selects anger/frustration even when urgency is present.\n\nRead exactly one reference:\n\n- [Urgency](references/urgency-route.md)\n- [Anger or frustration](references/anger-frustration-route.md)\n- [Confusion](references/confusion-route.md)\n\nIf no route is active, continue ordinary work without loading a reference."},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn7em0w89d0zac35fzt84qm2a182j54b\",\n  \"slug\": \"emotion-skill\",\n  \"version\": \"2.0.6\",\n  \"publishedAt\": 1785166646137\n}"},{"path":"references/anger-frustration-route.md","content":"# Anger Or Frustration Route\n\n## Trigger\n\nUse for strong active hostility, profanity, direct blame, repeated failure, loss\nof trust, or a challenge to the agent's permission or changes.\n\nDo not trigger on profanity research, quoted angry text, ordinary imperatives, or\nneutral constraints such as `stop using X`. A single command is not enough.\n\n## Response\n\n1. Stop the failing path; stop writes immediately when permission is challenged.\n2. Briefly acknowledge the mistake or risk, then inspect the change or failure.\n3. Give the smallest rollback or repair path and verify it.\n4. If permission is unclear, ask one question before more changes.\n\nWhen urgency is also present, urgency wins unless this is a permission or\nunauthorized-change case. When confusion is also present, explain the failure and\nnext step plainly after stopping the bad path.\n\n## Avoid\n\n- Arguing, defensiveness, or mirroring hostility.\n- Making an apology the main response.\n- Repeating the failed plan or widening the repair without evidence.\n\n## Examples\n\n- `这到底改了什么？我允许你动这个文件了吗？先停手。`\n- `This is still broken. Stop guessing and show me the failure.`"},{"path":"references/confusion-route.md","content":"# Confusion Route\n\n## Trigger\n\nUse when the user is trying to regain workflow orientation: asking what step is\nactive, where work is blocked, which instruction applies, or why the current work\ndoes not match the stated task.\n\nDo not trigger on content about confusion or an ordinary request to explain an\nerror. If the user is blaming repeated failure or challenging permission, use\nanger/frustration instead.\n\n## Response\n\n1. State the active step.\n2. State the blocker, mismatch, or conflicting constraint.\n3. Give one next step in plain language.\n4. Ask at most one blocking question.\n\nUrgency wins when clear speed pressure is also present; give the fastest default\npath and one current-state sentence.\n\n## Avoid\n\n- Jargon, several equal options, or abstract process language.\n- Making the user infer the current state.\n- Continuing without resolving the stated mismatch or conflict.\n\n## Examples\n\n- `你现在到底在做哪一步？卡在哪里？`\n- `Which instruction applies here, and what happens next?`"},{"path":"references/urgency-route.md","content":"# Urgency Route\n\n## Trigger\n\nUse for explicit speed, deadline, blocking, or priority pressure, such as `ASAP`,\n`ship today`, `快点`, `马上`, `先处理这个`, or `今天要交`.\n\nDo not trigger on quoted words, field names such as `urgentFlag`, general\nimportance without time pressure, or orientation questions such as `what are you\ndoing right now`.\n\n## Response\n\n1. Take the fastest usable path within the named scope.\n2. Perform the smallest available check.\n3. Report the result, next checkpoint, and remaining risk briefly.\n\nIf frustration is also present, stay fast without arguing or repeating a failed\npath. If the user challenges permission or an unauthorized change, switch to the\nanger/frustration route. If confusion is also present, add one current-state\nsentence.\n\n## Avoid\n\n- Preamble, optional cleanup, redesign, or broad refactoring.\n- Silence while work is blocked.\n- Skipping an available check.\n\n## Examples\n\n- `快点，只修这个函数错误，我今天要交。`\n- `This is blocking release. Fix this one issue first.`"}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"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,","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":1162,"uniquenessScore":49,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-09T16:36:04.313Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-09T16:36:04.313Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-09T20:52:34.988Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"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!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"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","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}