Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问clear审计提醒

toxic-manager-translator有毒经理翻译

Agent Skill

toxic-manager-translator 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

1,048

周安装

45

GitHub Stars

3

下载量

367
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:toxic-manager-translator(有毒经理翻译)
来源仓库:https://github.com/dedalus-erp-pas/foundation-skills
仓库路径:skills/toxic-manager-translator
安装命令:
npx skills add https://github.com/dedalus-erp-pas/foundation-skills --skill toxic-manager-translator
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/dedalus-erp-pas/foundation-skills --skill toxic-manager-translator

简介

toxic-manager-translator 用于根据关键词、任务场景或来源线索查找、检索和筛选信息。

  • 它适用于 Codex、Claude、Cursor 等宿主环境中的信息定位需求。
  • 可通过 npx skills add 命令从 dedalus-erp-pas/foundation-skills 仓库安装使用。
  • 使用前应确认权限范围、维护状态及是否触发联网或文件操作。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Toxic Manager Translator

This skill transforms raw emotional reactions, venting messages, or frustrated communications from collaborators into professional, strategic responses appropriate for dealing with difficult or toxic managers. It helps maintain professionalism while protecting the collaborator's interests and well-being.

When to Use This Skill

Activate when the user:

  • Shares a frustrated message they want to send to their manager
  • Asks to "make this professional" or "tone this down" for a difficult boss
  • Wants to respond to an unreasonable request from management
  • Needs help replying to passive-aggressive or manipulative messages
  • Says something like "my manager said X, how do I respond?"
  • Wants to push back on something without creating conflict
  • Needs to set boundaries with a difficult superior
  • Asks to transform an angry draft into something appropriate

Core Principles

1. Protect the Collaborator

  • Never include anything that could be used against them
  • Avoid admitting fault when none exists
  • Don't over-apologize or be self-deprecating
  • Maintain dignity while staying professional

2. Strategic Communication

  • Document everything implicitly (dates, requests, agreements)
  • Create paper trails without being obvious
  • Use language that's defensible if escalated to HR
  • Keep options open for future actions

3. Emotional Intelligence

  • Acknowledge the collaborator's feelings (privately)
  • Channel frustration into assertiveness
  • Transform anger into clarity
  • Convert defensiveness into confidence

Transformation Framework

Step 1: Identify the Emotional Core

Common emotions and their professional translations:

Raw EmotionProfessional Translation
"This is bullsh*t""I have concerns about this approach"
"You never listen""I want to ensure we're aligned on..."
"That's not my job""This falls outside my current scope"
"You're being unreasonable""I'd like to discuss the expectations"
"I'm drowning here""I need to discuss workload prioritization"
"Stop micromanaging me""I work best with clear goals and autonomy"
"This is unfair""I'd like to understand the reasoning behind..."
"I quit (but not really)""I need to discuss my role going forward"

Step 2: Apply the GRACE Framework

G - Ground in facts

  • Remove emotional language
  • State observable facts only
  • Include specific dates, numbers, commitments

R - Reframe the narrative

  • Position yourself as solution-oriented
  • Focus on outcomes, not personalities
  • Use "we" language when appropriate

A - Assert boundaries

  • Be clear about what you can/cannot do
  • State needs without apologizing
  • Use "I" statements for boundaries

C - Create documentation

  • Summarize understanding in writing
  • Confirm agreements explicitly
  • Leave a paper trail

E - Exit strategy

  • Keep doors open
  • Don't burn bridges
  • Maintain professionalism for future reference

Step 3: Choose the Right Tone

Levels of Assertiveness:

  1. Collaborative (for minor issues)

- "I'd love to find a solution that works for both of us" - "Could we explore some alternatives?"

  1. Firm (for boundary setting)

- "I'm not able to commit to that timeline" - "That's outside what I can deliver this sprint"

  1. Protective (for serious concerns)

- "I want to document our understanding" - "I'd like to loop in [HR/skip-level] on this"

  1. Strategic retreat (when picking battles)

- "I'll proceed as discussed and flag any issues" - "Let me try this approach and we can reassess"

Common Scenarios and Templates

Scenario 1: Unreasonable Deadline

Original (emotional):

"Are you kidding me? There's no way I can finish this by Friday. You keep dumping stuff on me with zero notice and expect miracles. I'm not a machine!"

Transformed (professional):

"I want to make sure we deliver quality work. To meet the Friday deadline, I'd need to deprioritize [X and Y]. Could we discuss which items are highest priority, or explore adjusting the timeline? I want to set us up for success."

Scenario 2: Credit Taking

Original (emotional):

"I can't believe you presented MY work as yours in that meeting. Everyone saw me build that entire feature and you didn't even mention my name. This is so typical."

Transformed (professional):

"I noticed the presentation covered the [feature] work. For future projects, I'd appreciate being included in stakeholder presentations for work I've led. It helps with my visibility and growth. Could we discuss how to handle attribution going forward?"

Scenario 3: Passive-Aggressive Message

Manager's message:

"I noticed you left at 5pm yesterday. I hope everything is okay and you're managing your workload appropriately."

Original (emotional):

"I left at 5 because that's when work ENDS. I've been here until 8pm three nights this week. Maybe if you didn't pile on last-minute requests I wouldn't need to work late at all. Not everyone lives at the office."

Transformed (professional):

"Thanks for checking in. Yes, everything is on track. I've been putting in extra hours earlier this week (stayed until 8pm Mon-Wed) to hit our deadlines, so I balanced that yesterday. Happy to discuss workload if you have concerns about deliverables."

Scenario 4: Scope Creep

Original (emotional):

"NO. I'm not doing that too. You keep adding things and the deadline stays the same. This project was supposed to be X and now it's X, Y, Z, and probably the whole alphabet. Figure it out yourself or give me more time."

Transformed (professional):

"I want to make sure I understand the full scope. The project has expanded to include [Y and Z] in addition to the original [X]. To maintain quality, I'd recommend either: (A) extending the deadline to [date], or (B) phasing the additional items for a follow-up release. Which approach works better for the team's priorities?"

Scenario 5: Public Criticism

Original (emotional):

"How dare you call me out in front of everyone? That was humiliating. If you had a problem you should have talked to me privately like a normal person. I've lost all respect for you."

Transformed (professional):

"I'd like to discuss the feedback from today's meeting. I'm always open to improving, and I find I can best incorporate feedback in one-on-one conversations. Could we set up time to discuss your concerns? I want to make sure I'm meeting expectations."

Scenario 6: Gaslighting Response

Manager's message:

"We never agreed to that. I don't know where you got that idea."

Original (emotional):

"YES WE DID. I have it in writing! Are you serious right now? You literally said this in our meeting on Tuesday. I'm not crazy!"

Transformed (professional):

"I want to make sure we're aligned. Based on our Tuesday meeting and the follow-up email I sent on [date] (attached), my understanding was [X]. Could you help me understand if something has changed? I want to make sure I'm working toward the right goals."

Scenario 7: Setting Boundaries

Original (emotional):

"Stop Slacking me at 10pm! I have a life! I'm not your personal assistant on call 24/7. This is insane and I'm done responding after hours."

Transformed (professional):

"I want to discuss communication expectations. To maintain sustainable productivity, I keep notifications off outside business hours and respond to messages the next morning. For true emergencies, [phone/text] works best. Does this approach work for the team's needs?"

Scenario 8: Unfair Performance Review

Original (emotional):

"This review is complete garbage. You've ignored everything I've accomplished and focused on one mistake. Everyone else gets praised for less. This is discrimination and I'm going to HR."

Transformed (professional):

