Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
| 1 | # AGENTS.md |
| 2 | |
| 3 | Python provider guidance. |
| 4 | |
| 5 | ## Scope |
| 6 | |
| 7 | Each child directory is a Python provider package that adapts Composio to a framework or agent runtime. |
| 8 | |
| 9 | ## Skill Routing |
| 10 | |
| 11 | Use `python-providers` for provider implementation and `python-testing` for nox/pytest verification. Use `cross-sdk-parity` when the provider mirrors a TypeScript package. |
| 12 | |
| 13 | ## Commands |
| 14 | |
| 15 | Run from `python/`: |
| 16 | |
| 17 | ```bash |
| 18 | make create-provider name=<provider-name> |
| 19 | make create-provider name=<provider-name> agentic=true |
| 20 | make chk |
| 21 | make tst |
| 22 | make type_inference |
| 23 | ``` |
| 24 | |
| 25 | ## Rules |
| 26 | |
| 27 | - Keep provider dependencies in the provider package metadata unless shared tooling needs them. |
| 28 | - Preserve Python naming conventions and public import paths. |
| 29 | - Add provider tests and type-inference coverage when public return types change. |
| 30 | - New providers or renamed provider packages usually need explicit entries in `python/noxfile.py`'s `type_inference` install list and checked-file list. |
| 31 | - Verify package metadata before release-facing changes. |