Token导航 LogoToken导航

Agent Skill · 研究检索

toxic-manager-translator(有毒经理翻译)

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

toxic-manager-translator 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证为 MIT,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 42,706。

总安装 1,048周安装 45GitHub Stars 3下载 367核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT

安装方式

通过对话安装

复制提示词发给支持本地命令或 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

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

toxic-manager-translator 用于根据关键词、任务场景或来源线索查找、检索和筛选信息。它适用于 Codex、Claude、Cursor 等宿主环境中的信息定位需求。可通过 npx skills add 命令从 dedalus-erp-pas/foundation-skills 仓库安装使用。

使用前应确认权限范围、维护状态及是否触发联网或文件操作。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/toxic-manager-translator

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/dedalus-erp-pas/foundation-skills --skill toxi…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

toxic-manager-translator 怎么安装?

在终端执行 npx skills add https://github.com/dedalus-erp-pas/foundation-skills --skill toxic-manager-…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

toxic-manager-translator 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

toxic-manager-translator 需要什么权限?

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

toxic-manager-translator 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

toxic-manager-translator 用的人多吗?

公开数据是累计安装 1,048 次,近一周安装 45 次,下载 367 次,GitHub 3 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

toxic-manager-translator 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 3 个目录同时收录,说明这个 Skill 流传比较广。
  • 许可证明确为 MIT,商用和分发边界好判断。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
toxic-manager-translator

有毒经理翻译 · 本页

1,0483只读MIT有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

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.

平台分布

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 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。

继续浏览同类 Skills