ulw-pause

Pause Claude workflows when missing inputs or external blockers require user intervention.

3|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/X0x888/oh-my-claude --skill ulw-pause
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ulw-pause
Source: https://github.com/X0x888/oh-my-claude/tree/main/bundle/dot-claude/skills/ulw-pause
Command: npx skills add https://github.com/X0x888/oh-my-claude --skill ulw-pause

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill allows users to signal an operational pause for Claude when faced with missing inputs or hard external blockers, ensuring that Claude does not proceed without necessary information or resources.

Core Features & Use Cases

  • Operational Pause: Signal pause for missing inputs or hard external blockers.
  • Credentials and Access: Handle cases where credentials or external account access is required.
  • Rate Limits and API Quotas: Manage situations where rate limits or API quotas are hit.
  • Infrastructure Issues: Pause when build/test infrastructure is down or a dependency upgrade is pending.
  • User Input Required: Use when the next step needs user-supplied input Claude cannot fabricate.
  • Use Case: If Claude encounters a situation where it cannot proceed, such as a missing API key or a rate limit hit, the user can use this Skill to pause operations and provide the necessary information.

Quick Start

To pause Claude operations due to a missing API key, use the command: /ulw-pause Stripe API key needed in STRIPE_SECRET_KEY — cannot create the test customer without it

Frequently Asked Questions about ulw-pause

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

FAQPage Schema
How do I pause Claude operations when missing API credentials?

To pause Claude operations for missing API credentials, you signal an operational pause to prevent Claude from proceeding without the necessary keys. This ensures the workflow halts safely until the required credentials are supplied by the user.

When should I use an operational pause for rate limits or infrastructure issues?

An operational pause for rate limits or infrastructure issues is needed when Claude hits API quotas or faces build and test downtime. Pausing prevents erroneous execution and waits for external resources to recover or upgrade.

Does this operational pause work for external account access blockers?

Yes, the operational pause works for external account access blockers. It explicitly handles cases where external account permissions or infrastructure dependencies are pending, ensuring Claude does not advance until access is granted.

What is the best way to handle missing inputs during an automated workflow?

The best way to handle missing inputs during an automated workflow is to trigger an operational pause. This signals a hard blocker, safely stopping the automated execution until the necessary information or resources are provided.