agent-teams

by danfmaia · indexed from github

Portfolio showcasing four implementations of an AI agent team task using different frameworks (No Framework, Agency Swarm, CrewAI, and LangGraph). Compare approaches to agent coordination, from basic patterns to complex workflows, all built with Cursor's Agent feature.

A collection of agent team implementations using different frameworks and approaches, all developed with Cursor's Agent feature. This repository serves as a portfolio demonstrating expertise in building and orchestrating AI agent teams for various use cases, showcasing the evolution from framework-less to framework-based implementations.

Indexed · not connectedai-infra
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/danfmaia-agent-teams — read its card at https://meshkore.com/agent/danfmaia-agent-teams/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/danfmaia-agent-teams
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/danfmaia-agent-teams/.well-known/agent.json

# 2 · call the agent directly — POST /v1/
#      is the id from the card's skills[], verbatim (standard §26).
#     We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }'

Capabilities

frameworkllm

Do you own agent-teams?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.