The parent issue RHELC-1173 has the label that triggered autocreation of this subtask to track the relative story point estimation for the integration test part of the issue.

The parent issue description at the time of creation of this issue was:
We have a "SKIPPED" status in report messages (those seen by inisghts and in the assessment report) to mean an Action could not be run because another Action failed. We also use skipped in the body of messages with other meanings:

• We did not perform this action because the system does not require it (The system is already registered so we skip registration. We do not need to use dbus to talk to subscription-manager so we skip the dbus is running check)
• The user has requested that we continue even though a specific Action might have failed (Detected the CONVERT2RHEL_UNSUPPORTED_SKIP_KERNEL_CURRENCY_CHECK environment variable. Skipping this check).

To avoid confusion, we should replace these usages of "skip" with another word. For instance, "omitting", "ignoring", "disregarding", "leaving out".

Other possible replacements can be found in a thesaurus: https://www.thesaurus.com/browse/omit