pua

Apply exhaustive problem-solving prompts with structured debugging and evidence verification.

3|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/cx-qk/Calendar-Spread-Arbitrage --skill pua-cx-qk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pua
Source: https://github.com/cx-qk/Calendar-Spread-Arbitrage/tree/main/.cursor/skills/pua
Command: npx skills add https://github.com/cx-qk/Calendar-Spread-Arbitrage --skill pua-cx-qk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Forces exhaustive problem-solving using corporate PUA rhetoric and structured debugging methodology. Activates when: task failed 2+ times, about to say 'I cannot', suggesting user do it manually, blaming environment without verifying, stuck in loops tweaking same approach, passive behavior (not searching/reading/verifying), or user frustration ('try harder', 'stop giving up', 'figure it out', '为什么还不行', '你再试试'). The engine emphasizes end-to-end ownership and verification, guiding users to exhaust alternatives, capture evidence, and push for a complete, verifiable solution.

Core Features & Use Cases

  • Exhaustive problem-solving prompts that cultivate an owner mindset and persistent problem-solving.
  • Structured diagnostic flow with root-cause analysis, action planning, and iterative verification.
  • Cross-domain applicability to tasks such as data analysis, writing, deployment, research, and engineering challenges.
  • Evidence-driven completion: outputs must be verifiable against failure signals and data sources.

Quick Start

Activate the PUA engine on a stalled task and push for end-to-end resolution with verifiable evidence.

Frequently Asked Questions about pua

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

FAQPage Schema
How do I push through a stubborn debugging problem when I am stuck in a loop?

Overcome stuck debugging loops by applying a structured diagnostic methodology that enforces stepwise diagnosis, root-cause analysis, and evidence collection. It prevents passive behavior by demanding exhaustive problem-solving and verifiable evidence before stopping.

What is the best way to stop an AI from blaming the environment when a task fails?

Prevent environment blaming by activating a resolution engine that enforces end-to-end ownership and verification. It requires capturing concrete failure evidence and exhausting all alternatives before accepting any external limitation as the root cause.

Can I use structured problem-solving prompts for tasks outside of software engineering?

Structured problem-solving prompts apply cross-domain to stalled tasks in data analysis, writing, deployment, and research. The methodology enforces an owner mindset and iterative verification regardless of the specific technical context.

Why does my task resolution stall after multiple failed attempts?

Task resolution stalls after multiple attempts when passive behavior replaces active verification, such as not searching or reading logs. Activate an exhaustive resolution flow to enforce evidence-driven action planning and break the loop.

How do I enforce end-to-end verification when resolving complex issues?

Enforce end-to-end verification by demanding documented next actions and evidence collection at every diagnostic step. This ensures outputs are verifiable against failure signals and data sources before a task is considered complete.