agentsclimarketplace
Sign in

Error classification

Skill amadeus-dlc/amadeus/amadeus/spaces/default/knowledge/amadeus-shared/software-design/error-classification

Use when clarifying software abnormal-state terminology such as error, defect, fault, failure, bug, incident, and exception. Helps choose handling, testing, and mitigation strategies from precise classification. Trigger for error terminology, fault versus failure, defect versus bug, abnormal-state design, failure analysis, or test classification.From its SKILL.md

Install
npx -y skills add amadeus-dlc/amadeus --skill error-classification

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.9 KB, 293 tokens by cl100k_base, as published. Nobody here has run it

Error Classification

Classify abnormal states before designing their handling. Different words imply different interventions.

Working Vocabulary

  • Error: a human or system mistake in reasoning, input, configuration, or operation.

  • Defect: a flaw in an artifact such as code, requirements, tests, or documentation.

  • Bug: an informal report or label for a defect, fault, or failure; clarify which precise category is meant before choosing a response.

  • Fault: an incorrect internal state or latent condition that can cause failure.

  • Failure: externally observable deviation from expected service.

  • Incident: an operational event requiring response.

  • Exception: a language/runtime control mechanism or signal, not a domain classification by itself; classify the condition it represents.

Workflow

  1. Describe what was observed and by whom.

  2. Separate external failure from internal fault and underlying defect.

  3. Identify whether the condition is recoverable, retryable, user-correctable, or fatal.

  4. Choose handling: validation error, typed domain error, exception, retry, circuit breaker, alert, or defect fix.

Detailed Reference

For non-trivial implementation, review, or refactoring work, read references/details.md before giving final guidance. It contains the detailed rules, examples, smells, and migration notes that do not belong in the short invocation body.

Output

Return the classification chain, handling strategy, tests to add, and terms the team should use consistently.

What ships with it: 1 file

1.4 KB alongside SKILL.md

references/

Keep looking

Skills are one crate of 326,852. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.