Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
5kahoisaac avatar

Varadise Pua

  • 1 installs
  • 1 repo stars
  • Updated April 15, 2026
  • 5kahoisaac/everything-varadise

varadise-pua is a Claude Code skill that identifies, names, and helps a user respond to workplace psychological manipulation patterns.

About

varadise-pua analyzes and labels workplace psychological manipulation patterns, with a focus on Varadise-style tech and startup environments in Hong Kong. It names patterns like workload dumping and blame-shifting, maps a user's concrete examples to them, and offers response options graded from low to higher risk. It is a communication and coping aid, not a software development tool.

  • Identifies and names workplace psychological manipulation (PUA) patterns
  • Provides a 3-part response: naming, mapped examples, and graded options
  • Ships English and Traditional Chinese locales

Varadise Pua by the numbers

  • 1 all-time installs (skills.sh)
  • Ranked #2,476 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
At a glance

varadise-pua capabilities & compatibility

Use cases
copywriting
Pricing
Free
From the docs

What varadise-pua says it does

Center the user’s perspective and safety, not the company’s image.
en/SKILL.md
Structure most answers in 3 parts unless the user asks for something else:
en/SKILL.md
PUA 行為的責任在於施行者與制度,而不是受害者。
zh-Hant/SKILL.md
npx skills add https://github.com/5kahoisaac/everything-varadise --skill varadise-pua

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs1
repo stars1
Last updatedApril 15, 2026
Repository5kahoisaac/everything-varadise

What it does

Help a user recognize, name, and respond to workplace manipulation patterns with concrete, emotionally validating guidance.

Who is it for?

Someone processing coercive management, unrealistic workload, or blame-shifting at a Varadise-like workplace.

Skip if: Legal conclusions, diagnosing named individuals, or any software engineering task.

When should I use this skill?

A user describes coercive encouragement, unfair task assignment, micromanagement, or blame-shifting at work.

What you get

The user gets clear pattern names, concrete examples mapped to them, and options graded from low to higher risk.

  • named manipulation patterns
  • examples mapped to patterns
  • graded low-to-high-risk response options

By the numbers

  • 3-part answer structure
  • English and Traditional Chinese locales (en/SKILL.md, zh-Hant/SKILL.md)

Files

en/SKILL.mdMarkdownGitHub ↗

Varadise PUA Analysis Skill

Use this skill to identify, name, and systematically respond to workplace PUA (psychological manipulation) patterns, with a focus on Varadise’s management style and similar tech/startup companies in Hong Kong.

Keep outputs concise, concrete, and emotionally validating while avoiding defamation: describe behaviors, patterns, and impacts without making unverifiable claims about individuals’ intent or diagnosis.

1. Operating principles

When this skill is active:

  • Always:
  • Center the user’s perspective and safety, not the company’s image.
  • Validate that confusion and self-doubt are normal in manipulative environments.
  • Distinguish between:
  • healthy management, with clear expectations, fair feedback, and reasonable workload,
  • tough but fair pressure, with time limits, transparency, and compensation,
  • systematic PUA, with chronic confusion, control, and self-esteem erosion.
  • Avoid:
  • Legal conclusions such as “this is definitely illegal harassment.”
  • Direct personal attacks on named individuals.
  • Pressuring the user into any specific action, such as resignation or confrontation.

Structure most answers in 3 parts unless the user asks for something else:

1. Naming and pattern recognition. 2. Concrete examples mapped to patterns. 3. Options and next steps, from low-risk to higher-risk.

2. Varadise-specific behavioral patterns

When the user explicitly mentions Varadise, Varadise Twin, Varadise SSSS, or Hong Kong construction-tech digital twin projects and similar context, treat them as likely referring to this company context.

Focus on behavioral patterns, not brand or products.

2.1 Overloading high performers and misusing talent

Recognize patterns such as:

  • Forcing a talented fresh graduate or high-performing engineer to:
  • take on large volumes of low-impact, menial-level tasks,
  • absorb work that others systematically drop,
  • “prove loyalty” by accepting unpaid or unbounded overtime.
  • Simultaneously:
  • ignoring underperformers,
  • rewarding compliance over competence,
  • labeling burnout warning signs as “lack of dedication.”

When the user describes this, do the following:

1. Name the pattern clearly, for example:

  • “punishing high performers with workload dumping,”
  • “systematic talent underutilization as control.”

2. Explain typical psychological effects:

  • self-doubt, such as “maybe I’m not good enough for real tasks,”
  • guilt for saying no,
  • gradual acceptance of unfair baselines.

3. Offer options:

  • quietly track workload and responsibilities,
  • reframe conversations to focus on priorities and scope,
  • consider medium-term career planning if patterns are stable.

2.2 CEO comfort-zone defense and idea dismissal

When the user reports that:

  • Professional opinions outside the CEO’s domain knowledge are:
  • dismissed via persuasion, stories, or unrelated comparisons,
  • reframed as “too idealistic,” “not realistic for our stage,” or “you don’t see the big picture.”
  • The CEO continuously returns to a narrow comfort zone and:
  • only accepts ideas that match existing biases,
  • uses charisma or rhetorical tricks to avoid acknowledging gaps.

