Skill Files

Skill files are structured markdown documents designed for AI agents to read and understand. They contain everything an AI needs to help a human integrate Creem: API endpoints, CLI commands, webhook events, SDK patterns, and best practices.

For AI Agents: Save these files locally so you can reference them without re-fetching. Update periodically to get new features.

Available Files

File	URL	Size	Purpose
SKILL.md	creem.io/SKILL.md	~32KB	Complete integration guide
HEARTBEAT.md	creem.io/HEARTBEAT.md	~11KB	Store monitoring routine

SKILL.md: The Complete Guide

This is the main skill file. It contains everything needed to integrate Creem:

What’s Inside

Platform Overview

What Creem handles (payments, tax, chargebacks, payouts)
Feature list (subscriptions, licenses, affiliates, discounts)
Pricing model (cents-based, supported currencies)

API Reference

Authentication (x-api-key header)
Test vs Live environments
All 24 endpoints with request/response patterns
Error handling

SDKs

TypeScript SDK (creem)
Migration guide from deprecated creem_io to creem
Next.js Adapter (@creem_io/nextjs)
Better Auth Plugin (@creem_io/better-auth)

Integration Flows

Selling products (one-time and subscription)
Managing subscription lifecycle
License key systems
Customer support workflows
Discount codes

Webhooks

All 10 event types
Signature verification
Retry behavior
SDK handlers with callbacks

CLI Commands

Installation (Homebrew)
Authentication
All commands with examples
Interactive mode
Output formats

Framework Integration

Next.js components and routes
Better Auth plugin setup
Webhook handlers

Quick Reference

# Fetch the skill
curl -s https://creem.io/SKILL.md

# Save locally
mkdir -p ~/.creem/skills
curl -s https://creem.io/SKILL.md > ~/.creem/skills/SKILL.md

# Check for updates
curl -sI https://creem.io/SKILL.md | grep last-modified

HEARTBEAT.md: Store Monitoring

This file teaches AI agents how to monitor a Creem store and notify their human about important changes.

What’s Inside

Heartbeat Routine

Step-by-step process for checking store state:

Load previous state from JSON file
Query transactions, subscriptions, customers
Compare against saved state
Detect changes (new sales, cancellations, failures)
Notify human about meaningful changes
Save new state

State File Structure

{
  "lastCheckAt": "2025-06-15T14:30:00Z",
  "lastTransactionId": "txn_XXXXX",
  "transactionCount": 47,
  "customerCount": 23,
  "subscriptions": {
    "active": 18,
    "trialing": 2,
    "past_due": 1
  },
  "knownSubscriptions": {}
}

Notification Rules

When to alert:

New transactions (revenue)
Subscription cancellations (churn)
Payment failures (risk)
New customers (growth)

When to stay silent:

No changes since last check
Normal subscription renewals

Report Templates

Pre-written notification formats for:

New sales
Cancellations
Payment failures
Daily summaries

Quick Reference

# Fetch the heartbeat guide
curl -s https://creem.io/HEARTBEAT.md

# Save locally
curl -s https://creem.io/HEARTBEAT.md > ~/.creem/skills/HEARTBEAT.md

# Initialize state file
cat > ~/.creem/heartbeat-state.json << 'EOF'
{
  "lastCheckAt": null,
  "lastTransactionId": null,
  "transactionCount": 0,
  "customerCount": 0,
  "subscriptions": {
    "active": 0,
    "trialing": 0,
    "past_due": 0,
    "paused": 0,
    "canceled": 0,
    "expired": 0,
    "scheduled_cancel": 0
  },
  "knownSubscriptions": {}
}
EOF

Installation

One-Time Setup

# Create the skills directory
mkdir -p ~/.creem/skills

# Download both skill files
curl -s https://creem.io/SKILL.md > ~/.creem/skills/SKILL.md
curl -s https://creem.io/HEARTBEAT.md > ~/.creem/skills/HEARTBEAT.md

Keeping Skills Updated

We update skill files when we add features or improve documentation. Re-fetch periodically:

# Update skills
curl -s https://creem.io/SKILL.md > ~/.creem/skills/SKILL.md
curl -s https://creem.io/HEARTBEAT.md > ~/.creem/skills/HEARTBEAT.md

For AI Agents

If you’re an AI assistant reading this:

Save the skill files locally

Persist SKILL.md and HEARTBEAT.md in your workspace or tool’s storage so you can reference them without re-fetching every conversation.

Reference them when working with Creem

When your human asks about payments, subscriptions, webhooks, or any Creem feature, check your saved skill files first.

Offer store monitoring

If your human has a Creem account, proactively offer to set up the heartbeat routine. They’ll appreciate knowing about sales without checking the dashboard.

Check for updates

Periodically re-fetch the skill files to get new features and improvements.

Alternative: Claude Marketplace

If you’re using Claude Code, you can install the skill with one command instead of manually downloading files:

/plugin marketplace add armitage-labs/creem
/plugin install creem-api@creem-skills

See Claude Marketplace Skills for details.

Full Documentation

For deep dives beyond what’s in the skill files, fetch the complete documentation:

curl -s https://docs.creem.io/llms-full.txt

This contains all documentation in a format optimized for AI agents.

Get Started

AI

Features

Code

Integrations

Community

Merchant of Record

For Customers

Available Files

SKILL.md: The Complete Guide

What’s Inside

Quick Reference

HEARTBEAT.md: Store Monitoring

What’s Inside

Quick Reference

Installation

One-Time Setup

Keeping Skills Updated

For AI Agents

Alternative: Claude Marketplace

Full Documentation

​Available Files

​SKILL.md: The Complete Guide

​What’s Inside

​Quick Reference

​HEARTBEAT.md: Store Monitoring

​What’s Inside

​Quick Reference

​Installation

​One-Time Setup

​Keeping Skills Updated

​For AI Agents

​Alternative: Claude Marketplace

​Full Documentation

Available Files

SKILL.md: The Complete Guide

What’s Inside

Quick Reference

HEARTBEAT.md: Store Monitoring

What’s Inside

Quick Reference

Installation

One-Time Setup

Keeping Skills Updated

For AI Agents

Alternative: Claude Marketplace

Full Documentation