Agent Skills for Engineering Managers
Engineering manager skills help you run a team: the people side (growth, hiring, hard conversations), delivery (shipping at a sustainable pace), process (how the team decides, builds, and learns), technical direction (which bets you're making and which you're not), stakeholders (translating between the team and the rest of the company), and operations (the machinery that keeps the team able to work). These skills are for the manager's own workflow — not for managing code or infrastructure. Use the ranked list by scanning for the sub-topic you're weakest on right now, then read the skill's description to confirm it matches your context. The order reflects observed search demand, with direct matches first and a cap on any single publisher, so the top entries are the ones other managers are actually looking for.
5 to start with10 top options
Start with these.
Engineering management is people, process, and technical direction — delivery is the visible output of those three.
These are the closest matches for this work. Start with the first one and open it to install.
- Rank 01View Agent SkillDirect
1on1s
NotablePrepare agendas, diagnose struggling 1:1 relationships, and run effective 1:1 meetings with direct reports.
- Rank 02View Agent SkillDirect
team-health
NotableAssess and improve team health across morale, cohesion, delivery culture, and engagement.
- Rank 03View Agent SkillDirect
career-development
NotableSupport direct-report growth with a stage model of engineering impact and non-linear career planning.
- Rank 04View Agent SkillDirect
delegation
NotableGuide managers out of the bottleneck role with Team Rep, Epic Ownership, and Task-Relevant Maturity frameworks.
- Rank 05View Agent SkillDirect
hiring
NotableStructure the interview process, calibrate the hiring bar, counter bias, and evaluate a new hire's first 90 days.
Explore 5 more Agent Skills
- Rank 09View Agent SkillPossible
persona-team-lead
A team-lead persona that runs standups, prepares 1:1s and meetings, shares weekly digests, delegates email action items, and tracks OKRs using Google Workspace CLI workflows.
29,324 · popularity - Rank 10View Agent SkillPossible
linear
OfficialManages issues, projects, and team workflows in Linear via the Linear MCP server, covering sprint planning, bug triage, workload balance, release planning, and status updates.
10,135 · popularity - Rank 11View Agent SkillPossible
team-composition-analysis
Designs team structures, hiring plans, compensation strategies, and equity allocation for early-stage startups from pre-seed through Series A, including role-by-role planning and benchmarks.
9,938 · popularity - Rank 12View Agent SkillPossible
strategy-red-team
Red-teams a PRD, roadmap, or strategy by steelmanning then attacking load-bearing assumptions, ranking failure modes, and returning the cheapest test and kill criteria for each.
8,942 · popularity - Rank 13View Agent SkillPossible
sales-org-structure
Designs a sales organization's structure for its stage, covering role mix, topology, SDR-to-AE ratios, hunter/farmer split, span of control, and specialization by segment.
8,001 · popularity
What this topic covers
Each sub-topic groups Agent Skills for a specific situation.
- People
- The team as humans: growth, hiring, and hard conversations.
- Delivery
- Work that actually ships, at a pace the team can sustain.
- Process
- How the team decides, builds, and learns in public.
- Technical direction
- Which technical bets the team is making, and which it is not.
- Stakeholders
- Translate between the team and the rest of the company.
- Operations
- The unglamorous machinery that keeps a team able to work.
Frequently asked questions
- How is this list ordered?
- It's ranked by observed search demand, with direct matches to the topic placed first and a cap on how many skills any single publisher can occupy. That means the top of the list reflects what engineering managers are actively searching for, not a hand-picked editorial ranking.
- What's the difference between the Delivery and Process sub-topics?
- Delivery covers work that actually ships at a pace the team can sustain. Process covers how the team decides, builds, and learns in public — the mechanics behind that delivery.
- Do I need a separate skill for each sub-topic?
- Not necessarily. Some skills address a single sub-topic like hiring or stakeholder translation, while others span several. Start with the sub-topic where your team is currently struggling most, then check whether one skill covers enough ground or you need a few.
- Where does technical direction fit if I'm not the most technical person on the team?
- Technical direction is about which technical bets the team is making and which it is not — a decision-making responsibility, not a coding one. Skills in this sub-topic focus on framing and communicating those choices rather than implementing them.
How to install an Agent Skill
Start with the first skill on this page. Claude Code reads a SKILL.md once it is in the skills directory:
- Claude Code — copy the SKILL.md for 1on1s into ~/.claude/skills/1on1s/ for yourself, or .claude/skills/1on1s/ to share it with a project.
- From the registry — run npx skills add manager-dot-dev/manager-skills@1on1s.
- Or download 1on1s from its source and place that SKILL.md in the directory above.
How to choose Check the source and the skill’s own instructions before you install. Official and Notable describe where a skill comes from.