create-provider skill
✓ VerifiedCreate new AtlasClaw providers with structured documentation, directory layouts, and executable skills for external system integrations.
- GitHub stars
- 17
- Files
- 2
- Last commit
- Nov 2, 2026
- License
- Apache-2.0
- Allowed tools
- —
What does the create-provider skill do?
create-provider creates new AtlasClaw providers with structured documentation, directory layouts, and executable skills for external system integrations.
Summary generated from the skill's SKILL.md.
About the create-provider skill
Building integrations for external systems like APIs, ITSM, or CRM platforms is what this skill facilitates for developers working within the AtlasClaw ecosystem. It provides a structured framework to generate new providers, complete with necessary directory layouts, documentation templates, and executable skills. By following a standardized process, developers can ensure that new integrations include the required PROVIDER.md and SKILL.md files needed for proper LLM context and skill discovery.
An agent should load this skill when it needs to expand its capabilities to interact with third-party services. The process involves gathering requirements such as authentication methods and base URL patterns, then creating a specific directory structure under the providers folder. The output includes a configured provider directory containing Python-based handlers, metadata for the AI to understand when to use specific tools, and the necessary entries for the atlasclaw.json configuration file.
What an agent can do with it
- 1Integrate an ITSM systemCreate a new provider to manage incidents and tickets in a service like ServiceNow.
- 2Set up monitoring capabilitiesDevelop a provider that allows an agent to query metrics and alerts from Datadog.
- 3Automate version control tasksBuild a provider to manage repositories and pull requests through GitHub.
- 4Establish CRM connectivityGenerate a provider to handle leads and accounts within Salesforce.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the create-provider skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the create-provider skill in Claude Code
~/.claude/skills/create-provider/SKILL.md
$ npx degit CloudChef/atlasclaw-providers/skills/create-atlasclaw-provider ~/.claude/skills/create-providerInstall the create-provider skill in Claude Code (project)
.claude/skills/create-provider/SKILL.md
$ npx degit CloudChef/atlasclaw-providers/skills/create-atlasclaw-provider .claude/skills/create-providerInstall the create-provider skill in Codex
~/.agents/skills/create-provider/SKILL.md
$ npx degit CloudChef/atlasclaw-providers/skills/create-atlasclaw-provider ~/.agents/skills/create-providerInstall the create-provider skill in Gemini CLI
~/.gemini/skills/create-provider/SKILL.md
$ npx degit CloudChef/atlasclaw-providers/skills/create-atlasclaw-provider ~/.gemini/skills/create-providerInstall the create-provider skill in Claude.ai
npx degit CloudChef/atlasclaw-providers/skills/create-atlasclaw-provider create-provider && zip -r create-provider.zip create-provider # claude.ai → Customize → Skills → + → Create skill → Upload a skill → create-provider.zip
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the scripts before you let an agent run them. How checks work · What to fix for more points
- Source repository linked and reachablecloudchef/atlasclaw-providers/skills/create-atlasclaw-provider is public and reachablegithub.com/cloudchef/atlasclaw-providers/tree/HEAD/skills/cr ↗Pass
- Open source license (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Pass
- Commit or release in the last yearLast commit 2026-11-02github.com/cloudchef/atlasclaw-providers/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/cloudchef/atlasclaw-providers/blob/HEAD/skills/cr ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/cloudchef/atlasclaw-providers/blob/HEAD/skills/cr ↗Pass
- SKILL.md follows the Agent Skills formatname "create-provider" differs from the folder "create-atlasclaw-provider"github.com/cloudchef/atlasclaw-providers/blob/HEAD/skills/cr ↗Finding
SKILL.md
View on GitHubCreate AtlasClaw Provider
Guide for creating new providers that integrate external systems with the AtlasClaw AI Agent.
Quick Start Checklist
Provider Creation Progress:
- [ ] 1. Gather requirements (system type, auth method, capabilities)
- [ ] 2. Create provider directory structure
- [ ] 3. Write PROVIDER.md with LLM context fields
- [ ] 4. Create skills for each capability
- [ ] 5. Add configuration to atlasclaw.json
- [ ] 6. Test provider loading and skill execution
Phase 1: Gather Requirements
Before creating a provider, determine:
| Question | Example Answer |
|---|---|
| Provider type | servicenow, github, datadog |
| Display name | ServiceNow, GitHub, Datadog |
| Authentication method | Basic Auth, API Token, OAuth 2.0, Cookie |
| Base URL pattern | https://instance.service-now.com |
| Key capabilities | CRUD incidents, manage users, query metrics |
| Target keywords | incident, ticket, alert, deployment |
Phase 2: Directory Structure
Create provider at: {workspace}/providers/{provider-name}/
providers/{provider-name}/
├── PROVIDER.md # Required - provider metadata and documentation
├── README.md # Optional - human documentation
├── skills/ # Required - at least one skill
│ └── {skill-name}/
│ ├── SKILL.md # Required - skill metadata
│ └── scripts/ # Required for executable skills
│ └── handler.py
└── references/ # Optional - API docs, mappings
└── api_mapping.md
Phase 3: PROVIDER.md Template
---
# === Required Fields ===
provider_type: {provider-name} # Must match directory name
display_name: {Display Name}
version: "1.0.0"
# === LLM Context Fields (for Skill Discovery) ===
keywords:
- keyword1 # Domain-specific terms users might say
- keyword2
- keyword3
capabilities:
- Capability description 1
- Capability description 2
use_when:
- User intent scenario 1
- User intent scenario 2
avoid_when:
- Scenario when other provider is better (suggest alternative)
---
# {Display Name} Provider
Brief description of what this provider integrates with.
## Connection Parameters
| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `base_url` | string | Yes | API base URL |
| `username` | string | Conditional | Username for auth |
| `password` | string | Conditional | Password or token |
| `api_key` | string | Conditional | API key if applicable |
## Authentication Modes
| Mode | Parameters | Notes |
|------|------------|-------|
| Basic Auth | `username` + `password` | Standard HTTP Basic |
| API Token | `api_key` | Bearer token auth |
## Configuration Example
```json
{
"service_providers": {
"{provider-name}": {
"default": {
"base_url": "${PROVIDER_URL}",
"api_key": "${PROVIDER_API_KEY}"
}
}
}
}
Environment Variables
PROVIDER_URL=https://api.example.com
PROVIDER_API_KEY=your-api-key
Provided Skills
| Skill | Description |
|---|---|
{provider}-{action} |
Brief description |
## Phase 4: SKILL.md Template
```yaml
---
name: "{provider}-{action}"
description: "Brief description. Trigger when user wants to {action}."
category: "provider:{provider-name}"
provider_type: "{provider-name}"
instance_required: "true"
# === LLM Context Fields ===
triggers:
- action phrase 1
- action phrase 2
use_when:
- User intent scenario 1
- User intent scenario 2
avoid_when:
- Scenario when other skill is better
examples:
- "Example user input 1"
- "Example user input 2"
related:
- related-skill-1
- related-skill-2
# === Tool Registration ===
tool_name: "{provider}_{action}"
tool_entrypoint: "scripts/handler.py:handler"
---
# {provider}-{action}
## Purpose
What this skill does and when to use it.
## Parameters
| Name | Type | Required | Description |
|------|------|----------|-------------|
| param1 | string | Yes | Description |
| param2 | integer | No | Description (default: 10) |
## Usage Examples
**Example 1**: Basic usage
```bash
python scripts/handler.py --param1 "value"
Error Handling
| Error | Cause | Resolution |
|---|---|---|
| AUTH_FAILED | Invalid credentials | Check API key |
## Phase 5: Handler Template
Create `scripts/handler.py`:
```python
# -*- coding: utf-8 -*-
"""
{Skill Name} Handler
Implements the {action} functionality for {Provider} provider.
"""
from __future__ import annotations
import argparse
import json
import os
import sys
from typing import Any, Optional
import requests
def get_provider_config() -> dict[str, Any]:
"""Load provider configuration from atlasclaw.json."""
config_path = os.environ.get("ATLASCLAW_CONFIG", "atlasclaw.json")
with open(config_path, "r", encoding="utf-8") as f:
config = json.load(f)
provider_config = config.get("service_providers", {}).get("{provider-name}", {})
instance = os.environ.get("PROVIDER_INSTANCE", "default")
return provider_config.get(instance, {})
def handler(params: dict[str, Any]) -> dict[str, Any]:
"""
Main handler function.
Args:
params: Input parameters
Returns:
Result dictionary with success, message, and data
"""
config = get_provider_config()
base_url = config.get("base_url", "").rstrip("/")
api_key = config.get("api_key", "")
headers = {
"Authorization": f"Bearer {api_key}",
"Content-Type": "application/json"
}
try:
# Implement API call here
response = requests.get(
f"{base_url}/api/endpoint",
headers=headers,
timeout=30
)
response.raise_for_status()
return {
"success": True,
"message": "Operation completed successfully",
"data": response.json()
}
except requests.RequestException as e:
return {
"success": False,
"message": f"API request failed: {str(e)}",
"error": {"code": "API_ERROR", "details": str(e)}
}
def main():
"""CLI entry point."""
parser = argparse.ArgumentParser(description="{Skill description}")
parser.add_argument("--param1", required=True, help="Parameter 1")
parser.add_argument("--param2", type=int, default=10, help="Parameter 2")
args = parser.parse_args()
result = handler({
"param1": args.param1,
"param2": args.param2
})
print(json.dumps(result, indent=2))
sys.exit(0 if result["success"] else 1)
if __name__ == "__main__":
main()
Phase 6: Configuration
Add to atlasclaw.json:
{
"service_providers": {
"{provider-name}": {
"default": {
"base_url": "${PROVIDER_URL}",
"api_key": "${PROVIDER_API_KEY}"
},
"production": {
"base_url": "${PROVIDER_PROD_URL}",
"api_key": "${PROVIDER_PROD_API_KEY}"
}
}
}
}
Add to .env:
PROVIDER_URL=https://api.example.com
PROVIDER_API_KEY=your-api-key
Phase 7: Verification
- Restart service (or wait for hot reload)
- Check logs for provider loading:
[AtlasClaw] Provider loaded: {provider-name} [AtlasClaw] Skills loaded: X from {provider-name} - Test via API:
curl http://localhost:8000/api/skills | grep {provider-name}
LLM Context Best Practices
Keywords
- Use domain-specific terms users naturally say
- Avoid generic terms like "create", "update", "manage"
- Include abbreviations and synonyms
use_when
- Describe user intent, not technical actions
- Focus on business scenarios
- Include common phrasings
avoid_when
- Critical for disambiguation between similar providers
- Always suggest the correct alternative
- Include commonly confused scenarios
Common Provider Types
| Type | Examples | Typical Keywords |
|---|---|---|
| ITSM | ServiceNow, Jira | incident, ticket, issue, sprint |
| Monitoring | Datadog, Prometheus | alert, metric, dashboard |
| Communication | Slack, Teams | message, channel, notification |
| Version Control | GitHub, GitLab | repository, PR, merge, commit |
| CRM | Salesforce | lead, opportunity, account |
| Cloud | AWS, Azure | instance, resource, deployment |
Additional Resources
- PROVIDER_GUIDE.md - Full documentation
- SKILL_GUIDE.md - Skill development guide
- Jira Provider - Reference implementation
Files in this skill
2create-provider skill questions
How do I install the create-provider skill in Claude Code?
Run npx degit CloudChef/atlasclaw-providers/skills/create-atlasclaw-provider ~/.claude/skills/create-provider. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the create-provider skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
How do I configure authentication for a new provider?
Authentication can be configured via the PROVIDER.md template and atlasclaw.json, supporting modes like Basic Auth (username/password) or API Token (api_key).