Error Message Improver

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 4 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.

Requirement

Use this skill to help application developers, support teams, SaaS operators, and users who lose time when vague errors block troubleshooting 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 4 source families, so it represents broader demand rather than a single isolated request.

Demand score: 100/100 (70/70 demand, 30/30 local feasibility). Evidence: 12 signals across 4 source families.

Read references/requirement-plan.md when source evidence, planning details, or review criteria are needed.

Workflow

1. Restate the user's outcome, constraints, available inputs, and success criteria.
2. Create a concise work plan, template, automation outline, or decision aid that reduces manual coordination.
3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.
4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.
5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.
6. Validate the output against the success criteria and list any remaining risks or follow-up work.

Expected Outputs

• A tailored answer or artifact for the user's immediate situation.
• A reusable checklist or workflow when the task is repeatable.
• A verification note showing how the result was checked.

Validation

• The output directly addresses the discovered requirement.
• The user can act on the result without reading the original source post.
• Assumptions, limits, and required inputs are visible.
• The final response includes a short usage or next-step note when helpful.

Triggers

Keywords: work-productivity, error messages, debugging, user feedback, support, troubleshooting

Example trigger sentences:

• Help me Users and support teams need clearer error messages that explain what failed, why it failed, and what action to take nex.
• 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.
• 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.