@manager-dot-dev/manager-skills
AAn OPINIONATED library of Agent Skills for engineering managers, tech leads, and directors.
Install
agr install @manager-dot-dev/manager-skills --target codexWrites 1 file into AGENTS.md, pinned to git-7a86fb26.
- AGENTS.md
Document
AGENTS.md
Guidelines for AI agents working in this repository.
Repository Overview
This repository contains Agent Skills for engineering managers, following the Agent Skills specification. Skills install to .agents/skills/ (the cross-agent standard).
- Name: Engineering Management Skills
- License: MIT
Repository Structure
engineeringmanagementskills/
├── skills/ # Agent Skills
│ └── skill-name/
│ ├── SKILL.md # Required skill file
│ └── references/ # Optional supporting docs
├── CONTRIBUTING.md
├── AGENTS.md
├── LICENSE
└── README.md
Skill File Requirements
Every SKILL.md must have valid YAML frontmatter:
---
name: skill-name
description: When to use this skill. Include trigger phrases.
metadata:
version: 1.0.0
---
Rules:
namemust match directory name exactlynameis 1-64 chars, lowercase alphanumeric + hyphens onlydescriptionis 1-1024 characters- Keep
SKILL.mdunder 500 lines; move reference material toreferences/
Foundation Skill
em-context is the foundation. All other skills should instruct the agent to read .agents/em-context.md (or .agents/skills/em-context/SKILL.md) before proceeding, so they have team and org context.
Repository README
Describes manager-dot-dev/manager-skills as a whole, which may contain artifacts other than this one. Where this artifact had no useful description of its own, its summary was taken from here.
Engineering Management Skills
An OPINIONATED library of Agent Skills for engineering managers, tech leads, and directors.
LLMs were trained on the whole internet, and they suck at advice related to management.
This repo is based on the best articles I've read in the last 10 years, engineering management and leadership books, my course, and my own articles and posts based on my own experience. No link to the course here, so nobody can blame me for promotion. For the books, I used only my own notes. I did not upload the full books to LLMs.
You may strongly disagree with an answer. That's good, and that's the point. Generic shit advice is not helpful. If you disagree, follow your own opinion.
My goal is to provide some useful perspective, like you had talked to a fellow EM and shared your dilemma.
The opinions are mine. They are not universal truth, and this is not a how-to guide.
I encourage you to stress these skills. Dive deep. Ask for ideas, suggestions, alternatives, and pushback. The point is not to get a perfect answer on the first try, but to use the skill as a thinking partner for a real management situation.
I also included a database of 100 practical ideas for improving your team and supporting your engineers, so the skills can suggest concrete actions instead of staying at the level of abstract advice.
The skills are heavily based on articles from my blog and newsletter, newsletter.manager.dev. See the Resources section for the full list of articles and books that inspired this repo, including resources that did not end up being used directly in a skill.
What This Repository Is
These skills help AI agents give sharper management support for 1:1s, feedback, hiring, performance, roadmap tradeoffs, team health, delegation, stakeholder communication, and related engineering leadership work.
The repository follows the Agent Skills specification. Each skill lives in skills/<skill-name>/SKILL.md and may include focused supporting material under references/.
How The Skills Work
em-context is the foundation skill. It stores team, org, manager, and direct-report context. Other skills should read that context first when it exists, and update it automatically when a conversation reveals durable new information, so advice can stay grounded in the user's actual team.
Each management skill is designed to:
- Trigger from realistic manager prompts, not only exact skill names
- Ask only for missing context that materially changes the advice
- Give concise, direct, manager-ready guidance by default
- Provide scripts, next steps, tradeoffs, and risks where useful
- Preserve a clear point of view instead of flattening everything into generic advice
- Link to source material in
references/sources.md
Skills By Management Area
The skills/ directory stays flat so skills are easy to install and publish. This grouping is only here to make the library easier to browse.
Foundation
| Skill | Purpose |
|---|---|
| em-context | Stores team/org context and direct-report profiles used by the other skills, and acts as shared memory across conversations |
Managing People
Individual humans: growth, feedback, motivation, performance, retention, hiring, and direct manager/report conversations.
| Skill | Purpose |
|---|---|
| 1on1s | Prepare, run, improve, and follow up on 1:1s |
| career-development | Support career growth, promotion readiness, and career conversations |
| engineer-motivation | Diagnose what drives engineers and match work to motivation |
| feedback | Give specific positive or corrective feedback and ask for feedback upward |
| hiring | Define roles, structure interviews, calibrate hiring, and evaluate new hires |
| managing-high-performers | Manage top engineers, brilliant jerks, boredom, ambition, and burnout risk |
| performance-reviews | Diagnose underperformance, write reviews, and decide on PIPs or exits |
| retaining-developers | Diagnose attrition risk and prepare retention conversations |
Building The Team
The team as a system: ownership, trust, rituals, staffing shape, knowledge flow, and sensitive team-level situations.
| Skill | Purpose |
|---|---|
| delegation | Move managers out of the bottleneck role and build ownership |
| difficult-situations | Handle high-stakes management edge cases and sensitive situations |
| knowledge-sharing | Break knowledge silos and improve documentation/onboarding flow |
| meetings | Decide whether to meet, run better meetings, and protect engineering focus time |
| team-composition | Diagnose team capability gaps and hiring/assignment needs |
| team-health | Assess and improve morale, trust, intensity, engagement, and team culture |
Delivery And Execution
Getting work through the system: prioritization, deadlines, productivity, hidden work, delivery tradeoffs, and capacity.
| Skill | Purpose |
|---|---|
| developer-productivity | Measure team productivity without harmful individual scoring |
| managing-urgency | Handle deadlines, fake urgency, crisis pressure, and tradeoff conversations |
| roadmap-planning | Plan roadmaps, prioritize tech work, and communicate tradeoffs |
| shadow-work | Identify hidden capacity drains like support, glue work, and shadow backlogs |
Product, Business, And Stakeholders
Operating outside the team boundary: PM partnership, business framing, stakeholder trust, upward communication, architecture collaboration, and written alignment.
| Skill | Purpose |
|---|---|
| business-literacy | Translate engineering work into business and finance language |
| influence | Persuade stakeholders and get buy-in without direct authority |
| managing-up | Build a reliable relationship with your manager and communicate upward |
| working-with-architects | Work effectively with architects, staff engineers, and principal engineers |
| working-with-pm | Build a stronger PM-EM partnership and improve product orientation |
| written-communication | Draft clear Slack messages, announcements, and stakeholder updates |
Managing Yourself
Your own operating system as a manager: role transitions, personal traps, bad-day patterns, and recurring leadership tensions.
| Skill | Purpose |
|---|---|
| management-transitions | Navigate new-manager, inherited-team, peer-to-manager, and acquisition transitions |
| managing-yourself | Diagnose personal EM traps, bad-day patterns, and recurring leadership tensions |
Installation
Use the Skills CLI in the project where you want to install the skills:
npx skills init
npx skills add manager-dot-dev/manager-skills
You can also install a specific skill from the repo:
npx skills add manager-dot-dev/manager-skills/skills/1on1s
Then create or update .agents/em-context.md with your team context so the other skills can tailor their advice.
Repository Structure
skills/
skill-name/
SKILL.md
references/
sources.md
Resources
The skills are heavily based on articles from newsletter.manager.dev, plus the articles and books below. This list includes sources that inspired the repo even when they did not end up directly referenced in a specific skill.
Articles
Books
| # | Title | Author |
|---|---|---|
| 1 | The Everything Store | Brad Stone |
| 2 | Amp It Up: Leading for Hypergrowth | Frank Slootman |
| 3 | An Elegant Puzzle: Systems of Engineering Management | Will Larson |
| 4 | High Output Management | Andrew Grove |
| 5 | Atomic Habits | James Clear |
| 6 | Become an Effective Software Engineering Manager | James Stanier |
| 7 | Crossing the Chasm | Geoffrey Moore |
| 8 | Deep Work | Cal Newport |
| 9 | Empowered: Ordinary People, Extraordinary Products | Marty Cagan |
| 10 | Extreme Ownership | Jocko Willink & Leif Babin |
| 11 | From Worst to First | Gordon Bethune |
| 12 | Hit Refresh | Satya Nadella |
| 13 | How Big Things Get Done | Bent Flyvbjerg & Dan Gardner |
| 14 | Influence: The Psychology of Persuasion | Robert Cialdini |
| 15 | Intercom on Jobs to be Done | Intercom |
| 16 | It Doesn't Have to Be Crazy at Work | Jason Fried & David Heinemeier Hansson |
| 17 | Competing Against Luck | Clayton M. Christensen, Karen Dillon, Taddy Hall & David S. Duncan |
| 18 | Leading Snowflakes | Oren Ellenbogen |
| 19 | Mistakes Were Made (But Not by Me) | Carol Tavris & Elliot Aronson |
| 20 | Never Split the Difference | Chris Voss |
| 21 | No Rules Rules | Reed Hastings |
| 22 | Hackers & Painters | Paul Graham |
| 23 | Peopleware: Productive Projects and Teams | Tom DeMarco & Tim Lister |
| 24 | Radical Candor | Kim Scott |
| 25 | Setting the Table | Danny Meyer |
| 26 | The Five Dysfunctions of a Team | Patrick Lencioni |
| 27 | The Almanack of Naval Ravikant | Eric Jorgenson |
| 28 | The Art of Leadership: Small Things, Done Well | Michael Lopp |
| 29 | The Diary of a CEO: The 33 Laws of Business and Life | Steven Bartlett |
| 30 | The Dichotomy of Leadership | Jocko Willink & Leif Babin |
| 31 | The Goal | Eliyahu M. Goldratt |
| 32 | The Hard Thing About Hard Things | Ben Horowitz |
| 33 | The Making of a Manager | Julie Zhuo |
| 34 | The Mom Test | Rob Fitzpatrick |
| 35 | The Mythical Man-Month | Frederick P. Brooks Jr. |
| 36 | The Nvidia Way: Jensen Huang and the Making of a Tech Giant | Tae Kim |
| 37 | Turn the Ship Around! | L. David Marquet |
| 38 | Work Rules! | Laszlo Bock |
Contributing
See CONTRIBUTING.md for how to add or improve skills.
Each SKILL.md should:
- Use valid YAML frontmatter
- Keep
nameequal to the directory name - Keep
descriptionunder 1024 characters - Stay under 500 lines
- Read
em-contextbefore giving personalized advice - Prefer concise, direct, manager-ready output
Trustgrade A
- passBody integrity
Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.
- passType matchnot applicable to this artifact type
Whether the artifact is really the kind of thing its metadata claims it is.
- passFreshness
How long since the source repository was last pushed to.
- passPrompt injection
Scans the artifact's own text for instructions aimed at your agent rather than at you.
- passLicense
Whether the source repository declares an SPDX license permissive enough to redistribute.
How the grade is calculated
Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:
- Aevery check passed
- Bone warning
- Ctwo warnings
- Dprompt injection or body integrity failed, or three warnings
- Fone of those failed, and something else is wrong
These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.
Versions
git-7a86fb26ab8c2026-08-06