# Contributing to Awesome OpenClaw

Thanks for helping improve **awesome-openclaw**.

This repository is a curated list of useful resources for the OpenClaw ecosystem. The bar here is not GitHub stars or broad OSS prestige; the main test is whether something is genuinely useful to OpenClaw users now.

---

## What Belongs Here

Good additions usually have all or most of the following:

- clear, direct OpenClaw relevance
- a working repository, website, or documentation page
- latest meaningful commit within the last **30 days**
- a specific, understandable purpose
- a natural fit in an existing README category

Examples:

- official OpenClaw resources
- skills, registries, and workflow packs
- dashboards, control centers, and alternative clients
- deployment tools and integrations
- high-signal tutorials, guides, and community resources

## What to Avoid

Please avoid adding:

- unrelated projects that only happen to mention `claw`
- generic AI tools with no meaningful OpenClaw connection
- duplicate entries already in the list
- obvious mirrors, low-value forks, or rename-lineage copies
- spammy directories or thin landing pages with little substance
- marketing-heavy descriptions or hype language

---

## Curation Rules

- Prefer the canonical repo over mirrors or duplicates.
- Keep descriptions short, factual, and neutral.
- Put each project in its strongest single category.
- If a project is already listed, improve the existing entry instead of duplicating it elsewhere.
- For code repositories, require a latest meaningful commit within the last **30 days**.
- Prefer quality over quantity.

## Entry Format

Use this format for GitHub repos:

```md
- [owner/repo](https://github.com/owner/repo) ![GitHub Repo stars](https://img.shields.io/github/stars/owner/repo?style=social) - Short factual description.
```

For non-GitHub official sites or docs, follow the local README style already used in that section.

Descriptions should be:

- one sentence
- factual
- easy to scan
- free of promotional wording

---

## How to Contribute

### Add a new resource

When suggesting a new entry, include:

- the repository or page link
- the best category for it
- a short factual description
- why it is relevant to OpenClaw

### Improve an existing entry

Useful improvements include:

- fixing categorization
- removing duplicates
- correcting broken links
- replacing a weaker mirror with the canonical source
- shortening descriptions
- improving consistency and formatting

---

## Pull Request Guidelines

Small focused pull requests are best.

Before opening a PR, check:

- the link works
- the project is actually relevant to OpenClaw
- the description is concise and neutral
- the entry is placed in the right section
- the same repo is not already listed elsewhere in the README

### Automation Note

- PRs authored by the trusted automation account `alvinreal` may be auto-merged **only** when they are README-only, non-structural, mechanically safe changes that pass all required checks.
- Community PRs are never auto-merged.
- Changes to `.moltfounders/` and other governance/process files never auto-merge.

### Mechanical-safe agent PRs

The unattended auto-merge path is intentionally narrow. It is limited to changes such as:

- broken-link fixes or removals
- deduplication or canonical-source replacement
- obvious category corrections
- official OpenClaw resource additions or updates

Third-party additions may still be valid, but they should generally wait for human review.

Thanks.