tessl-labs/good-oss-citizen

Rules and skills that teach AI agents how to contribute to open source projects without being the villain.

3.55x

Quality

91%

Does it follow best practices?

Impact

96%

3.55x

Average score across 20 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Preflight — Research References

Name: tessl-labs/good-oss-citizen
Rating: 95.54 (1 reviews)
Author: tessl-labs

Each preflight check is grounded in documented failure modes from real OSS projects. Findings live in the tile's research notes.

Check	Finding
1: AI disclosure	Finding 5 — AI policy is local and varies widely
2: Diff size and focus	Finding 4 — Accepted contributions are scoped, explicit, and test-backed, Finding 16 — The asymmetric effort problem is the root economic failure
3: PR template compliance	Finding 1 — Repo-local process is the real contract
4: Style and convention compliance	Finding 9 — Code convention files are part of the contract
5: Tests and CI	Finding 4 — Accepted contributions are scoped, explicit, and test-backed
7: Legal requirements (DCO/CLA)	Finding 10 — DCO/CLA requirements are a hard boundary the agent must not cross
8: Agent artifact cleanup	Finding 13 — Agent metafiles must never leak into contributions, Finding 15 — Security-aware code generation is a specific responsibility
9: Slop detector patterns	Finding 12 — Slop detection tools exist and the agent should know how to not trigger them
10: Human ownership verification	Finding 6 — "AI wrote it" is not enough by itself, Finding 7 — Trust starts before the pull request