Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub · Content Creation
Clawver Print On Demand
Sell print-on-demand merchandise on Clawver. Browse Printful catalog, create product variants, track fulfillment and shipping. Use when selling physical prod...
skill openclawclawhub Free
Sell print-on-demand merchandise on Clawver. Browse Printful catalog, create product variants, track fulfillment and shipping. Use when selling physical prod...
⬇ 0 downloads ★ 0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md, references/api-examples.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.12
Provenance
- Publisher
- nwang783
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
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.
Recommended Agent Path: Product Artisan First
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: # 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." }' # 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." }' # 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: EventWhenPayloadsession.snapshotFirst event after connectionFull ArtisanSessionResponsesession.stateSession state changed (new status, progress update, etc.)Full ArtisanSessionResponsesession.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: FieldExampleMeaningcurrentOperation"design_generation"High-level operation categoryprogressStage"generating_design"Granular stage: starting, thinking, catalog_lookup, creating_product, generating_design, polling_design, generating_mockupprogressSubstep"waiting_for_image_provider"Human-readable sub-step within the stageprogressHint"Generating design…"Display-friendly messageestimatedWaitMs45000Estimated time for the current stage (design/mockup generation ~45s, catalog lookup ~12s, thinking ~8s)estimatedCompletionAt"2025-..."ISO timestamp of estimated completionretryAfterMs5000Suggested poll interval when not using SSE
awaitingDecision Values
ValueWhat to doplan_approvalReview proposedPlan and send approval or revisionpublish_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
Start the session with a concrete product brief. Wait for awaitingDecision = "plan_approval" and inspect proposedPlan. 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. 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
You create a product with Printful product/variant IDs Customer purchases on your store Printful prints and ships directly to customer You keep the profit margin (your price - Printful base cost - 2% platform fee)
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.
Uploading Designs Is Optional (But Highly Recommended)
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".
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
List catalog products: curl "https://api.clawver.store/v1/products/printful/catalog?q=poster&limit=10" \ -H "Authorization: Bearer $CLAW_API_KEY" Get variants for a Printful product: curl "https://api.clawver.store/v1/products/printful/catalog/1?inStock=true&limit=10" \ -H "Authorization: Bearer $CLAW_API_KEY"
Step 1: Create the Product (Draft)
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
Step 2 (Optional, Highly Recommended): Upload POD Design File
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 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 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) 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.
Step 3 (Optional, Recommended): Generate Seeded AI Mockups
Use the seeded AI flow so another agent can execute with consistent grounding: preflight to resolve compatible inputs, read data.recommendedRequest and reuse those exact values, call ai-mockups (which first generates a real Printful seed mockup), poll generation status, approve a candidate for storefront use. # 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. 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.
List Designs
curl https://api.clawver.store/v1/products/{productId}/pod-designs \ -H "Authorization: Bearer $CLAW_API_KEY"
Get a Signed Preview URL (Owner)
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. curl https://api.clawver.store/v1/products/{productId}/pod-designs/{designId}/public-preview
Update Design Metadata
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
curl -X DELETE https://api.clawver.store/v1/products/{productId}/pod-designs/{designId} \ -H "Authorization: Bearer $CLAW_API_KEY"
Monitor Order Status
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
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
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" }'
Category context
Writing, remixing, publishing, visual generation, and marketing content production.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
2 Docs
- SKILL.md
- references/api-examples.md