Token导航 LogoToken导航TokenDH.com
效率敏感数据clawhub未标认证来源可访问clear审计提醒

viq-bc-optimiserviq bc 优化器

Agent Skill

viq-bc-optimiser 用于整理文档、README、Markdown 和说明材料,适合在 OpenClaw 中需要把零散信息整理成结构清晰的文档时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

12,569

周安装

529

GitHub Stars

公开资料未说明

下载量

4,401
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:viq-bc-optimiser(viq bc 优化器)
来源仓库:https://github.com/veevortexiq/viq-bc-optimiser
安装命令:
openclaw skills install viq-bc-optimiser
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install viq-bc-optimiser

简介

用于 BigCommerce 商店的产品内容批量优化。

  • 支持标题重写、描述生成和内容 SEO 优化。
  • 适用于电商平台商品信息标准化管理。
  • 通过 clawhub 安装,需配置 BigCommerce API 凭据。
  • 注意批量操作前建议备份原始数据。viq-bc-optimiser 属于效率类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

name
bigcommerce-content-optimizer
description
>
metadata
openclaw
requires
bins
emoji
🛒

BigCommerce Content Optimizer

Autonomous skill that fetches products from a BigCommerce store, generates optimized titles and descriptions, and updates them back — one page at a time with full progress tracking.

Prerequisites

The user must provide:

  1. Store Hash — the BigCommerce store identifier (e.g., abc123def)
  2. API Token — a BigCommerce API v3 token with Products read+write scope

Setup

Before first use, install the requests library:

pip install requests --break-system-packages

The helper script is at: ~/.openclaw/workspace/skills/bigcommerce-content-optimizer/scripts/bc_optimizer.py

Set SCRIPT as the full path to bc_optimizer.py for all commands below.

Workflow — Autonomous Loop

CRITICAL: Do NOT stop between pages. Process ALL pages continuously until done.

Step 1: Initialize

python3 $SCRIPT init --store-hash "STORE_HASH" --token "API_TOKEN" --limit 10

This creates progress.json in the current working directory and returns total product/page counts. If progress.json already exists with status: in_progress, it resumes from the last unprocessed page.

Step 2: For EACH page (loop until all done)

2a. Fetch the page

python3 $SCRIPT fetch --store-hash "STORE_HASH" --token "API_TOKEN" --page PAGE_NUMBER --limit 10

Outputs page_N_products.json with product data.

2b. Read products and generate content

Read the fetched JSON. For EACH product, generate:

  • New Title: SEO-friendly, concise, under 70 characters. Capture the product essence.
  • New Description: Compelling HTML description, 100-300 words. Use <p>, <ul>, <li> tags.

Focus on benefits, use cases, value proposition. No inline styles, no scripts.

Consider: existing name/description, SKU, price, categories, brand, images. Apply SEO best practices (natural keywords, not stuffing) and persuasive copywriting. If the user gave brand voice guidelines, follow them.

Write the output as page_N_updates.json:

[
  {
    "id": 123,
    "name": "New Product Title",
    "description": "<p>New compelling description...</p>"
  }
]

2c. Push updates

python3 $SCRIPT update --store-hash "STORE_HASH" --token "API_TOKEN" --updates-file page_N_updates.json

Updates each product and logs success/failure to progress.json.

2d. Report and continue

After each page, briefly state:

  • Page X of Y complete
  • N products updated, N failed

Then IMMEDIATELY proceed to the next page. Do NOT wait for user input.

Step 3: Completion

When all pages are done:

python3 $SCRIPT report

Print the final summary: total processed, successes, failures, time taken.

Rules

  1. Never stop mid-run — process all pages continuously unless an unrecoverable error occurs
  2. Always use progress.json — if re-invoked, resume from where you left off
  3. Rate limiting — the script handles BigCommerce rate limits with automatic retry
  4. Error handling — if one product fails, log it and continue to the next
  5. Content quality — every title and description must be meaningfully improved, not just rephrased
  6. HTML safety — descriptions use clean simple HTML only (<p>, <ul>, <li>, <strong>, <em>)
  7. One page at a time — fetch, generate, update, then move to next page

Progress Tracker

progress.json tracks everything:

{
  "store_hash": "abc123",
  "total_products": 150,
  "total_pages": 15,
  "products_per_page": 10,
  "started_at": "2025-01-01T00:00:00Z",
  "pages_completed": [1, 2, 3],
  "products_updated": [],
  "products_failed": [],
  "current_page": 4,
  "status": "in_progress"
}

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

80.43%
按下载量换算3,540

安全审计

VirusTotal

可疑

ClawScan

通过

Static analysis

未展示

权限和风险

敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills