New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Klaviyo Developer

by thatrebeccarae in thatrebeccarae/claude-marketing

Klaviyo API and developer integration expertise. An agent skill from thatrebeccarae/claude-marketing.

MITAuto-check: notesBackend & APIs

Install Klaviyo Developer

skills CLI
$ npx skills add thatrebeccarae/claude-marketing --skill klaviyo-developer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install thatrebeccarae/claude-marketing klaviyo-developer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/thatrebeccarae/claude-marketing.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/klaviyo-developer .claude/skills/klaviyo-developer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
klaviyo-developer
GitHub stars
162
Token cost
~4.9k tokens
SKILL.md length
2,104 words
Files
8 (incl. scripts)
Skills in repo
55
Repo updated
First seen
Licence
MIT

At a glance

Klaviyo API and developer integration expertise. An agent skill from thatrebeccarae/claude-marketing.

  • Works in 10 steps: API key management — Store private keys… → Revision header — Always include… → Rate limit handling — Implement… → …
  • The user asks about Klaviyo API
  • SKILL.md covers Install, MCP vs. SDK: When to Use Which, Core Capabilities and SDK Quick Reference, plus 10 more sections
  • Runs Python scripts from its folder; calls python, pip and git; reaches mcp.klaviyo.com; needs KLAVIYO_API_KEY

What it does

Klaviyo Developer is an agent skill from thatrebeccarae/claude-marketing. Klaviyo API and developer integration expertise. Event tracking, SDKs, webhooks, rate limits, OAuth, catalog sync, and code patterns. Use when the user asks about Klaviyo API, integrating with Klaviyo, tracking events, building custom integrations, webhook handling, or developer implementation. For marketing strategy, flow optimization, and campaign auditing, see the klaviyo-analyst skill.

Its SKILL.md is about 4.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including scripts (for example `EXAMPLES.md`, `REFERENCE.md` and `scripts/dev_tools.py`).

It sits in Backend & APIs, covering Email marketing, Webhooks and Product analytics. It works with Model Context Protocol. The repository describes itself as: A full marketing department for Claude Code. Skill packs for Klaviyo, Shopify, GA4, Looker Studio, paid media, and more. Audit, optimize, and report using natural language. The licence is MIT.

When your agent uses it

  • The user asks about Klaviyo API
  • Integrating with Klaviyo
  • Tracking events
  • Building custom integrations

Example prompts

  • “/klaviyo-developer”

Requirements

  • Python 3
  • Node.js

Workflow steps

10 steps, taken from the first numbered list in SKILL.md.

  1. API key management — Store private keys in environment variables, never commit to source. Rotate keys periodically.
  2. Revision header — Always include revision: YYYY-MM-DD header. Pin to a specific version.
  3. Rate limit handling — Implement exponential backoff with jitter on 429 responses.
  4. Idempotent events — Include a unique unique_id property to prevent duplicate event tracking.
  5. Profile upserts — Use POST /profiles/ with existing identifier for upsert behavior (creates or updates).
  6. Webhook verification — Validate webhook signatures before processing payloads.
  7. Pagination — Use cursor-based pagination for list endpoints. Never assume result counts.
  8. Error handling — Parse JSON:API error responses. Handle 4xx (client) and 5xx (server) differently.
  9. SDK initialization — Configure SDK with API key at app startup, not per-request.
  10. Testing — Use Klaviyo test/sandbox accounts. Mock API responses in unit tests.

What it can do on your machine

Read from SKILL.md and the folder at commit a8a63ec. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 2 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python
    • pip
    • git
    • npm
    • gem
    • composer

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • mcp.klaviyo.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • KLAVIYO_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Klaviyo Developer loads about 4.9k tokens when it runs. Until then it costs about 103 tokens; SKILL.md has 2,104 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~103
When it runs · the whole SKILL.md, loaded when a task matches
~4.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:350
    set as an environment variable or in a `.env` file
  • NoteMentions a .env fileSKILL.md:372
    Store keys in environment variables or `.env` files
  • NoteMentions a .env fileSKILL.md:373
    - Add `.env` to `.gitignore`

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from thatrebeccarae/claude-marketing at commit a8a63ec, republished under its MIT licence (© thatrebeccarae). 2,104 words, ~4,915 tokens.

