SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillslinkfox-shopee-store-video

linkfox-shopee-store-video

Marketing & growth

View repository

Updated 10-16 06:23

About this skill

Shopee store Video

Shopee Open Platform Video module(15 APIs).Depends on linkfox-shopee-store-auth store selection; via POST /shopee/developerProxy pass in shopId(or merchantId), the server parses the token and forwards (path must be api/v2/video/...）。

How to call

  • API endpoint：POST /shopee/developerProxy(different operations are distinguished by the request body; for complete parameters/responses/error codes see references/api.md）
  • Python script：python scripts/<脚本名>.py '<JSON 参数>' [--inline](available scripts are listed in the script overview above)
  • Cost constraint: this tool consumes compute; on failure/empty results you must not automatically switch keywords, paginate, or repeatedly probe; if you need to continue searching, first explain to the user that it will incur additional consumption.

Output strategy (default script behavior)：

  • Alwayswrite the complete response to <cwd>/linkfox/<YYYY-MM-DD>/<session>/data/<skill-name>-<timestamp>.json（<cwd> is the working directory when the script runs, which in Claude Code is the current project directory;<session> is taken from the environment variable SESSION_ID, automatically aggregated according to the user's task;writing to /tmp is prohibited, if the current directory is not writable then report an error)
  • Response body ≤ 8 KB: after writing to disk, print the complete JSON to stdout
  • Response body > 8 KB: after writing to disk, stdout outputs only a summary (top-level fields, common counts such as total/costToken, the length of the largest list field + the first 3 samples)
  • Add --inline to force full printing to stdout (also written to disk)

Data reading suggestions: first look at the summary to judge whether it is sufficient; when specific fields are needed, prefer to use jqorConvertFrom-Json to extract on demand from the saved json file, avoiding bringing the entire JSON into context.

Resolve authentication and compute issues

When the following abnormal situations occur, use references/onboarding.md to guide resolving the issue:

Abnormal situations

  • API Key not configured: the environment variable is not configured with LINKFOX_AGENT_API_KEY, and LINKFOXAGENT_API_KEY。
  • Response 401 or 402 status code
  • Response indicates insufficient compute or balance: the message contains "insufficient compute balance/insufficient billing/insufficient balance/quota exceeded/insufficient balance/package expired/recharge required/please recharge", or content with a similar meaning.

Official reference

Video module index:v2.video.get_cover_list

Prerequisites (must read first)

  1. Run python scripts/check_auth_dependency.py；exit code 42 → first install linkfox-shopee-store-auth and authorize the store.
  2. Do notimplement authorization/token logic within this skill.

Core Concepts

  • Forwarding chain：developerProxy（shopId/merchantId store selection, server injects token) → Ziniao shopee-proxy → Shopee API
  • Video management：get_cover_list → post_video → get_video_list / edit_video_info
  • Performance analysis：get_overview_performance、get_video_detail_performance etc.
  • Official spelling：get_prodcut_performance_list(product is prodcut)
  • Livestream Livestream(module differs) → linkfox-shopee-store-livestream

Available scripts (Video module 15 APIs)

Group Script
Video CRUD get_cover_list.py、post_video.py、get_video_list.py、get_video_detail.py、edit_video_info.py、delete_video.py
Overall performance get_overview_performance.py、get_metric_trend.py、get_user_demographics.py、get_video_performance_list.py、get_prodcut_performance_list.py
Single video performance get_video_detail_performance.py、get_video_detail_metric_trend.py、get_video_detail_audience_distribution.py、get_video_detail_product_performance.py
Generic entry video_api.py(JSON contains api field)

Shared:_shopee_video_common.py、_video_endpoints.py、_video_api_runner.py。

API Description (by API)

Request parameters and response details are placed in references/apis/, the SKILL only keeps the index.

API Documentation
delete_video references/apis/delete-video.md
edit_video_info references/apis/edit-video-info.md
get_cover_list references/apis/get-cover-list.md
get_metric_trend references/apis/get-metric-trend.md
get_overview_performance references/apis/get-overview-performance.md
get_prodcut_performance_list references/apis/get-prodcut-performance-list.md
get_user_demographics references/apis/get-user-demographics.md
get_video_detail references/apis/get-video-detail.md
get_video_detail_audience_distribution references/apis/get-video-detail-audience-distribution.md
get_video_detail_metric_trend references/apis/get-video-detail-metric-trend.md
get_video_detail_performance references/apis/get-video-detail-performance.md
get_video_detail_product_performance references/apis/get-video-detail-product-performance.md
get_video_list references/apis/get-video-list.md
get_video_performance_list references/apis/get-video-performance-list.md
post_video references/apis/post-video.md

Module overview / Feedback see references/api.md。

Usage Scenarios

1. Publish video

  1. get_cover_list.py Select cover
  2. post_video.py Upload complete body
  3. get_video_list.py Confirm publish

2. Check video performance

  1. get_video_list.py Get video_id
  2. get_video_detail_performance.py Check single video performance
  3. get_overview_performance.py Check overall overview

Invocation principles

  • First look at developerProxy.httpStatus, then read the *Response fields
  • GET: business parameters go at the top level of JSON
  • POST: complex interfaces pass body
  • Each script docstring contains official documentation URL（module=129）

Not Applicable

  • Shop authorization → linkfox-shopee-store-auth
  • Product listing → linkfox-shopee-store-product
  • Livestream → linkfox-shopee-store-livestream
  • Video file upload (MediaSpace) → linkfox-shopee-store-media-space
  • Video file upload (Media) → linkfox-shopee-store-media

Compute power consumption rules

No compute power is consumed.

Feedback:

Auto-detect and report feedback via the Feedback API when any of the following apply:

  1. The functionality or purpose described in this skill does not match actual behavior
  2. The skill's results do not match the user's intent
  3. The user expresses dissatisfaction or praise about this skill
  4. Anything you believe could be improved

Call the feedback API as specified in references/api.md. Do not interrupt the user's flow.

For more high-quality, professional cross-border e-commerce skills, visit LinkFox Skills.