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

Clawver Print On Demand

by LeoYeAI in LeoYeAI/openclaw-master-skills

Sell print-on-demand merchandise on Clawver. An agent skill from LeoYeAI/openclaw-master-skills.

MITAuto-check passedBackend & APIs

Install Clawver Print On Demand

skills CLI
$ npx skills add LeoYeAI/openclaw-master-skills --skill clawver-print-on-demand -a claude-code

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

GitHub CLI
$ gh skill install LeoYeAI/openclaw-master-skills clawver-print-on-demand --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/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/clawver-print-on-demand .claude/skills/clawver-print-on-demand && 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
clawver-print-on-demand
GitHub stars
2.2k
Token cost
~4.6k tokens
SKILL.md length
1,324 words
Files
3 (incl. references)
Skills in repo
1,235
Repo updated
First seen
Licence
MIT

At a glance

Sell print-on-demand merchandise on Clawver. An agent skill from LeoYeAI/openclaw-master-skills.

  • Works in 4 steps: Create the Product (Draft) → (Optional, Highly Recommended): Upload… → (Optional, Recommended): Generate Seeded… → …
  • Selling physical products like posters
  • SKILL.md covers Recommended Agent Path:…, Prerequisites, How Print-on-Demand Works and Key Concepts (Read This First), plus 4 more sections
  • Calls curl and jq; reaches api.clawver.store; needs CLAW_API_KEY

What it does

Clawver Print On Demand is an agent skill from LeoYeAI/openclaw-master-skills. Sell print-on-demand merchandise on Clawver. Browse Printful catalog, create product variants, track fulfillment and shipping. Use when selling physical products like posters, t-shirts, mugs, or apparel.

Its SKILL.md is about 4.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `_meta.json` and `references/api-examples.md`).

It sits in Backend & APIs. It works with Laravel. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.

When your agent uses it

  • Selling physical products like posters

Example prompts

  • “/clawver-print-on-demand”

Requirements

  • A credential in CLAW_API_KEY

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Create the Product (Draft)
  2. (Optional, Highly Recommended): Upload POD Design File
  3. (Optional, Recommended): Generate Seeded AI Mockups
  4. Publish

What it can do on your machine

Read from SKILL.md and the folder at commit e5199b5. 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

    Shell commands in SKILL.md call:

    • curl
    • jq

    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:

    • api.clawver.store

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

  • Credentials

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

    • CLAW_API_KEY

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

Context cost

Clawver Print On Demand loads about 4.6k tokens when it runs, and up to ~5.1k if it reads all its reference files. Until then it costs about 57 tokens; SKILL.md has 1,324 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~57
When it runs · the whole SKILL.md, loaded when a task matches
~4.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.1k

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 passed

The automated check found no risky patterns in SKILL.md.

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 1,324 words, ~4,558 tokens.

Download SKILL.mdSave it as .claude/skills/clawver-print-on-demand/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
clawver-print-on-demand
description
Sell print-on-demand merchandise on Clawver. Browse Printful catalog, create product variants, track fulfillment and shipping. Use when selling physical products like posters, t-shirts, mugs, or apparel.
version
1.3.1
homepage
https://clawver.store

Clawver Print-on-Demand

Sell physical merchandise on Clawver using Printful integration. No inventory required—products are printed and shipped on demand when customers order.

If your goal is "make me a good POD product on Clawver," prefer the Product Artisan workflow before dropping to the raw POD endpoints below.

Use Product Artisan when you want the platform to handle:

  • brief clarification
  • product and blank selection
  • plan approval before credits are spent
  • automatic draft creation after plan approval
  • automatic design generation and mockup generation after plan approval
  • publish-ready proposal assembly
  • final publish confirmation

Core Artisan endpoints:

bash
# Start a new artisan session
curl -X POST https://api.clawver.store/v1/artisan/sessions \
  -H "Authorization: Bearer $CLAW_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "message": "Create a premium oversized vintage Japanese streetwear tee with a quiet front and statement back."
  }'
bash
# Approve the plan and let the automatic pipeline run
curl -X PATCH https://api.clawver.store/v1/artisan/sessions/{sessionId} \
  -H "Authorization: Bearer $CLAW_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "message": "Approve the plan and continue."
  }'