Download SKILL.mdSave it as .claude/skills/klaviyo-developer/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
klaviyo-developer
description
Klaviyo API and developer integration expertise. Event tracking, SDKs, webhooks, rate limits, OAuth, catalog sync, and code patterns. Use when the user asks about Klaviyo API, integrating with Klaviyo, tracking events, building custom integrations, webhook handling, or developer implementation. For marketing strategy, flow optimization, and campaign auditing, see the klaviyo-analyst skill.
license
MIT
origin
custom
author
Rebecca Rae Barton
author_url
https://github.com/thatrebeccarae
metadata.version
1.1.0
metadata.category
email-lifecycle
metadata.domain
klaviyo
metadata.updated
2026-05-14
metadata.tested
2026-05-14
metadata.tested_with
Claude Code v2.1, Klaviyo MCP API revision 2026-04-15

Klaviyo Developer

Expert-level guidance for building with the Klaviyo API — custom event tracking, profile management, SDK integration, webhooks, catalog sync, and data pipeline architecture.

For marketing strategy, flow auditing, segmentation, deliverability, and campaign optimization, see the klaviyo-analyst skill.

Install

bash
git clone https://github.com/thatrebeccarae/claude-marketing.git && cp -r claude-marketing/skills/klaviyo-developer ~/.claude/skills/

MCP vs. SDK: When to Use Which

This skill is SDK-first by design — you're building production integrations against the Klaviyo API, not running ad-hoc queries. That said, Klaviyo's official MCP server is the right tool for parts of integration work, and you should know when to reach for it.

