Token导航 LogoToken导航

Agent Skill · 研究检索

managing-up(向上管理)

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

managing-up 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 5,813。

总安装 24,284周安装 992GitHub Stars 734下载 7,857核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/refoundai/lenny-skills --skill managing-up

这个 Skill 是做什么的

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

与来自 35 位产品领导者的经理和高管有效合作的策略。

使用一致的格式(例如每周电子邮件)定期向上沟通优先事项、阻碍因素和进度,而不是等待被询问 向您的经理提出建议和观点,而不仅仅是问题,减少他们的认知负担,并将自己定位为盟友 了解经理的优先事项和两个级别,以定制沟通并使您的工作与更广泛的组织战略保持一致 使用具体的工件、数据和实验来支持你的想法,而不是抽象的论点或观点 利用你的经理作为资源来清除阻碍和障碍,而不是试图独立解决所有问题

来源仓库内路径:skills/managing-up

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/refoundai/lenny-skills --skill managing-up;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

managing-up 怎么安装?

在终端执行 npx skills add https://github.com/refoundai/lenny-skills --skill managing-up。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

managing-up 支持哪些 AI 工具?

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

managing-up 需要什么权限?

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

managing-up 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

managing-up 用的人多吗?

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

managing-up 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 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调用外部服务未明确有提醒
managing-up

向上管理 · 本页

24,284734只读未明确通过

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

SKILL.md 原文

Managing Up

Help the user work effectively with their manager and executives using strategies from 35 product leaders.

How to Help

When the user asks for help managing up:

  1. Understand the relationship - Ask about their manager's style, what they care about, and where the friction or challenge is
  2. Diagnose the gap - Determine if this is a communication issue, alignment issue, trust issue, or visibility issue
  3. Apply the right approach - Help them choose between proactive updates, reframing conversations, building trust through wins, or direct feedback conversations
  4. Build sustainable habits - Guide them toward ongoing practices rather than one-time fixes

Core Principles

Your manager is a resource to leverage, not an obstacle

Boz: "The advice I give more frequently than any other is for people to more directly leverage their leaders." Your primary job is to achieve results. Your manager has tools and authority to clear paths. Ask for help to bulldoze blockers rather than trying to solve everything yourself.

Proactively communicate before they have to ask

Casey Winters: "People just way under communicate upward. Then they complain that executives are out of touch when they aren't telling executives what they need to know." Send weekly "state of" emails with priorities, blockers, and thoughts. Frame updates as "no response required" to keep leaders informed without creating burden.

Understand two levels up

Fareed Mosavat: "You should understand your boss's priorities and your boss's boss's priorities. Eventually, that means you have to know what the board is thinking." Build a mental model of how your work creates leverage in the larger system. Tailor communication to address senior leadership's specific concerns.

Bring recommendations, not just problems

Wes Kao: "When you ask 'Hey manager, what should we do?' you're putting a lot of cognitive load on them. Instead say 'Hey manager, here's what I think we should do.'" Present a point of view even if it's just an initial hunch. Provide insights and takeaways, not just raw data.

Use structured update formats

Boz: "We used HPM - Highlight, People, Me. Every manager at Facebook would send this to their manager." Use consistent formats. Ask your manager: "How do you like to get information about me?" Consider weekly emails with priorities, blockers, and general thoughts.

Position yourself as an ally who reduces burden

Ethan Evans: "Management can be a lonely job. Having an ally is a huge weight off people's shoulders." Recognize managers are overwhelmed. Move from asking "How can I help?" to suggesting specific solutions. Keep them in the loop by proactively fixing problems before they ask.

Start with Chapter 1 when talking to execs

Casey Winters: "You have to start with chapter one, which is what part of the company strategy are you working on? What metrics are you trying to improve? What assumptions are you making?" Find the last point that's obvious to the audience and build from there. Don't dive into "Chapter 6" details without the strategic context.

Use concrete artifacts, not abstract ideas

Dylan Field: "The more concrete an artifact is or the more you can debate something, the better. I ask for examples a lot." Present designs and docs rather than abstract ideas. If you lack data for a follow-up question, pause to find the answer rather than guessing.

Run experiments to challenge strong opinions

Itamar Gilad: "If you run a secret experiment and come back with data, either they get extremely mad at you... or more commonly, they're pleasantly surprised." Use evidence to flip a leader's perspective rather than engaging in a battle of opinions.

Understand the spirit, then offer better options

Jiaona Zhang: "It's understanding the spirit of what they're trying to achieve. Being able to go back with 'I understand the spirit, but here's a better way to achieve it.'" Align on the underlying goal first. Present automated or scalable alternatives rather than just saying no.

Use the U-curve for founder involvement

Noah Weiss: "High involvement at the start for strategy and at the end for quality, with autonomy in the middle." Involve founders early for strategic buy-in on goals. Bring them back at the end to ensure the product meets quality standards.

Say what you'll do, say you're doing it, say you did it

Peter Deng: "Say you're going to do the thing, say that you're doing the thing, and then say that you did it." This repetitive communication ensures alignment and provides opportunities for course correction.

Questions to Help Users

  • "What does your manager care most about right now? What's keeping them up at night?"
  • "How does your manager prefer to receive information - email, Slack, meetings?"
  • "Do they know what you're working on this week without having to ask?"
  • "When you bring problems to them, are you also bringing recommendations?"
  • "What does success look like for your team from your manager's perspective?"
  • "Have you asked your manager directly how they'd like you to communicate?"

Common Mistakes to Flag

  • Under-communicating - If your manager has to ask what's going on, you're not communicating enough. Proactive updates build trust
  • Bringing problems without recommendations - This puts cognitive load on your manager. Always come with a point of view
  • Starting with details, not strategy - Executives need context. Start with "Chapter 1" (strategy) before "Chapter 6" (details)
  • Trying to solve everything alone - Your manager has tools and authority you don't. Leverage them to clear blockers
  • Waiting to be managed - The most senior people got there by being great at managing up. It's a proactive skill, not resentment

Deep Dive

For all 50 insights from 35 guests, see references/guest-insights.md

Related Skills

  • Running Effective 1:1s
  • Having Difficult Conversations
  • Stakeholder Alignment
  • Written Communication

平台分布

Codex

35.94%
按下载量换算2,824

Claude

29.12%
按下载量换算2,288

Cursor

18.36%
按下载量换算1,443

Gemini CLI

8.32%
按下载量换算654

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills