skip

Skip the active pipeline prompt while preserving recoverable state.

24|3|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/HypoxanthineOvO/Hypo-Workflow --skill skip
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skip
Source: https://github.com/HypoxanthineOvO/Hypo-Workflow/tree/main/skills/skip
Command: npx skills add https://github.com/HypoxanthineOvO/Hypo-Workflow --skill skip

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skip the current prompt or step when the user explicitly wants to bypass work while keeping the pipeline state recoverable.

Core Features & Use Cases

  • Safely mark the current prompt as skipped with a machine-readable reason.
  • Update logs and progress indicators to reflect the skip without advancing completed prompts.
  • Move to the next prompt and continue the pipeline recovery flow, preserving state continuity across cycles.

Quick Start

Instruct the system to skip the active prompt in the pipeline while preserving recoverable state.

Frequently Asked Questions about skip

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I skip a prompt in a pipeline without losing recoverable state?

To skip a prompt without losing recoverable state, the pipeline marks the current prompt as skipped, updates the state file, appends a machine-readable skip entry to the log, and advances to the next prompt while maintaining recoverable history.

What happens to pipeline logs when I bypass a workflow step?

When you bypass a workflow step, the pipeline appends a machine-readable skip entry to the log file and refreshes the progress file to reflect the skip without advancing completed prompt metrics.

Can I bypass a pipeline step without advancing completed metrics?

Yes, you can bypass a pipeline step without advancing completed metrics by applying a skip operation that updates the state and log files while preserving the count of successfully completed prompts.

How do I preserve pipeline state continuity across recovery cycles?

You preserve pipeline state continuity across recovery cycles by skipping the active prompt, which updates the state file and log, then advances to the next prompt while maintaining recoverable history.

Why does skipping a prompt still update the state and progress files?

Skipping a prompt still updates the state and progress files to ensure the pipeline records the bypass with a machine-readable reason, keeping the workflow context accurate and recoverable for future cycles.

Does skipping a workflow step affect the next prompt in the pipeline?

Skipping a workflow step does not halt the pipeline; it safely advances to the next prompt and continues the recovery flow while preserving state continuity across the ongoing cycle.