Use the SDK (klaviyo-api) when…Use the MCP (https://mcp.klaviyo.com/mcp) when…
Writing production event-tracking codeExploring an account's event schema before writing the integration
Building bulk import / sync pipelinesSanity-checking that events landed with the right property shape
Implementing webhook handlersPulling a quick property inventory during integration design
Catalog sync jobsInspecting flow trigger conditions while debugging why an event isn't firing a flow
Anything in CI, cron, or a deployed serviceIterating on event schema design with the marketing analyst in the room

The MCP wraps the same API this skill targets, so the schema rules, rate limits, and nesting constraints below apply equally to MCP-driven calls. The MCP is currently pinned to API revision 2026-04-15 — keep that in mind if you're versioning your own SDK code against an older revision.

For the full MCP tool inventory, OAuth setup, and read-only mode flag, see REFERENCE.md. For audit/analyst work, see the klaviyo-analyst skill — it's built around the MCP.

Core Capabilities

API Authentication & Versioning
  • Private API key setup and key management best practices
  • Public API key usage for client-side tracking (klaviyo.js)
  • OAuth 2.0 authorization flow for third-party apps
  • API revision headers and version lifecycle management
Custom Event Tracking
  • Server-side event tracking via Events API
  • Client-side tracking with klaviyo.js
  • Event schema design and property naming conventions
  • Idempotent event submission patterns
Profile Management
  • Profile create, upsert, and bulk import patterns
  • Custom property management and data types
  • Subscription management (email, SMS consent)
  • Profile merge and deduplication strategies
Webhooks
  • Webhook subscription setup and event types
  • Payload verification and signature validation
  • Retry handling and idempotent webhook processing
SDK Usage & Libraries
  • Python SDK (klaviyo-api)
  • Node.js SDK (klaviyo-api-node)
  • Ruby, PHP, and other community SDKs
  • SDK initialization, error handling, and retry configuration
Catalog & Product Feed Sync
  • Catalog item create/update/delete via API
  • Category and variant management
  • Product feed sync architecture for recommendations
  • Handling large catalogs with bulk operations
Data Export & Warehouse Sync
  • Metric aggregation API for reporting
  • Profile and event export patterns
  • Cursor-based pagination for large datasets
  • ETL pipeline design for data warehouse integration

SDK Quick Reference

LanguagePackageInstall
Pythonklaviyo-apipip install klaviyo-api
Node.jsklaviyo-apinpm install klaviyo-api
Rubyklaviyo-api-sdkgem install klaviyo-api-sdk
PHPklaviyo/apicomposer require klaviyo/api

Rate Limits

Endpoint CategoryLimitWindow
Most endpoints75 requestsper second
Bulk imports10 requestsper second
Profile/Event create350 requestsper second
Campaign send10 requestsper second

Headers returned: RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset

API Revision Timeline

RevisionKey Changes
2026-01-15Latest. Custom Objects Ingestion, Geofencing API (beta).
2025-10-15Forms API, Flow Actions API, SMS ROI reporting.
2025-07-15Mapped Metrics API, Custom Objects API (GA).
2025-04-15Web Feeds API, Custom Metrics, Push Token registration.
2025-01-15Reviews APIs, Flows Create API, Campaign image management.
2024-10-15Universal Content API, Form/Segment Reporting, Reviews API.
2024-07-15Forms API (retrieval), Webhooks API.
2024-02-15Reporting API, Create or Update Profile (upsert).

Always include the revision header in API requests.

Essential Developer Checklist

  1. API key management — Store private keys in environment variables, never commit to source. Rotate keys periodically.
  2. Revision header — Always include revision: YYYY-MM-DD header. Pin to a specific version.
  3. Rate limit handling — Implement exponential backoff with jitter on 429 responses.
  4. Idempotent events — Include a unique unique_id property to prevent duplicate event tracking.
  5. Profile upserts — Use POST /profiles/ with existing identifier for upsert behavior (creates or updates).
  6. Webhook verification — Validate webhook signatures before processing payloads.
  7. Pagination — Use cursor-based pagination for list endpoints. Never assume result counts.
  8. Error handling — Parse JSON:API error responses. Handle 4xx (client) and 5xx (server) differently.
  9. SDK initialization — Configure SDK with API key at app startup, not per-request.
  10. Testing — Use Klaviyo test/sandbox accounts. Mock API responses in unit tests.

Workflow: Custom Integration Setup

When building a custom Klaviyo integration:

  1. Define requirements — What events to track, what profile data to sync, what triggers are needed
  2. API key provisioning — Create a private API key with minimum required scopes
  3. Event schema design — Map business events to Klaviyo metric names and properties
  4. Profile sync strategy — Determine identifier (email vs phone vs external_id), upsert frequency
  5. Implement tracking — Server-side event tracking with proper error handling and retries
  6. Catalog sync (if applicable) — Product feed sync for recommendations and browse abandonment
  7. Webhook setup — Subscribe to relevant events, implement handler with signature verification
  8. Rate limit strategy — Queue and throttle API calls, implement backoff
  9. Monitoring — Log API errors, track event delivery rates, alert on failures
  10. Testing & validation — Verify events appear in Klaviyo, test flow triggers, validate profile data

Workflow: Integration Health Audit

When auditing an existing Klaviyo integration for health and data quality:

  1. Inventory active integrations — List all configured integrations (built-in and custom). Identify active vs stale connections.
  2. Map event sources — For each metric in the account, identify its source (built-in integration, custom API, Klaviyo-internal, form). Flag metrics with zero recent volume.
  3. Audit event schemas — Pull property structures for key events (Placed Order, Started Checkout, Viewed Product, Added to Cart). Check for:
    • Missing standard properties (e.g., $value, ItemNames, line items)
    • Duplicate/redundant metrics (e.g., "Placed Order" and "Order Placed" from different sources)
    • Inconsistent property naming (camelCase vs snake_case across events)
  4. Check profile data pipeline — Verify profile properties are being synced correctly. Look for:
    • Properties set by API vs properties set by events
    • Stale properties (set once, never updated)
    • Properties used in segmentation vs properties sitting unused
  5. Review catalog sync — Verify product catalog is synced and fresh. Check:
    • Total catalog items vs expected product count
    • Last sync timestamp
    • Variant coverage (are variants synced or just parent products?)
    • Category structure completeness
  6. Assess flow trigger architecture — Map how flows are triggered:
    • Direct metric triggers (robust) vs segment-entry triggers via API-synced properties (brittle)
    • Single points of failure (if API sync breaks, do all flows stop?)
    • Trigger redundancy and fallback patterns
  7. Identify data accessibility gaps — Check for data that exists in event payloads but isn't usable:
    • Nested objects in event properties (can use in templates, cannot use in segments/splits)
    • Properties available in events but not synced to profiles (can't segment on them)
    • Events tracked but not used in any flow or segment
  8. Produce integration health report — Document findings with severity ratings:
    • Critical: Integration failures, broken event tracking, data loss
    • High: Missing standard events, duplicate metrics, flow trigger fragility
    • Medium: Unused events, incomplete catalog, stale profile properties
    • Low: Naming inconsistencies, optimization opportunities

Event Schema Best Practices

Property Naming Conventions
  • Use PascalCase for standard Klaviyo properties: ProductName, ItemPrice, OrderId
  • Use snake_case for custom properties: business_type, account_id, reorder_count
  • Never mix conventions within a single event — pick one and be consistent
  • Prefix custom properties to avoid collision with Klaviyo-reserved names
Required Properties by Event
EventRequired PropertiesRevenue Property
Placed Order$value, OrderId, Items[] (line items)$value
Started Checkout$value, CheckoutURL, Items[]$value
Viewed ProductProductName, ProductID, URL, ImageURL—
Added to Cart$value, AddedItemProductName, AddedItemProductID, Items[]$value
Fulfilled Order$value, OrderId—
Show full SKILL.md (879 more words)Show less
Nesting Rules and Limitations

Klaviyo handles nested objects differently depending on where you access them:

ContextAccess LevelExample
Email/SMS templatesFull access via Jinja — can loop over arrays, access nested properties{% for item in event.Items %}{{ item.ProductName }}{% endfor %}
Flow conditional splitsTop-level properties ONLY — cannot access nested object fieldsCan split on event.OrderId, cannot split on event.Items[0].ProductName
SegmentsTop-level properties ONLY — cannot filter by nested object fieldsCan segment on "has done Placed Order where $value > 100", cannot segment on "where Items contains ProductName = X"
Flow triggersTop-level properties for trigger filtersSame as conditional splits

Workaround for nested data: If you need to segment or split on nested data, flatten it to top-level properties:

python
# Instead of relying on Items[] array for segmentation:
properties = {
    "$value": 149.99,
    "OrderId": "ORD-123",
    "Items": [{"ProductName": "Wireless Headphones", "Category": "Electronics"}],
    # Flatten for segmentation:
    "ItemCategories": "Electronics,Accessories",  # Comma-joined for "contains" filter
    "HasElectronics": True,                        # Boolean flag for split
    "TopItemCategory": "Electronics"               # Top category for split
}
Custom Event Patterns (DTC / Subscription / Marketplace)

Additional events beyond the standard Shopify/e-commerce schema:

Event NameTriggerKey Properties
Account CreatedNew account registeredaccount_type, referral_source, signup_channel
Subscription StartedRecurring order activated$value, frequency, product_ids, plan_name
Subscription CancelledRecurring order stoppedreason, plan_name, lifetime_charges
Reorder PlacedRepeat purchase of consumable$value, OrderId, days_since_last_order, reorder_items
Wishlist AddedItem saved for laterProductName, ProductID, Categories, Price
Catalog BrowsedCategory/search activitycategory, search_term, results_count

Sync key customer properties to profiles for segmentation:

python
profile_properties = {
    "customer_type": "Subscriber",
    "interests": ["Skincare", "Wellness"],
    "subscription_plan": "Monthly Box",
    "account_tier": "VIP",
    "first_order_date": "2024-03-15",
    "lifetime_order_count": 8,
    "avg_order_value": 72.50,
    "preferred_categories": ["Skincare", "Supplements"]
}

Data Accessibility Diagnosis

When data exists in Klaviyo but isn't usable where expected:

Symptoms
  • "We track [event] but can't segment on [property]"
  • "Flow split doesn't see the property we're sending"
  • "Profile has the data but segment doesn't pick it up"
Root Causes and Solutions
SymptomRoot CauseSolution
Can't segment on event propertyProperty is nested inside an array/objectFlatten to top-level property on the event
Can't split flow on event propertyProperty is nestedFlatten, or use profile property instead
Segment doesn't match profilesProperty is on events, not profilesSync property to profile via API or "Update Profile Property" flow action
Profile property exists but segment emptyProperty value format mismatch (string "true" vs boolean true)Standardize data types in API sync
Event tracked but no flow triggersMetric name mismatch (case-sensitive)Verify exact metric name in Klaviyo matches API call
Flow triggers but filter excludes everyoneSegment used as flow filter evaluates incorrectlyCheck segment conditions — may reference stale or incorrectly-typed properties
Diagnosis Workflow
  1. Check metric exists: Use GET /metrics/ to verify the event name appears
  2. Check event properties: Use GET /events/?filter=... to pull recent events and inspect property structure
  3. Check profile properties: Use GET /profiles/{id}/ to verify expected properties are on the profile
  4. Test segment conditions: Compare segment definition against actual profile data — look for type mismatches, case sensitivity issues
  5. Test flow trigger: Send a test event and trace whether the flow fires, where it stops, and why

How to Use This Skill

Ask me questions like:

  • "How do I track a custom event from my Node.js backend?"
  • "Help me set up a bulk profile import script"
  • "What are Klaviyo's rate limits and how should I handle them?"
  • "How do I verify Klaviyo webhook signatures?"
  • "Set up catalog sync for my custom e-commerce platform"
  • "How do I implement OAuth for a Klaviyo app?"
  • "Design a data pipeline to export Klaviyo data to BigQuery"
  • "Help me migrate from Klaviyo v1/v2 API to the current API"
  • "Audit my integration — are events structured correctly?"
  • "Why can't I segment on a property I'm tracking in events?"

Integration Examples

For complete integration patterns, worked examples with sample output, and code snippets, see EXAMPLES.md.

Scripts

The skill includes utility scripts for API interaction and integration management:

Developer Client
bash
# Track a custom event
python scripts/klaviyo_client.py --action track-event \
    --email user@example.com --event "Placed Order" \
    --properties '{"value": 99.99, "OrderId": "ORD-123"}'

# Upsert a profile
python scripts/klaviyo_client.py --action upsert-profile \
    --email user@example.com \
    --properties '{"first_name": "Jane", "loyalty_tier": "Gold"}'

# List catalog items
python scripts/klaviyo_client.py --action catalog-items --format table

# Export profiles to CSV
python scripts/klaviyo_client.py --action export-profiles \
    --max-pages 10 --format csv --output profiles.csv
Developer Tools
bash
# Integration health check
python scripts/dev_tools.py --tool health-check

# Validate event tracking
python scripts/dev_tools.py --tool validate-events \
    --events "Placed Order,Started Checkout,Viewed Product"

# Test webhook endpoint
python scripts/dev_tools.py --tool test-webhook \
    --webhook-url https://example.com/webhooks/klaviyo

# Import profiles from CSV
python scripts/dev_tools.py --tool import-csv \
    --file contacts.csv --list-id LIST_ID

# Export data with pagination
python scripts/dev_tools.py --tool export-data \
    --resource profiles --max-records 5000 --output profiles.csv

The scripts handle API authentication, rate limiting, and JSON:API formatting. I'll help interpret results and provide implementation guidance.

Troubleshooting

Authentication Error: Verify that:

  • KLAVIYO_API_KEY is set as an environment variable or in a .env file
  • The key starts with pk_ (private API key, not public)
  • The key has the required scopes for your operation (e.g., events:write for tracking, profiles:write for imports)

Rate Limit Errors (429): The SDK handles retries automatically (up to 3 retries with 60s max delay). If you still hit limits:

  • Queue and throttle bulk operations (max 10 req/s for imports)
  • Check RateLimit-Remaining header proactively
  • Implement exponential backoff with jitter for raw HTTP

Bulk Import Errors: Check that:

  • Batch size does not exceed 10,000 profiles per job
  • Email or phone is provided for each profile (at least one identifier)
  • CSV column names match expected field names

Import Errors: Install required packages:

bash
pip install klaviyo-api python-dotenv pandas

Security Notes

  • Never hardcode API keys in code or commit them to version control
  • Store keys in environment variables or .env files
  • Add .env to .gitignore
  • Use minimum required scopes — only enable write access where needed
  • Rotate API keys periodically in Klaviyo Settings
  • For OAuth integrations, store client secrets securely and refresh tokens before expiry

Data Privacy

This skill interacts with the Klaviyo API for integration development. When using write operations:

  • Validate data before sending to avoid corrupting profile records
  • Never log or store API keys, webhook secrets, or PII in plain text
  • Use idempotency keys to prevent duplicate events
  • Implement webhook signature verification to prevent spoofing
  • Follow GDPR/CCPA requirements when handling profile data
  • Use the Data Privacy Deletion endpoint for right-to-erasure requests

All operations are performed via the official Klaviyo API with proper authentication.

For detailed API endpoint reference, code patterns, authentication, and architecture diagrams, see REFERENCE.md.

For marketing strategy, flow optimization, and campaign auditing, use the klaviyo-analyst skill.

© thatrebeccarae, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 7 other files (scripts) in skills/klaviyo-developer of thatrebeccarae/claude-marketing.

  • SKILL.md
  • .env.example
  • EXAMPLES.md
  • LICENSE
  • REFERENCE.md
  • requirements.txt
  • scripts/dev_tools.py
  • scripts/klaviyo_client.py

Open the folder on GitHubat commit a8a63ec

Compare with similar skills

Klaviyo Developer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Klaviyo Developer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Klaviyo Developer this skillthatrebeccarae/claude-marketing162—~4.9kAutomated safety check: NotesMIT
Neon Functionsneondatabase/agent-skills100—~12kAutomated safety check: NotesApache-2.0
Databuddydatabuddy-analytics/Databuddy1.2k—~2.1kAutomated safety check: PassAGPL-3.0
X Twitter ScraperXquik-dev/x-twitter-scraper2101 repos~2.6kAutomated safety check: PassMIT
API Patternsdilolabs/nosia2131 repos~2.5kAutomated safety check: PassMIT
Zalo AgentPhucMPham/zalo-agent-cli164—~2.3kAutomated safety check: PassMIT

Similar skills

  • Neon Functions

    neondatabase/agent-skills

    Official

    Long-running, serverless Node.js HTTP functions deployed onto your Neon branch, with DATABASEURL injected automatically and compute that runs next to your data.

    100 GitHub stars~12k tokensUpdated today
    Backend & APIsAuto-check: notes

  • Databuddy

    databuddy-analytics/Databuddy

    Integrate Databuddy analytics using the SDK, REST API, or MCP.

    1.2k GitHub stars~2.1k tokensUpdated today
    Backend & APIsAuto-check passed

  • X Twitter Scraper

    Xquik-dev/x-twitter-scraper

    Use Xquik to fetch X (Twitter) data or act through a connected account: search, profiles, followers, replies, threads, timelines, media downloads, bulk exports, trends, monitors, signed webhooks…

    210 GitHub starsUsed in 1 repo~2.6k tokens
    Backend & APIsAuto-check passed

  • API Patterns

    dilolabs/nosia

    Builds REST APIs using respondto blocks with Jbuilder templates following the 37signals same-controllers-different-formats philosophy.

    213 GitHub starsUsed in 1 repo~2.5k tokens
    Backend & APIsAuto-check passed

  • Zalo Agent

    PhucMPham/zalo-agent-cli

    Automate Zalo messaging, Official Account (OA), and MCP server integration via zalo-agent-cli.

    164 GitHub stars~2.3k tokensUpdated 1 mo ago
    Backend & APIsAuto-check passed

  • Xquik

    understudy-ai/understudy

    Use Xquik REST and MCP APIs for X data workflows: search public posts, inspect users, export datasets, download media, monitor accounts or keywords, and send webhook events.

    462 GitHub stars~1k tokensUpdated 3 mo ago
    Backend & APIsAuto-check passed

More from thatrebeccarae/claude-marketing

All 55 skills in this repo

  • Google Analytics

    thatrebeccarae/claude-marketing

    Analyze Google Analytics data, review website performance metrics, identify traffic patterns, and suggest data-driven improvements.

    162 GitHub starsUsed in 3 repos~1.3k tokens
    Auto-check: notes

  • Content Creator

    thatrebeccarae/claude-marketing

    Comprehensive content marketing toolkit with brand voice analysis, SEO optimization scripts, content frameworks, social media strategy, and content calendar planning.

    162 GitHub stars~1.1k tokensUpdated 4 mo ago
    Auto-check passed

  • Klaviyo Analyst

    thatrebeccarae/claude-marketing

    Klaviyo marketing operations and analyst expertise. An agent skill from thatrebeccarae/claude-marketing.

    162 GitHub stars~5k tokensUpdated 4 mo ago
    Auto-check: notes

  • Looker Studio

    thatrebeccarae/claude-marketing

    Looker Studio (formerly Google Data Studio) expertise. An agent skill from thatrebeccarae/claude-marketing.

    162 GitHub stars~3.6k tokensUpdated 4 mo ago
    Auto-check: notes

  • Shopify

    thatrebeccarae/claude-marketing

    Shopify e-commerce platform marketing expertise. An agent skill from thatrebeccarae/claude-marketing.

    162 GitHub stars~2.4k tokensUpdated 4 mo ago
    Auto-check: notes

  • Ab Testing Framework

    thatrebeccarae/claude-marketing

    A/B and multivariate testing methodology. An agent skill from thatrebeccarae/claude-marketing.

    162 GitHub stars~1.3k tokensUpdated 4 mo ago
    Auto-check passed

Works with

Categories

Questions about Klaviyo Developer

What does Klaviyo Developer do?

Klaviyo API and developer integration expertise. An agent skill from thatrebeccarae/claude-marketing. Klaviyo Developer is an agent skill from thatrebeccarae/claude-marketing. Klaviyo API and developer integration expertise.

When should I use Klaviyo Developer?

Klaviyo Developer fits situations like: the user asks about Klaviyo API; integrating with Klaviyo; tracking events; building custom integrations.

How do I install Klaviyo Developer in Claude Code?

Run `npx skills add thatrebeccarae/claude-marketing --skill klaviyo-developer -a claude-code`. Or copy the skill folder (skills/klaviyo-developer in thatrebeccarae/claude-marketing) into .claude/skills/klaviyo-developer in your project. Claude Code loads it when a task matches its description.

How do I install Klaviyo Developer in Codex?

Run `npx skills add thatrebeccarae/claude-marketing --skill klaviyo-developer -a codex`. Or copy the skill folder (skills/klaviyo-developer in thatrebeccarae/claude-marketing) into .agents/skills/klaviyo-developer in your project. Codex loads it when a task matches its description.

Can I use Klaviyo Developer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add thatrebeccarae/claude-marketing --skill klaviyo-developer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/klaviyo-developer, .gemini/skills/klaviyo-developer, .github/skills/klaviyo-developer and .opencode/skills/klaviyo-developer in your project.

What does Klaviyo Developer need to run?

Going by SKILL.md and its folder, Klaviyo Developer needs Python for the scripts in its folder, the command-line tools its instructions call (python, pip, git, npm, gem and composer) and credentials named KLAVIYO_API_KEY. Our summary lists: Python 3; Node.js.

Does Klaviyo Developer access the network?

SKILL.md names 1 domain. In commands or code: mcp.klaviyo.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Klaviyo Developer safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Klaviyo Developer use?

Klaviyo Developer is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Klaviyo Developer use?

About 4.9k tokens (SKILL.md is roughly 20k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Klaviyo Developer?

Skills that share tags, products or a category with Klaviyo Developer: Neon Functions (neondatabase/agent-skills, 100 stars), Databuddy (databuddy-analytics/Databuddy, 1.2k stars), X Twitter Scraper (Xquik-dev/x-twitter-scraper, 210 stars) and API Patterns (dilolabs/nosia, 213 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Klaviyo Developer?

thatrebeccarae (a GitHub user) maintains it in thatrebeccarae/claude-marketing, which has 162 GitHub stars. The repository holds 55 skills in this directory. The repository was last updated on May 14, 2026.

Source: thatrebeccarae/claude-marketing on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.