Build a trusted, community-driven repository of reusable OpenClaw agents and sub-agents that is easy to contribute to, easy to validate, and reliable to use.
- Fit for purpose: strong templates, validators, and behavioral testing framework are in place.
- Fit for use: onboarding and contribution docs are solid; governance baseline and security disclosure path are now in place.
- Immediate focus: preserve CI quality signal while making contribution pathways clearer for new contributors.
Governance baseline setup.Complexity: S. Owner: Maintainers. ✅ Complete.Security disclosure path publication.Complexity: S. Owner: Maintainers. ✅ Complete.Secrets hygiene hardening in ignore rules and docs.Complexity: S. Owner: Maintainers. ✅ Complete.- First contribution checklist in contributor docs. Complexity: S. Owner: Docs.
- Coverage gap index for missing tests and fixtures. Complexity: M. Owner: Community.
- Dependency graph visualization generation. Complexity: M. Owner: Community.
- Behavioral test expansion for featured agents and core sub-agents. Complexity: M. Owner: Community.
- Pytest CI enforcement as required PR check. Complexity: M. Owner: Maintainers.
- Release and versioning guide publication. Complexity: S. Owner: Docs.
- Troubleshooting and FAQ docs rollout. Complexity: S. Owner: Docs.
- Searchable static agent registry. Complexity: L. Owner: Community.
- Executable eval harness for selected fixtures. Complexity: L. Owner: Maintainers.
- Automated changelog pipeline from metadata and PRs. Complexity: M. Owner: Community.
- RFC process for major schema and architecture changes. Complexity: M. Owner: Maintainers.
- Add one golden behavioral test for an uncovered sub-agent. Complexity: S. Owner: Community.
- Improve one template section with clearer examples and validation tips. Complexity: S. Owner: Docs.
- Add one FAQ entry from a recurring issue. Complexity: S. Owner: Docs.
- Add one missing cross-link between an agent README and required sub-agent README. Complexity: S. Owner: Community.
- Keep branch protections aligned with required CI checks.
- Triage new issues within 72 hours.
- Publish monthly roadmap updates and completion recap.
- Track contribution health metrics and onboarding bottlenecks.
- At least 90 percent of active agents have one executable behavioral test within two release cycles.
- Median time-to-first-response on community PRs is under 3 days.
- Monthly CI success rate stays above 98 percent.
- Community contributions close at least 20 percent of roadmap items each quarter.
- Documentation issue volume trends downward after FAQ and troubleshooting rollout.