bash
# Stream active turn progress via SSE
curl -N \
  -H "Authorization: Bearer $CLAW_API_KEY" \
  -H "Accept: text/event-stream" \
  "https://api.clawver.store/v1/artisan/sessions/{sessionId}/events"

Structured fields to inspect:

  • awaitingDecision: current checkpoint (plan_approval, publish_confirmation)
  • agentGuidance: structured next-step hints
  • proposedPlan: machine-readable plan before approval
  • approvedPlan: plan after approval
  • activeStep: current server-side operation label while processing
  • mostRecentToolEvent: latest summarized tool result for progress UIs
SSE Event Reference

The /events endpoint emits the following Server-Sent Event types:

EventWhenPayload
session.snapshotFirst event after connectionFull ArtisanSessionResponse
session.stateSession state changed (new status, progress update, etc.)Full ArtisanSessionResponse
session.completeProcessing finished; session is waiting for input or terminal{ sessionId, status, awaitingDecision }
session.errorError or stream timeout{ code, message }

Important SSE notes:

  • The stream has a max duration of ~20 minutes. If you receive a STREAM_TIMEOUT error, reconnect or switch to polling.
  • Keep-alive comments (: keep-alive) are sent every 15 seconds. If you stop receiving them, the connection may have dropped.
  • After receiving session.complete, close your connection and inspect awaitingDecision to decide your next action.
Understanding Progress Fields

When status is "processing", inspect these response fields:

FieldExampleMeaning
currentOperation"design_generation"High-level operation category
progressStage"generating_design"Granular stage: starting, thinking, catalog_lookup, creating_product, generating_design, polling_design, generating_mockup
progressSubstep"waiting_for_image_provider"Human-readable sub-step within the stage
progressHint"Generating design…"Display-friendly message
estimatedWaitMs45000Estimated time for the current stage (design/mockup generation ~45s, catalog lookup ~12s, thinking ~8s)
estimatedCompletionAt"2025-..."ISO timestamp of estimated completion
retryAfterMs5000Suggested poll interval when not using SSE
awaitingDecision Values
ValueWhat to do
plan_approvalReview proposedPlan and send approval or revision
publish_confirmationConfirm publish to make the product live

When status is "processing", check pendingAwaitingDecision — it shows what decision will be required once processing completes.

Simple Artisan Flow
  1. Start the session with a concrete product brief.
  2. Wait for awaitingDecision = "plan_approval" and inspect proposedPlan.
  3. Approve the plan with a PATCH /v1/artisan/sessions/{sessionId} message. This automatically kicks off draft creation, design generation, mockup generation, and publish-ready proposal assembly.
  4. Wait for awaitingDecision = "publish_confirmation", review proposal.products[].designs for the mockup-backed draft, then publish only if the caller wants it live.
Session Lifecycle
  • sessionExpiresAt in every response shows when the session will expire (1 hour from last activity).
  • sessionTtlMs shows the TTL in milliseconds.
  • Expired sessions cannot be resumed; start a new session.
Simplified Publish Response

After publish, the response includes convenience fields:

  • productId: the published product ID
  • productUrl: direct link to the product (currently null; use proposal.products[0].productId to construct the URL)
  • mockupUrls: { "front": "https://...", "back": "https://..." } extracted from proposal.products[].designs

Operational advice for agent clients:

  • Prefer SSE during active turns; fall back to polling if SSE drops
  • Use retryAfterMs from the response as your poll interval (typically 5s)
  • In the standard happy path, there are only two explicit caller approvals: plan approval and publish confirmation
  • Plan approval is not just advisory; it starts the automatic production pipeline for the approved blank and variants
  • Check estimatedWaitMs for realistic wait time estimates per stage

Use the raw POD APIs below when you need manual control over catalog selection, design uploads, or custom fulfillment flows.

Prerequisites

  • CLAW_API_KEY environment variable
  • Stripe onboarding completed
  • High-resolution design files as HTTPS URLs or base64 data (the platform stores them — no external hosting required; optional but highly recommended)

For platform-specific good and bad API patterns from claw-social, use references/api-examples.md.

How Print-on-Demand Works

  1. You create a product with Printful product/variant IDs
  2. Customer purchases on your store
  3. Printful prints and ships directly to customer
  4. You keep the profit margin (your price - Printful base cost - 2% platform fee)

Key Concepts (Read This First)

Printful IDs Are Strings

printOnDemand.printfulProductId and printOnDemand.printfulVariantId must be strings (e.g. "1", "4013"), even though the Printful catalog returns numeric IDs.

Variants Are Required For Activation

When publishing a print_on_demand product (PATCH /v1/products/{id} {"status":"active"}), your product must have a non-empty printOnDemand.variants array configured.

You can sell POD products without uploading design files (legacy / external sync workflows), but uploading designs is highly recommended because it enables:

  • Attaching design files to orders (when configured)
  • Mockup generation for storefront images
  • Better operational reliability and fewer fulfillment surprises

If you want the platform to enforce design uploads before activation and at fulfillment time, set metadata.podDesignMode to "local_upload".

Show full SKILL.md (550 more words)Show less
Variant Strategy for Size Selection

When you sell multiple sizes, define one entry per size in printOnDemand.variants.

  • Each variant maps to a buyer-facing size option in the storefront.
  • Use explicit priceInCents per variant when size-based pricing differs.
  • Include optional fields when available: size, inStock, availabilityStatus.
  • Prefer buyer-friendly name values such as "Bella + Canvas 3001 / XL".
Pricing Behavior
  • Storefront, cart, and checkout use the selected variant's priceInCents when provided.
  • Legacy products with only printOnDemand.printfulVariantId fall back to product-level priceInCents.
Stock Visibility
  • Out-of-stock variants are disabled in the storefront size selector.
  • Out-of-stock variants (inStock: false) are rejected at checkout (HTTP 400).
  • Keep variant stock metadata updated (inStock, availabilityStatus) so buyer-facing availability remains accurate.

Browse the Printful Catalog

  1. List catalog products:
bash
curl "https://api.clawver.store/v1/products/printful/catalog?q=poster&limit=10" \
  -H "Authorization: Bearer $CLAW_API_KEY"
  1. Get variants for a Printful product:
bash
curl "https://api.clawver.store/v1/products/printful/catalog/1?inStock=true&limit=10" \
  -H "Authorization: Bearer $CLAW_API_KEY"

Create a POD Product

Step 1: Create the Product (Draft)
bash
curl -X POST https://api.clawver.store/v1/products \
  -H "Authorization: Bearer $CLAW_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "AI Studio Tee",
    "description": "Soft premium tee with AI-designed front print.",
    "type": "print_on_demand",
    "priceInCents": 2499,
    "images": ["https://your-storage.com/tee-preview.jpg"],
    "printOnDemand": {
      "printfulProductId": "71",
      "printfulVariantId": "4012",
      "variants": [
        {
          "id": "tee-s",
          "name": "Bella + Canvas 3001 / S",
          "priceInCents": 2499,
          "printfulVariantId": "4012",
          "size": "S",
          "inStock": true
        },
        {
          "id": "tee-m",
          "name": "Bella + Canvas 3001 / M",
          "priceInCents": 2499,
          "printfulVariantId": "4013",
          "size": "M",
          "inStock": true
        },
        {
          "id": "tee-xl",
          "name": "Bella + Canvas 3001 / XL",
          "priceInCents": 2899,
          "printfulVariantId": "4014",
          "size": "XL",
          "inStock": false,
          "availabilityStatus": "out_of_stock"
        }
      ]
    },
    "metadata": {
      "podDesignMode": "local_upload"
    }
  }'

Required for POD creation/publishing:

  • printOnDemand.printfulProductId (string)
  • printOnDemand.printfulVariantId (string)
  • printOnDemand.variants (must be non-empty to publish)

Optional but recommended:

  • metadata.podDesignMode: "local_upload" to enforce design uploads before activation and at fulfillment time

Before publishing, validate:

  • printOnDemand.variants is non-empty
  • each variant has a unique printfulVariantId
  • variant priceInCents aligns with your margin strategy
  • optional size is normalized (S, M, L, XL, etc.) when available
  • inStock is accurate per variant—out-of-stock variants are rejected at checkout

Upload one or more design files to the product. These can be used for previews and for fulfillment (depending on podDesignMode).

Option A: Upload from URL

bash
curl -X POST https://api.clawver.store/v1/products/{productId}/pod-designs \
  -H "Authorization: Bearer $CLAW_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "fileUrl": "https://your-storage.com/design.png",
    "fileType": "png",
    "placement": "default",
    "variantIds": ["4012", "4013", "4014"]
  }'

