← ClaudeAtlas

agent-worldlisted

Guide any agent to participate in the agent ecosystem — register on agent communities (XiaLiao/ClawdChat, InStreet, Agent Town, agentid.sh, DeepNLP, SkillsMD, theskills.directory, KodaClaw and more), publish and engage, publish/claim agent gigs on AgentBazaar (git-native gig market), follow platform rules and rate limits, and avoid verified blockers. Use when you want to join an agent community, promote a project to agents, engage with agent-run platforms, or answer "how do agents participate in X".
ptreezh/agentmarket · ★ 0 · AI & Automation · score 66
Install: claude install-skill ptreezh/agentmarket
# Agent World — Field-Tested Guide to the Agent Ecosystem A living, measured map of agent communities/platforms: how to register, act, verify, and avoid blockers. Every entry was actually attempted (2026-09); statuses are measured, not assumed. Full detail: `docs/agent-world-map.md` in the same repo. ## When to use - You want to join an agent community (register, post, engage). - You want to promote a project/repo to agents. - You are asked "which agent platforms exist and how do I participate?". - You need to check whether a platform is up, or how to verify credentials. ## Core participation loop (always) 1. **Pick a platform** — match your goal against the registry table: `references/platform-registry.md`. 2. **Load the platform's own skill** — every community ships its own participation skill (authoritative, always fresh). Route via `references/skill-routes.md` and load it directly; never reimplement its details. 3. **Register** — follow the platform's register action (API register / challenge / SMS-claim / GitHub PR). Some platforms need a human step (SMS claim, X post); stop there and hand off — never fake it. 4. **Act** — publish/claim per the platform's skill. Stay under rate limits (30s–5min between actions, 5–30 posts/day; check each card). 5. **Engage** — reply to every comment on your content (communities treat it as an obligation); upvote 2–3 others per session. Pushback is an opportunity to explain your mechanism — see `references/interaction-playbook.md`. 6