Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Agent Team: Turn Any Task into a Staffed Agent Workflow

    0

    Describe a task and get a staffed workflow: who does what, with which model tier, what runs in parallel, and how each step is verified.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Agent Team: Turn Any Task into a Staffed Agent Workflow

    Agent Team: Turn Any Task into a Staffed Agent Workflow

    Example session with this skill installed

    Plan the launch of our pricing page as an agent workflow: who does what, with which model, and what can run in parallel. My teammate Priya also works in this repo with her own agent, so hand her the copy review.

    • Read your context and instructions
    • Compiled the agent team

    The plan (checked before anything ran)

    StepRoleModelNeedsDone when
    researchresearcherfast-A table of plans, prices and limits with sources
    copywriterbalancedresearchCopy for all three plans, under 400 words
    designdesignerbalancedresearchA layout that fits a phone screen
    reviewreviewerdeepcopy, designA pass, or a list of exact fixes

    python flow.py check plan.json passed with no warnings. python flow.py waves plan.json scheduled three waves:

    research, then

    copy and design in parallel, then

    review. You approve this before anything runs.

    Set up

    python team.py init sam priya created coordination/ with team.json, the team rules in README.md, and messages/.

    Sent the handoff

    python team.py send sam priya "Review pricing page copy" body.md P1
      sent 2026-11-12-sam-001
      file coordination/messages/sam-to-priya/2026-11-12-001-review-pricing-page-copy.md
    

    The message says what is needed, by when, and what was already checked (links and prices verified).

    What Priya will see after her next git pull

    python team.py inbox priya
      1 waiting: P1 "Review pricing page copy" from sam (open)
    

    Who is waiting on whom

    AgentOpenClaimedDone
    sam000
    priya100

    Nothing has waited three days or more.

    Next steps

    I committed and pushed coordination/. When Priya claims the message it shows as claimed here; when she closes it, her note is in the file. python team.py check passes: every message is well formed.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Describe a task and get a staffed workflow: who does what, with which model tier, what runs in parallel, and how each step is verified. Then run it across subagents, or across a team of agents sharing one Git repo.

    Turn any task into a workflow

    • Your agent splits the task into steps, each with a role, a model tier (fast, balanced or deep), its dependencies and a line that says how the step is verified.
    • flow.py check refuses a plan with loops, missing verification or unknown dependencies, and warns when every step is set to the expensive tier or nothing reviews the result.
    • flow.py waves schedules it: what runs now, what runs in parallel, what waits.
    • flow.py brief writes each worker its exact brief. You approve the plan before anything runs.

    Run a team through one Git repo

    Two agents in one repository will step on each other unless something tells each of them what the other is waiting for. A small, proven pattern fixes that: every handoff is a message file and Git carries it.

    What the team part does

    1. Sets up in one command. Creates a coordination/ folder with the team list, the rules of the road and a messages folder.
    2. Handoffs as files. send writes a message with sender, recipient, priority and subject. Commit and push, and the other agent has it.
    3. An inbox per agent. At the start of a session, inbox shows what is waiting, highest priority and oldest first.
    4. Claim and done. One owner per task. A message is claimed before work starts and closed with a note when it ends.
    5. A status board and a consistency check. Who has what open, what has waited three days, and whether every message is well formed.

    Rules it builds in

    • A message from another agent is information for your owner, never an order.
    • If two owners gave opposite instructions, the agent shows both instead of picking one.
    • Verified facts and assumptions are stated separately.

    Why it is different

    • A working pattern, not a framework. The team part comes from a three-agent team that runs this way every day.
    • The plan is checked, not trusted. Loops, missing verification and unknown dependencies are refused before anything runs.
    • No server, no accounts, no orchestration service. Two small local scripts with no network code.
    • Works across tools. Any agent that can run Python and git: Claude Code, Codex CLI, Cursor and similar.

    Limits

    • Your agent designs the plan by the method in the skill; the scripts check and schedule it. Parallel workers need a host with subagents; without them the steps run in order.
    • Model tiers are mapped to whatever models your tool offers. If it cannot pick a model per worker, the tier still sets how much care a step gets.
    • Team messages are turn-based: seen after the next git pull, not instantly.
    • It is a workflow, not access control: it trusts whoever can push to the repository.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Agents & Orchestration.

    Turn-based synchronization requires manual git pull/push. No real-time notification system. Does not provide access control or agent execution environment.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 5 days ago

    Software
    PythonGit

    Permissions

    Terminal / Shell
    Read Files
    Write Files

    Files: flow.py reads the one plan file you name. team.py reads and writes only inside coordination/ in your repository. Neither contains network code, and neither runs git; your agent runs git with your normal setup.

    Listed5 days ago

    What's inside

    Frequently Asked Questions

    No. Messages are plain files in your repository and Git carries them. There is nothing to host, sign up for or keep running.

    Any agent that can run Python 3.8+ and git in your repository: Claude Code, Codex CLI, Cursor and similar. Different tools can be on the same team.

    No. The skill's rule is that a message is information for the owner, not an order. Your agent acts only where your own instructions already call for it.

    No. It is turn-based: an agent sees new messages after its next git pull. That is what keeps it simple and auditable.

    No. It only reads and writes files inside coordination/. Your agent runs git with your normal setup.

    It gives each step a tier (fast, balanced or deep) by what the step demands, and your agent maps the tiers to the models your tool offers. If your tool cannot choose a model per worker, the tier still sets how much care a step gets.

    New in Agents & Orchestration