Token导航 LogoToken导航

Agent Skill · 运维

xianyu-auto-ops(闲鱼汽车行动)

xianyu-auto-ops 用于补充运维相关能力,适合在 OpenClaw 中需要让 Agent 承接运维相关任务时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

xianyu-auto-ops 是运维类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为只读;许可证为 MIT-0,第三方扫描已通过,按安装量在运维类的 954 个 Skill 里排第 483。

总安装 7,579周安装 319GitHub Stars 1下载 2,654核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
0.3.0

安装方式

通过对话安装

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

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

命令行安装

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

ClawHubOpenClaw
openclaw skills install xianyu-auto-ops

这个 Skill 是做什么的

运维类 Skill 处理部署、监控、日志和云资源,多数需要较高的执行权限。

双语闲鱼上架工具,用于二手货、副业和市场分销运营。提供轻量级运营流程,支持商品发布和信息管理。使用时需提供相关配置参数,具体功能依赖实际部署环境。适合需要自动化闲鱼店铺管理的用户使用。xianyu-auto-ops 属于运维类 Skill,可作为该场景下的辅助能力补充。

安装前需确认权限、维护状态及是否触发联网或命令执行。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install xianyu-auto-ops;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

xianyu-auto-ops 怎么安装?

在终端执行 openclaw skills install xianyu-auto-ops。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

xianyu-auto-ops 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

xianyu-auto-ops 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

xianyu-auto-ops 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

xianyu-auto-ops 用的人多吗?

公开数据是累计安装 7,579 次,近一周安装 319 次,下载 2,654 次,GitHub 1 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

xianyu-auto-ops 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理运维类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

运维类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
docker-essentials

Docker 基础 · OpenClaw

1,005,15130接触敏感数据MIT-0通过
playwright-scraper-skill

Playwright scraper 技能 · OpenClaw

923,55754接触敏感数据MIT-0有提醒
moltguard

moltguard 搜索 · OpenClaw

825,096110接触敏感数据MIT-0通过
finance-news

财经新闻 · OpenClaw

275,51210需要联网MIT-0有提醒
security-monitor

安全监视器 · OpenClaw

224,1695需要联网MIT-0有提醒
xianyu-auto-ops

闲鱼汽车行动 · 本页

7,5791只读MIT-0通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
xianyu-auto-ops
description
Bilingual Xianyu (闲鱼) listing and lightweight operations workflow for second-hand goods, side-hustle products, and marketplace distribution. Use when the user wants to create, optimize, or batch-produce Xianyu listing assets such as titles, selling points, product descriptions, image prompts, reply scripts, pricing angles, posting checklists, or simple operating SOPs in Chinese and English. Also use when the user asks to turn product info or CSV-like SKU data into publish-ready marketplace materials, wants category-specific Xianyu templates, needs buyer chat replies, or wants a reusable batch-oriented Xianyu sales process for physical goods, digital products, or AI services.

Xianyu Auto Ops

Use this skill to turn rough product information into a repeatable Xianyu / Idle Fish operating package.

Default output language: bilingual Chinese + English. Default business goal: faster listing, clearer positioning, better inquiry conversion.

Core workflow

Follow this sequence unless the user asks for only one part.

  1. Clarify the offer

- Identify product type, condition, target buyer, price band, and delivery method. - If key details are missing, make lightweight assumptions and label them clearly.

  1. Choose the operating mode

- Single listing mode: one product, one polished package. - Batch listing mode: multiple SKUs, concise per-item outputs. - Reply mode: buyer inquiry handling, objection answers, negotiation copy. - Optimization mode: improve an existing listing. - Poster mode: generate ad-style image prompts for listing cover or off-platform promo.

  1. Pick a category template

Use the closest category framing: - Digital / 数码: specs, condition, accessories, battery, warranty, authenticity cues. - Home / 家居: size, cleanliness, usage marks, pickup logistics, scene fit. - Fashion / 服饰: size, fabric, season, flaws, try-on expectation. - Virtual / 虚拟产品或服务: delivery scope, usage rights, support boundaries, trust language. - Training / Side-hustle / AI services: results, delivery format, onboarding, trust signals, support boundaries. Read references/ai-services-template.md when the product is training, installation, deployment, consulting, or AI service resale.

  1. Produce the listing package

Return, in this order when relevant: - Chinese title ×3 - English title ×1 - Core selling points / 卖点摘要 - Chinese listing description - English summary description - Suggested tags / keywords - Suggested price anchor and negotiation room - Cover image prompt(s) - Buyer reply scripts - Posting checklist

  1. Keep it platform-native

