Contribution standards
- Be clear about what it does. Describe the agent or skill’s purpose, the actions it can take, and the environment it expects.
- Scope permissions tightly. A skill should request only the actions it needs. Prefer read and investigation actions; gate state-changing ones.
- Version your changes. Publish updates as new versions so adopters can review what changed.
- Keep it honest. Document limitations and assumptions. Do not overstate what an agent can guarantee.
Using community contributions
- Review a shared skill’s declared actions and permissions before you run it.
- Start in a low-autonomy mode and raise it as you build trust.
- Report issues so the author and the community can improve the library.