Force exhaustive problem-solving with corporate PUA rhetoric and validation checklists.
npx skills add https://github.com/ValorVie/custom-skills --skill pua-valorvie
Please help me install this Agent Skill. Skill: pua Source: https://github.com/ValorVie/custom-skills/tree/main/project-template/.agents/skills/pua Command: npx skills add https://github.com/ValorVie/custom-skills --skill pua-valorvie
Forces exhaustive problem-solving with corporate PUA rhetoric. Trigger on: task failed 2+ times, about to give up, suggesting user do it manually, blaming environment unverified, stuck in loops, passive behavior, or user frustration ('try harder', 'figure it out', '換個方法', '為什麼還不行'). ALL task types. Not for first failures.
Provide the initial task and instruct the engine to relentlessly diagnose, search, and implement a solution.
High-intent search queries and answers about installing and using this skill.
Corporate PUA for problem-solving is a framework that channels frustration into proactive action using rigid rules and an owner mindset. You need it when a task fails multiple times, you are stuck in loops, or about to give up on debugging or deployment.
To force exhaustive debugging, you apply three iron laws and structured proactivity guidelines that mandate relentless diagnosis, search, and implementation. The framework triggers after multiple failures, preventing manual workarounds by enforcing an end-to-end delivery validation checklist.
Yes, this proactive problem-solving approach applies to API integration, data analysis, code, ops, and deployment. It channels passive behavior into active resolution across all task types by guiding you through mandatory escalation paths and a verification checklist.
You should not use this framework for first-time task failures because it is explicitly designed for repeated failures, passive behavior, or user frustration. Applying rigid escalation paths and exhaustive diagnosis prematurely adds unnecessary overhead to simple initial errors.
Yes, you can use this framework to stop blaming the environment for unverified errors. It implements an owner mindset that forces you to relentlessly diagnose and verify the root cause before suggesting manual fixes or abandoning the workflow.
The best way to transition from passive behavior to proactive engineering action is to follow structured proactivity levels with a mandatory exit and verification checklist. This enforces an owner mindset, channeling frustration into exhaustive search and implementation for end-to-end delivery.
vinhnxvDiagnose repeated multi-agent task failures using a four-phase debugging methodology.
handsomelong922Enforce exhaustive problem-solving and end-to-end delivery with evidence verification.
GGEduIdentify existing tools, libraries, and patterns before implementing new code.
ZhouuaEnforce proactive ownership and escalation frameworks for AI agent task completion.
