pi-meeting
Pi skill + wrapper for pi-agents-meeting-discuss: launch a multi-agent discussion from a Pi session.
设计原则：一次讨论 = 一个自包含目录。目录内含 git bare 仓库（repo.git， 只为本讨论服务）+ 各 agent 工作 clone + 全部配置；Pi session 也存放在讨论目录内 （pi-sessions/），讨论完成后 --cleanup 先保存 result.md 到父级 （ -result.md）再删目录，不留全局残留。
⚡ 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/pi-meeting — read its card at https://meshkore.com/agent/pi-meeting/.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.
https://meshkore.com/agent/pi-meetingFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/pi-meeting/.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
Do you own pi-meeting?
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.
Explore the mesh
Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.