Team & Operations

Team & Operations skills for your AI agent.

Four skills addressing four different scales of the same complaint — that effort goes in and output doesn’t come out. High Output Management works at the scale of your own week: which hours multiply, how to match 1:1 cadence to how experienced someone is, why every decision routing through you leaves work waiting. Drive Motivation works at the scale of one person and the incentive quietly crowding out the motivation they arrived with. Team Topologies works at the scale of the boundaries between teams. Traction EOS works at the scale of the whole company — Rocks with a single owner, a weekly scorecard, a meeting that ends in decisions.

With these installed, an agent asked to “fix the team” stops proposing a reorg and better communication. It asks whether the problem is one manager’s leverage, one person’s autonomy, cognitive load spread across too many domains, or the absence of any operating rhythm — and it will tell you when a reorg is the wrong instrument for a motivation problem.

4 skills Updated August 2026 Free & MIT-licensed

Choosing

Which team skill fits the problem I have?

Route by the size of the broken thing. Your own week — it’s full, the team’s week isn’t productive, every decision waits for your approval, and you run identical 1:1s for last month’s hire and your most experienced engineer → High Output Management, which computes the multiplier on managerial time. One person — your strongest contributor stopped volunteering for anything and nothing about their compensation explains it, or you added a bonus and the work got narrower and more gamed → Drive Motivation, which audits incentives against autonomy, mastery and purpose. The space between teams — a routine change needs three teams to coordinate and spends more time waiting than being worked on, or your platform team is a bottleneck people route around → Team Topologies, which classifies every team as stream-aligned, enabling, complicated-subsystem or platform and trims scope until cognitive load fits. The whole company — leadership meetings are ninety minutes of status updates and the same three issues resurface monthly → Traction EOS.

The pairing worth having is Traction EOS with High Output Management: one gives the company a rhythm, the other gives you leverage inside it. Hold Team Topologies until you have more than three teams — below that the boundaries aren’t what’s slowing you down, and redrawing them is expensive theatre.

The skills

All 4 Team & Operations skills

Traction EOS

Traction — Gino Wickman

Traction EOS is the Entrepreneurial Operating System from Gino Wickman’s Traction, rebuilt as a free skill your AI agent runs. It writes the Vision/Traction Organizer, sets three to seven quarterly Rocks with a single owner each, designs a weekly scorecard of leading numbers, and structures a Level 10 meeting that ends in decisions.

Vision/Traction Organizer (V/TO)
Rocks (90-Day Priorities)
The Accountability Chart

Try “Create a V/TO (Vision/Traction Organizer) for my startup using traction-eos skill”

Drive Motivation

Drive — Daniel Pink

Drive Motivation packages Daniel Pink’s Drive for AI agents, because carrots and sticks degrade performance on any work that requires thought. Your agent audits incentives, goals, and reviews against autonomy, mastery, and purpose, then redesigns the if-then rewards that are quietly crowding out the motivation people already brought with them.

Autonomy
Mastery
Purpose

Try “Design a gamification system based on intrinsic motivation, not just points using drive-motivation skill”

High Output Management

High Output Management — Andrew S. Grove

Every hour a manager spends has a multiplier, and High Output Management is the skill that makes your AI agent compute it. Andy Grove’s Intel-era manual supplies the equation — a manager’s output is the output of their organization — and your agent applies it to your calendar, your metrics, your 1:1 cadence, and how decisions get made.

Managerial Leverage
Output Indicators
One-on-Ones

Try “Redesign my weekly calendar around high-leverage activities using high-output-management skill”

Team Topologies

Team Topologies — Matthew Skelton & Manuel Pais

When work keeps getting stuck between teams rather than inside them, Team Topologies is the skill to load. It brings Matthew Skelton and Manuel Pais’s book to your AI agent, which classifies every team as stream-aligned, enabling, complicated-subsystem, or platform, declares the interaction mode for each pair, and trims scope until cognitive load fits.

Four Team Types
Three Interaction Modes
Conway's Law

Try “Classify our teams into the four types and flag the misfits using team-topologies skill”

npx skills add wondelai/skills --all --global

This skill is compatible with Claude, Claude Code, Claude Cowork, Codex, Cursor, OpenClaw, Hermes Agent, and other agentskills.io-compatible agents.

FAQ

Frequently asked questions

I lead a team of four. Is Traction EOS overkill?

Usually, yes. EOS assumes a leadership layer with separate functional owners, quarterly Rocks and a scorecard someone maintains — machinery that costs more than it returns at four people, where everyone already knows what everyone is doing. High Output Management scales down much better: its ideas about leverage, delegation and task-relevant maturity apply to any manager with two reports. Revisit Traction EOS when you can no longer hold the whole company in one meeting.

Do Traction EOS and Team Topologies pull in different directions?

In one specific place, yes. EOS wants a clean accountability chart with one name over each function, which tends to organize people by discipline. Team Topologies argues that functional splits are exactly what stops anyone owning a change end to end, and wants stream-aligned teams that cross those lines. If you run both, let EOS supply the cadence and Team Topologies supply the boundaries, rather than letting the org chart decide both.

Can an AI agent be useful on people problems it can’t observe?

It can’t read the room, and neither framework pretends otherwise. What it does well is structural: examining your calendar for low-leverage hours, spotting an if-then incentive that will predictably narrow behavior, noticing that a change requires three handoffs, drafting 1:1 agendas that surface disengagement before it becomes a resignation. The judgment about a specific person stays with you — the diagnosis of the system around them is where this earns its place.

I’m a founder with no managers yet. Which of these is worth installing?

Drive Motivation and High Output Management. The first shapes how you design work and rewards before any bad incentive is embedded, which is far cheaper than removing one later. The second is really about leverage, and applies whether you’re managing five people or your own attention. Traction EOS and Team Topologies both assume structure you don’t have; installing them early tends to produce ceremony rather than clarity.

Other domains

The rest of the library

Design & UX 9 Marketing & Messaging 6 Sales & Persuasion 6 Product & Innovation 10 Strategy & Growth 4 Code Quality 5 Architecture & Systems 6

Prove it

Don’t guess your AI engineering level.
Measure it.

25 questions · ~8 min · Free

For hands-on developers

AI Developer Scorecard

How production-grade is your AI engineering?

Twenty-five questions across the practices that separate vibe-coding from production-grade engineering. Instant score, per-section breakdown, and a 30/60/90-day playbook.

Score 0–75 · 30/60/90-day playbook Score yourself For CTOs & founders

CTO Scorecard

Is your engineering team ready for AI at scale?

Twenty-five questions on how your org adopts AI — adoption, governance, automation, and ROI. See where you sit on the path from Reactive to Strategic Leader.

Score 0–75 · Reactive → Strategic Leader Score your org

Work with us

We build the skills you already use. Now we’ll build yours.

Custom skills · Subagents · MCP integrations — shipped to production, not demoed.

See what we build Book a 15-min call

Sprints from $3K · shipped to production, or you don’t pay the final milestone.