Teams do

.do Agent Skills — reusable, composable skill modules

Install

npx -y skills add dot-do/skills --skill teams-do

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

teams.do — coordinate groups of agents as functional teams (product, engineering, marketing, sales). Team-level imports and cross-team workflow patterns.

SKILL.md

2.2 KB, 470 tokens by cl100k_base, as published. Nobody here has run it

teams.do

You are an expert in teams.do — group agents into functional teams for higher-level coordination.

When to Use

Activate when the user wants to coordinate multiple agents as a team rather than orchestrating individuals.

Core Usage

import { product, engineering, marketing, sales } from 'teams.do'

// Team-level calls — the team coordinates internally
const mvp  = await product`define the MVP for ${idea}`
const app  = await engineering`build ${mvp}`
await marketing`launch ${app}`
await sales`start outreach for ${app}`

Team Composition

Team	Agents	Responsibility
`product`	Priya	Specs, roadmaps, priorities, stakeholder coordination
`engineering`	Ralph, Tom, Quinn	Build, architecture, testing, code review
`marketing`	Mark	Copy, content, launches, brand
`sales`	Sally	Outreach, demos, pipeline, closing
`design`	Rae	UI, frontend, accessibility, components

Individual vs Team

import { ralph, tom, quinn } from 'agents.do'   // individuals
import { engineering } from 'teams.do'           // team

// Individual — direct control
const code = await ralph`implement ${spec}`
const review = await tom`review ${code}`

// Team — let the team coordinate
const shipped = await engineering`implement, review, and test ${spec}`

Use individuals when you need predictable, sequential handoffs. Use teams when you want the group to self-organize.

Custom Teams

import { Startup } from 'startups.do'
import { engineering, product } from 'teams.do'

// Teams are composable
export default Startup({
  name: 'MyStartup',
  teams: {
    core: { ...engineering, ...product },
    growth: { ...sales, ...marketing },
  }
})

Best Practices

Prefer team-level calls for strategic work (product\plan Q2``)
Use individual agents for precise, sequential workflows
Teams self-coordinate — don't micromanage the internal handoffs

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most product growth skills give in 470 tokens

Counted across 728 of the 1,010 authors here whose files we hold, read 2026-08-07

Read product marketing context before asking questionsin 24 of 728, across 18 files
Define the ideal customer profilein 21 of 728, across 3 files
Document a rollback plan before deploymentin 21 of 728, across 12 files
Analyze the codebase to understand the productin 19 of 728, across 1 file
Ask clarifying questions about the value propositionin 19 of 728, across 1 file
Search for companies matching the criteriain 19 of 728, across 1 file
Look for signals of immediate needin 19 of 728, across 1 file
Assign a fit score from one to tenin 19 of 728, across 1 file
Identify the target decision-maker rolein 19 of 728, across 1 file
Suggest a personalized contact strategyin 19 of 728, across 1 file
Provide conversation starters for outreachin 19 of 728, across 1 file
Format results in a scannable markdown templatein 19 of 728, across 1 file

Said here and by no other author read

import teams from teams.do
prefer team-level calls for strategic work
use individual agents for sequential workflows
do not micromanage internal team handoffs

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.