Skip to content
Back to skills

Keitaro Setup

ASecurity

Keitaro API connection setup and verification. Configures KEITARO_URL and KEITARO_API_KEY, tests connection, shows tracker status. Use when user says "setup", "connect", "configure keitaro", "API key", or first-time setup.

  • 23 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added May 26, 2026
securitypythonshellbashapisecurity

Works with

  • claude code
  • api

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add iso73-ops/claude-keitaro --skill keitaro-setup --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Keitaro Setup?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Keitaro Setup
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/iso73-ops-keitaro-setup/badge)](https://www.skillsdirectory.com/skills/iso73-ops-keitaro-setup)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: keitaro-setup
description: >
  Keitaro API connection setup and verification. Configures KEITARO_URL and
  KEITARO_API_KEY, tests connection, shows tracker status. Use when user says
  "setup", "connect", "configure keitaro", "API key", or first-time setup.
---

# Keitaro Setup

## Process

1. Ask user for their Keitaro tracker URL (e.g. https://tracker.example.com)
2. Ask for API key (found in Account → API keys in Keitaro dashboard)
3. Test connection by calling `GET /campaigns` via the API helper
4. If successful, show tracker status (number of campaigns, domains, etc.)
5. Save config for session

## Connection Test

Run the API helper to verify connection:

```bash
KEITARO_URL="<user-url>" KEITARO_API_KEY="<user-key>" \
  python3 ~/.claude/skills/keitaro/scripts/keitaro_api.py test
```

## Expected Output on Success

```
Connection successful!
Tracker: https://tracker.example.com
Campaigns: 15 active, 3 archived
Domains: 5 active
Offers: 23 active
```

## If Connection Fails

Common issues:
1. **401 Unauthorized** — wrong API key. Check Account → API keys
2. **Connection refused** — wrong URL or tracker is down
3. **SSL error** — tracker uses self-signed cert or HTTP instead of HTTPS
4. **404** — URL path is wrong, ensure no trailing slash

## Environment Variables

After successful connection, remind user to set in their shell profile:

```bash
export KEITARO_URL="https://tracker.example.com"
export KEITARO_API_KEY="your-api-key-here"
```

Or in Claude Code settings for persistent use across sessions.

## Security Note

- Never display the full API key — show only first 4 and last 4 characters
- Never commit API keys to files
- Recommend using environment variables, not hardcoded values

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.