Skip to content

Latest commit

 

History

History
44 lines (30 loc) · 1.45 KB

File metadata and controls

44 lines (30 loc) · 1.45 KB

Contributing

Thanks for helping improve this list.

Additions

Please submit a PR with:

  • Repository link.
  • Short description (what it does and why it matters).
  • Which section it belongs in.
  • Evidence of relevance to OpenClaw/Moltbot/Clawdbot.
  • Linked issue (use the "Add Resource Request" template before opening the PR).

Formatting Rules (Required)

  • Keep entries in strict A-Z order within each section.
  • Keep each entry to a single bullet line (no wrapped sub-bullets for descriptions).
  • Use this format: - [name](url) - short description.
  • Add status markers only when applicable: 🎖️ for official resources and 💵 for paid services.
  • For GitHub repository links, append stars badge: ![GitHub stars](https://img.shields.io/github/stars/owner/repo?style=social).

Commit and PR Conventions

  • Use semantic commit prefixes: feat:, fix:, docs:, chore:, refactor:, test:, ci:.
  • Keep commit messages scoped and specific (example: feat(readme): add memory plugin integrations).
  • PR title should also follow semantic format.
  • Link the issue in your PR body (example: Closes #123).

Quality Bar

Prefer projects that are:

  • Directly relevant to OpenClaw ecosystem usage.
  • Maintained (recent activity, responses, or updates).
  • Practical (docs, examples, active users, or integrations).

Cleanup

You can also submit PRs for:

  • Dead links.
  • Archived/unmaintained projects that should be removed.
  • Better categorization.