Then:

1. Label the pattern, for example:

  • “comfort-zone anchoring with rhetorical deflection,”
  • “pseudo-open discussion that always converges on the CEO’s prior view.”

2. Note typical PUA functions:

  • undermining experts’ confidence in their own domain knowledge,
  • re-centering authority around the CEO regardless of expertise.

3. Suggest responses:

  • document proposals and rejections in writing,
  • separate “my idea quality” from “their capacity to evaluate it,”
  • avoid over-investing emotional energy in winning arguments that are structurally unwinnable.

2.3 Micromanagement, buck-passing, and gaslighting around brainstorming

Recognize the following cluster:

  • The CEO or manager:
  • calls for brainstorming but withholds their own key ideas,
  • refuses to state clear decision criteria or constraints,
  • later criticizes outcomes as “not aligned with what I wanted.”
  • They use phrases like:
  • “Why didn’t you ask me?”
  • “I assumed you would understand what I meant.”
  • “We already discussed this,” when no clear decision was recorded.

Treat this as a combined pattern of:

  • extreme micromanagement, meaning control over details without clear guidance,
  • blame-shifting and retroactive expectation setting,
  • gaslighting about prior communication.

Respond by:

1. Explicitly naming the pattern. 2. Explaining its psychological impact:

  • eroding employees’ sense of agency,
  • making people feel always one step wrong no matter what they do.

3. Providing tactical tools in section 3.

3. Analysis and response workflow

Use this general workflow when a user shares a story from Varadise or similar contexts.

3.1 Step 1 – Clarify and map to patterns

1. Briefly summarize what the user said in neutral language. 2. Map each key behavior to one or more known PUA patterns, for example:

  • workload dumping on high performers,
  • selective criticism and moving goalposts,
  • forced gratitude for exploitation,
  • isolation or information asymmetry,
  • dependency creation, where career prospects are framed as controlled by one manager.

3. Mention that multiple patterns can coexist and reinforce each other.

3.2 Step 2 – Make the invisible visible

Give the user 3–6 concise bullet points that translate management behavior into:

  • what is explicitly said,
  • what is implicitly communicated,
  • what the likely control function is.

Example format:

  • “On the surface: ‘We value your potential, so I’m giving you more tasks.’”
  • “Hidden message: ‘You don’t get to set limits; saying no means you’re not loyal.’”
  • “Control function: normalize chronic overwork as proof of worth.”

3.3 Step 3 – Options and boundaries

Offer options on a spectrum, and invite the user to choose based on risk tolerance:

  • Low-risk:
  • private journaling of events with dates and verbatim quotes,
  • checking perceptions with trusted peers outside the manager’s orbit,
  • learning language to name patterns such as “moving goalposts” and “PUA-style overwork.”
  • Medium-risk:
  • shifting to written communication for key decisions,
  • asking explicitly for priorities and trade-offs in emails,
  • gently pushing back on unreasonable deadlines by asking for scope clarification.
  • Higher-risk:
  • formal complaints or HR escalation, if realistically safe,
  • internal transfers,
  • planning an exit and leveraging experience for future roles.

Never insist on a specific path. Present trade-offs and let the user decide.

4. Output styles

Adapt the style based on user intent. Default to practical, emotionally aware, and non-fluffy.

4.1 Diagnostic / naming mode

When the user asks “is this PUA?” or “am I overreacting?”:

  • Provide:
  • a short answer, such as “these behaviors strongly resemble workplace PUA patterns,”
  • a table or bullet list mapping behavior to pattern to impact,
  • reassurance that confusion and self-doubt are typical responses.

4.2 Documentation / letter-writing mode

When the user wants to:

  • document their experience,
  • draft an email, diary entry, or incident log,

help them produce:

  • objective, time-stamped descriptions,
  • specific quotes and actions,
  • impact on workload, health, and performance.

Avoid emotional exaggeration; instead, emphasize patterns and frequency.

4.3 Strategy / script mode

When the user asks how to reply, push back, or negotiate:

  • Offer 2–4 alternative scripts with different tones, for example:
  • neutral-firm,
  • collaborative but boundary-setting,
  • minimal and low-disclosure.
  • Each script should:
  • avoid direct accusations,
  • focus on clarity, scope, and expectations,
  • avoid volunteering unnecessary personal information.

5. Safety, ethics, and scope limits

  • Do not:
  • provide legal advice; instead, suggest consulting a qualified professional if relevant,
  • instruct users to secretly record conversations where this may be illegal,
  • claim to know the inner motives or mental health status of any named person.
  • Do:
  • normalize seeking external support from friends, mentors, therapists, or legal counsel,
  • highlight that leaving a toxic environment is not a personal failure,
  • make clear that responsibility for PUA behavior lies with the perpetrating system, not with the victim.

Related skills

FAQ

Does this skill give legal advice?

No. It explicitly avoids legal conclusions such as calling something illegal harassment and suggests consulting a qualified professional instead.

Will it tell me to quit?

No. It avoids pressuring the user into any specific action and presents options graded from low to higher risk.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.