A system for working with your manager through regular updates, structured one-to-one meetings, decision notes, and clear requests for help. Managing up means giving a manager the context needed to make decisions and remove obstacles.

Use it to create a communication schedule, weekly update template, escalation plan, executive memo, or plan for gaining more influence.

It reduces surprises and makes trade-offs, blockers, and expectations visible to leadership. It also helps set boundaries when the requested pace or workload is unrealistic.

managing-up — Skill for Claude Code and Codex by liqiongyu

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add liqiongyu/lenny_skills_plus --skill managing-up

Clone the repo

git clone --depth 1 https://github.com/liqiongyu/lenny_skills_plus

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/managing-up/github.svg)](https://agentmods.dev/skills/liqiongyu/lenny_skills_plus/managing-up)

Your own site

<a href="https://agentmods.dev/skills/liqiongyu/lenny_skills_plus/managing-up"><img src="https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/managing-up/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/liqiongyu/lenny_skills_plus/managing-up"><img src="https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/managing-up.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,220 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00024	$0.02220
Opus 5.5	$0.00010	$0.00888
Sonnet 5.5	$0.00005	$0.00444
Haiku 4.5	$0.00002	$0.00222

Measured 2mo ago against content hash b0f59250adad, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

managing-up scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/managing-up/SKILL.md · 139 lines

How it starts

The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Managing Up

Scope

Covers

Building a proactive partnership with your manager (vs waiting to be managed)
Setting a clear upward communication system (async updates, 1:1 structure, decision memos)
Leveraging leaders to remove blockers and accelerate decisions (clear asks + escalation triggers)
Communicating trade-offs and context so leadership can make good calls
Creating a “seat at the table” path: showing business-level perspective before you’re invited
Setting boundaries when leadership pace/expectations are misaligned (without being adversarial)

When to use

“Help me manage up with my boss—set a cadence and a weekly update template.”
“My exec stakeholders feel out of touch—help me communicate context and trade-offs better.”
“I need a clean escalation plan and how to ask my leader for help without sounding needy.”
“I want more influence / a seat at the table—create a plan and artifacts.”

When NOT to use

You need HR/legal guidance (harassment, discrimination, retaliation, threats, investigations) — follow your company process and involve HR/legal.
You’re negotiating compensation/title or a formal performance process — use your company process; this skill can help with communication artifacts but not with policy/legal strategy.
You have a personal safety or mental-health crisis — seek professional help and follow company policy.
You want to set up a cross-functional collaboration system across multiple teams (use cross-functional-collaboration).
You want to design your 1:1 cadence, coaching toolkit, or career conversation system (use running-effective-1-1s).
You need to delegate work effectively to your own reports (use delegating-work).
You need broad buy-in from multiple stakeholders beyond your direct manager (use stakeholder-alignment).

Inputs

Minimum required

Your role, scope, and current priorities (what you own; what “good” looks like in the next 4–8 weeks)
Who you’re managing up to (manager level; decision power; relationship stage: new/stable/strained)
Current friction (2–5 concrete examples) and desired outcome (clarity, autonomy, speed, influence, boundaries)
Communication environment (remote/hybrid, time zones, tools, meeting cadence)
Constraints (sensitive topics, confidentiality/PII rules, upcoming deadlines)

Read the full file on GitHub · 139 lines

Files

What ships with it

13 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 139 lines · 24 tokens per session scan A b0f59250adad

Subscribe to this mod's changes

managing-up is a skill published in the GitHub repository liqiongyu/lenny_skills_plus (53 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 24 tokens to every session and 2,220 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Planning Productivity agent-skills ai-agents automation claude codex prompt-engineering

managing-up next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
managing-upliqiongyu/lenny_skills_plus	Skill	53	5mo ago	Apache-2.0	A	24	Claude Code, Codex
wayfindervinvcn/mattpocock-skills-zh-CN	Skill	5.6k	9d ago	MIT	A	40	Claude Code, Codex
codebase-designvinvcn/mattpocock-skills-zh-CN	Skill	5.6k	9d ago	MIT	A	56	Claude Code, Codex
setup-matt-pocock-skillsvinvcn/mattpocock-skills-zh-CN	Skill	5.6k	9d ago	MIT	A	44	Claude Code, Codex
triagevinvcn/mattpocock-skills-zh-CN	Skill	5.6k	9d ago	MIT	A	34	Claude Code, Codex
setup-ts-deep-modulesvinvcn/mattpocock-skills-zh-CN	Skill	5.6k	9d ago	MIT	A	49	Claude Code, Codex
writing-fragmentsvinvcn/mattpocock-skills-zh-CN	Skill	5.6k	9d ago	MIT	A	23	Claude Code, Codex