- Prefer short, direct, benefit-led copy. - Avoid exaggerated claims that sound fake or risky. - Make the listing feel like a real seller wrote it, not a brand brochure.

Batch listing mode

When the user gives multiple items, default to a compact table-like structure using bullets, not markdown tables on chat surfaces.

For each SKU, include:

  • SKU / item name
  • Chinese title ×2
  • One short Chinese description
  • One short English summary
  • Suggested listed price / expected close price
  • One key reply note
  • One image direction

If the user provides a CSV or spreadsheet, use scripts/batch_csv_to_brief.py <file> to normalize the rows first, then use the JSON output as batch input.

Expected columns can include: sku, name, category, brand, condition, price_target, flaws, accessories, city, delivery, notes

Chinese headers like 商品名 / 类目 / 成色 / 价格 / 瑕疵 / 配件 / 城市 / 发货 / 备注 are also supported.

Do not ask the user to perfect the data before starting. Fill gaps with assumptions and mark them.

Output rules

Titles

Write titles that are:

  • easy to scan
  • keyword-rich without obvious stuffing
  • benefit-forward
  • believable for Xianyu

Prefer this rough formula:

[brand/category] + [core item] + [condition / key value] + [buyer use case / bonus point]

Descriptions

For each Chinese description, keep this structure:

  1. What it is
  2. Why selling / product background
  3. Condition / usage / delivery details
  4. Why worth buying
  5. Call to action

For English, provide a shorter mirror summary rather than a full literal translation unless the user asks for full bilingual parity.

Pricing

When suggesting price, provide three layers when possible:

  • Listed price / 挂价
  • Expected成交价 / expected closing price
  • 最低可谈区间 / lowest negotiable band

Base suggestions on:

  • condition
  • urgency to sell
  • scarcity / uniqueness
  • bundled extras
  • local delivery convenience

Buyer reply scripts

When generating reply scripts, include short ready-to-send messages for:

  • “还在吗?” / “Is this still available?”
  • “最低多少?” / “What’s your lowest price?”
  • “有瑕疵吗?” / “Any flaws?”
  • “包邮吗?” / “Is shipping included?”
  • “怎么交易更稳妥?” / “How do we trade safely?”
  • closing push / 成交推进

Keep replies short and human.

Poster prompts

When the user asks for ad visuals, output two prompt layers:

  • Platform-safe cover prompt: more realistic, cleaner, product-led.
  • Promotional poster prompt: more visual tension, more marketing feel, more negative space for title text.

Prefer 16:9 for article covers and 1:1 / 4:5 for feed-like visuals unless the user says otherwise.

Recommended response format

Use this template unless the user asks for a different one.

1. 商品定位 / Positioning

  • Chinese:
  • English:

2. 标题建议 / Title Options

  • CN-1:
  • CN-2:
  • CN-3:
  • EN-1:

3. 卖点提炼 / Selling Points

4. 商品文案 / Listing Copy

中文版本

English version

5. 配图建议 / Image Plan

  • Cover idea:
  • Detail shots:
  • Platform-safe AI image prompt:
  • Promotional poster prompt:

6. 价格建议 / Pricing Strategy

  • Listed price:
  • Expected close price:
  • Lowest negotiable range:

7. 私聊回复模板 / Chat Reply Scripts

  • 在的 / Available:
  • 最低价 / Lowest price:
  • 瑕疵说明 / Flaw disclosure:
  • 安全交易 / Safe trade:
  • 成交推进 / Closing push:

8. 发布清单 / Posting Checklist

  • [ ] photos ready
  • [ ] condition disclosed
  • [ ] delivery method stated
  • [ ] keywords included
  • [ ] price strategy set
  • [ ] reply script ready

Bilingual handling

When the user asks for bilingual output, do not translate mechanically.

  • Chinese should sound like a native Xianyu seller.
  • English should sound like a concise marketplace assistant summary.
  • If the target buyers are Chinese users only, keep English shorter.

Safety and quality guardrails

  • Do not fabricate certifications, warranties, invoices, or brand authorization.
  • Do not hide material defects if the user explicitly mentions them.
  • Do not promise impossible delivery times.
  • Flag risky categories, compliance-sensitive products, or obvious fraud patterns.
  • For virtual goods or services, clearly describe what is and is not delivered.

References

Read references/playbook.md when the user needs stronger title formulas, batch handling, category-specific patterns, buyer reply banks, or poster prompt templates.

平台分布

OpenClaw

77.26%
按下载量换算2,050

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills