Click to enlarge Provider runtime overview
The Provider keeps auth, Context, typed domain operations, thin Skill adapters, and downstream execution inside one explicit boundary.
Integrations start with providers.
Providers are AtlasClaw's integration boundary. Each Provider packages target-system metadata, configuration and auth contracts, reusable domain operations, thin Skills, optional page Context, and the references needed to keep enterprise AI integrations understandable.
Runtime architecture
See how a provider carries runtime execution.
This diagram shows how a Provider carries configuration schema, auth and Context, reusable domain code, thin Skills, and downstream execution.
Click to enlarge Provider runtime overview
Close preview The Provider keeps auth, Context, typed domain operations, thin Skill adapters, and downstream execution inside one explicit boundary.
Package structure
Provider package shape.
providers/<provider-name>/
├── PROVIDER.md
├── provider.schema.json
├── README.md
├── pyproject.toml # optional importable package
├── assets/ # optional static assets
├── src/<provider_package>/ # optional reusable domain code
├── assistant_context/ # optional page Context
└── skills/
├── <skill-a>/
│ ├── SKILL.md
│ ├── scripts/
│ └── references/
└── <skill-b>/ Key rules
Keep boundaries explicit and adapters thin.
- The provider owns how AtlasClaw identity becomes provider-native target-system auth.
- Reusable authentication, API, typed model, and business operations belong in the importable Provider package.
- Skills stay human-readable and thin while binding to explicit `file.py:callable` entrypoints.
- Optional `assistant_context` routes resolve the current enterprise-system page without accepting business DTOs from the host.
- Provider-qualified naming avoids collisions across integrations.
- Callable results may carry small trace-bound continuation metadata, while public evidence remains visible to the Agent and user.
Naming
Provider-qualified skills.
Provider prefixes prevent skill collisions across systems.
{
"providers_root": "../atlasclaw-providers/providers",
"webhook": {
"systems": [
{
"allowed_skills": ["jira:jira-issue"]
}
]
}
} Examples