Option B: Upload base64 data

bash
curl -X POST https://api.clawver.store/v1/products/{productId}/pod-designs \
  -H "Authorization: Bearer $CLAW_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "fileData": "iVBORw0KGgoAAAANSUhEUgAA...",
    "fileType": "png",
    "placement": "default"
  }'

Notes:

  • placement is typically "default" unless you know the Printful placement name (e.g. front, back for apparel).
  • Use variantIds to map a design to specific variants (strings). If omitted, the platform will fall back to the first eligible design for fulfillment and previews.

Option C: Generate a design file with AI (credit-gated)

bash
curl -X POST https://api.clawver.store/v1/products/{productId}/pod-design-generations \
  -H "Authorization: Bearer $CLAW_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "prompt": "Minimal monochrome tiger head logo with bold clean lines",
    "placement": "front",
    "variantId": "4012",
    "idempotencyKey": "podgen-1"
  }'

curl https://api.clawver.store/v1/products/{productId}/pod-design-generations/{generationId} \
  -H "Authorization: Bearer $CLAW_API_KEY"

Use idempotencyKey for retry safety. Identical retries reuse the same generation task; conflicting payloads return validation errors.

Use the seeded AI flow so another agent can execute with consistent grounding:

  1. preflight to resolve compatible inputs,
  2. read data.recommendedRequest and reuse those exact values,
  3. call ai-mockups (which first generates a real Printful seed mockup),
  4. poll generation status,
  5. approve a candidate for storefront use.
bash
# 3a) Preflight and extract recommendedRequest
PREFLIGHT=$(curl -sS -X POST https://api.clawver.store/v1/products/{productId}/pod-designs/{designId}/mockup/preflight \
  -H "Authorization: Bearer $CLAW_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "variantId": "4012",
    "placement": "front"
  }')
echo "$PREFLIGHT" | jq '.data.recommendedRequest'
REC_VARIANT_ID=$(echo "$PREFLIGHT" | jq -r '.data.recommendedRequest.variantId')
REC_PLACEMENT=$(echo "$PREFLIGHT" | jq -r '.data.recommendedRequest.placement')
REC_TECHNIQUE=$(echo "$PREFLIGHT" | jq -r '.data.recommendedRequest.technique // empty')

# 3b) Generate seeded AI mockups
# Internal order of operations: Printful seed first, then GenAI candidates.
curl -X POST https://api.clawver.store/v1/products/{productId}/pod-designs/{designId}/ai-mockups \
  -H "Authorization: Bearer $CLAW_API_KEY" \
  -H "Content-Type: application/json" \
  -d "{
    \"variantId\": \"$REC_VARIANT_ID\",
    \"placement\": \"$REC_PLACEMENT\",
    \"idempotencyKey\": \"ai-mockup-1\",
    \"promptHints\": {
      \"printMethod\": \"$REC_TECHNIQUE\",
      \"safeZonePreset\": \"apparel_chest_standard\"
    }
  }"

# 3c) Poll generation status
curl https://api.clawver.store/v1/products/{productId}/pod-designs/{designId}/ai-mockups/{generationId} \
  -H "Authorization: Bearer $CLAW_API_KEY"

# 3d) Approve chosen candidate and persist product mockup
curl -X POST https://api.clawver.store/v1/products/{productId}/pod-designs/{designId}/ai-mockups/{generationId}/approve \
  -H "Authorization: Bearer $CLAW_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"candidateId":"cand_white","mode":"primary_and_append"}'

If you need a non-AI deterministic path, use the direct Printful task endpoints:

  • POST /v1/products/{productId}/pod-designs/{designId}/mockup-tasks
  • GET /v1/products/{productId}/pod-designs/{designId}/mockup-tasks/{taskId}
  • POST /v1/products/{productId}/pod-designs/{designId}/mockup-tasks/{taskId}/store

When calling mockup-tasks, pass the same REC_VARIANT_ID, REC_PLACEMENT, and REC_TECHNIQUE. If task creation or polling returns 429/RATE_LIMITED, retry with exponential backoff and jitter.

Step 4: Publish

Publishing requires a non-empty printOnDemand.variants array. If metadata.podDesignMode is "local_upload", you must upload at least one design before activating.

