Creator Commerce Context

v1.0.0

Normalize fragmented creator, product, and campaign details into a structured, reusable context pack for streamlined ecommerce and affiliate workflows.

0· 176·0 current·0 all-time
byLeroyCreates@leooooooow

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for leooooooow/creator-commerce-context.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Creator Commerce Context" (leooooooow/creator-commerce-context) from ClawHub.
Skill page: https://clawhub.ai/leooooooow/creator-commerce-context
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install creator-commerce-context

ClawHub CLI

Package manager switcher

npx clawhub@latest install creator-commerce-context
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name, description, and SKILL.md consistently describe normalizing ecommerce/creator notes into a context pack. There are no unrelated requirements (no credentials, binaries, or config paths) that would be disproportionate to this purpose.
Instruction Scope
The runtime instructions only ask the agent to extract facts from user-provided messy notes, separate facts vs assumptions, and assemble a structured output. The skill does not instruct the agent to read arbitrary system files, access environment variables, or transmit data to external endpoints.
Install Mechanism
This is an instruction-only skill with no install spec and no code files. That minimizes disk writes and external code execution risk.
Credentials
No environment variables, credentials, or config paths are requested. The absence of secrets/keys is proportionate to the described text-normalization purpose.
Persistence & Privilege
The skill is not force-included (always: false) and uses the default autonomous invocation setting. It does not request elevated persistence or permissions and does not modify other skills or system configuration.
Assessment
This skill appears coherent and low-risk: it only restructures whatever text you give it. Before using, avoid pasting secrets or sensitive personal data into the input (API keys, passwords, unredacted PII). Review the generated context pack for mistaken assumptions the skill marks as 'assumptions' or 'missing information' before handing it to downstream automation. If you intend to pass the output to other skills that can make network calls or perform actions, verify those downstream skills' permissions and credentials separately.

Like a lobster shell, security has layers — review code before you run it.

latestvk972nrszdj1mx20jcfjnm1k8gx8328z8
176downloads
0stars
1versions
Updated 1mo ago
v1.0.0
MIT-0

Creator Commerce Context

Turn messy creator, product, campaign, and store information into a structured context pack that downstream ecommerce skills can actually use.

Use this skill when a user has fragmented information about a creator program, TikTok Shop campaign, product launch, affiliate push, or DTC promotion and needs it normalized into a reusable operating context. This is useful before scripting, offer design, creator briefing, landing page review, or performance analysis.

Use when

  • The user has scattered notes about creators, products, offers, campaign goals, and channels
  • A downstream skill needs cleaner context before it can give quality output
  • The team needs a single structured brief from messy raw information
  • You want to reduce repeated back-and-forth questions across ecommerce tasks
  • You need a reusable operating context for multiple creator or affiliate workflows

Do not use when

  • The user only wants one direct answer and no reusable context pack
  • The input is already clean, structured, and complete
  • The task requires market research rather than information normalization

Inputs to gather

  • Brand / store name
  • Product name and core category
  • Price point and offer structure
  • Target audience or customer profile
  • Primary sales channel: TikTok Shop / Shopify / Amazon / live selling / DTC site
  • Creator type: affiliate / UGC / ambassador / live seller / paid influencer
  • Campaign objective: awareness / traffic / conversion / retention / testing
  • Constraints: budget, timeline, compliance, claims, usage rights, inventory, geo
  • Existing assets: PDP, landing page, scripts, reviews, briefs, analytics, creator roster
  • Known risks or open questions

Workflow

  1. Extract raw facts from the user's messy notes
  2. Separate confirmed facts from assumptions and missing pieces
  3. Group the information into a stable ecommerce operating context
  4. Highlight what matters most for downstream creative, offer, or creator tasks
  5. Produce a compact context pack that another skill can immediately consume

Output requirements

Return a context pack with these sections:

  1. Business snapshot
  2. Product / offer snapshot
  3. Customer and creator profile
  4. Channel and campaign objective
  5. Constraints and risks
  6. Missing information
  7. Recommended downstream next skills or next actions

Quality bar

  • Structured but not bloated
  • Clearly distinguishes facts vs assumptions
  • Useful for real creator / affiliate / ecommerce workflows
  • Designed to feed other skills cleanly
  • Avoids filler strategy language

Example prompts

  • Turn these messy TikTok Shop campaign notes into a reusable creator commerce context
  • Normalize this affiliate brief, product info, and creator roster into one context pack
  • Build a clean operating context before we write scripts and offers for this product launch
  • Summarize this product, audience, and creator program into a brief other skills can use

Comments

Loading comments...