myteam 0.2.3

Agent roster CLI

Myteam

myteam is a package for building agent systems where agents load their own roles and skills from files on disk.

The core model is simple:

• users define roles, skills, and tools inside .myteam/
• agents assume a role by running myteam get role <role>
• agents load a skill by running myteam get skill <skill>
• each loaded role or skill reveals the next layer of discoverable roles, skills, and tools

This makes myteam useful for hierarchical multi-agent systems where instructions should be explicit, inspectable, and versioned in Git.

Agent-Centered Workflow

myteam is primarily for agents, not humans.

A human author creates the role and skill structure. After that, the intended workflow is that agents load their own instructions.

Typical flow:

1. A user or top-level agent sets up .myteam/.
2. A sub-agent is assigned a role such as developer.
3. That sub-agent runs myteam get role developer.
4. myteam prints the role instructions plus any immediately available child roles, child skills, and tools.
5. If the agent needs a skill, it runs myteam get skill <skill>.

In other words, roles and skills are loaded by the agent that is assuming them.

What Happens When An Agent Loads A Role

When an agent runs:

myteam get role developer

myteam executes that role's load.py, which:

1. Prints the contents of role.md or ROLE.md
2. Prints built-in guidance about roles, skills, and tools
3. Lists the immediate child roles in that directory
4. Lists the immediate child skills in that directory
5. Lists Python tools in that directory

The same pattern applies to skills:

myteam get skill python/testing

This layered discovery is the main idea behind the package. An agent sees the instructions for its current node and the next available things it can assume or use.

Mental Model

myteam stores an agent system in plain files.

• A role is a team member with instructions.
• A skill is a reusable capability with instructions.
• A tool is a Python script colocated with a role or skill.
• A roster is a reusable bundle that can be downloaded into .myteam/.

Roles and skills are identified by definition files:

• role directories contain role.md or ROLE.md
• skill directories contain skill.md or SKILL.md

Each loadable node also has a load.py that prints the node's instructions and its immediate discoverable children.

Quick Start

Initialize a new agent system:

myteam init

This creates:

AGENTS.md
.myteam/
  load.py
  role.md

The root .myteam/ directory is the default root role.

Edit .myteam/role.md with the instructions that should be given to the default agent. Then that agent can load its instructions with:

myteam get role

Create a sub-role and a skill:

myteam new role developer
myteam new skill python
myteam new skill python/testing

That agent system now supports commands like:

myteam get role
myteam get role developer
myteam get skill python/testing

Directory Structure

Example:

AGENTS.md
.myteam/
  load.py
  role.md
  developer/
    load.py
    role.md
  python/
    load.py
    skill.md
    testing/
      load.py
      skill.md

In this layout:

• the root agent runs myteam get role
• a developer agent runs myteam get role developer
• an agent needing the testing skill runs myteam get skill python/testing

Discovery is local to the node being loaded. An agent sees only the next layer beneath its current role or skill.

For nested roles or skills to be discoverable, each parent layer must also be defined. For example, python/testing is only visible if python itself exists as a loadable node.

Authoring Roles And Skills

Instruction files are Markdown.

Example role.md:

---
name: Developer
description: Implements product changes and fixes
---

You are responsible for writing and validating code changes.
Load relevant skills before implementing complex work.
Delegate frontend work to `frontend` if that role is available.

Example skill.md:

---
name: Python Testing
description: Test-writing and debugging guidance
---

Prefer focused tests before broad suites.
Use the existing project test helpers where available.

Behavior:

• YAML frontmatter is stripped before the instructions are printed to the agent
• name and description are used for listings when present
• if frontmatter metadata is absent, myteam falls back to info.md when available

Commands

myteam init

Creates the root .myteam/ role and AGENTS.md in the current directory.

myteam new role <path>

Creates a new role under .myteam/ with:

• role.md
• load.py

Examples:

myteam new role developer
myteam new role engineer/frontend

myteam new skill <path>

Creates a new skill under .myteam/ with:

• skill.md
• load.py

Examples:

myteam new skill python
myteam new skill python/testing
myteam new skill research
myteam new skill research/literature-review

myteam get role [path]

Loads a role's instructions.

• omit path to load the root role at .myteam/
• use slash-delimited paths for nested roles

Examples:

myteam get role
myteam get role developer
myteam get role engineer/frontend

myteam get skill <path>

Loads a skill's instructions.

Examples:

myteam get skill python/testing
myteam get skill research/literature-review

myteam remove <path>

Deletes a role or skill directory from .myteam/.

myteam list

Lists available downloadable rosters from the default roster repository.

myteam download <roster>

Downloads a roster into .myteam/ by default.

Useful when you want to seed an agent system from a reusable template instead of authoring it from scratch.

Why Use Myteam

• agents load their own instructions directly from the filesystem
• roles and skills are explicit, inspectable, and Git-friendly
• discovery is layered, which fits hierarchical agent systems
• tools can live next to the roles and skills that use them
• rosters let you reuse agent-system structures across projects

Installation

pip install myteam

Requirements

• Python 3.11+

License

MIT