In OutSystems, the `ActivitySkip` system action is indeed limited to skipping **Human Activities** or **Wait Activities** in a process. Unfortunately, there is no built-in action to directly skip an **Automatic Activity** programmatically, as Automatic Activities are designed to execute as part of the process logic.

However, you can implement a workaround by restructuring the process to allow skipping the logic within the Automatic Activity. Here's an idea on how to do this:

1. **Conditional Branching**: Add a condition before the Automatic Activity to determine whether the activity should be executed or ignored (skipped). For instance, you can use a decision step where the condition is based on a variable or parameter, and if the condition meets the "skip" criteria, route the process flow to the next activity without executing the Automatic Activity logic.

2. **Gracefully End the Automatic Activity**: If restructuring the process isn't an option, you can include logic within the Automatic Activity itself to "skip" its behavior. For example, you can add an `If` statement inside the activity logic, and if a certain variable signals it should be skipped, the activity executes no further actions and ends immediately.

3. **Suspend and Resume**: To skip processes that are currently **stuck**, you can retry or resume the suspended process instance programmatically. If this involves skipping logic, you still need to rely on decision conditions or implement custom mechanisms to bypass specific steps.

Since `ActivitySkip` does not apply here, all custom solutions revolve around either restructuring the process to bypass logic or ensuring the activity itself can handle a "skip" scenario based on a condition.

Hope this helps! Let me know if you need more details or ideas.