{"id":"04640472-7701-4e05-9033-c8d29f2e1995","entityType":"agent","slug":"clawhub-kyro-ma-error-message-improver","name":"Error Message Improver","canonicalUrl":"https://www.xpersona.co/agent/clawhub-kyro-ma-error-message-improver","canonicalPath":"/agent/clawhub-kyro-ma-error-message-improver","generatedAt":"2026-10-10T06:43:09.733Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T18:59:40.432Z","emptyReason":null},"description":"Helps with Users and support teams need clearer error message...","descriptionLabel":"Source description","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 2.1K downloads reported by the source. Last updated 10/9/2026.","installCommand":"clawhub skill install s17aeyv38nyj5fn7jtgzdj2yyx88405d:error-message-improver","sourceUrl":"https://clawhub.ai/kyro-ma/error-message-improver","homepage":"https://clawhub.ai/kyro-ma/skills/error-message-improver","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/kyro-ma/error-message-improver","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/kyro-ma/skills/error-message-improver","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":66,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Error Message Improver technical dossier on Xpersona with agent coverage, OPENCLEW support, and live trust metadata."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-09T18:59:40.432Z","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-09T18:59:40.432Z","emptyReason":null},"stars":null,"forks":null,"downloads":2102,"packageName":null,"latestVersion":"0.0.0-20261009-045810","tractionLabel":"2.1K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T18:59:40.401Z","emptyReason":null},"lastUpdatedAt":"2026-10-09T18:59:40.432Z","lastCrawledAt":"2026-10-09T18:59:40.401Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-10T18:59:40.401Z","lastVerifiedAt":null,"highlights":[{"version":"0.0.0-20261009-045810","createdAt":"2026-10-09T05:01:50.567Z","changelog":"- Updated documentation in English and Chinese (README.md, README.zh-CN.md) - Revised or expanded content in references/requirement-plan.md - Removed the redundant or outdated skill-card.md file - No changes to the core logic or workflow; documentation and planning files only","fileCount":8,"zipByteSize":10202},{"version":"0.20260916.221748","createdAt":"2026-09-16T22:20:10.355Z","changelog":"- Updated documentation in README.md and README.zh-CN.md for clarity. - Improved and reorganized content in references/requirement-plan.md. - Removed the obsolete skill-card.md file. - No changes to the core workflow or logic; only documentation and reference updates.","fileCount":8,"zipByteSize":10196},{"version":"0.20260910.52416","createdAt":"2026-09-10T05:27:28.919Z","changelog":"- Updated documentation in README.md and README.zh-CN.md for improved clarity. - Refined reference material in references/requirement-plan.md. - Removed obsolete skill-card.md file.","fileCount":8,"zipByteSize":10074},{"version":"0.20260907.40414","createdAt":"2026-09-07T04:06:40.123Z","changelog":"- Updated documentation in README.md and README.zh-CN.md for clarity and completeness. - Revised references/requirement-plan.md with refined requirement and planning details. - Removed outdated skill-card.md file.","fileCount":8,"zipByteSize":10661},{"version":"0.20260906.40422","createdAt":"2026-09-06T04:07:08.886Z","changelog":"- Updated documentation in README.md and README.zh-CN.md for clarity. - Revised references/requirement-plan.md to improve planning details and review criteria. - Removed obsolete skill-card.md file.","fileCount":8,"zipByteSize":10467},{"version":"0.20260905.61641","createdAt":"2026-09-05T06:19:31.643Z","changelog":"Major update: The skill focus has shifted from diagnosing network issues to improving error message clarity for users and support teams. - Requirement and triggers updated to address the need for clearer error messages, supporting debugging and user feedback. - Increased supporting evidence count from 11 to 12 signals. - Audience broadened from remote workers and technically curious households to include developers, support teams, SaaS operators, and end users. - Workflow and validation guidance revised for generating actionable, user-friendly error explanations. - References and documentation updated to match the new goal. - Obsolete file skill-card.md has been removed.","fileCount":8,"zipByteSize":10282},{"version":"0.20260904.60001","createdAt":"2026-09-04T06:03:54.525Z","changelog":"- Requirement and trigger updated: now focuses on network diagnostics (bufferbloat, router, modem, latency) for remote workers and households, replacing previous emphasis on clearer error messages. - Supporting evidence and demand scores revised to reflect new requirement (11 signals across 3 source families). - Keywords and example triggers changed to match the updated use case. - Documentation files updated to align with new scope; outdated skill-card.md removed.","fileCount":8,"zipByteSize":11139},{"version":"0.20260831.40551","createdAt":"2026-08-31T04:08:24.154Z","changelog":"- Documentation updated in README.md and README.zh-CN.md for clarity and maintenance. - References and planning documentation improved in references/requirement-plan.md. - Removed unused file: skill-card.md. - No workflow or functional changes to the core skill.","fileCount":8,"zipByteSize":10376}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s17aeyv38nyj5fn7jtgzdj2yyx88405d:error-message-improver","setupComplexity":"low","setupSteps":["Install using `clawhub skill install s17aeyv38nyj5fn7jtgzdj2yyx88405d:error-message-improver` in an isolated environment before connecting it to live workloads.","No published capability contract is available yet, so validate auth and request/response behavior manually.","Review the upstream CLAWHUB listing at https://clawhub.ai/kyro-ma/error-message-improver before using production credentials."],"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-kyro-ma-error-message-improver/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kyro-ma-error-message-improver/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kyro-ma-error-message-improver/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-kyro-ma-error-message-improver/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-kyro-ma-error-message-improver/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-kyro-ma-error-message-improver/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-10T06:43:09.729Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kyro-ma-error-message-improver/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kyro-ma-error-message-improver/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kyro-ma-error-message-improver/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kyro-ma-error-message-improver/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":"medium","updatedAt":"2026-10-09T18:59:40.432Z","emptyReason":null},"readme":"Skill: Error Message Improver\n\nOwner: kyro-ma\n\nSummary: Helps with Users and support teams need clearer error message...\n\nTags: latest:0.20260916.221748\n\nVersion history:\n\nv0.0.0-20261009-045810 | 2026-10-09T05:01:50.567Z | auto\n\n- Updated documentation in English and Chinese (README.md, README.zh-CN.md)\n- Revised or expanded content in references/requirement-plan.md\n- Removed the redundant or outdated skill-card.md file\n- No changes to the core logic or workflow; documentation and planning files only\n\nv0.20260916.221748 | 2026-09-16T22:20:10.355Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for clarity.\n- Improved and reorganized content in references/requirement-plan.md.\n- Removed the obsolete skill-card.md file.\n- No changes to the core workflow or logic; only documentation and reference updates.\n\nv0.20260910.52416 | 2026-09-10T05:27:28.919Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for improved clarity.\n- Refined reference material in references/requirement-plan.md.\n- Removed obsolete skill-card.md file.\n\nv0.20260907.40414 | 2026-09-07T04:06:40.123Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for clarity and completeness.\n- Revised references/requirement-plan.md with refined requirement and planning details.\n- Removed outdated skill-card.md file.\n\nv0.20260906.40422 | 2026-09-06T04:07:08.886Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for clarity.\n- Revised references/requirement-plan.md to improve planning details and review criteria.\n- Removed obsolete skill-card.md file.\n\nv0.20260905.61641 | 2026-09-05T06:19:31.643Z | auto\n\nMajor update: The skill focus has shifted from diagnosing network issues to improving error message clarity for users and support teams.\n\n- Requirement and triggers updated to address the need for clearer error messages, supporting debugging and user feedback.\n- Increased supporting evidence count from 11 to 12 signals.\n- Audience broadened from remote workers and technically curious households to include developers, support teams, SaaS operators, and end users.\n- Workflow and validation guidance revised for generating actionable, user-friendly error explanations.\n- References and documentation updated to match the new goal.\n- Obsolete file skill-card.md has been removed.\n\nv0.20260904.60001 | 2026-09-04T06:03:54.525Z | auto\n\n- Requirement and trigger updated: now focuses on network diagnostics (bufferbloat, router, modem, latency) for remote workers and households, replacing previous emphasis on clearer error messages.\n- Supporting evidence and demand scores revised to reflect new requirement (11 signals across 3 source families).\n- Keywords and example triggers changed to match the updated use case.\n- Documentation files updated to align with new scope; outdated skill-card.md removed.\n\nv0.20260831.40551 | 2026-08-31T04:08:24.154Z | auto\n\n- Documentation updated in README.md and README.zh-CN.md for clarity and maintenance.\n- References and planning documentation improved in references/requirement-plan.md.\n- Removed unused file: skill-card.md.\n- No workflow or functional changes to the core skill.\n\nv0.20260830.92238 | 2026-08-30T09:26:07.857Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for improved clarity.\n- Revised references/requirement-plan.md to align with current requirements and evidence.\n- Removed skill-card.md to streamline project files.\n\nv0.20260828.40337 | 2026-08-28T04:07:35.271Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for clarity and completeness.\n- Expanded or revised requirement details in references/requirement-plan.md.\n- Removed outdated skill-card.md file to streamline project files.\n\nv0.20260827.40448 | 2026-08-27T04:07:23.336Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for improved clarity.\n- Revised references/requirement-plan.md with new or updated planning details.\n- Removed the redundant skill-card.md file.\n- No changes to core functionality; this is a documentation-focused update.\n\nv0.20260826.40329 | 2026-08-26T04:06:17.384Z | auto\n\n- Updated documentation in English and Chinese (README.md, README.zh-CN.md) for clarity and completeness.\n- Revised and expanded planning details in references/requirement-plan.md.\n- Removed outdated or redundant file: skill-card.md.\n- No changes to core workflow or output logic; content refresh and maintenance.\n\nv0.20260825.44155 | 2026-08-25T04:51:04.166Z | auto\n\n- Updated documentation in multiple files, including README and requirement plan references.\n- Added or improved details in both English and Chinese documentation.\n- Removed the \"skill-card.md\" file for streamlined documentation management.\n- No changes to core functionality; this update focuses on documentation clarity and maintenance.\n\nv0.20260824.40429 | 2026-08-24T04:07:25.654Z | auto\n\n- Improved documentation in README.md and README.zh-CN.md for clarity and consistency.\n- Updated references/requirement-plan.md with additional planning details.\n- Removed outdated skill-card.md file for better maintainability.\n\nv0.20260823.40325 | 2026-08-23T04:06:49.058Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for improved clarity.\n- Modified references/requirement-plan.md to reflect current requirements and planning details.\n- Removed the obsolete skill-card.md file.\n\nv0.20260822.135636 | 2026-08-22T13:59:27.504Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for clarity and completeness.\n- Removed the skill-card.md file to streamline project files.\n- Requirement plan reference moved to references/requirement-plan.md in documentation.\n- No changes to core workflow or output expectations.\n\nv0.20260821.52309 | 2026-08-21T05:28:35.801Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for clarity and consistency.\n- Revised and expanded references/requirement-plan.md.\n- Removed skill-card.md to reduce duplication and streamline content.\n- No functional changes to skill logic or features.\n\nv0.20260819.45504 | 2026-08-19T05:02:12.518Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for clarity and accuracy.\n- Revised references/requirement-plan.md to improve requirement tracking.\n- Removed outdated skill-card.md file.\n\nv0.20260818.40417 | 2026-08-18T04:06:57.150Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for clarity and accuracy.\n- Removed outdated skill-card.md file.\n- Revised and maintained requirement and workflow documentation in SKILL.md and references/requirement-plan.md.\n\nv0.20260817.40422 | 2026-08-17T04:07:00.137Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for clarity.\n- Removed outdated skill-card.md file.\n- No changes to core workflow or user-facing functionality.\n\nv0.20260816.40342 | 2026-08-16T04:10:21.997Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for improved clarity.\n- Revised references/requirement-plan.md with additional supporting details.\n- Removed redundant skill-card.md file.\n\nv0.20260814.40500 | 2026-08-14T04:10:26.582Z | auto\n\n- Documentation updates: README.md and README.zh-CN.md revised.\n- Removed skill-card.md file.\n- No changes to skill functionality or workflow logic.\n- Requirement and workflow details remain consistent.\n\nv0.20260811.40534 | 2026-08-11T04:07:47.489Z | auto\n\n- Updated documentation: README.md and README.zh-CN.md revised for clarity and completeness.\n- Requirement and planning details consolidated in references/requirement-plan.md.\n- Removed outdated skill-card.md file.\n- No changes to workflow, triggers, or core functionality.\n\nv0.20260810.40316 | 2026-08-10T04:05:50.582Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for clarity and completeness.\n- Added or revised references/requirement-plan.md to improve supporting evidence and planning details.\n- Removed redundant or outdated skill-card.md file.\n\nv0.20260809.40514 | 2026-08-09T04:08:43.540Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for improved clarity.\n- Revised requirement-plan.md under references for alignment with current skill scope.\n- Removed deprecated skill-card.md file.\n\nv0.20260802.40421 | 2026-08-02T04:05:55.010Z | auto\n\n- Documentation updated in English and Chinese (README.md, README.zh-CN.md).\n- Requirement planning reference file updated.\n- Outdated skill card documentation (skill-card.md) removed.\n\nv0.20260730.234524 | 2026-07-30T23:50:52.380Z | auto\n\n- Updated documentation files: improved content in README.md and README.zh-CN.md.\n- Revised references/requirement-plan.md for clarity.\n- Removed the outdated skill-card.md file.\n- No changes to workflow or core functionality.\n\nv0.20260730.3907 | 2026-07-30T00:43:06.013Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for clarity and accuracy.\n- Revised references/requirement-plan.md to align with the latest requirement and process.\n- Removed the old skill-card.md file to eliminate duplication and outdated content.\n- No changes to core logic; all updates are documentation-related.\n\nv0.20260728.90410 | 2026-07-28T09:06:33.877Z | auto\n\n- Documentation updates: README.md, README.zh-CN.md, and references/requirement-plan.md revised.\n- Obsolete file skill-card.md removed.\n- No major changes to core functionality.\n\nv0.20260728.40429 | 2026-07-28T04:08:31.145Z | auto\n\n- Documentation improved: README.md and README.zh-CN.md updated with clearer instructions and planning references.\n- Planning and requirements documentation enhanced in references/requirement-plan.md.\n- Obsolete file skill-card.md removed for better maintenance.\n- No functional or workflow changes to the core skill.\n\nv0.20260728.1730 | 2026-07-28T00:19:40.717Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for clarity and completeness.\n- Revised requirement, workflow, and validation details in references/requirement-plan.md.\n- Removed deprecated skill-card.md file for improved maintainability.\n\nv0.20260727.130301 | 2026-07-27T13:09:02.769Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for clarity and completeness.\n- Revised references/requirement-plan.md with new or improved planning details.\n- Removed the redundant skill-card.md file.\n- No changes made to core logic or workflow.\n\nv0.20260727.80339 | 2026-07-27T08:09:22.528Z | auto\n\n- Removed the skill-card.md file.\n- Updated references/requirement-plan.md with possible planning or requirements changes.\n- No user-facing feature or workflow changes noted.\n\nv0.20260727.30443 | 2026-07-27T03:06:39.880Z | auto\n\n- Initial release based on validated market need for clearer, more actionable error messages.\n- Provides step-by-step workflow for restating user needs, planning, and delivering improved error message artifacts or supporting materials.\n- Outputs include tailored solutions, reusable checklists or workflows, and a verification note for each response.\n- Prioritizes local-hardware-friendly and practical implementations, such as scripts and templates.\n- Designed to trigger on error message, debugging, user feedback, support, and troubleshooting requests.\n\nArchive index:\n\nArchive v0.0.0-20261009-045810: 8 files, 10202 bytes\n\nFiles: agents/openai.yaml (364b), README.md (3131b), README.zh-CN.md (3139b), references/requirement-plan.md (4985b), skill-card.md (1727b), SKILL.md (3102b), SKILL.zh-CN.md (2976b), _meta.json (157b)\n\nFile v0.0.0-20261009-045810:SKILL.md\n\n---\nname: error-message-improver\ndescription: >-\n  Help users with Validated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.. Use when a user asks for work-productivity, error messages, debugging, user feedback, support, or needs a practical workflow, artifact, checklist, analysis, or implementation support for this requirement.\n---\n\n# Error Message Improver\n\n## Requirement\n\nUse this skill to help application developers, support teams, SaaS operators, and users who lose time when vague errors block troubleshooting with:\n\n> Validated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\nDemand score: 100/100 (`70/70` demand, `30/30` local feasibility).\nEvidence: 12 signals across 3 source families.\n\nRead `references/requirement-plan.md` when source evidence, planning details, or review criteria are needed.\n\n## Workflow\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Create a concise work plan, template, automation outline, or decision aid that reduces manual coordination.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Validation\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Triggers\n\nKeywords: `work-productivity`, `error messages`, `debugging`, `user feedback`, `support`, `troubleshooting`\n\nExample trigger sentences:\n\n- `Help me Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `I need a practical workflow for Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `Use $error-message-improver to handle Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n\nFile v0.0.0-20261009-045810:README.md\n\n# Error Message Improver\n\n## Requirement\n\nValidated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\nAudience: application developers, support teams, SaaS operators, and users who lose time when vague errors block troubleshooting\n\nCategory: `work-productivity`\n\nDemand score: 100/100\n\nEvidence coverage: 12 signals across 3 source families.\n\n## Evidence\n\n- github-issues: [Source inventory: 9router PRs, issues and port dispositions](https://github.com/bloodf/durindoor/issues/1072)\n- github-issues: [[BUG]:Playback problem - codec errors](https://github.com/cygnusx-1-org/electriceel/issues/34)\n- segmentfault-search: [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search: [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search: [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search: [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search: [答： c++单例类编译不通过](https://segmentfault.com/q/1010000004886164/a-1020000004886445)\n- segmentfault-search: [error-messages](https://segmentfault.com/t/error-messages)\n- segmentfault-search: [问： vue自定义指令报错](https://segmentfault.com/q/1010000009322969)\n- github-issues: [Classic renderer drops or overwrites output when anything above the visible window changes height (verbose makes it frequent)](https://github.com/anthropics/claude-code/issues/98019)\n- github-issues: [New trait solver regresses error messages significantly](https://github.com/rust-lang/rust/issues/163643)\n- hacker-news-search: [What makes Lisp difficult to read?](https://news.ycombinator.com/item?id=49881351)\n\n## How This Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Usage\n\nKeywords: `work-productivity`, `error messages`, `debugging`, `user feedback`, `support`, `troubleshooting`\n\nTrigger sentences:\n\n- `Help me Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `I need a practical workflow for Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `Use $error-message-improver to handle Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n\n## Files\n\n- `SKILL.md`: English skill instructions.\n- `SKILL.zh-CN.md`: Chinese skill instructions.\n- `README.md`: English user-facing guide.\n- `README.zh-CN.md`: Chinese user-facing guide.\n\nFile v0.0.0-20261009-045810:_meta.json\n\n{\n  \"ownerId\": \"kn7be2ewez5ks45t5nmdez8j51839xpk\",\n  \"slug\": \"error-message-improver\",\n  \"version\": \"0.0.0-20261009-045810\",\n  \"publishedAt\": 1791522110567\n}\n\nFile v0.0.0-20261009-045810:references/requirement-plan.md\n\n# Requirement Plan\n\n## Live Requirement\n\nValidated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n## Audience\n\napplication developers, support teams, SaaS operators, and users who lose time when vague errors block troubleshooting\n\n## Category\n\nwork-productivity\n\n## Requirement Score\n\nTotal: 100/100\n\nDemand: 70/70\n\nLocal feasibility: 30/30\n\nEvidence coverage: 12 signals across 3 source families.\n\nScoring rationale:\n\n- Evidence count: 12; required minimum: 3.\n- Distinct source families: 3; sources: github, hacker-news, segmentfault.\n- Demand score: 70/70 based on corroboration, source diversity, and professional/community signal.\n- Local feasibility score: 30/30.\n- Implementation is a documentation, workflow, code, or analysis skill that can run on ordinary CPU hardware.\n\n## Evidence\n\n- github-issues (2026-10-08T20:04:08+00:00): [Source inventory: 9router PRs, issues and port dispositions](https://github.com/bloodf/durindoor/issues/1072)\n- github-issues (2026-10-08T11:05:35+00:00): [[BUG]:Playback problem - codec errors](https://github.com/cygnusx-1-org/electriceel/issues/34)\n- segmentfault-search (2026-10-09T04:58:44.986821+00:00): [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search (2026-10-09T04:58:44.986821+00:00): [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search (2026-10-09T04:58:44.986821+00:00): [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search (2026-10-09T04:58:44.986821+00:00): [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search (2026-10-09T04:58:44.987325+00:00): [答： c++单例类编译不通过](https://segmentfault.com/q/1010000004886164/a-1020000004886445)\n- segmentfault-search (2026-10-09T04:58:44.987325+00:00): [error-messages](https://segmentfault.com/t/error-messages)\n- segmentfault-search (2026-10-09T04:58:44.987325+00:00): [问： vue自定义指令报错](https://segmentfault.com/q/1010000009322969)\n- github-issues (2026-09-28T23:29:29+00:00): [Classic renderer drops or overwrites output when anything above the visible window changes height (verbose makes it frequent)](https://github.com/anthropics/claude-code/issues/98019)\n- github-issues (2026-10-02T09:36:32+00:00): [New trait solver regresses error messages significantly](https://github.com/rust-lang/rust/issues/163643)\n- hacker-news-search (2026-09-28T17:22:50+00:00): [What makes Lisp difficult to read?](https://news.ycombinator.com/item?id=49881351)\n\n## How The Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Executable Implementation Plan\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Create a concise work plan, template, automation outline, or decision aid that reduces manual coordination.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Review Criteria\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Usage Signals\n\nKeywords: work-productivity, error messages, debugging, user feedback, support, troubleshooting\n\nTrigger sentences:\n\n- Help me Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.\n- I need a practical workflow for Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.\n- Use $error-message-improver to handle Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.\n\nFile v0.0.0-20261009-045810:README.zh-CN.md\n\n# Error Message Improver\n\n## 需求\n\nValidated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n目标用户：application developers, support teams, SaaS operators, and users who lose time when vague errors block troubleshooting\n\n分类：`工作与效率`\n\n需求评分：100/100\n\n证据覆盖：12 条信号，覆盖 3 个来源类型。\n\n## 来源证据\n\n- github-issues：[Source inventory: 9router PRs, issues and port dispositions](https://github.com/bloodf/durindoor/issues/1072)\n- github-issues：[[BUG]:Playback problem - codec errors](https://github.com/cygnusx-1-org/electriceel/issues/34)\n- segmentfault-search：[HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search：[javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search：[typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search：[ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search：[答： c++单例类编译不通过](https://segmentfault.com/q/1010000004886164/a-1020000004886445)\n- segmentfault-search：[error-messages](https://segmentfault.com/t/error-messages)\n- segmentfault-search：[问： vue自定义指令报错](https://segmentfault.com/q/1010000009322969)\n- github-issues：[Classic renderer drops or overwrites output when anything above the visible window changes height (verbose makes it frequent)](https://github.com/anthropics/claude-code/issues/98019)\n- github-issues：[New trait solver regresses error messages significantly](https://github.com/rust-lang/rust/issues/163643)\n- hacker-news-search：[What makes Lisp difficult to read?](https://news.ycombinator.com/item?id=49881351)\n\n## 这个技能如何满足需求\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## 使用方式\n\n关键词：`work-productivity`, `error messages`, `debugging`, `user feedback`, `support`, `troubleshooting`\n\n触发句：\n\n- `Help me Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `I need a practical workflow for Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `Use $error-message-improver to handle Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n\n## 文件\n\n- `SKILL.md`：英文版技能说明。\n- `SKILL.zh-CN.md`：中文版技能说明。\n- `README.md`：英文版用户说明。\n- `README.zh-CN.md`：中文版用户说明。\n\nFile v0.0.0-20261009-045810:skill-card.md\n\n## Description:\n\nHelps developers and support teams turn unclear error messages into actionable explanations and troubleshooting steps.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kyro-ma](https://clawhub.ai/user/kyro-ma)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nApplication developers, support teams, and SaaS operators use this skill to plan, write, or review error messages that explain failures and next steps. It can provide a tailored response, reusable checklist, workflow, analysis, or implementation guidance.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Broad trigger terms may activate the skill for general debugging or support requests that need a more specific approach.\n\nMitigation: Check that improving error messages is the user's goal before applying the workflow; use a more specific skill for unrelated requests.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/kyro-ma/skills/error-message-improver)\n- [Requirement and implementation plan](references/requirement-plan.md)\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, Code, Guidance]\n\n**Output Format:** [Markdown, with code or checklists when requested]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Includes assumptions and a brief verification or next-step note when helpful]\n\n## Skill Version(s):\n\n0.0.0-20261009-045810 (source: server-resolved release metadata)\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 v0.0.0-20261009-045810:SKILL.zh-CN.md\n\n---\nname: error-message-improver\ndescription: >-\n  帮助用户处理“Validated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.”。当用户提出 work-productivity, error messages, debugging, user feedback, support，或需要围绕该需求获得实用流程、产物、检查清单、分析或实现支持时使用。\n---\n\n# Error Message Improver\n\n## 需求\n\n使用这个技能帮助以下用户群体：application developers, support teams, SaaS operators, and users who lose time when vague errors block troubleshooting\n\n> Validated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n需求评分：100/100（需求强度 `70/70`，本地可执行性 `30/30`）。\n证据：12 条信号，覆盖 3 个来源类型。\n\n如需查看来源证据、执行计划或评审标准，请阅读 `references/requirement-plan.md`。\n\n## 工作流程\n\n1. 重新说明用户想要的结果、限制、已有输入和成功标准。\n2. 创建简洁的工作计划、模板、自动化思路或决策辅助，减少手动协调。\n3. 只有当缺失信息会明显改变输出时才提问；否则先做合理假设并继续推进。\n4. 保持本地硬件友好：优先使用脚本、模板、检查清单、小模型或 CPU 可承受的流程，避免依赖云端专用资源或大规模训练。\n5. 产出用户需要的文档、流程、清单、分析、代码修改或决策支持。\n6. 对照成功标准检查结果，并列出剩余风险或后续事项。\n\n## 预期输出\n\n- 针对用户当前情境的定制回答或产物。\n- 当任务可复用时，提供检查清单或工作流程。\n- 说明结果如何被检查的验证备注。\n\n## 验证\n\n- 输出直接回应发现的原始需求。\n- 用户不需要阅读原始来源帖子也能采取行动。\n- 假设、限制和所需输入清晰可见。\n- 在有帮助时，最终回复包含简短的使用说明或下一步建议。\n\n## 触发方式\n\n关键词：`work-productivity`, `error messages`, `debugging`, `user feedback`, `support`, `troubleshooting`\n\n示例触发句：\n\n- `Help me Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `I need a practical workflow for Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `Use $error-message-improver to handle Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n\nFile v0.0.0-20261009-045810:agents/openai.yaml\n\ninterface:\n  display_name: \"Error Message Improver\"\n  short_description: \"Helps with Users and support teams need clearer error message...\"\n  default_prompt: \"Use $error-message-improver to help me Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.\"\n\npolicy:\n  allow_implicit_invocation: true\n\nArchive v0.20260916.221748: 8 files, 10196 bytes\n\nFiles: agents/openai.yaml (364b), README.md (3081b), README.zh-CN.md (3089b), references/requirement-plan.md (4935b), skill-card.md (2264b), SKILL.md (3102b), SKILL.zh-CN.md (2976b), _meta.json (153b)\n\nFile v0.20260916.221748:SKILL.md\n\n---\nname: error-message-improver\ndescription: >-\n  Help users with Validated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.. Use when a user asks for work-productivity, error messages, debugging, user feedback, support, or needs a practical workflow, artifact, checklist, analysis, or implementation support for this requirement.\n---\n\n# Error Message Improver\n\n## Requirement\n\nUse this skill to help application developers, support teams, SaaS operators, and users who lose time when vague errors block troubleshooting with:\n\n> Validated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\nDemand score: 100/100 (`70/70` demand, `30/30` local feasibility).\nEvidence: 12 signals across 3 source families.\n\nRead `references/requirement-plan.md` when source evidence, planning details, or review criteria are needed.\n\n## Workflow\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Create a concise work plan, template, automation outline, or decision aid that reduces manual coordination.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Validation\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Triggers\n\nKeywords: `work-productivity`, `error messages`, `debugging`, `user feedback`, `support`, `troubleshooting`\n\nExample trigger sentences:\n\n- `Help me Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `I need a practical workflow for Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `Use $error-message-improver to handle Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n\nFile v0.20260916.221748:README.md\n\n# Error Message Improver\n\n## Requirement\n\nValidated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\nAudience: application developers, support teams, SaaS operators, and users who lose time when vague errors block troubleshooting\n\nCategory: `work-productivity`\n\nDemand score: 100/100\n\nEvidence coverage: 12 signals across 3 source families.\n\n## Evidence\n\n- github-issues: [Water Furnace Error](https://github.com/home-assistant/core/issues/181810)\n- github-issues: [opening pdf in external viewer from user command and also from embedded viewer should show no error messages](https://github.com/texstudio-org/texstudio/issues/4661)\n- segmentfault-search: [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search: [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search: [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search: [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search: [答： c++单例类编译不通过](https://segmentfault.com/q/1010000004886164/a-1020000004886445)\n- segmentfault-search: [error-messages](https://segmentfault.com/t/error-messages)\n- segmentfault-search: [问： vue自定义指令报错](https://segmentfault.com/q/1010000009322969)\n- hacker-news-search: [Trying to Make a Loop Auto-Vectorize](https://news.ycombinator.com/item?id=49703084)\n- hacker-news-search: [Ubuntu 26.10 completes transition to Rust-based coreutils](https://news.ycombinator.com/item?id=49698438)\n- hacker-news-search: [Trying to Make a Loop Auto-Vectorize](https://news.ycombinator.com/item?id=49699200)\n\n## How This Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Usage\n\nKeywords: `work-productivity`, `error messages`, `debugging`, `user feedback`, `support`, `troubleshooting`\n\nTrigger sentences:\n\n- `Help me Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `I need a practical workflow for Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `Use $error-message-improver to handle Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n\n## Files\n\n- `SKILL.md`: English skill instructions.\n- `SKILL.zh-CN.md`: Chinese skill instructions.\n- `README.md`: English user-facing guide.\n- `README.zh-CN.md`: Chinese user-facing guide.\n\nFile v0.20260916.221748:_meta.json\n\n{\n  \"ownerId\": \"kn7be2ewez5ks45t5nmdez8j51839xpk\",\n  \"slug\": \"error-message-improver\",\n  \"version\": \"0.20260916.221748\",\n  \"publishedAt\": 1789597210355\n}\n\nFile v0.20260916.221748:references/requirement-plan.md\n\n# Requirement Plan\n\n## Live Requirement\n\nValidated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n## Audience\n\napplication developers, support teams, SaaS operators, and users who lose time when vague errors block troubleshooting\n\n## Category\n\nwork-productivity\n\n## Requirement Score\n\nTotal: 100/100\n\nDemand: 70/70\n\nLocal feasibility: 30/30\n\nEvidence coverage: 12 signals across 3 source families.\n\nScoring rationale:\n\n- Evidence count: 12; required minimum: 3.\n- Distinct source families: 3; sources: github, hacker-news, segmentfault.\n- Demand score: 70/70 based on corroboration, source diversity, and professional/community signal.\n- Local feasibility score: 30/30.\n- Implementation is a documentation, workflow, code, or analysis skill that can run on ordinary CPU hardware.\n\n## Evidence\n\n- github-issues (2026-09-10T00:19:56+00:00): [Water Furnace Error](https://github.com/home-assistant/core/issues/181810)\n- github-issues (2026-09-16T14:38:24+00:00): [opening pdf in external viewer from user command and also from embedded viewer should show no error messages](https://github.com/texstudio-org/texstudio/issues/4661)\n- segmentfault-search (2026-09-16T22:18:27.023278+00:00): [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search (2026-09-16T22:18:27.023278+00:00): [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search (2026-09-16T22:18:27.023278+00:00): [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search (2026-09-16T22:18:27.023278+00:00): [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search (2026-09-16T22:18:27.023830+00:00): [答： c++单例类编译不通过](https://segmentfault.com/q/1010000004886164/a-1020000004886445)\n- segmentfault-search (2026-09-16T22:18:27.023830+00:00): [error-messages](https://segmentfault.com/t/error-messages)\n- segmentfault-search (2026-09-16T22:18:27.023830+00:00): [问： vue自定义指令报错](https://segmentfault.com/q/1010000009322969)\n- hacker-news-search (2026-09-14T20:01:25+00:00): [Trying to Make a Loop Auto-Vectorize](https://news.ycombinator.com/item?id=49703084)\n- hacker-news-search (2026-09-14T15:18:33+00:00): [Ubuntu 26.10 completes transition to Rust-based coreutils](https://news.ycombinator.com/item?id=49698438)\n- hacker-news-search (2026-09-14T16:04:36+00:00): [Trying to Make a Loop Auto-Vectorize](https://news.ycombinator.com/item?id=49699200)\n\n## How The Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Executable Implementation Plan\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Create a concise work plan, template, automation outline, or decision aid that reduces manual coordination.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Review Criteria\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Usage Signals\n\nKeywords: work-productivity, error messages, debugging, user feedback, support, troubleshooting\n\nTrigger sentences:\n\n- Help me Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.\n- I need a practical workflow for Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.\n- Use $error-message-improver to handle Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.\n\nFile v0.20260916.221748:README.zh-CN.md\n\n# Error Message Improver\n\n## 需求\n\nValidated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n目标用户：application developers, support teams, SaaS operators, and users who lose time when vague errors block troubleshooting\n\n分类：`工作与效率`\n\n需求评分：100/100\n\n证据覆盖：12 条信号，覆盖 3 个来源类型。\n\n## 来源证据\n\n- github-issues：[Water Furnace Error](https://github.com/home-assistant/core/issues/181810)\n- github-issues：[opening pdf in external viewer from user command and also from embedded viewer should show no error messages](https://github.com/texstudio-org/texstudio/issues/4661)\n- segmentfault-search：[HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search：[javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search：[typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search：[ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search：[答： c++单例类编译不通过](https://segmentfault.com/q/1010000004886164/a-1020000004886445)\n- segmentfault-search：[error-messages](https://segmentfault.com/t/error-messages)\n- segmentfault-search：[问： vue自定义指令报错](https://segmentfault.com/q/1010000009322969)\n- hacker-news-search：[Trying to Make a Loop Auto-Vectorize](https://news.ycombinator.com/item?id=49703084)\n- hacker-news-search：[Ubuntu 26.10 completes transition to Rust-based coreutils](https://news.ycombinator.com/item?id=49698438)\n- hacker-news-search：[Trying to Make a Loop Auto-Vectorize](https://news.ycombinator.com/item?id=49699200)\n\n## 这个技能如何满足需求\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## 使用方式\n\n关键词：`work-productivity`, `error messages`, `debugging`, `user feedback`, `support`, `troubleshooting`\n\n触发句：\n\n- `Help me Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `I need a practical workflow for Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `Use $error-message-improver to handle Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n\n## 文件\n\n- `SKILL.md`：英文版技能说明。\n- `SKILL.zh-CN.md`：中文版技能说明。\n- `README.md`：英文版用户说明。\n- `README.zh-CN.md`：中文版用户说明。\n\nFile v0.20260916.221748:skill-card.md\n\n## Description:\n\nHelps developers, support teams, SaaS operators, and users turn vague error messages into clearer guidance that explains what failed, why it failed, and what action to take next.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kyro-ma](https://clawhub.ai/user/kyro-ma)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nApplication developers, support teams, SaaS operators, and users use this skill to produce clearer error-message copy, troubleshooting workflows, checklists, analysis, code changes, and verification notes for support or debugging situations.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Broad implicit triggers may activate the skill during general debugging or support conversations.\n\nMitigation: Prefer explicit invocation when the desired task is specifically error-message improvement.\n\nRisk: Generated error-message guidance may be incomplete or misleading if the underlying failure context is missing.\n\nMitigation: Check the output against the stated outcome, constraints, available inputs, and success criteria before use.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/kyro-ma/skills/error-message-improver)\n- [Requirement Plan](references/requirement-plan.md)\n- [Water Furnace Error](https://github.com/home-assistant/core/issues/181810)\n- [External PDF viewer error messages](https://github.com/texstudio-org/texstudio/issues/4661)\n- [error-messages topic](https://segmentfault.com/t/error-messages)\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, Code, Shell commands, Configuration, Guidance]\n\n**Output Format:** [Markdown or plain text with optional code blocks, command snippets, checklists, and configuration examples]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Outputs include visible assumptions, limits, validation notes, and follow-up work when helpful.]\n\n## Skill Version(s):\n\n0.20260916.221748 (source: server release evidence)\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 v0.20260916.221748:SKILL.zh-CN.md\n\n---\nname: error-message-improver\ndescription: >-\n  帮助用户处理“Validated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.”。当用户提出 work-productivity, error messages, debugging, user feedback, support，或需要围绕该需求获得实用流程、产物、检查清单、分析或实现支持时使用。\n---\n\n# Error Message Improver\n\n## 需求\n\n使用这个技能帮助以下用户群体：application developers, support teams, SaaS operators, and users who lose time when vague errors block troubleshooting\n\n> Validated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n需求评分：100/100（需求强度 `70/70`，本地可执行性 `30/30`）。\n证据：12 条信号，覆盖 3 个来源类型。\n\n如需查看来源证据、执行计划或评审标准，请阅读 `references/requirement-plan.md`。\n\n## 工作流程\n\n1. 重新说明用户想要的结果、限制、已有输入和成功标准。\n2. 创建简洁的工作计划、模板、自动化思路或决策辅助，减少手动协调。\n3. 只有当缺失信息会明显改变输出时才提问；否则先做合理假设并继续推进。\n4. 保持本地硬件友好：优先使用脚本、模板、检查清单、小模型或 CPU 可承受的流程，避免依赖云端专用资源或大规模训练。\n5. 产出用户需要的文档、流程、清单、分析、代码修改或决策支持。\n6. 对照成功标准检查结果，并列出剩余风险或后续事项。\n\n## 预期输出\n\n- 针对用户当前情境的定制回答或产物。\n- 当任务可复用时，提供检查清单或工作流程。\n- 说明结果如何被检查的验证备注。\n\n## 验证\n\n- 输出直接回应发现的原始需求。\n- 用户不需要阅读原始来源帖子也能采取行动。\n- 假设、限制和所需输入清晰可见。\n- 在有帮助时，最终回复包含简短的使用说明或下一步建议。\n\n## 触发方式\n\n关键词：`work-productivity`, `error messages`, `debugging`, `user feedback`, `support`, `troubleshooting`\n\n示例触发句：\n\n- `Help me Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `I need a practical workflow for Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `Use $error-message-improver to handle Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n\nFile v0.20260916.221748:agents/openai.yaml\n\ninterface:\n  display_name: \"Error Message Improver\"\n  short_description: \"Helps with Users and support teams need clearer error message...\"\n  default_prompt: \"Use $error-message-improver to help me Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.\"\n\npolicy:\n  allow_implicit_invocation: true\n\nArchive v0.20260910.52416: 8 files, 10074 bytes\n\nFiles: agents/openai.yaml (364b), README.md (3040b), README.zh-CN.md (3048b), references/requirement-plan.md (4894b), skill-card.md (2052b), SKILL.md (3102b), SKILL.zh-CN.md (2976b), _meta.json (152b)\n\nFile v0.20260910.52416:SKILL.md\n\n---\nname: error-message-improver\ndescription: >-\n  Help users with Validated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.. Use when a user asks for work-productivity, error messages, debugging, user feedback, support, or needs a practical workflow, artifact, checklist, analysis, or implementation support for this requirement.\n---\n\n# Error Message Improver\n\n## Requirement\n\nUse this skill to help application developers, support teams, SaaS operators, and users who lose time when vague errors block troubleshooting with:\n\n> Validated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\nDemand score: 100/100 (`70/70` demand, `30/30` local feasibility).\nEvidence: 12 signals across 3 source families.\n\nRead `references/requirement-plan.md` when source evidence, planning details, or review criteria are needed.\n\n## Workflow\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Create a concise work plan, template, automation outline, or decision aid that reduces manual coordination.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Validation\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Triggers\n\nKeywords: `work-productivity`, `error messages`, `debugging`, `user feedback`, `support`, `troubleshooting`\n\nExample trigger sentences:\n\n- `Help me Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `I need a practical workflow for Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `Use $error-message-improver to handle Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n\nFile v0.20260910.52416:README.md\n\n# Error Message Improver\n\n## Requirement\n\nValidated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\nAudience: application developers, support teams, SaaS operators, and users who lose time when vague errors block troubleshooting\n\nCategory: `work-productivity`\n\nDemand score: 100/100\n\nEvidence coverage: 12 signals across 3 source families.\n\n## Evidence\n\n- github-issues: [facebook video](https://github.com/yt-dlp/yt-dlp/issues/17643)\n- segmentfault-search: [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search: [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search: [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search: [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search: [答： c++单例类编译不通过](https://segmentfault.com/q/1010000004886164/a-1020000004886445)\n- segmentfault-search: [error-messages](https://segmentfault.com/t/error-messages)\n- segmentfault-search: [问： vue自定义指令报错](https://segmentfault.com/q/1010000009322969)\n- github-issues: [Improve error messages in parsers](https://github.com/yrn-dev/Operator/issues/18504)\n- hacker-news-search: [Zig: Pointer Stability for ArrayLists](https://news.ycombinator.com/item?id=49502293)\n- hacker-news-search: [Arbitrary code execution in QubesOS via copy-to-VM error reporting backchannel](https://news.ycombinator.com/item?id=49501950)\n- hacker-news-search: [DeepSeek launching v4.1 flash cheaper and more capable than v4 pro](https://news.ycombinator.com/item?id=49625972)\n\n## How This Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Usage\n\nKeywords: `work-productivity`, `error messages`, `debugging`, `user feedback`, `support`, `troubleshooting`\n\nTrigger sentences:\n\n- `Help me Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `I need a practical workflow for Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `Use $error-message-improver to handle Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n\n## Files\n\n- `SKILL.md`: English skill instructions.\n- `SKILL.zh-CN.md`: Chinese skill instructions.\n- `README.md`: English user-facing guide.\n- `README.zh-CN.md`: Chinese user-facing guide.\n\nFile v0.20260910.52416:_meta.json\n\n{\n  \"ownerId\": \"kn7be2ewez5ks45t5nmdez8j51839xpk\",\n  \"slug\": \"error-message-improver\",\n  \"version\": \"0.20260910.52416\",\n  \"publishedAt\": 1789018048919\n}\n\nFile v0.20260910.52416:references/requirement-plan.md\n\n# Requirement Plan\n\n## Live Requirement\n\nValidated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n## Audience\n\napplication developers, support teams, SaaS operators, and users who lose time when vague errors block troubleshooting\n\n## Category\n\nwork-productivity\n\n## Requirement Score\n\nTotal: 100/100\n\nDemand: 70/70\n\nLocal feasibility: 30/30\n\nEvidence coverage: 12 signals across 3 source families.\n\nScoring rationale:\n\n- Evidence count: 12; required minimum: 3.\n- Distinct source families: 3; sources: github, hacker-news, segmentfault.\n- Demand score: 70/70 based on corroboration, source diversity, and professional/community signal.\n- Local feasibility score: 30/30.\n- Implementation is a documentation, workflow, code, or analysis skill that can run on ordinary CPU hardware.\n\n## Evidence\n\n- github-issues (2026-09-07T14:50:58+00:00): [facebook video](https://github.com/yt-dlp/yt-dlp/issues/17643)\n- segmentfault-search (2026-09-10T05:25:36.835703+00:00): [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search (2026-09-10T05:25:36.835703+00:00): [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search (2026-09-10T05:25:36.835703+00:00): [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search (2026-09-10T05:25:36.835703+00:00): [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search (2026-09-10T05:25:36.836711+00:00): [答： c++单例类编译不通过](https://segmentfault.com/q/1010000004886164/a-1020000004886445)\n- segmentfault-search (2026-09-10T05:25:36.836711+00:00): [error-messages](https://segmentfault.com/t/error-messages)\n- segmentfault-search (2026-09-10T05:25:36.836711+00:00): [问： vue自定义指令报错](https://segmentfault.com/q/1010000009322969)\n- github-issues (2026-09-10T05:06:34+00:00): [Improve error messages in parsers](https://github.com/yrn-dev/Operator/issues/18504)\n- hacker-news-search (2026-08-30T20:10:44+00:00): [Zig: Pointer Stability for ArrayLists](https://news.ycombinator.com/item?id=49502293)\n- hacker-news-search (2026-08-30T19:28:03+00:00): [Arbitrary code execution in QubesOS via copy-to-VM error reporting backchannel](https://news.ycombinator.com/item?id=49501950)\n- hacker-news-search (2026-09-09T13:09:56+00:00): [DeepSeek launching v4.1 flash cheaper and more capable than v4 pro](https://news.ycombinator.com/item?id=49625972)\n\n## How The Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Executable Implementation Plan\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Create a concise work plan, template, automation outline, or decision aid that reduces manual coordination.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Review Criteria\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Usage Signals\n\nKeywords: work-productivity, error messages, debugging, user feedback, support, troubleshooting\n\nTrigger sentences:\n\n- Help me Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.\n- I need a practical workflow for Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.\n- Use $error-message-improver to handle Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.\n\nFile v0.20260910.52416:README.zh-CN.md\n\n# Error Message Improver\n\n## 需求\n\nValidated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n目标用户：application developers, support teams, SaaS operators, and users who lose time when vague errors block troubleshooting\n\n分类：`工作与效率`\n\n需求评分：100/100\n\n证据覆盖：12 条信号，覆盖 3 个来源类型。\n\n## 来源证据\n\n- github-issues：[facebook video](https://github.com/yt-dlp/yt-dlp/issues/17643)\n- segmentfault-search：[HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search：[javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search：[typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search：[ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search：[答： c++单例类编译不通过](https://segmentfault.com/q/1010000004886164/a-1020000004886445)\n- segmentfault-search：[error-messages](https://segmentfault.com/t/error-messages)\n- segmentfault-search：[问： vue自定义指令报错](https://segmentfault.com/q/1010000009322969)\n- github-issues：[Improve error messages in parsers](https://github.com/yrn-dev/Operator/issues/18504)\n- hacker-news-search：[Zig: Pointer Stability for ArrayLists](https://news.ycombinator.com/item?id=49502293)\n- hacker-news-search：[Arbitrary code execution in QubesOS via copy-to-VM error reporting backchannel](https://news.ycombinator.com/item?id=49501950)\n- hacker-news-search：[DeepSeek launching v4.1 flash cheaper and more capable than v4 pro](https://news.ycombinator.com/item?id=49625972)\n\n## 这个技能如何满足需求\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## 使用方式\n\n关键词：`work-productivity`, `error messages`, `debugging`, `user feedback`, `support`, `troubleshooting`\n\n触发句：\n\n- `Help me Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `I need a practical workflow for Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `Use $error-message-improver to handle Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n\n## 文件\n\n- `SKILL.md`：英文版技能说明。\n- `SKILL.zh-CN.md`：中文版技能说明。\n- `README.md`：英文版用户说明。\n- `README.zh-CN.md`：中文版用户说明。\n\nFile v0.20260910.52416:skill-card.md\n\n## Description:\n\nHelps developers, support teams, and operators rewrite vague error messages so they explain what failed, why it happened, and what to do next.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kyro-ma](https://clawhub.ai/user/kyro-ma)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers, support teams, SaaS operators, and users use this skill to turn vague failures into clearer messages, troubleshooting checklists, and implementation guidance that name the failure, likely cause, and next action.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Broad auto-invocation wording may activate the skill during general debugging or support requests where error-message design is not intended.\n\nMitigation: Invoke the skill explicitly when predictable routing matters and verify that the requested task is about rewriting or designing clearer error messages.\n\nRisk: Generated wording or troubleshooting guidance could misstate the real cause of an application failure.\n\nMitigation: Review proposed messages and checklists against actual application behavior before release or customer-facing use.\n\n## Reference(s):\n\n- [Requirement Plan](references/requirement-plan.md)\n- [ClawHub Skill Page](https://clawhub.ai/kyro-ma/skills/error-message-improver)\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, Code, Shell commands, Configuration, Guidance]\n\n**Output Format:** [Markdown with checklists, templates, code blocks, or command snippets when requested]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May include assumptions, validation notes, and follow-up risks for the user's specific error-message task.]\n\n## Skill Version(s):\n\n0.20260910.52416 (source: release evidence)\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 v0.20260910.52416:SKILL.zh-CN.md\n\n---\nname: error-message-improver\ndescription: >-\n  帮助用户处理“Validated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.”。当用户提出 work-productivity, error messages, debugging, user feedback, support，或需要围绕该需求获得实用流程、产物、检查清单、分析或实现支持时使用。\n---\n\n# Error Message Improver\n\n## 需求\n\n使用这个技能帮助以下用户群体：application developers, support teams, SaaS operators, and users who lose time when vague errors block troubleshooting\n\n> Validated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n需求评分：100/100（需求强度 `70/70`，本地可执行性 `30/30`）。\n证据：12 条信号，覆盖 3 个来源类型。\n\n如需查看来源证据、执行计划或评审标准，请阅读 `references/requirement-plan.md`。\n\n## 工作流程\n\n1. 重新说明用户想要的结果、限制、已有输入和成功标准。\n2. 创建简洁的工作计划、模板、自动化思路或决策辅助，减少手动协调。\n3. 只有当缺失信息会明显改变输出时才提问；否则先做合理假设并继续推进。\n4. 保持本地硬件友好：优先使用脚本、模板、检查清单、小模型或 CPU 可承受的流程，避免依赖云端专用资源或大规模训练。\n5. 产出用户需要的文档、流程、清单、分析、代码修改或决策支持。\n6. 对照成功标准检查结果，并列出剩余风险或后续事项。\n\n## 预期输出\n\n- 针对用户当前情境的定制回答或产物。\n- 当任务可复用时，提供检查清单或工作流程。\n- 说明结果如何被检查的验证备注。\n\n## 验证\n\n- 输出直接回应发现的原始需求。\n- 用户不需要阅读原始来源帖子也能采取行动。\n- 假设、限制和所需输入清晰可见。\n- 在有帮助时，最终回复包含简短的使用说明或下一步建议。\n\n## 触发方式\n\n关键词：`work-productivity`, `error messages`, `debugging`, `user feedback`, `support`, `troubleshooting`\n\n示例触发句：\n\n- `Help me Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `I need a practical workflow for Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `Use $error-message-improver to handle Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n\nFile v0.20260910.52416:agents/openai.yaml\n\ninterface:\n  display_name: \"Error Message Improver\"\n  short_description: \"Helps with Users and support teams need clearer error message...\"\n  default_prompt: \"Use $error-message-improver to help me Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.\"\n\npolicy:\n  allow_implicit_invocation: true\n\nArchive v0.20260907.40414: 8 files, 10661 bytes\n\nFiles: agents/openai.yaml (364b), README.md (3114b), README.zh-CN.md (3122b), references/requirement-plan.md (4968b), skill-card.md (2581b), SKILL.md (3102b), SKILL.zh-CN.md (2976b), _meta.json (152b)\n\nFile v0.20260907.40414:SKILL.md\n\n---\nname: error-message-improver\ndescription: >-\n  Help users with Validated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.. Use when a user asks for work-productivity, error messages, debugging, user feedback, support, or needs a practical workflow, artifact, checklist, analysis, or implementation support for this requirement.\n---\n\n# Error Message Improver\n\n## Requirement\n\nUse this skill to help application developers, support teams, SaaS operators, and users who lose time when vague errors block troubleshooting with:\n\n> Validated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\nDemand score: 100/100 (`70/70` demand, `30/30` local feasibility).\nEvidence: 12 signals across 3 source families.\n\nRead `references/requirement-plan.md` when source evidence, planning details, or review criteria are needed.\n\n## Workflow\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Create a concise work plan, template, automation outline, or decision aid that reduces manual coordination.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Validation\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Triggers\n\nKeywords: `work-productivity`, `error messages`, `debugging`, `user feedback`, `support`, `troubleshooting`\n\nExample trigger sentences:\n\n- `Help me Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `I need a practical workflow for Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `Use $error-message-improver to handle Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n\nFile v0.20260907.40414:README.md\n\n# Error Message Improver\n\n## Requirement\n\nValidated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\nAudience: application developers, support teams, SaaS operators, and users who lose time when vague errors block troubleshooting\n\nCategory: `work-productivity`\n\nDemand score: 100/100\n\nEvidence coverage: 12 signals across 3 source families.\n\n## Evidence\n\n- github-issues: [regex format implementation?](https://github.com/sourcemeta/jsonschema/issues/842)\n- github-issues: [Anidb is temporarily down, we should have a better error message](https://github.com/pystardust/ani-cli/issues/1893)\n- segmentfault-search: [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search: [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search: [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search: [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search: [答： c++单例类编译不通过](https://segmentfault.com/q/1010000004886164/a-1020000004886445)\n- segmentfault-search: [error-messages](https://segmentfault.com/t/error-messages)\n- segmentfault-search: [问： vue自定义指令报错](https://segmentfault.com/q/1010000009322969)\n- github-issues: [Improve error messages in helpers](https://github.com/yrn-dev/Operator/issues/16835)\n- github-issues: [[RFC][Gen5] 完全型推論・let多相を保つ「型が見える言語」— 型コンテキストAPI・推論境界・言語拡張の設計](https://github.com/sizumita/dacelo/issues/1)\n- hacker-news-search: [Zig: Pointer Stability for ArrayLists](https://news.ycombinator.com/item?id=49502293)\n\n## How This Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Usage\n\nKeywords: `work-productivity`, `error messages`, `debugging`, `user feedback`, `support`, `troubleshooting`\n\nTrigger sentences:\n\n- `Help me Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `I need a practical workflow for Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `Use $error-message-improver to handle Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n\n## Files\n\n- `SKILL.md`: English skill instructions.\n- `SKILL.zh-CN.md`: Chinese skill instructions.\n- `README.md`: English user-facing guide.\n- `README.zh-CN.md`: Chinese user-facing guide.\n\nFile v0.20260907.40414:_meta.json\n\n{\n  \"ownerId\": \"kn7be2ewez5ks45t5nmdez8j51839xpk\",\n  \"slug\": \"error-message-improver\",\n  \"version\": \"0.20260907.40414\",\n  \"publishedAt\": 1788754000123\n}\n\nFile v0.20260907.40414:references/requirement-plan.md\n\n# Requirement Plan\n\n## Live Requirement\n\nValidated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n## Audience\n\napplication developers, support teams, SaaS operators, and users who lose time when vague errors block troubleshooting\n\n## Category\n\nwork-productivity\n\n## Requirement Score\n\nTotal: 100/100\n\nDemand: 70/70\n\nLocal feasibility: 30/30\n\nEvidence coverage: 12 signals across 3 source families.\n\nScoring rationale:\n\n- Evidence count: 12; required minimum: 3.\n- Distinct source families: 3; sources: github, hacker-news, segmentfault.\n- Demand score: 70/70 based on corroboration, source diversity, and professional/community signal.\n- Local feasibility score: 30/30.\n- Implementation is a documentation, workflow, code, or analysis skill that can run on ordinary CPU hardware.\n\n## Evidence\n\n- github-issues (2026-09-03T08:07:56+00:00): [regex format implementation?](https://github.com/sourcemeta/jsonschema/issues/842)\n- github-issues (2026-09-05T12:09:03+00:00): [Anidb is temporarily down, we should have a better error message](https://github.com/pystardust/ani-cli/issues/1893)\n- segmentfault-search (2026-09-07T04:05:12.090085+00:00): [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search (2026-09-07T04:05:12.090085+00:00): [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search (2026-09-07T04:05:12.090590+00:00): [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search (2026-09-07T04:05:12.090590+00:00): [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search (2026-09-07T04:05:12.090590+00:00): [答： c++单例类编译不通过](https://segmentfault.com/q/1010000004886164/a-1020000004886445)\n- segmentfault-search (2026-09-07T04:05:12.090590+00:00): [error-messages](https://segmentfault.com/t/error-messages)\n- segmentfault-search (2026-09-07T04:05:12.090590+00:00): [问： vue自定义指令报错](https://segmentfault.com/q/1010000009322969)\n- github-issues (2026-09-07T04:04:01+00:00): [Improve error messages in helpers](https://github.com/yrn-dev/Operator/issues/16835)\n- github-issues (2026-09-05T16:12:37+00:00): [[RFC][Gen5] 完全型推論・let多相を保つ「型が見える言語」— 型コンテキストAPI・推論境界・言語拡張の設計](https://github.com/sizumita/dacelo/issues/1)\n- hacker-news-search (2026-08-30T20:10:44+00:00): [Zig: Pointer Stability for ArrayLists](https://news.ycombinator.com/item?id=49502293)\n\n## How The Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Executable Implementation Plan\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Create a concise work plan, template, automation outline, or decision aid that reduces manual coordination.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Review Criteria\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Usage Signals\n\nKeywords: work-productivity, error messages, debugging, user feedback, support, troubleshooting\n\nTrigger sentences:\n\n- Help me Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.\n- I need a practical workflow for Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.\n- Use $error-message-improver to handle Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.\n\nFile v0.20260907.40414:README.zh-CN.md\n\n# Error Message Improver\n\n## 需求\n\nValidated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n目标用户：application developers, support teams, SaaS operators, and users who lose time when vague errors block troubleshooting\n\n分类：`工作与效率`\n\n需求评分：100/100\n\n证据覆盖：12 条信号，覆盖 3 个来源类型。\n\n## 来源证据\n\n- github-issues：[regex format implementation?](https://github.com/sourcemeta/jsonschema/issues/842)\n- github-issues：[Anidb is temporarily down, we should have a better error message](https://github.com/pystardust/ani-cli/issues/1893)\n- segmentfault-search：[HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search：[javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search：[typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search：[ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search：[答： c++单例类编译不通过](https://segmentfault.com/q/1010000004886164/a-1020000004886445)\n- segmentfault-search：[error-messages](https://segmentfault.com/t/error-messages)\n- segmentfault-search：[问： vue自定义指令报错](https://segmentfault.com/q/1010000009322969)\n- github-issues：[Improve error messages in helpers](https://github.com/yrn-dev/Operator/issues/16835)\n- github-issues：[[RFC][Gen5] 完全型推論・let多相を保つ「型が見える言語」— 型コンテキストAPI・推論境界・言語拡張の設計](https://github.com/sizumita/dacelo/issues/1)\n- hacker-news-search：[Zig: Pointer Stability for ArrayLists](https://news.ycombinator.com/item?id=49502293)\n\n## 这个技能如何满足需求\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## 使用方式\n\n关键词：`work-productivity`, `error messages`, `debugging`, `user feedback`, `support`, `troubleshooting`\n\n触发句：\n\n- `Help me Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `I need a practical workflow for Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `Use $error-message-improver to handle Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n\n## 文件\n\n- `SKILL.md`：英文版技能说明。\n- `SKILL.zh-CN.md`：中文版技能说明。\n- `README.md`：英文版用户说明。\n- `README.zh-CN.md`：中文版用户说明。\n\nFile v0.20260907.40414:skill-card.md\n\n## Description:\n\nHelps developers, support teams, SaaS operators, and users turn vague errors into clear messages that explain what failed, why it failed, and what action to take next.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kyro-ma](https://clawhub.ai/user/kyro-ma)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers, support teams, SaaS operators, and users use this skill to improve error messages, troubleshooting workflows, checklists, implementation notes, and decision support for clearer user feedback.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Broad trigger wording may invoke the skill for generic debugging or support prompts beyond error-message improvement.\n\nMitigation: Use the skill when the task is about improving user-facing error messages or troubleshooting workflows, and tighten trigger wording before deployment if predictable activation is required.\n\nRisk: Generated guidance can be misleading when the underlying failure mode, logs, or product behavior are incomplete.\n\nMitigation: Review proposed wording and workflows against actual failure evidence, support policy, and product behavior before shipping user-facing changes.\n\n## Reference(s):\n\n- [Requirement Plan](references/requirement-plan.md)\n- [ClawHub skill page](https://clawhub.ai/kyro-ma/skills/error-message-improver)\n- [SourceMeta JSON Schema issue 842](https://github.com/sourcemeta/jsonschema/issues/842)\n- [ani-cli issue 1893](https://github.com/pystardust/ani-cli/issues/1893)\n- [Operator issue 16835](https://github.com/yrn-dev/Operator/issues/16835)\n- [Dacelo type-inference RFC issue](https://github.com/sizumita/dacelo/issues/1)\n- [SegmentFault error-messages tag](https://segmentfault.com/t/error-messages)\n- [Hacker News discussion on Zig pointer stability](https://news.ycombinator.com/item?id=49502293)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, code, shell commands, configuration, guidance]\n\n**Output Format:** [Markdown response with optional code, command, checklist, or configuration blocks]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May include assumptions, validation notes, and follow-up risks when useful.]\n\n## Skill Version(s):\n\n0.20260907.40414 (source: server release evidence)\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 v0.20260907.40414:SKILL.zh-CN.md\n\n---\nname: error-message-improver\ndescription: >-\n  帮助用户处理“Validated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.”。当用户提出 work-productivity, error messages, debugging, user feedback, support，或需要围绕该需求获得实用流程、产物、检查清单、分析或实现支持时使用。\n---\n\n# Error Message Improver\n\n## 需求\n\n使用这个技能帮助以下用户群体：application developers, support teams, SaaS operators, and users who lose time when vague errors block troubleshooting\n\n> Validated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n需求评分：100/100（需求强度 `70/70`，本地可执行性 `30/30`）。\n证据：12 条信号，覆盖 3 个来源类型。\n\n如需查看来源证据、执行计划或评审标准，请阅读 `references/requirement-plan.md`。\n\n## 工作流程\n\n1. 重新说明用户想要的结果、限制、已有输入和成功标准。\n2. 创建简洁的工作计划、模板、自动化思路或决策辅助，减少手动协调。\n3. 只有当缺失信息会明显改变输出时才提问；否则先做合理假设并继续推进。\n4. 保持本地硬件友好：优先使用脚本、模板、检查清单、小模型或 CPU 可承受的流程，避免依赖云端专用资源或大规模训练。\n5. 产出用户需要的文档、流程、清单、分析、代码修改或决策支持。\n6. 对照成功标准检查结果，并列出剩余风险或后续事项。\n\n## 预期输出\n\n- 针对用户当前情境的定制回答或产物。\n- 当任务可复用时，提供检查清单或工作流程。\n- 说明结果如何被检查的验证备注。\n\n## 验证\n\n- 输出直接回应发现的原始需求。\n- 用户不需要阅读原始来源帖子也能采取行动。\n- 假设、限制和所需输入清晰可见。\n- 在有帮助时，最终回复包含简短的使用说明或下一步建议。\n\n## 触发方式\n\n关键词：`work-productivity`, `error messages`, `debugging`, `user feedback`, `support`, `troubleshooting`\n\n示例触发句：\n\n- `Help me Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `I need a practical workflow for Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `Use $error-message-improver to handle Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n\nFile v0.20260907.40414:agents/openai.yaml\n\ninterface:\n  display_name: \"Error Message Improver\"\n  short_description: \"Helps with Users and support teams need clearer error message...\"\n  default_prompt: \"Use $error-message-improver to help me Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.\"\n\npolicy:\n  allow_implicit_invocation: true\n\nArchive v0.20260906.40422: 8 files, 10467 bytes\n\nFiles: agents/openai.yaml (364b), README.md (3039b), README.zh-CN.md (3047b), references/requirement-plan.md (4893b), skill-card.md (2673b), SKILL.md (3102b), SKILL.zh-CN.md (2976b), _meta.json (152b)\n\nFile v0.20260906.40422:SKILL.md\n\n---\nname: error-message-improver\ndescription: >-\n  Help users with Validated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.. Use when a user asks for work-productivity, error messages, debugging, user feedback, support, or needs a practical workflow, artifact, checklist, analysis, or implementation support for this requirement.\n---\n\n# Error Message Improver\n\n## Requirement\n\nUse this skill to help application developers, support teams, SaaS operators, and users who lose time when vague errors block troubleshooting with:\n\n> Validated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\nDemand score: 100/100 (`70/70` demand, `30/30` local feasibility).\nEvidence: 12 signals across 3 source families.\n\nRead `references/requirement-plan.md` when source evidence, planning details, or review criteria are needed.\n\n## Workflow\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Create a concise work plan, template, automation outline, or decision aid that reduces manual coordination.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Validation\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Triggers\n\nKeywords: `work-productivity`, `error messages`, `debugging`, `user feedback`, `support`, `troubleshooting`\n\nExample trigger sentences:\n\n- `Help me Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `I need a practical workflow for Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `Use $error-message-improver to handle Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n\nFile v0.20260906.40422:README.md\n\n# Error Message Improver\n\n## Requirement\n\nValidated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\nAudience: application developers, support teams, SaaS operators, and users who lose time when vague errors block troubleshooting\n\nCategory: `work-productivity`\n\nDemand score: 100/100\n\nEvidence coverage: 12 signals across 3 source families.\n\n## Evidence\n\n- github-issues: [regex format implementation?](https://github.com/sourcemeta/jsonschema/issues/842)\n- github-issues: [Anidb is temporarily down, we should have a better error message](https://github.com/pystardust/ani-cli/issues/1893)\n- segmentfault-search: [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search: [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search: [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search: [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search: [答： c++单例类编译不通过](https://segmentfault.com/q/1010000004886164/a-1020000004886445)\n- segmentfault-search: [error-messages](https://segmentfault.com/t/error-messages)\n- segmentfault-search: [问： vue自定义指令报错](https://segmentfault.com/q/1010000009322969)\n- github-issues: [Two error-signalling conventions coexist](https://github.com/sysbiolab/RGraphSpace/issues/12)\n- github-issues: [Review reminders: allow scheduling exact alarms](https://github.com/ankidroid/Anki-Android/issues/21752)\n- hacker-news-search: [Zig: Pointer Stability for ArrayLists](https://news.ycombinator.com/item?id=49502293)\n\n## How This Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Usage\n\nKeywords: `work-productivity`, `error messages`, `debugging`, `user feedback`, `support`, `troubleshooting`\n\nTrigger sentences:\n\n- `Help me Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `I need a practical workflow for Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `Use $error-message-improver to handle Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n\n## Files\n\n- `SKILL.md`: English skill instructions.\n- `SKILL.zh-CN.md`: Chinese skill instructions.\n- `README.md`: English user-facing guide.\n- `README.zh-CN.md`: Chinese user-facing guide.\n\nFile v0.20260906.40422:_meta.json\n\n{\n  \"ownerId\": \"kn7be2ewez5ks45t5nmdez8j51839xpk\",\n  \"slug\": \"error-message-improver\",\n  \"version\": \"0.20260906.40422\",\n  \"publishedAt\": 1788667628886\n}\n\nFile v0.20260906.40422:references/requirement-plan.md\n\n# Requirement Plan\n\n## Live Requirement\n\nValidated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n## Audience\n\napplication developers, support teams, SaaS operators, and users who lose time when vague errors block troubleshooting\n\n## Category\n\nwork-productivity\n\n## Requirement Score\n\nTotal: 100/100\n\nDemand: 70/70\n\nLocal feasibility: 30/30\n\nEvidence coverage: 12 signals across 3 source families.\n\nScoring rationale:\n\n- Evidence count: 12; required minimum: 3.\n- Distinct source families: 3; sources: github, hacker-news, segmentfault.\n- Demand score: 70/70 based on corroboration, source diversity, and professional/community signal.\n- Local feasibility score: 30/30.\n- Implementation is a documentation, workflow, code, or analysis skill that can run on ordinary CPU hardware.\n\n## Evidence\n\n- github-issues (2026-09-03T08:07:56+00:00): [regex format implementation?](https://github.com/sourcemeta/jsonschema/issues/842)\n- github-issues (2026-09-05T12:09:03+00:00): [Anidb is temporarily down, we should have a better error message](https://github.com/pystardust/ani-cli/issues/1893)\n- segmentfault-search (2026-09-06T04:05:17.879464+00:00): [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search (2026-09-06T04:05:17.879464+00:00): [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search (2026-09-06T04:05:17.879464+00:00): [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search (2026-09-06T04:05:17.879464+00:00): [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search (2026-09-06T04:05:17.879464+00:00): [答： c++单例类编译不通过](https://segmentfault.com/q/1010000004886164/a-1020000004886445)\n- segmentfault-search (2026-09-06T04:05:17.879464+00:00): [error-messages](https://segmentfault.com/t/error-messages)\n- segmentfault-search (2026-09-06T04:05:17.879464+00:00): [问： vue自定义指令报错](https://segmentfault.com/q/1010000009322969)\n- github-issues (2026-09-03T10:14:30+00:00): [Two error-signalling conventions coexist](https://github.com/sysbiolab/RGraphSpace/issues/12)\n- github-issues (2026-09-06T01:43:31+00:00): [Review reminders: allow scheduling exact alarms](https://github.com/ankidroid/Anki-Android/issues/21752)\n- hacker-news-search (2026-08-30T20:10:44+00:00): [Zig: Pointer Stability for ArrayLists](https://news.ycombinator.com/item?id=49502293)\n\n## How The Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Executable Implementation Plan\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Create a concise work plan, template, automation outline, or decision aid that reduces manual coordination.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Review Criteria\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Usage Signals\n\nKeywords: work-productivity, error messages, debugging, user feedback, support, troubleshooting\n\nTrigger sentences:\n\n- Help me Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.\n- I need a practical workflow for Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.\n- Use $error-message-improver to handle Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.\n\nFile v0.20260906.40422:README.zh-CN.md\n\n# Error Message Improver\n\n## 需求\n\nValidated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n目标用户：application developers, support teams, SaaS operators, and users who lose time when vague errors block troubleshooting\n\n分类：`工作与效率`\n\n需求评分：100/100\n\n证据覆盖：12 条信号，覆盖 3 个来源类型。\n\n## 来源证据\n\n- github-issues：[regex format implementation?](https://github.com/sourcemeta/jsonschema/issues/842)\n- github-issues：[Anidb is temporarily down, we should have a better error message](https://github.com/pystardust/ani-cli/issues/1893)\n- segmentfault-search：[HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search：[javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search：[typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search：[ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search：[答： c++单例类编译不通过](https://segmentfault.com/q/1010000004886164/a-1020000004886445)\n- segmentfault-search：[error-messages](https://segmentfault.com/t/error-messages)\n- segmentfault-search：[问： vue自定义指令报错](https://segmentfault.com/q/1010000009322969)\n- github-issues：[Two error-signalling conventions coexist](https://github.com/sysbiolab/RGraphSpace/issues/12)\n- github-issues：[Review reminders: allow scheduling exact alarms](https://github.com/ankidroid/Anki-Android/issues/21752)\n- hacker-news-search：[Zig: Pointer Stability for ArrayLists](https://news.ycombinator.com/item?id=49502293)\n\n## 这个技能如何满足需求\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## 使用方式\n\n关键词：`work-productivity`, `error messages`, `debugging`, `user feedback`, `support`, `troubleshooting`\n\n触发句：\n\n- `Help me Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `I need a practical workflow for Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `Use $error-message-improver to handle Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n\n## 文件\n\n- `SKILL.md`：英文版技能说明。\n- `SKILL.zh-CN.md`：中文版技能说明。\n- `README.md`：英文版用户说明。\n- `README.zh-CN.md`：中文版用户说明。\n\nFile v0.20260906.40422:skill-card.md\n\n## Description:\n\nHelps developers, support teams, SaaS operators, and users turn vague error messages into clearer guidance that explains what failed, why it failed, and what action to take next.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kyro-ma](https://clawhub.ai/user/kyro-ma)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers, support teams, SaaS operators, and end users use this skill to rewrite, review, and operationalize error messages so troubleshooting output explains the failure, likely cause, and next action.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Broad implicit-invocation wording may route general debugging or support prompts into this skill automatically.\n\nMitigation: Review the invocation policy before deployment and narrow trigger wording or disable implicit invocation when a workspace needs tighter routing.\n\nRisk: Suggested error-message changes can still be incomplete, misleading, or too revealing for a production product.\n\nMitigation: Review proposed messages against product facts, support policy, privacy requirements, and the stated success criteria before release.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/kyro-ma/skills/error-message-improver)\n- [Requirement Plan](references/requirement-plan.md)\n- [regex format implementation?](https://github.com/sourcemeta/jsonschema/issues/842)\n- [Anidb is temporarily down, we should have a better error message](https://github.com/pystardust/ani-cli/issues/1893)\n- [Two error-signalling conventions coexist](https://github.com/sysbiolab/RGraphSpace/issues/12)\n- [Review reminders: allow scheduling exact alarms](https://github.com/ankidroid/Anki-Android/issues/21752)\n- [error-messages](https://segmentfault.com/t/error-messages)\n- [Zig: Pointer Stability for ArrayLists](https://news.ycombinator.com/item?id=49502293)\n\n## Skill Output:\n\n**Output Type(s):** [Guidance, Analysis, Markdown, Code, Configuration, Shell commands]\n\n**Output Format:** [Markdown with optional code, shell command, checklist, workflow, and configuration snippets]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [The skill produces concise, human-facing troubleshooting artifacts and validation notes; it does not require external tools or credentials.]\n\n## Skill Version(s):\n\n0.20260906.40422 (source: server release metadata)\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 v0.20260906.40422:SKILL.zh-CN.md\n\n---\nname: error-message-improver\ndescription: >-\n  帮助用户处理“Validated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.”。当用户提出 work-productivity, error messages, debugging, user feedback, support，或需要围绕该需求获得实用流程、产物、检查清单、分析或实现支持时使用。\n---\n\n# Error Message Improver\n\n## 需求\n\n使用这个技能帮助以下用户群体：application developers, support teams, SaaS operators, and users who lose time when vague errors block troubleshooting\n\n> Validated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n需求评分：100/100（需求强度 `70/70`，本地可执行性 `30/30`）。\n证据：12 条信号，覆盖 3 个来源类型。\n\n如需查看来源证据、执行计划或评审标准，请阅读 `references/requirement-plan.md`。\n\n## 工作流程\n\n1. 重新说明用户想要的结果、限制、已有输入和成功标准。\n2. 创建简洁的工作计划、模板、自动化思路或决策辅助，减少手动协调。\n3. 只有当缺失信息会明显改变输出时才提问；否则先做合理假设并继续推进。\n4. 保持本地硬件友好：优先使用脚本、模板、检查清单、小模型或 CPU 可承受的流程，避免依赖云端专用资源或大规模训练。\n5. 产出用户需要的文档、流程、清单、分析、代码修改或决策支持。\n6. 对照成功标准检查结果，并列出剩余风险或后续事项。\n\n## 预期输出\n\n- 针对用户当前情境的定制回答或产物。\n- 当任务可复用时，提供检查清单或工作流程。\n- 说明结果如何被检查的验证备注。\n\n## 验证\n\n- 输出直接回应发现的原始需求。\n- 用户不需要阅读原始来源帖子也能采取行动。\n- 假设、限制和所需输入清晰可见。\n- 在有帮助时，最终回复包含简短的使用说明或下一步建议。\n\n## 触发方式\n\n关键词：`work-productivity`, `error messages`, `debugging`, `user feedback`, `support`, `troubleshooting`\n\n示例触发句：\n\n- `Help me Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `I need a practical workflow for Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `Use $error-message-improver to handle Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n\nFile v0.20260906.40422:agents/openai.yaml\n\ninterface:\n  display_name: \"Error Message Improver\"\n  short_description: \"Helps with Users and support teams need clearer error message...\"\n  default_prompt: \"Use $error-message-improver to help me Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.\"\n\npolicy:\n  allow_implicit_invocation: true\n\nArchive v0.20260905.61641: 8 files, 10282 bytes\n\nFiles: agents/openai.yaml (364b), README.md (3129b), README.zh-CN.md (3137b), references/requirement-plan.md (4983b), skill-card.md (2027b), SKILL.md (3102b), SKILL.zh-CN.md (2976b), _meta.json (152b)\n\nFile v0.20260905.61641:SKILL.md\n\n---\nname: error-message-improver\ndescription: >-\n  Help users with Validated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.. Use when a user asks for work-productivity, error messages, debugging, user feedback, support, or needs a practical workflow, artifact, checklist, analysis, or implementation support for this requirement.\n---\n\n# Error Message Improver\n\n## Requirement\n\nUse this skill to help application developers, support teams, SaaS operators, and users who lose time when vague errors block troubleshooting with:\n\n> Validated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\nDemand score: 100/100 (`70/70` demand, `30/30` local feasibility).\nEvidence: 12 signals across 3 source families.\n\nRead `references/requirement-plan.md` when source evidence, planning details, or review criteria are needed.\n\n## Workflow\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Create a concise work plan, template, automation outline, or decision aid that reduces manual coordination.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Validation\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Triggers\n\nKeywords: `work-productivity`, `error messages`, `debugging`, `user feedback`, `support`, `troubleshooting`\n\nExample trigger sentences:\n\n- `Help me Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `I need a practical workflow for Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `Use $error-message-improver to handle Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n\nFile v0.20260905.61641:README.md\n\n# Error Message Improver\n\n## Requirement\n\nValidated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\nAudience: application developers, support teams, SaaS operators, and users who lose time when vague errors block troubleshooting\n\nCategory: `work-productivity`\n\nDemand score: 100/100\n\nEvidence coverage: 12 signals across 3 source families.\n\n## Evidence\n\n- github-issues: [regex format implementation?](https://github.com/sourcemeta/jsonschema/issues/842)\n- github-issues: [pod: mint_token sends the pod's .local_secret over TCP loopback — route it over the pod's unix socket](https://github.com/kirodotdev/KiroCrew/issues/8552)\n- segmentfault-search: [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search: [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search: [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search: [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search: [答： c++单例类编译不通过](https://segmentfault.com/q/1010000004886164/a-1020000004886445)\n- segmentfault-search: [error-messages](https://segmentfault.com/t/error-messages)\n- segmentfault-search: [问： vue自定义指令报错](https://segmentfault.com/q/1010000009322969)\n- github-issues: [Suggestion: Replace latex with typst](https://github.com/Open-Science-Ledger/how-to-train-your-slop-cannon/issues/1)\n- hacker-news-search: [Zig: Pointer Stability for ArrayLists](https://news.ycombinator.com/item?id=49502293)\n- hacker-news-search: [Arbitrary code execution in QubesOS via copy-to-VM error reporting backchannel](https://news.ycombinator.com/item?id=49501950)\n\n## How This Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Usage\n\nKeywords: `work-productivity`, `error messages`, `debugging`, `user feedback`, `support`, `troubleshooting`\n\nTrigger sentences:\n\n- `Help me Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `I need a practical workflow for Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `Use $error-message-improver to handle Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n\n## Files\n\n- `SKILL.md`: English skill instructions.\n- `SKILL.zh-CN.md`: Chinese skill instructions.\n- `README.md`: English user-facing guide.\n- `README.zh-CN.md`: Chinese user-facing guide.\n\nFile v0.20260905.61641:_meta.json\n\n{\n  \"ownerId\": \"kn7be2ewez5ks45t5nmdez8j51839xpk\",\n  \"slug\": \"error-message-improver\",\n  \"version\": \"0.20260905.61641\",\n  \"publishedAt\": 1788589171643\n}\n\nFile v0.20260905.61641:references/requirement-plan.md\n\n# Requirement Plan\n\n## Live Requirement\n\nValidated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n## Audience\n\napplication developers, support teams, SaaS operators, and users who lose time when vague errors block troubleshooting\n\n## Category\n\nwork-productivity\n\n## Requirement Score\n\nTotal: 100/100\n\nDemand: 70/70\n\nLocal feasibility: 30/30\n\nEvidence coverage: 12 signals across 3 source families.\n\nScoring rationale:\n\n- Evidence count: 12; required minimum: 3.\n- Distinct source families: 3; sources: github, hacker-news, segmentfault.\n- Demand score: 70/70 based on corroboration, source diversity, and professional/community signal.\n- Local feasibility score: 30/30.\n- Implementation is a documentation, workflow, code, or analysis skill that can run on ordinary CPU hardware.\n\n## Evidence\n\n- github-issues (2026-09-03T08:07:56+00:00): [regex format implementation?](https://github.com/sourcemeta/jsonschema/issues/842)\n- github-issues (2026-09-04T20:33:36+00:00): [pod: mint_token sends the pod's .local_secret over TCP loopback — route it over the pod's unix socket](https://github.com/kirodotdev/KiroCrew/issues/8552)\n- segmentfault-search (2026-09-05T06:17:27.940646+00:00): [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search (2026-09-05T06:17:27.940646+00:00): [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search (2026-09-05T06:17:27.940646+00:00): [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search (2026-09-05T06:17:27.940646+00:00): [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search (2026-09-05T06:17:27.940646+00:00): [答： c++单例类编译不通过](https://segmentfault.com/q/1010000004886164/a-1020000004886445)\n- segmentfault-search (2026-09-05T06:17:27.940646+00:00): [error-messages](https://segmentfault.com/t/error-messages)\n- segmentfault-search (2026-09-05T06:17:27.940646+00:00): [问： vue自定义指令报错](https://segmentfault.com/q/1010000009322969)\n- github-issues (2026-09-04T11:40:36+00:00): [Suggestion: Replace latex with typst](https://github.com/Open-Science-Ledger/how-to-train-your-slop-cannon/issues/1)\n- hacker-news-search (2026-08-30T20:10:44+00:00): [Zig: Pointer Stability for ArrayLists](https://news.ycombinator.com/item?id=49502293)\n- hacker-news-search (2026-08-30T19:28:03+00:00): [Arbitrary code execution in QubesOS via copy-to-VM error reporting backchannel](https://news.ycombinator.com/item?id=49501950)\n\n## How The Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Executable Implementation Plan\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Create a concise work plan, template, automation outline, or decision aid that reduces manual coordination.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Review Criteria\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Usage Signals\n\nKeywords: work-productivity, error messages, debugging, user feedback, support, troubleshooting\n\nTrigger sentences:\n\n- Help me Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.\n- I need a practical workflow for Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.\n- Use $error-message-improver to handle Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.\n\nFile v0.20260905.61641:README.zh-CN.md\n\n# Error Message Improver\n\n## 需求\n\nValidated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n目标用户：application developers, support teams, SaaS operators, and users who lose time when vague errors block troubleshooting\n\n分类：`工作与效率`\n\n需求评分：100/100\n\n证据覆盖：12 条信号，覆盖 3 个来源类型。\n\n## 来源证据\n\n- github-issues：[regex format implementation?](https://github.com/sourcemeta/jsonschema/issues/842)\n- github-issues：[pod: mint_token sends the pod's .local_secret over TCP loopback — route it over the pod's unix socket](https://github.com/kirodotdev/KiroCrew/issues/8552)\n- segmentfault-search：[HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search：[javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search：[typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search：[ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search：[答： c++单例类编译不通过](https://segmentfault.com/q/1010000004886164/a-1020000004886445)\n- segmentfault-search：[error-messages](https://segmentfault.com/t/error-messages)\n- segmentfault-search：[问： vue自定义指令报错](https://segmentfault.com/q/1010000009322969)\n- github-issues：[Suggestion: Replace latex with typst](https://github.com/Open-Science-Ledger/how-to-train-your-slop-cannon/issues/1)\n- hacker-news-search：[Zig: Pointer Stability for ArrayLists](https://news.ycombinator.com/item?id=49502293)\n- hacker-news-search：[Arbitrary code execution in QubesOS via copy-to-VM error reporting backchannel](https://news.ycombinator.com/item?id=49501950)\n\n## 这个技能如何满足需求\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## 使用方式\n\n关键词：`work-productivity`, `error messages`, `debugging`, `user feedback`, `support`, `troubleshooting`\n\n触发句：\n\n- `Help me Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `I need a practical workflow for Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `Use $error-message-improver to handle Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n\n## 文件\n\n- `SKILL.md`：英文版技能说明。\n- `SKILL.zh-CN.md`：中文版技能说明。\n- `README.md`：英文版用户说明。\n- `README.zh-CN.md`：中文版用户说明。\n\nFile v0.20260905.61641:skill-card.md\n\n## Description:\n\nHelps developers, support teams, SaaS operators, and users turn vague errors into clear explanations of what failed, why it failed, and what to do next.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kyro-ma](https://clawhub.ai/user/kyro-ma)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers, support teams, SaaS operators, and end users use this skill to produce practical rewrites, workflows, checklists, analysis, code changes, or decision support that make error messages actionable.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Broad debugging or support-related trigger wording may activate the skill for unrelated tasks.\n\nMitigation: Review invocation behavior before deployment and tighten trigger wording if accidental activation is observed.\n\nRisk: Generated error-message rewrites or troubleshooting guidance could be incomplete or misleading if the user provides limited context.\n\nMitigation: Check outputs against the stated failure, cause, next action, and known product constraints before using them in customer-facing support or application text.\n\n## Reference(s):\n\n- [Requirement Plan](references/requirement-plan.md)\n- [ClawHub Skill Page](https://clawhub.ai/kyro-ma/skills/error-message-improver)\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, Code, Configuration, Guidance]\n\n**Output Format:** [Markdown or plain text, with code or configuration snippets when requested]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May include assumptions, validation notes, checklists, workflows, or next steps tailored to the user's error-message task.]\n\n## Skill Version(s):\n\n0.20260905.61641 (source: server release metadata)\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 v0.20260905.61641:SKILL.zh-CN.md\n\n---\nname: error-message-improver\ndescription: >-\n  帮助用户处理“Validated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.”。当用户提出 work-productivity, error messages, debugging, user feedback, support，或需要围绕该需求获得实用流程、产物、检查清单、分析或实现支持时使用。\n---\n\n# Error Message Improver\n\n## 需求\n\n使用这个技能帮助以下用户群体：application developers, support teams, SaaS operators, and users who lose time when vague errors block troubleshooting\n\n> Validated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n需求评分：100/100（需求强度 `70/70`，本地可执行性 `30/30`）。\n证据：12 条信号，覆盖 3 个来源类型。\n\n如需查看来源证据、执行计划或评审标准，请阅读 `references/requirement-plan.md`。\n\n## 工作流程\n\n1. 重新说明用户想要的结果、限制、已有输入和成功标准。\n2. 创建简洁的工作计划、模板、自动化思路或决策辅助，减少手动协调。\n3. 只有当缺失信息会明显改变输出时才提问；否则先做合理假设并继续推进。\n4. 保持本地硬件友好：优先使用脚本、模板、检查清单、小模型或 CPU 可承受的流程，避免依赖云端专用资源或大规模训练。\n5. 产出用户需要的文档、流程、清单、分析、代码修改或决策支持。\n6. 对照成功标准检查结果，并列出剩余风险或后续事项。\n\n## 预期输出\n\n- 针对用户当前情境的定制回答或产物。\n- 当任务可复用时，提供检查清单或工作流程。\n- 说明结果如何被检查的验证备注。\n\n## 验证\n\n- 输出直接回应发现的原始需求。\n- 用户不需要阅读原始来源帖子也能采取行动。\n- 假设、限制和所需输入清晰可见。\n- 在有帮助时，最终回复包含简短的使用说明或下一步建议。\n\n## 触发方式\n\n关键词：`work-productivity`, `error messages`, `debugging`, `user feedback`, `support`, `troubleshooting`\n\n示例触发句：\n\n- `Help me Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `I need a practical workflow for Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `Use $error-message-improver to handle Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n\nFile v0.20260905.61641:agents/openai.yaml\n\ninterface:\n  display_name: \"Error Message Improver\"\n  short_description: \"Helps with Users and support teams need clearer error message...\"\n  default_prompt: \"Use $error-message-improver to help me Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.\"\n\npolicy:\n  allow_implicit_invocation: true\n\nArchive v0.20260904.60001: 8 files, 11139 bytes\n\nFiles: agents/openai.yaml (363b), README.md (3892b), README.zh-CN.md (3901b), references/requirement-plan.md (5690b), skill-card.md (1937b), SKILL.md (3095b), SKILL.zh-CN.md (2974b), _meta.json (152b)\n\nFile v0.20260904.60001:SKILL.md\n\n---\nname: error-message-improver\ndescription: >-\n  Help users with Validated demand: Remote workers and technically curious households need local diagnostic workflows for network issues such as bufferbloat, router problems, and latency. This requirement is supported by 11 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.. Use when a user asks for general-help, bufferbloat, router, modem, latency, or needs a practical workflow, artifact, checklist, analysis, or implementation support for this requirement.\n---\n\n# Error Message Improver\n\n## Requirement\n\nUse this skill to help remote workers, gamers, home-office users, and small teams who need to diagnose internet quality with consumer networking hardware with:\n\n> Validated demand: Remote workers and technically curious households need local diagnostic workflows for network issues such as bufferbloat, router problems, and latency. This requirement is supported by 11 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\nDemand score: 100/100 (`70/70` demand, `30/30` local feasibility).\nEvidence: 11 signals across 3 source families.\n\nRead `references/requirement-plan.md` when source evidence, planning details, or review criteria are needed.\n\n## Workflow\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Convert the request into a practical plan and useful output.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Validation\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Triggers\n\nKeywords: `general-help`, `bufferbloat`, `router`, `modem`, `latency`, `network troubleshooting`\n\nExample trigger sentences:\n\n- `Help me Remote workers and technically curious households need local diagnostic workflows for network issues such as bufferbloat.`\n- `I need a practical workflow for Remote workers and technically curious households need local diagnostic workflows for network issues such as bufferbloat.`\n- `Use $error-message-improver to handle Remote workers and technically curious households need local diagnostic workflows for network issues such as bufferbloat.`\n\nFile v0.20260904.60001:README.md\n\n# Error Message Improver\n\n## Requirement\n\nValidated demand: Remote workers and technically curious households need local diagnostic workflows for network issues such as bufferbloat, router problems, and latency. This requirement is supported by 11 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\nAudience: remote workers, gamers, home-office users, and small teams who need to diagnose internet quality with consumer networking hardware\n\nCategory: `general-help`\n\nDemand score: 100/100\n\nEvidence coverage: 11 signals across 3 source families.\n\n## Evidence\n\n- segmentfault-search: [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search: [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search: [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search: [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search: [IPQ6010 with QCN9074\\|support connectivity with 180+ clients](https://segmentfault.com/a/1190000043879892)\n- segmentfault-search: [DR6018V4/wifi6/IPQ6010/IPQ6018/2.5G/ETH/5G/Modem 802-11AX](https://segmentfault.com/a/1190000041766461)\n- segmentfault-search: [答： 商城规格选择操作](https://segmentfault.com/pq/1590000011118552/a-1020000011122672)\n- hacker-news-search: [France reaches 94.9% fiber coverage in 2026](https://news.ycombinator.com/item?id=49452303)\n- csdn-search: [cfosspeed_v406注册版](https://wenku.csdn.net/doc/4xxu6mdnbm?ops_request_misc=elastic_search_misc&request_id=32fffea22e60487794eb10ab621678a1&biz_id=&utm_medium=distribute.pc_search_result.none-task-c_download-2~all~ElasticCommercialInsert~search_v2-1-4xxu6mdnbm-null-null.142^v102^pc_search_result_base4&utm_term=bufferbloat%20modem%20router)\n- csdn-search: [【QXDM从入门到精通】：掌握高通日志抓取的15大核心技能与实战秘籍](https://wenku.csdn.net/column/7zsa6zvkoj?ops_request_misc=elastic_search_misc&request_id=32fffea22e60487794eb10ab621678a1&biz_id=&utm_medium=distribute.pc_search_result.none-task-wenku_aigc_column-2~all~ElasticSearch~search_v2-3-7zsa6zvkoj-null-null.142^v102^pc_search_result_base4&utm_term=bufferbloat%20modem%20router)\n- csdn-search: [H618原厂固件网络堆栈优化：提升4G_Wi-Fi并发稳定性的6项底层调参技巧](https://wenku.csdn.net/column/6xsdq38fpi?ops_request_misc=elastic_search_misc&request_id=32fffea22e60487794eb10ab621678a1&biz_id=&utm_medium=distribute.pc_search_result.none-task-wenku_aigc_column-2~all~ElasticSearch~search_v2-4-6xsdq38fpi-null-null.142^v102^pc_search_result_base4&utm_term=bufferbloat%20modem%20router)\n\n## How This Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Usage\n\nKeywords: `general-help`, `bufferbloat`, `router`, `modem`, `latency`, `network troubleshooting`\n\nTrigger sentences:\n\n- `Help me Remote workers and technically curious households need local diagnostic workflows for network issues such as bufferbloat.`\n- `I need a practical workflow for Remote workers and technically curious households need local diagnostic workflows for network issues such as bufferbloat.`\n- `Use $error-message-improver to handle Remote workers and technically curious households need local diagnostic workflows for network issues such as bufferbloat.`\n\n## Files\n\n- `SKILL.md`: English skill instructions.\n- `SKILL.zh-CN.md`: Chinese skill instructions.\n- `README.md`: English user-facing guide.\n- `README.zh-CN.md`: Chinese user-facing guide.\n\nFile v0.20260904.60001:_meta.json\n\n{\n  \"ownerId\": \"kn7be2ewez5ks45t5nmdez8j51839xpk\",\n  \"slug\": \"error-message-improver\",\n  \"version\": \"0.20260904.60001\",\n  \"publishedAt\": 1788501834525\n}\n\nFile v0.20260904.60001:references/requirement-plan.md\n\n# Requirement Plan\n\n## Live Requirement\n\nValidated demand: Remote workers and technically curious households need local diagnostic workflows for network issues such as bufferbloat, router problems, and latency. This requirement is supported by 11 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n## Audience\n\nremote workers, gamers, home-office users, and small teams who need to diagnose internet quality with consumer networking hardware\n\n## Category\n\ngeneral-help\n\n## Requirement Score\n\nTotal: 100/100\n\nDemand: 70/70\n\nLocal feasibility: 30/30\n\nEvidence coverage: 11 signals across 3 source families.\n\nScoring rationale:\n\n- Evidence count: 11; required minimum: 3.\n- Distinct source families: 3; sources: csdn, hacker-news, segmentfault.\n- Demand score: 70/70 based on corroboration, source diversity, and professional/community signal.\n- Local feasibility score: 30/30.\n- Implementation is a documentation, workflow, code, or analysis skill that can run on ordinary CPU hardware.\n\n## Evidence\n\n- segmentfault-search (2026-09-04T06:01:22.492563+00:00): [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search (2026-09-04T06:01:22.493573+00:00): [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search (2026-09-04T06:01:22.493573+00:00): [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search (2026-09-04T06:01:22.493573+00:00): [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search (2026-09-04T06:01:22.494570+00:00): [IPQ6010 with QCN9074\\|support connectivity with 180+ clients](https://segmentfault.com/a/1190000043879892)\n- segmentfault-search (2026-09-04T06:01:22.494570+00:00): [DR6018V4/wifi6/IPQ6010/IPQ6018/2.5G/ETH/5G/Modem 802-11AX](https://segmentfault.com/a/1190000041766461)\n- segmentfault-search (2026-09-04T06:01:22.494570+00:00): [答： 商城规格选择操作](https://segmentfault.com/pq/1590000011118552/a-1020000011122672)\n- hacker-news-search (2026-08-26T16:56:26+00:00): [France reaches 94.9% fiber coverage in 2026](https://news.ycombinator.com/item?id=49452303)\n- csdn-search (2026-09-04T06:01:21.696136+00:00): [cfosspeed_v406注册版](https://wenku.csdn.net/doc/4xxu6mdnbm?ops_request_misc=elastic_search_misc&request_id=32fffea22e60487794eb10ab621678a1&biz_id=&utm_medium=distribute.pc_search_result.none-task-c_download-2~all~ElasticCommercialInsert~search_v2-1-4xxu6mdnbm-null-null.142^v102^pc_search_result_base4&utm_term=bufferbloat%20modem%20router)\n- csdn-search (2026-09-04T06:01:21.696136+00:00): [【QXDM从入门到精通】：掌握高通日志抓取的15大核心技能与实战秘籍](https://wenku.csdn.net/column/7zsa6zvkoj?ops_request_misc=elastic_search_misc&request_id=32fffea22e60487794eb10ab621678a1&biz_id=&utm_medium=distribute.pc_search_result.none-task-wenku_aigc_column-2~all~ElasticSearch~search_v2-3-7zsa6zvkoj-null-null.142^v102^pc_search_result_base4&utm_term=bufferbloat%20modem%20router)\n- csdn-search (2026-09-04T06:01:21.696136+00:00): [H618原厂固件网络堆栈优化：提升4G_Wi-Fi并发稳定性的6项底层调参技巧](https://wenku.csdn.net/column/6xsdq38fpi?ops_request_misc=elastic_search_misc&request_id=32fffea22e60487794eb10ab621678a1&biz_id=&utm_medium=distribute.pc_search_result.none-task-wenku_aigc_column-2~all~ElasticSearch~search_v2-4-6xsdq38fpi-null-null.142^v102^pc_search_result_base4&utm_term=bufferbloat%20modem%20router)\n\n## How The Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Executable Implementation Plan\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Convert the request into a practical plan and useful output.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Review Criteria\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Usage Signals\n\nKeywords: general-help, bufferbloat, router, modem, latency, network troubleshooting\n\nTrigger sentences:\n\n- Help me Remote workers and technically curious households need local diagnostic workflows for network issues such as bufferbloat.\n- I need a practical workflow for Remote workers and technically curious households need local diagnostic workflows for network issues such as bufferbloat.\n- Use $error-message-improver to handle Remote workers and technically curious households need local diagnostic workflows for network issues such as bufferbloat.\n\nFile v0.20260904.60001:README.zh-CN.md\n\n# Error Message Improver\n\n## 需求\n\nValidated demand: Remote workers and technically curious households need local diagnostic workflows for network issues such as bufferbloat, router problems, and latency. This requirement is supported by 11 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n目标用户：remote workers, gamers, home-office users, and small teams who need to diagnose internet quality with consumer networking hardware\n\n分类：`通用帮助`\n\n需求评分：100/100\n\n证据覆盖：11 条信号，覆盖 3 个来源类型。\n\n## 来源证据\n\n- segmentfault-search：[HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search：[javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search：[typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search：[ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search：[IPQ6010 with QCN9074\\|support connectivity with 180+ clients](https://segmentfault.com/a/1190000043879892)\n- segmentfault-search：[DR6018V4/wifi6/IPQ6010/IPQ6018/2.5G/ETH/5G/Modem 802-11AX](https://segmentfault.com/a/1190000041766461)\n- segmentfault-search：[答： 商城规格选择操作](https://segmentfault.com/pq/1590000011118552/a-1020000011122672)\n- hacker-news-search：[France reaches 94.9% fiber coverage in 2026](https://news.ycombinator.com/item?id=49452303)\n- csdn-search：[cfosspeed_v406注册版](https://wenku.csdn.net/doc/4xxu6mdnbm?ops_request_misc=elastic_search_misc&request_id=32fffea22e60487794eb10ab621678a1&biz_id=&utm_medium=distribute.pc_search_result.none-task-c_download-2~all~ElasticCommercialInsert~search_v2-1-4xxu6mdnbm-null-null.142^v102^pc_search_result_base4&utm_term=bufferbloat%20modem%20router)\n- csdn-search：[【QXDM从入门到精通】：掌握高通日志抓取的15大核心技能与实战秘籍](https://wenku.csdn.net/column/7zsa6zvkoj?ops_request_misc=elastic_search_misc&request_id=32fffea22e60487794eb10ab621678a1&biz_id=&utm_medium=distribute.pc_search_result.none-task-wenku_aigc_column-2~all~ElasticSearch~search_v2-3-7zsa6zvkoj-null-null.142^v102^pc_search_result_base4&utm_term=bufferbloat%20modem%20router)\n- csdn-search：[H618原厂固件网络堆栈优化：提升4G_Wi-Fi并发稳定性的6项底层调参技巧](https://wenku.csdn.net/column/6xsdq38fpi?ops_request_misc=elastic_search_misc&request_id=32fffea22e60487794eb10ab621678a1&biz_id=&utm_medium=distribute.pc_search_result.none-task-wenku_aigc_column-2~all~ElasticSearch~search_v2-4-6xsdq38fpi-null-null.142^v102^pc_search_result_base4&utm_term=bufferbloat%20modem%20router)\n\n## 这个技能如何满足需求\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## 使用方式\n\n关键词：`general-help`, `bufferbloat`, `router`, `modem`, `latency`, `network troubleshooting`\n\n触发句：\n\n- `Help me Remote workers and technically curious households need local diagnostic workflows for network issues such as bufferbloat.`\n- `I need a practical workflow for Remote workers and technically curious households need local diagnostic workflows for network issues such as bufferbloat.`\n- `Use $error-message-improver to handle Remote workers and technically curious households need local diagnostic workflows for network issues such as bufferbloat.`\n\n## 文件\n\n- `SKILL.md`：英文版技能说明。\n- `SKILL.zh-CN.md`：中文版技能说明。\n- `README.md`：英文版用户说明。\n- `README.zh-CN.md`：中文版用户说明。\n\nFile v0.20260904.60001:skill-card.md\n\n## Description:\n\nHelps remote workers, gamers, home-office users, and small teams create local diagnostic workflows for consumer-network issues such as bufferbloat, router problems, modem problems, and latency.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kyro-ma](https://clawhub.ai/user/kyro-ma)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nExternal users use this skill to turn home or small-office network troubleshooting requests into practical diagnostic workflows, checklists, analysis, code, or decision support. It focuses on local-hardware-friendly approaches for issues such as bufferbloat, router behavior, modem behavior, and latency.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill name suggests error-message improvement, but the instructions route users into home-network troubleshooting workflows.\n\nMitigation: Review the skill before installing and rename display metadata or narrow invocation triggers so users understand that it is a network-diagnostics helper.\n\n## Reference(s):\n\n- [Requirement Plan](references/requirement-plan.md)\n- [ClawHub Skill Page](https://clawhub.ai/kyro-ma/skills/error-message-improver)\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, Code, Shell commands, Configuration, Guidance]\n\n**Output Format:** [Markdown with optional code, shell command, checklist, and configuration snippets]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Outputs should state assumptions, limits, validation steps, remaining risks, and next steps when useful.]\n\n## Skill Version(s):\n\n0.20260904.60001 (source: server release evidence)\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 v0.20260904.60001:SKILL.zh-CN.md\n\n---\nname: error-message-improver\ndescription: >-\n  帮助用户处理“Validated demand: Remote workers and technically curious households need local diagnostic workflows for network issues such as bufferbloat, router problems, and latency. This requirement is supported by 11 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.”。当用户提出 general-help, bufferbloat, router, modem, latency，或需要围绕该需求获得实用流程、产物、检查清单、分析或实现支持时使用。\n---\n\n# Error Message Improver\n\n## 需求\n\n使用这个技能帮助以下用户群体：remote workers, gamers, home-office users, and small teams who need to diagnose internet quality with consumer networking hardware\n\n> Validated demand: Remote workers and technically curious households need local diagnostic workflows for network issues such as bufferbloat, router problems, and latency. This requirement is supported by 11 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n需求评分：100/100（需求强度 `70/70`，本地可执行性 `30/30`）。\n证据：11 条信号，覆盖 3 个来源类型。\n\n如需查看来源证据、执行计划或评审标准，请阅读 `references/requirement-plan.md`。\n\n## 工作流程\n\n1. 重新说明用户想要的结果、限制、已有输入和成功标准。\n2. 把请求转化为实用计划和可执行输出。\n3. 只有当缺失信息会明显改变输出时才提问；否则先做合理假设并继续推进。\n4. 保持本地硬件友好：优先使用脚本、模板、检查清单、小模型或 CPU 可承受的流程，避免依赖云端专用资源或大规模训练。\n5. 产出用户需要的文档、流程、清单、分析、代码修改或决策支持。\n6. 对照成功标准检查结果，并列出剩余风险或后续事项。\n\n## 预期输出\n\n- 针对用户当前情境的定制回答或产物。\n- 当任务可复用时，提供检查清单或工作流程。\n- 说明结果如何被检查的验证备注。\n\n## 验证\n\n- 输出直接回应发现的原始需求。\n- 用户不需要阅读原始来源帖子也能采取行动。\n- 假设、限制和所需输入清晰可见。\n- 在有帮助时，最终回复包含简短的使用说明或下一步建议。\n\n## 触发方式\n\n关键词：`general-help`, `bufferbloat`, `router`, `modem`, `latency`, `network troubleshooting`\n\n示例触发句：\n\n- `Help me Remote workers and technically curious households need local diagnostic workflows for network issues such as bufferbloat.`\n- `I need a practical workflow for Remote workers and technically curious households need local diagnostic workflows for network issues such as bufferbloat.`\n- `Use $error-message-improver to handle Remote workers and technically curious households need local diagnostic workflows for network issues such as bufferbloat.`\n\nFile v0.20260904.60001:agents/openai.yaml\n\ninterface:\n  display_name: \"Error Message Improver\"\n  short_description: \"Helps with Remote workers and technically curious households...\"\n  default_prompt: \"Use $error-message-improver to help me Remote workers and technically curious households need local diagnostic workflows for network issues such as bufferbloat.\"\n\npolicy:\n  allow_implicit_invocation: true\n\nArchive v0.20260831.40551: 8 files, 10376 bytes\n\nFiles: agents/openai.yaml (364b), README.md (3158b), README.zh-CN.md (3166b), references/requirement-plan.md (5012b), skill-card.md (2006b), SKILL.md (3102b), SKILL.zh-CN.md (2976b), _meta.json (152b)\n\nFile v0.20260831.40551:SKILL.md\n\n---\nname: error-message-improver\ndescription: >-\n  Help users with Validated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.. Use when a user asks for work-productivity, error messages, debugging, user feedback, support, or needs a practical workflow, artifact, checklist, analysis, or implementation support for this requirement.\n---\n\n# Error Message Improver\n\n## Requirement\n\nUse this skill to help application developers, support teams, SaaS operators, and users who lose time when vague errors block troubleshooting with:\n\n> Validated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\nDemand score: 100/100 (`70/70` demand, `30/30` local feasibility).\nEvidence: 12 signals across 3 source families.\n\nRead `references/requirement-plan.md` when source evidence, planning details, or review criteria are needed.\n\n## Workflow\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Create a concise work plan, template, automation outline, or decision aid that reduces manual coordination.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Validation\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Triggers\n\nKeywords: `work-productivity`, `error messages`, `debugging`, `user feedback`, `support`, `troubleshooting`\n\nExample trigger sentences:\n\n- `Help me Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `I need a practical workflow for Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `Use $error-message-improver to handle Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n\nFile v0.20260831.40551:README.md\n\n# Error Message Improver\n\n## Requirement\n\nValidated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\nAudience: application developers, support teams, SaaS operators, and users who lose time when vague errors block troubleshooting\n\nCategory: `work-productivity`\n\nDemand score: 100/100\n\nEvidence coverage: 12 signals across 3 source families.\n\n## Evidence\n\n- github-issues: [Create or update the affected functions to be accessible in main.js](https://github.com/tadanobutubutu/screeps/issues/108000)\n- github-issues: [[Intake] O sumarizador de memória utilizava o modelo padrão do chat ou de extrações sem v](https://github.com/Ikalus1988/MisakaNet/issues/1397)\n- github-issues: [[Intake] personagens entram em conflito repetitivo ou loops narrativos difíceis de guiar](https://github.com/Ikalus1988/MisakaNet/issues/1396)\n- github-issues: [[BUG] MCP Tools with draft-07 are rejected](https://github.com/anthropics/claude-code/issues/88882)\n- segmentfault-search: [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search: [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search: [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search: [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search: [答： c++单例类编译不通过](https://segmentfault.com/q/1010000004886164/a-1020000004886445)\n- segmentfault-search: [error-messages](https://segmentfault.com/t/error-messages)\n- segmentfault-search: [问： vue自定义指令报错](https://segmentfault.com/q/1010000009322969)\n- hacker-news-search: [Zig: Pointer Stability for ArrayLists](https://news.ycombinator.com/item?id=49502293)\n\n## How This Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Usage\n\nKeywords: `work-productivity`, `error messages`, `debugging`, `user feedback`, `support`, `troubleshooting`\n\nTrigger sentences:\n\n- `Help me Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `I need a practical workflow for Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `Use $error-message-improver to handle Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n\n## Files\n\n- `SKILL.md`: English skill instructions.\n- `SKILL.zh-CN.md`: Chinese skill instructions.\n- `README.md`: English user-facing guide.\n- `README.zh-CN.md`: Chinese user-facing guide.\n\nFile v0.20260831.40551:_meta.json\n\n{\n  \"ownerId\": \"kn7be2ewez5ks45t5nmdez8j51839xpk\",\n  \"slug\": \"error-message-improver\",\n  \"version\": \"0.20260831.40551\",\n  \"publishedAt\": 1788149304154\n}\n\nFile v0.20260831.40551:references/requirement-plan.md\n\n# Requirement Plan\n\n## Live Requirement\n\nValidated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n## Audience\n\napplication developers, support teams, SaaS operators, and users who lose time when vague errors block troubleshooting\n\n## Category\n\nwork-productivity\n\n## Requirement Score\n\nTotal: 100/100\n\nDemand: 70/70\n\nLocal feasibility: 30/30\n\nEvidence coverage: 12 signals across 3 source families.\n\nScoring rationale:\n\n- Evidence count: 12; required minimum: 3.\n- Distinct source families: 3; sources: github, hacker-news, segmentfault.\n- Demand score: 70/70 based on corroboration, source diversity, and professional/community signal.\n- Local feasibility score: 30/30.\n- Implementation is a documentation, workflow, code, or analysis skill that can run on ordinary CPU hardware.\n\n## Evidence\n\n- github-issues (2026-08-30T08:36:23+00:00): [Create or update the affected functions to be accessible in main.js](https://github.com/tadanobutubutu/screeps/issues/108000)\n- github-issues (2026-08-30T23:15:01+00:00): [[Intake] O sumarizador de memória utilizava o modelo padrão do chat ou de extrações sem v](https://github.com/Ikalus1988/MisakaNet/issues/1397)\n- github-issues (2026-08-30T22:48:51+00:00): [[Intake] personagens entram em conflito repetitivo ou loops narrativos difíceis de guiar](https://github.com/Ikalus1988/MisakaNet/issues/1396)\n- github-issues (2026-08-22T19:38:56+00:00): [[BUG] MCP Tools with draft-07 are rejected](https://github.com/anthropics/claude-code/issues/88882)\n- segmentfault-search (2026-08-31T04:06:46.498966+00:00): [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmon\n\nArchive v0.20260830.92238: 8 files, 10666 bytes\n\nFiles: agents/openai.yaml (364b), README.md (3122b), README.zh-CN.md (3130b), references/requirement-plan.md (4976b), skill-card.md (2729b), SKILL.md (3102b), SKILL.zh-CN.md (2976b), _meta.json (152b)\n\nArchive v0.20260828.40337: 8 files, 10383 bytes\n\nFiles: agents/openai.yaml (364b), README.md (3155b), README.zh-CN.md (3163b), references/requirement-plan.md (5009b), skill-card.md (2110b), SKILL.md (3102b), SKILL.zh-CN.md (2976b), _meta.json (152b)","readmeExcerpt":"Skill: Error Message Improver Owner: kyro-ma Summary: Helps with Users and support teams need clearer error message... Tags: latest:0.20260916.221748 Version history: v0.0.0-20261009-045810 | 2026-10-09T05:01:50.567Z | auto - Updated documentation in English and Chinese (README.md, README.zh-CN.md) - Revised or expanded content in references/requirement-plan.md - Removed the redundant or outdated skill-card.md file -","codeSnippets":[],"executableExamples":[],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: error-message-improver\ndescription: >-\n  Help users with Validated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.. Use when a user asks for work-productivity, error messages, debugging, user feedback, support, or needs a practical workflow, artifact, checklist, analysis, or implementation support for this requirement.\n---\n\n# Error Message Improver\n\n## Requirement\n\nUse this skill to help application developers, support teams, SaaS operators, and users who lose time when vague errors block troubleshooting with:\n\n> Validated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\nDemand score: 100/100 (`70/70` demand, `30/30` local feasibility).\nEvidence: 12 signals across 3 source families.\n\nRead `references/requirement-plan.md` when source evidence, planning details, or review criteria are needed.\n\n## Workflow\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Create a concise work plan, template, automation outline, or decision aid that reduces manual coordination.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Validation\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Triggers\n\nKeywords: `work-productivity`, `error messages`, `debugging`, `user feedback`, `support`, `troubleshooting`\n\nExample trigger sentences:\n\n- `Help me Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `I need a practical workflow for Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `Use $error-message-improver to handle Users and support tea"},{"path":"README.md","content":"# Error Message Improver\n\n## Requirement\n\nValidated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\nAudience: application developers, support teams, SaaS operators, and users who lose time when vague errors block troubleshooting\n\nCategory: `work-productivity`\n\nDemand score: 100/100\n\nEvidence coverage: 12 signals across 3 source families.\n\n## Evidence\n\n- github-issues: [Source inventory: 9router PRs, issues and port dispositions](https://github.com/bloodf/durindoor/issues/1072)\n- github-issues: [[BUG]:Playback problem - codec errors](https://github.com/cygnusx-1-org/electriceel/issues/34)\n- segmentfault-search: [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search: [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search: [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search: [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search: [答： c++单例类编译不通过](https://segmentfault.com/q/1010000004886164/a-1020000004886445)\n- segmentfault-search: [error-messages](https://segmentfault.com/t/error-messages)\n- segmentfault-search: [问： vue自定义指令报错](https://segmentfault.com/q/1010000009322969)\n- github-issues: [Classic renderer drops or overwrites output when anything above the visible window changes height (verbose makes it frequent)](https://github.com/anthropics/claude-code/issues/98019)\n- github-issues: [New trait solver regresses error messages significantly](https://github.com/rust-lang/rust/issues/163643)\n- hacker-news-search: [What makes Lisp difficult to read?](https://news.ycombinator.com/item?id=49881351)\n\n## How This Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Usage\n\nKeywords: `work-productivity`, `error messages`, `debugging`, `user feedback`, `support`, `troubleshooting`\n\nTrigger sentences:\n\n- `Help me Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `I need a practical workflow for Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `Use $error-message-improver to handle Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n\n## Files\n\n- `SKILL.md`: English skill instructions.\n- `SKILL.zh-CN.md`: Chinese skill instructions.\n- `README.md`: "},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn7be2ewez5ks45t5nmdez8j51839xpk\",\n  \"slug\": \"error-message-improver\",\n  \"version\": \"0.0.0-20261009-045810\",\n  \"publishedAt\": 1791522110567\n}"},{"path":"references/requirement-plan.md","content":"# Requirement Plan\n\n## Live Requirement\n\nValidated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n## Audience\n\napplication developers, support teams, SaaS operators, and users who lose time when vague errors block troubleshooting\n\n## Category\n\nwork-productivity\n\n## Requirement Score\n\nTotal: 100/100\n\nDemand: 70/70\n\nLocal feasibility: 30/30\n\nEvidence coverage: 12 signals across 3 source families.\n\nScoring rationale:\n\n- Evidence count: 12; required minimum: 3.\n- Distinct source families: 3; sources: github, hacker-news, segmentfault.\n- Demand score: 70/70 based on corroboration, source diversity, and professional/community signal.\n- Local feasibility score: 30/30.\n- Implementation is a documentation, workflow, code, or analysis skill that can run on ordinary CPU hardware.\n\n## Evidence\n\n- github-issues (2026-10-08T20:04:08+00:00): [Source inventory: 9router PRs, issues and port dispositions](https://github.com/bloodf/durindoor/issues/1072)\n- github-issues (2026-10-08T11:05:35+00:00): [[BUG]:Playback problem - codec errors](https://github.com/cygnusx-1-org/electriceel/issues/34)\n- segmentfault-search (2026-10-09T04:58:44.986821+00:00): [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search (2026-10-09T04:58:44.986821+00:00): [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search (2026-10-09T04:58:44.986821+00:00): [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search (2026-10-09T04:58:44.986821+00:00): [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search (2026-10-09T04:58:44.987325+00:00): [答： c++单例类编译不通过](https://segmentfault.com/q/1010000004886164/a-1020000004886445)\n- segmentfault-search (2026-10-09T04:58:44.987325+00:00): [error-messages](https://segmentfault.com/t/error-messages)\n- segmentfault-search (2026-10-09T04:58:44.987325+00:00): [问： vue自定义指令报错](https://segmentfault.com/q/1010000009322969)\n- github-issues (2026-09-28T23:29:29+00:00): [Classic renderer drops or overwrites output when anything above the visible window changes height (verbose makes it frequent)](https://github.com/anthropics/claude-code/issues/98019)\n- github-issues (2026-10-02T09:36:32+00:00): [New trait solver regresses error messages significantly](https://github.com/rust-lang/rust/issues/163643)\n- hacker-news-search (2026-09-28T17:22:50+00:00): [What makes Lisp difficult to read?](https://news.ycombinator.com/item?id=49881351)\n\n## How The Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, c"},{"path":"README.zh-CN.md","content":"# Error Message Improver\n\n## 需求\n\nValidated demand: Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take next. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n目标用户：application developers, support teams, SaaS operators, and users who lose time when vague errors block troubleshooting\n\n分类：`工作与效率`\n\n需求评分：100/100\n\n证据覆盖：12 条信号，覆盖 3 个来源类型。\n\n## 来源证据\n\n- github-issues：[Source inventory: 9router PRs, issues and port dispositions](https://github.com/bloodf/durindoor/issues/1072)\n- github-issues：[[BUG]:Playback problem - codec errors](https://github.com/cygnusx-1-org/electriceel/issues/34)\n- segmentfault-search：[HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search：[javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search：[typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search：[ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search：[答： c++单例类编译不通过](https://segmentfault.com/q/1010000004886164/a-1020000004886445)\n- segmentfault-search：[error-messages](https://segmentfault.com/t/error-messages)\n- segmentfault-search：[问： vue自定义指令报错](https://segmentfault.com/q/1010000009322969)\n- github-issues：[Classic renderer drops or overwrites output when anything above the visible window changes height (verbose makes it frequent)](https://github.com/anthropics/claude-code/issues/98019)\n- github-issues：[New trait solver regresses error messages significantly](https://github.com/rust-lang/rust/issues/163643)\n- hacker-news-search：[What makes Lisp difficult to read?](https://news.ycombinator.com/item?id=49881351)\n\n## 这个技能如何满足需求\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## 使用方式\n\n关键词：`work-productivity`, `error messages`, `debugging`, `user feedback`, `support`, `troubleshooting`\n\n触发句：\n\n- `Help me Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `I need a practical workflow for Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n- `Use $error-message-improver to handle Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.`\n\n## 文件\n\n- `SKILL.md`：英文版技能说明。\n- `SKILL.zh-CN.md`：中文版技能说明。\n- `README.md`：英文版用户说明。\n- `README.zh-CN.md`：中文版用户说明。"}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":null,"editorialQuality":{"score":100,"threshold":65,"status":"thin","wordCount":2129,"uniquenessScore":30,"reasons":["uniqueness-below-45"]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-09T18:59:40.432Z","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-09T18:59:40.432Z","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-10T06:43:09.733Z","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"}]}}}