bash
curl -X PATCH https://api.clawver.store/v1/products/{productId} \
  -H "Authorization: Bearer $CLAW_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"status": "active"}'

Note: POD products must have printOnDemand.variants configured before activation.

Manage POD Designs

List Designs
bash
curl https://api.clawver.store/v1/products/{productId}/pod-designs \
  -H "Authorization: Bearer $CLAW_API_KEY"
Get a Signed Preview URL (Owner)
bash
curl https://api.clawver.store/v1/products/{productId}/pod-designs/{designId}/preview \
  -H "Authorization: Bearer $CLAW_API_KEY"
Public Preview (Active Products)

If the product is active, you can request a public preview (no API key). This will attempt to generate a Printful mockup and fall back to returning a signed source image URL if mockup generation fails.

bash
curl https://api.clawver.store/v1/products/{productId}/pod-designs/{designId}/public-preview
Update Design Metadata
bash
curl -X PATCH https://api.clawver.store/v1/products/{productId}/pod-designs/{designId} \
  -H "Authorization: Bearer $CLAW_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Front artwork v2",
    "placement": "default",
    "variantIds": ["4012", "4013", "4014"]
  }'
Archive a Design
bash
curl -X DELETE https://api.clawver.store/v1/products/{productId}/pod-designs/{designId} \
  -H "Authorization: Bearer $CLAW_API_KEY"

Track Fulfillment

Monitor Order Status
bash
curl "https://api.clawver.store/v1/orders?status=processing" \
  -H "Authorization: Bearer $CLAW_API_KEY"

POD order statuses:

  • confirmed - Payment confirmed (order status)
  • processing - Sent to Printful for production
  • shipped - In transit with tracking
  • delivered - Delivered to customer

paymentStatus is tracked separately (paid, partially_refunded, etc.).

Get Tracking Information
bash
curl https://api.clawver.store/v1/orders/{orderId} \
  -H "Authorization: Bearer $CLAW_API_KEY"

Response includes trackingUrl and trackingNumber when available.

Webhook for Shipping Updates
bash
curl -X POST https://api.clawver.store/v1/webhooks \
  -H "Authorization: Bearer $CLAW_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://your-server.com/webhook",
    "events": ["order.shipped"],
    "secret": "your-secret-min-16-chars"
  }'

© LeoYeAI, 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 2 other files (references) in skills/clawver-print-on-demand of LeoYeAI/openclaw-master-skills.

  • SKILL.md
  • _meta.json
  • references/api-examples.md

Open the folder on GitHubat commit e5199b5

Compare with similar skills

Clawver Print On Demand 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.

Clawver Print On Demand compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Clawver Print On Demand this skillLeoYeAI/openclaw-master-skills2.2k—~4.6kAutomated safety check: PassMIT
Configuring Horizoncoollabsio/coolify63k4 repos~898Automated safety check: PassMIT
Fortify Developmentcoollabsio/coolify63k4 repos~1.9kAutomated safety check: PassMIT
Laravel Best Practicesanonaddy/anonaddy4.9k13 repos~1.2kAutomated safety check: PassMIT
Laravel Actionscoollabsio/coolify63k—~2.4kAutomated safety check: PassApache-2.0
Infer Conventionsanonaddy/anonaddy4.9k5 repos~3.1kAutomated safety check: PassMIT

Similar skills

  • Configuring Horizon

    coollabsio/coolify

    A skill your agent uses whenever the user mentions Horizon by name in a Laravel context.

    63k GitHub starsUsed in 4 repos~898 tokens
    Backend & APIsAuto-check passed

  • Fortify Development

    coollabsio/coolify

    ACTIVATE when the user works on authentication in Laravel. An agent skill from coollabsio/coolify.

    63k GitHub starsUsed in 4 repos~1.9k tokens
    Backend & APIsAuto-check passed

  • Laravel Best Practices

    anonaddy/anonaddy

    Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code.

    4.9k GitHub starsUsed in 13 repos~1.2k tokens
    Backend & APIsAuto-check passed

  • Laravel Actions

    coollabsio/coolify

    Build, refactor, and troubleshoot Laravel Actions using lorisleiva/laravel-actions.

    63k GitHub stars~2.4k tokensUpdated yesterday
    Backend & APIsAuto-check passed

  • Infer Conventions

    anonaddy/anonaddy

    A skill your agent uses to analyze how a Laravel application is actually written and record its conventions as shared rules.

    4.9k GitHub starsUsed in 5 repos~3.1k tokens
    Backend & APIsAuto-check passed

  • Geoflow

    yaojingang/GEOFlow

    Operate/develop GEOFlow CLI/Laravel/admin/API, topics/专题 and topic tasks, theme libraries/replication, sites/leads/Agent, channel sync and legacy yao-geoflow-cli/design/template migration.

    3.8k GitHub stars~722 tokensUpdated today
    Backend & APIsAuto-check passed

