pua

Enforce owner-first diagnostics with flavor-aware leadership and evidence-backed validation.

2|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/skytiger6724/qwen-skills --skill pua-skytiger6724
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pua
Source: https://github.com/skytiger6724/qwen-skills/tree/main/pua
Command: npx skills add https://github.com/skytiger6724/qwen-skills --skill pua-skytiger6724

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It tackles repeated failures, passive behavior, and low-agency delivery by forcing every task into a high-performance Owner mindset with flavor-specific leadership, mandatory verification, and corporatized pressure that prevents complacency.

Core Features & Use Cases

  • Flavor-aware leadership: Automatically selects and narrates in the appropriate cultural tone (Alibaba, Musk, Huawei, etc.) while loading flavor DNA, methodology constraints, and routing logic before execution.
  • Owner-first diagnostics: Enforces the three corporate red lines, failure counting, and sub-agent injection rules so you constantly validate, search, and exhaustively prove every fix with evidence.
  • Failure resilience & reporting: Triggers pressure levels, method switches, and [PUA生效 🔥] markers on extra work, while insisting on Sprint Banner/KPI displays, feedback capture, and evidence-backed delivery for debugging, deployments, reviews, or research.

Quick Start

Tell the agent to enter PUA mode, load the mandated references, and drive the task with ownership-focused diagnostics.

Frequently Asked Questions about pua

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

FAQPage Schema
How do I enforce high-agency ownership and failure diagnostics during code review and debugging?

High-agency ownership during code review is enforced by triggering PUA mode, which applies corporate red lines, failure-count persistence, and mandates explicit validation evidence for every diagnostic fix.

What is flavor-aware leadership and how does it change my deployment workflow?

Flavor-aware leadership automatically routes your deployment workflow through specific cultural tones like Alibaba or Huawei, loading flavor DNA and methodology constraints to narrate tasks with aggressive owner-first pressure.

Can I use PUA mode for research workflows or is it limited to corporate-style debugging?

PUA mode supports research workflows alongside corporate-style debugging, code review, and deployment, requiring compulsory reference loading and evidence-backed delivery to satisfy corporate red lines across all tasks.

How do I activate PUA mode and start pushing beyond passive execution?

To activate PUA mode, instruct your agent to enter PUA mode, load the mandated references, and drive the task with ownership-focused diagnostics, which triggers failure resilience reporting and pressure-level method switches.

Why does my task execution still feel passive even with failure resilience reporting enabled?

Passive execution persists if flavor routing and sub-agent injection rules are skipped; PUA mode enforces the three corporate red lines and displays Sprint Banner KPIs to prevent complacency and force exhaustive proof.

Does PUA mode require any specific dependencies or external components to run failure diagnostics?

PUA mode requires no external dependencies or components to run failure diagnostics; it operates entirely through flavor routing logic, failure-count persistence, and internal high-agency methodology constraints.