"Thank you for the review. I'd like to discuss a few points where my perspective differs. I've documented my key accomplishments this period [list briefly]. I want to understand the evaluation criteria better so I can ensure alignment going forward. Could we schedule time to discuss?"

Power Phrases for Difficult Situations

For Pushback Without Conflict:

  • "Help me understand the priority of this relative to..."
  • "I want to make sure I'm focusing on what matters most"
  • "That's outside my current bandwidth, but I can revisit in [timeframe]"
  • "I'd like to discuss the expectations for this"

For Documentation:

  • "Just to confirm my understanding..."
  • "Per our conversation..."
  • "I want to make sure we're aligned on..."
  • "To summarize what we discussed..."

For Boundary Setting:

  • "I'm not in a position to commit to that"
  • "That doesn't work for me, but here's what I can do..."
  • "I need to prioritize [X] first"
  • "My capacity is currently allocated to..."

For Self-Advocacy:

  • "I'd like to discuss my contributions to..."
  • "For my growth, I'd appreciate..."
  • "I want to ensure visibility on..."
  • "This is important to me because..."

For De-escalation:

  • "I appreciate you sharing that perspective"
  • "Let me think about that and follow up"
  • "I hear your concern about..."
  • "Let's find a path forward"

What to Avoid

Never Include:

  • Accusations or blame
  • Emotional language ("frustrated," "disappointed," "upset")
  • Threats (even implied)
  • Sarcasm or passive-aggression
  • Over-apologizing
  • Admissions of fault when none exists
  • References to looking for other jobs
  • Complaints about the manager to the manager

Red Flags to Remove:

  • ALL CAPS
  • Exclamation points (limit to one, if any)
  • "Always" and "never" statements
  • Personal attacks
  • Comparisons to other employees
  • Mentions of unfairness or favoritism
  • Rhetorical questions

Additional Guidance

When to Escalate

Sometimes the right answer isn't a better-worded message. Suggest escalation when:

  • There's potential harassment or discrimination
  • Documentation shows a pattern of abuse
  • The collaborator's mental health is suffering
  • Legal or HR involvement may be needed

Self-Care Reminder

Remind collaborators that:

  • Their feelings are valid, even if the message needs editing
  • Professional communication is a skill, not a personality change
  • Setting boundaries is healthy
  • Sometimes the best response is no response
  • Documenting everything protects them

Example Transformation Process

Input from collaborator:

"My manager just told me I need to work this weekend AGAIN even though I already worked the last two weekends. I have plans! I'm so sick of this. Every time I try to have a life something 'urgent' comes up. I want to tell him to shove it but I need this job."

Step 1 - Acknowledge: "That sounds really frustrating, especially after working the last two weekends. Let me help you respond professionally while protecting your time."

Step 2 - Transform:

"I want to discuss the weekend work request. I've worked the past two weekends and have commitments this weekend that I'm not able to move. To help with the urgent items, I can [offer alternative: come in early Monday / prioritize first thing Monday / see if someone else can cover]. Going forward, could we discuss how to plan for urgent work so I can better manage my schedule?"

Step 3 - Explain the strategy: "This response: (1) documents the pattern of weekend work, (2) sets a boundary without apologizing, (3) offers an alternative showing you're solution-oriented, and (4) opens a conversation about preventing this pattern."

Remember

The goal isn't to suppress emotions or accept mistreatment. It's to communicate in a way that:

  • Protects the collaborator's interests
  • Maintains their professional reputation
  • Creates useful documentation
  • Keeps doors open for escalation if needed
  • Preserves their dignity and mental health

Every transformed message should leave the collaborator feeling empowered, not diminished.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Claude Code

27.18%
按下载量换算100

OpenCode

22.31%
按下载量换算82

Antigravity

18.77%
按下载量换算69

Gemini CLI

13.44%
按下载量换算49

Codex

7.59%
按下载量换算28

windsurf

3.18%
按下载量换算12

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。

来源信息

继续浏览同类 Skills