More from LeoYeAI/openclaw-master-skills

All 1,200 skills in this repo

  • DevOps Pipeline Management

    LeoYeAI/openclaw-master-skills

    Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.

    2.2k GitHub stars~4.2k tokensUpdated 2 mo ago
    Auto-check: notes

  • Feishu Document Collaboration

    LeoYeAI/openclaw-master-skills

    Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.

    2.2k GitHub stars~2k tokensUpdated 2 mo ago
    Auto-check passed

  • Files Memory System

    LeoYeAI/openclaw-master-skills

    Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.

    2.2k GitHub stars~3.8k tokensUpdated 2 mo ago
    Auto-check passed

  • GEO-Claw AI Visibility Agent

    LeoYeAI/openclaw-master-skills

    Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.

    2.2k GitHub stars~4.7k tokensUpdated 2 mo ago
    Auto-check passed

  • Google Workspace CLI

    LeoYeAI/openclaw-master-skills

    Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.

    2.2k GitHub stars~2.6k tokensUpdated 2 mo ago
    Auto-check: notes

  • HealthFit Health Advisors

    LeoYeAI/openclaw-master-skills

    Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.

    2.2k GitHub stars~4.4k tokensUpdated 2 mo ago
    Auto-check passed

Works with

Categories

Questions about Clawver Print On Demand

What does Clawver Print On Demand do?

Sell print-on-demand merchandise on Clawver. An agent skill from LeoYeAI/openclaw-master-skills. Clawver Print On Demand is an agent skill from LeoYeAI/openclaw-master-skills. Sell print-on-demand merchandise on Clawver.

When should I use Clawver Print On Demand?

Clawver Print On Demand fits situations like: selling physical products like posters.

How do I install Clawver Print On Demand in Claude Code?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill clawver-print-on-demand -a claude-code`. Or copy the skill folder (skills/clawver-print-on-demand in LeoYeAI/openclaw-master-skills) into .claude/skills/clawver-print-on-demand in your project. Claude Code loads it when a task matches its description.

How do I install Clawver Print On Demand in Codex?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill clawver-print-on-demand -a codex`. Or copy the skill folder (skills/clawver-print-on-demand in LeoYeAI/openclaw-master-skills) into .agents/skills/clawver-print-on-demand in your project. Codex loads it when a task matches its description.

Can I use Clawver Print On Demand 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 LeoYeAI/openclaw-master-skills --skill clawver-print-on-demand -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/clawver-print-on-demand, .gemini/skills/clawver-print-on-demand, .github/skills/clawver-print-on-demand and .opencode/skills/clawver-print-on-demand in your project.

What does Clawver Print On Demand need to run?

Going by SKILL.md and its folder, Clawver Print On Demand needs the command-line tools its instructions call (curl and jq) and credentials named CLAW_API_KEY. Our summary lists: A credential in CLAW_API_KEY.

Does Clawver Print On Demand access the network?

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

Is Clawver Print On Demand safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Clawver Print On Demand use?

Clawver Print On Demand is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Clawver Print On Demand use?

About 4.6k tokens (SKILL.md is roughly 18k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 517 tokens, read only when the agent opens those files.

What are the alternatives to Clawver Print On Demand?

Skills that share tags, products or a category with Clawver Print On Demand: Configuring Horizon (coollabsio/coolify, 63k stars), Fortify Development (coollabsio/coolify, 63k stars), Laravel Best Practices (anonaddy/anonaddy, 4.9k stars) and Laravel Actions (coollabsio/coolify, 63k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Clawver Print On Demand?

LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,161 GitHub stars. The repository holds 1,235 skills in this directory. The repository was last updated on July 20, 2026.

Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.