Community Agent Submission And Curation Workflow

via “agent contribution framework with standardized templates”

🎭 211 个即插即用的 AI 专家角色 — 支持 Hermes Agent/Claude Code/Cursor/Copilot 等 16 种工具，覆盖工程/设计/营销/金融等 18 个部门。含 46 个中国市场原创智能体（小红书/抖音/微信/飞书/钉钉等）

Unique: Treats agent contribution as a structured, templated process rather than ad-hoc submissions. The framework lowers the barrier to entry for contributors while ensuring quality and consistency through automated validation and peer review.

vs others: More accessible than contributing to generic prompt repositories because templates guide contributors; more consistent than ad-hoc contributions because templates enforce structure; enables community-driven library growth.

via “community-contributed use-case curation”

The 500 AI Agents Projects is a curated collection of AI agent use cases across various industries. It showcases practical applications and provides links to open-source projects for implementation, illustrating how AI agents are transforming sectors such as healthcare, finance, education, retail, a

Unique: Uses GitHub's native PR workflow as the curation mechanism rather than a separate submission platform or database. This approach leverages GitHub's built-in review, discussion, and version control features, eliminating the need for custom infrastructure while maintaining community transparency through public PR history.

vs others: More transparent than closed-submission systems (all contributions are public and auditable); more scalable than manual email-based submissions; leverages GitHub's existing social features (stars, followers, notifications) for discoverability unlike custom submission portals.

via “community co-creation projects with collaborative agent development”

📚 《从零开始构建智能体》——从零开始的智能体原理与实践教程

Unique: Structures the project to enable community contributions of specialized agents while maintaining framework compatibility, creating a growing ecosystem of reusable implementations rather than a monolithic framework

vs others: More extensible than closed frameworks, but requires more coordination and quality control than single-vendor solutions; enables rapid growth through community contributions

via “multi-agent research coordination with chiefeditoragent orchestration”

An autonomous agent that conducts deep research on any data using any LLM providers

Unique: Implements explicit ChiefEditorAgent orchestration with specialized agent roles (Planner, Researcher, Curator, Writer) and review-revision workflows, rather than generic multi-agent frameworks. Includes quality threshold monitoring and automatic revision triggering.

vs others: More structured than generic AG2 because it defines specific agent roles and responsibilities, and more quality-focused than single-agent systems because it includes review-revision loops and consensus building.

162 production-ready AI agent templates for OpenClaw. SOUL.md configs across 19 categories. Submit yours!

Unique: Implements a community-driven curation model where agents are submitted via pull requests and reviewed for quality before merging, ensuring repository consistency and production-readiness. This contrasts with open template libraries that accept any submissions without review.

vs others: More curated than open-source template collections because submissions are reviewed; more accessible than proprietary template libraries because community can contribute agents.

via “content voting and moderation by agents”

fruitflies.ai is a social network built exclusively for AI agents. Connect via MCP to register (with proof-of-work challenge), post updates, ask and answer questions, vote on content, send threaded DMs, join topic communities ("hives"), volunteer to moderate, and climb the reputation leaderboard. Ag

Unique: Combines a voting system with a volunteer moderation framework, allowing agents to actively shape the community while ensuring content quality, unlike passive feedback systems.

vs others: More proactive than traditional feedback systems by enabling agents to directly influence content visibility and quality.

via “community-validated-paper-curation”

A collection of recent papers on building autonomous agent. Two topics included: RL-based / LLM-based agents.

Unique: Uses GitHub as the curation platform itself, enabling transparent, community-driven validation through pull requests and stars rather than relying on a single curator's judgment or algorithmic ranking

vs others: More transparent and community-driven than expert-curated lists but less rigorous than peer-reviewed venues; provides lower barrier to contribution than academic journals

via “contributing guide and community curation workflow”

A repo lists papers related to LLM based agent

Unique: Formalizes a community contribution workflow with documented guidelines rather than ad-hoc contributions, enabling sustainable growth and community-driven taxonomy evolution

vs others: More sustainable than single-maintainer repositories because it distributes curation effort across the community, though requires more governance overhead than centralized curation

via “community agent publishing and contribution workflow”

** - An Open Source registry of hosted MCP Servers to accelerate AI agent workflows.

Unique: Treats agents as first-class publishable artifacts with versioning and community contribution workflows, similar to npm packages or Docker images. This enables rapid agent ecosystem growth through community contributions and collaborative improvement.

vs others: More accessible than publishing agents as standalone projects or services, but requires mkinf's infrastructure and governance to function.

via “agent marketplace and sharing with version control and collaboration”

AIDE for creating, deploying, monetizing agents

via “community contribution and curation workflow”

Like Michelin Guide for AI

via “content curation and aggregation”

via “community-driven directory submission and curation”

Unique: Leverages GitHub's native pull request and review workflow as the entire contribution and quality-control system, eliminating need for custom submission forms or moderation dashboards. This approach makes contribution transparent and auditable through Git history while distributing review burden to maintainers without additional tooling.

vs others: More transparent and version-controlled than form-based submissions because all changes are tracked in Git history and reviewable, but requires higher technical literacy from contributors compared to web forms or email submissions.