Setting Up CreatorDB Agentic Skills

Documentation Index

Fetch the complete documentation index at: https://docs.creatordb.app/llms.txt

Use this file to discover all available pages before exploring further.

​

Introduction

​

Available CreatorDB skills

​

Skill descriptions and supported platforms

​

Skills and primary API endpoints they call

​

System requirements

• A valid CreatorDB API key. Contact sales@creatordb.app to obtain one.
• A code editor or terminal installed on your device, for example Visual Studio Code.
• A Claude account that is Pro tier or above that supports Claude Code. For details, see Claude Pricing Plans.
• Claude Code installed and set up on your device. For details, see Claude Code Docs.

​

Installing CreatorDB skills

mkdir -p ~/.claude/skills

for skill in creator-search creator-enrichment brand-sponsorship content-analysis account creator-csv-workflow; do
  mkdir -p ~/.claude/skills/$skill
  curl -s "https://docs.creatordb.app/.well-known/agent-skills/$skill/SKILL.md" \
    -o ~/.claude/skills/$skill/SKILL.md
done

ls -la ~/.claude/skills/*/SKILL.md

New-Item -ItemType Directory -Force -Path "$HOME\.claude\skills" | Out-Null

$skills = @(
    "creator-search", "creator-enrichment", "brand-sponsorship",
    "content-analysis", "account", "creator-csv-workflow"
)
foreach ($skill in $skills) {
    $dir = "$HOME\.claude\skills\$skill"
    New-Item -ItemType Directory -Force -Path $dir | Out-Null
    Invoke-WebRequest `
        -Uri "https://docs.creatordb.app/.well-known/agent-skills/$skill/SKILL.md" `
        -OutFile "$dir\SKILL.md"
}

Get-ChildItem "$HOME\.claude\skills\*\SKILL.md" |
    Select-Object @{n="Skill";e={$_.Directory.Name}}, Length

​

API key handling

1. When prompted, enter your CreatorDB API key. This key is used to authenticate your requests to the CreatorDB API.
2. Claude Code will store your API key securely in its environment variables for the duration of your session, so you won’t need to enter it again for subsequent queries.
3. If you need to update or change your API key, you can do so by updating the environment variable in your terminal or code editor where Claude Code is running. Run the appropriate command for your operating system to set the YOUR_API_KEY environment variable to your new API key:

export YOUR_API_KEY=your_new_api_key

$env: YOUR_API_KEY="your_new_api_key"

​

Verify installation in Claude Code

  What CreatorDB skills do you have available?

  I have six CreatorDB-related skills available:                                                
                                                                                                  
  - `creator-search — Find influencers and creators across YouTube, Instagram, and TikTok by       
  criteria like follower count, engagement rate, country, niche, or natural-language query.       
  - creator-enrichment — Enrich a known creator (channel ID, handle, or username) with profile    
  data, contact emails, audience demographics, performance metrics, recent content, and pricing   
  estimates.                                                                                      
  - brand-sponsorship — Brand-side intelligence: which creators a brand sponsors, which brands    
  sponsor a vertical, estimated total spend / CPM / CPE, sponsored-content benchmarks, audience   
  demographics of a brand's creator pool.
  - content-analysis — Pull a creator's published content (videos, posts, shorts), sponsored      
  placements, subtitles/transcripts, and CreatorDB's topic/niche taxonomy.                        
  - account — Check API credit usage, remaining quota, and per-endpoint consumption history for
  your CreatorDB API key.                                                                         
  - creator-csv-workflow — Orchestration skill: take a CSV/list of creators, enrich it via the
  other skills, and export an enriched CSV.                                                                                                         
                  
  This matches your doc's catalog (six listed there). Want me to run a free account-skill smoke   
  test next to verify the API-key flow end-to-end?

Check my CreatorDB account balance

​

Troubleshooting

1. Check API credentials: Ensure that your API key is correctly set up in your environment variables and that you have the necessary permissions to access the endpoints you’re trying to use.
2. Check for errors in the response: If you receive an error response from the API, review the error message for clues about what went wrong. Common issues include invalid parameters, rate limits, or missing data.
3. Contact support: If you’re still having trouble, reach out to CreatorDB support for assistance. Provide them with details about the issue, including any error messages and the steps you’ve taken to troubleshoot.

​

Common errors and solutions

1. SKILL.md is 0 bytes after curl.
   Cause: This may be caused by blocked curl, network proxy issues, wrong URL, or the .well-known path moved.
   Fix: Pull each skill from the CreatorDB document site again. If the issue persists, check your network connectivity to the https://docs.creatordb.app and check the path returns content via the browser.
2. Claude Code doesn’t recognize a skill.
   Cause: The skill files were not placed in the path ~/.claude/skills/{skill-name}/SKILL.md, or Claude Code was running during installation and did not rescan available skills.
   Fix: Verify the directory layout with -la ~/.claude/skills/*/SKILL.md , each row should be several kilobytes (KB), then exit and relaunch Claude Code.
3. 401 Unauthorized or “invalid API key” response.
   Cause: An invalid key response may be caused by typos, wrong API key, or the key was revoked.
   Fix: You can contact sales@creatordb.app to verify the key is still active. Also try reconfiguring the env var (export YOUR_API_KEY=...).
4. Claude Code keeps asking for the API key every session.
   Cause: The env var is not persisted.
   Fix: Add export YOUR_API_API_KEY=... to ~/.zshrc or ~/.bashrc (macOS/Linux), or add to user env var (Windows).

5. Claude routes to the wrong skill. For example, uses creator-search when the prompt is about a brand’s roster.
   Cause: Your prompt phrasing matches multiple skills descriptions.
   Fix: Explicitly name the skill in the prompt. For example, “use the brand-sponsorship skill to…”, or rephrase to use the canonical trigger words from the skill description.
6. Skill returns no results or empty list.
   Cause: Your filter criteria might be too narrow, the niche or category doesn’t exist in CreatorDB’s supported list, or the location filter doesn’t match.
   Fix: Relax your filter criteria or try a broader search and narrow down results. You can also ask Claude Code to list available filters (“show me what’s available”) before applying.
7. Subtitle endpoint returned nothing for a recent video.
   Cause: CreatorDB might now have the subtitles for that video yet, since it may take a few days for the system to obtain the subtitles.
   Fix: Try getting the subtitles of an older video first, or try again a few days later.
8. CSV save fails with permission denied.
   Cause: The working directory isn’t writable, or Claude Code lacks the file-system permission.
   Fix: Run Claude Code from a writable directory, for example your Desktop or project folder. Grant Claude Code disk access to your operating system’s settings.