Content Asset Orchestrator

Plan, organize, and audit ecommerce content assets across short video (TikTok/Douyin), Xiaohongshu posts, Amazon A+ content, Shopify PDP images, email banner...

Security Scan

The skill's description, instructions, and visible code are coherent for a local, heuristic content-planning tool, but the provided handler.py appears truncated so I cannot fully verify there are no hidden network/env accesses — review the full file before installing.

Purpose & Capability

Name, description, SKILL.md and the visible handler.py logic align: the code tokenizes input, detects channels/goals/formats, and renders a markdown brief. No unrelated credentials, binaries, or config paths are requested.

Instruction Scope

SKILL.md explicitly states it does not connect to live social/DAM/analytics systems and limits outputs to a markdown brief. The visible code implements only local heuristics and rendering; the instructions do not request unrelated files or environment data.

Install Mechanism

There is no install specification (instruction-only style). The only artifacts are source files included with the skill — no external downloads, package installs, or extracts are declared.

Credentials

The skill declares no required environment variables or credentials and the visible code does not access environment variables or config paths. This is proportionate for a planning/orchestration skill.

Persistence & Privilege

No elevated persistence requested: always is false, user-invocable is true, and disable-model-invocation is false (normal). The skill does not request to modify other skills or system-wide settings in the visible materials.

What to consider before installing

What to check before installing: - Inspect the full handler.py (the provided snippet was truncated). Search the file for network calls (requests, urllib, socket, http, urllib3), subprocess/exec usage, and any os.environ access or file system writes that aren't necessary for local rendering. - Run the included tests locally (tests/test_handler.py) in a sandboxed environment to confirm behavior. - Note the skill has no declared homepage or known owner; consider this when deciding trust and avoid supplying sensitive credentials or proprietary asset inventories until you verify the code. - If you plan to let the agent invoke the skill autonomously, ensure it runs with least privilege and in a non-production test workspace first. If you provide product or customer data to the skill, avoid including PII until you confirm there is no exfiltration logic in the unseen portion of the code.

Overview

Use this skill to turn rough content goals, channel priorities, and production constraints into an organized content operations brief. It applies a built-in content type framework, channel requirement matrix, and production workflow to generate an actionable asset plan.

This MVP is heuristic. It does not connect to live social accounts, DAM systems, analytics platforms, or content management tools. It relies on the user's provided content context, channel mix, and production resources.

Trigger

Use this skill when the user wants to:

• plan a content production schedule across TikTok, Xiaohongshu, Amazon, Shopify, email, or Meta
• audit content assets for a product launch, campaign, or seasonal push
• identify content gaps across format types (short video, image, copy, UGC)
• build a content brief for a creator, photographer, or copywriter
• sequence content types across awareness, consideration, and conversion stages

Example prompts

• "Help me plan content for our summer campaign across TikTok, Xiaohongshu, and Amazon A+"
• "Audit our current content assets for gaps before our product launch"
• "Create a content production brief for our DTC brand's new SKU"
• "What content should we produce this month for our Shopify and Meta channels?"

Workflow

1. Capture the campaign or production window, target channels, and content goals.
2. Map content types to channels and identify required formats (video, image, copy, UGC).
3. Audit existing assets for completeness, quality, and channel fit.
4. Identify production gaps and assign owners or resource needs.
5. Return a markdown content operations brief with production calendar and asset brief.

Inputs

The user can provide any mix of:

• campaign window: specific dates, seasonal push, or general monthly planning
• target channels: TikTok, Douyin, Xiaohongshu, Amazon A+, Shopify PDP, email, Meta, Instagram, WeChat
• content goal: awareness, traffic, conversion, UGC seeding, review collection, SEO
• product or SKU context: new launch, best seller, seasonal, clearance
• existing asset inventory: what formats already exist (video, images, copy, UGC)
• production resources: in-house team, agency, creator, photographer, copywriter
• budget for content production

Outputs

Return a markdown brief with:

• content strategy summary (goal, channels, audience)
• channel requirement matrix (format, dimension, length, caption style)
• content type coverage map (what exists vs. what is needed)
• production gap analysis and asset priority list
• production calendar by week or content type
• brief for each content asset (video, image, copy, UGC) with key messages and format notes
• distribution and posting cadence recommendations

Safety

• No live social accounts, analytics, DAM, or content management tool access.
• Content recommendations are directional; platform policies and creative quality determine actual performance.
• Do not claim guaranteed engagement or conversion lift from content assets.
• Brand voice and creative decisions remain with the content team.

Best-fit Scenarios

• small-to-medium content teams managing 3-8 channels without a dedicated content director
• brands launching new products and needing a structured content production sequence
• operators transitioning from single-channel to multi-channel content operations

Not Ideal For

• real-time content performance tracking, automated posting, or live social media management
• teams with enterprise-scale content operations requiring DAM or MAM integrations
• workflows that require automated approval routing or compliance review

Acceptance Criteria

• Return markdown text.
• Include channel requirement matrix, gap analysis, and production calendar.
• Cover at least 3 channels with specific format requirements.
• Make resource assumptions explicit.
• Keep the brief practical for content teams and ecommerce operators.