Token导航 LogoToken导航

Agent Skill · 开发

selzy-api-skill(selzy API 技能)

用于辅助 API 设计、接口文档、请求响应结构和服务集成说明。它适合让 Agent 梳理 endpoint、生成 OpenAPI 草稿、检查字段命名、整理错误码或辅助前后端联调。使用时需要确认真实业务语义、鉴权方式、分页和错误处理规则;涉及生成接口文档时,应避免凭空补字段,最好从现有代码、schema 或接口样例中提取事实。

selzy-api-skill 是开发类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为接触敏感数据;许可证为 MIT-0,第三方扫描已通过,按安装量在开发类的 21,746 个 Skill 里排第 4,696。

总安装 7,684周安装 317GitHub Stars 公开资料未说明下载 2,511核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

ClawHubOpenClaw
openclaw skills install selzy-api-skill

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

通过 Selzy API 管理电子邮件营销活动全流程。支持联系人分组、模板设计与 A/B 测试分析。适用于客户触达与转化优化场景。selzy-api-skill 属于开发类 Skill,可作为该场景下的辅助能力补充。安装命令:openclaw skills install selzy-api-skill。

需妥善保管 API 密钥并遵守邮件发送规范。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它需要接触敏感数据,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

selzy-api-skill 怎么安装?

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

selzy-api-skill 支持哪些 AI 工具?

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

selzy-api-skill 需要什么权限?

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

selzy-api-skill 是免费的吗?

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

selzy-api-skill 用的人多吗?

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

selzy-api-skill 安全吗?

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

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

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 需要接触敏感数据,装到常用环境前要先评估影响面。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

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

不太适合

  • 环境里有大量密钥、凭证,不方便给第三方 Skill 读取的人。
  • 需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

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

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
selzy-api-skill

selzy API 技能 · 本页

7,684—接触敏感数据MIT-0通过

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

SKILL.md 原文

name
selzy
description
>
metadata
openclaw
emoji
✉️
requires
env
primaryEnv
SELZY_API_KEY
version
2.3
lastUpdated
2026-02-26
changelog

Selzy Email Marketing API — Complete Guide

Selzy is an email marketing platform with a REST API for managing contacts, creating campaigns, and analyzing performance. This skill lets you run your entire email marketing from an AI assistant.


🚨 CRITICAL WARNING — Read Before Using

⚠️ Common Pitfall: Campaigns Sent to Wrong Recipients

Problem: If you create a campaign without explicitly specifying list_id, Selzy will send to ONLY 1 contact (default behavior), not your entire list.

Solution: ALWAYS follow this workflow:

  1. Call getLists → get the correct list_id AND verify contact count
  2. Pass list_id to createEmailMessage (REQUIRED parameter)
  3. Verify recipient count matches expectations BEFORE calling createCampaign
  4. Get explicit user confirmation before sending

This affects ALL users. The fix is in the workflow, not the API.


🚫 RATE LIMIT WARNING — Account Ban Risk

REAL INCIDENT (2026-02-25): User sent 35 email campaigns in a few minutes using createCampaign. Selzy blocked the account for suspicious bulk activity.

Official Selzy API Rate Limits (from https://selzy.com/en/support/api/common/selzy-api-limits/):

Endpoint / ActionLimit
General API1200 requests / 60 seconds (per API key or IP)
checkEmail method300 requests / 60 seconds
subscribe methodLimited (exact value not published)
sendEmail method1,000 emails/day default for new users (auto-increases)
sendSms method150 numbers per call
getCampaigns method10,000 campaigns per response
getMessages limit100 records per request (default 50)
importContacts timeout30 seconds per call

⚠️ CRITICAL: Campaign Creation Rate (UNPUBLISHED but ENFORCED)

While general API allows 1200 req/min, creating campaigns (createCampaign) has additional fraud detection:

  • MAX 1 campaign creation per HOUR (strict limit after ban incident)
  • Burst of 35 campaigns in <5 min = instant account block (real incident 2026-02-25)
  • Selzy's fraud system flags rapid campaign creation as suspicious bulk activity

Why the discrepancy?

  • 1200 req/min is for read operations (getLists, getCampaigns, stats)
  • Write operations (createCampaign, importContacts) have stricter anti-abuse limits
  • No official documentation on campaign creation rate — enforced heuristically

Symptoms of Rate Limit Violation:

  • API returns count=0 for all campaigns (even valid ones)
  • Campaigns stuck in scheduled status but never send
  • Account flagged for manual review

Recovery:

  1. STOP all campaign creation immediately
  2. Wait 24-48 hours for automatic unblock OR contact Selzy support
  3. Request manual review + explain it was automation error
  4. When unblocked: implement rate limiting (1 campaign / hour MAX)

Prevention:

  • Wait 1 HOUR between createCampaign calls — this is now the hard limit
  • For batch sends: create max 1 campaign per hour, spread across days
  • Monitor API responses: count=0 across multiple campaigns = RED FLAG
  • NEVER automate bulk campaign creation without rate limiting
  • Remember: 1200 req/min is for READ operations, not campaign creation

If you need to send to multiple segments:

1. Create all email messages first (no rate limit on createEmailMessage)
2. Schedule campaigns across multiple days (1 per hour max)
3. OR: use single campaign with segmented list (preferred)
4. Use cron jobs with hourly spacing for automated sends

This is now MANDATORY: Any automation creating >1 campaign per hour will risk permanent ban. 1 campaign per hour = HARD LIMIT.


📊 Official Selzy API Limits Summary

OperationLimitNotes
General API calls1200 / minPer API key or IP
checkEmail300 / minEmail validation
sendEmail (transactional)1000 / dayNew users, auto-increases
sendSms150 / callMax numbers per request
getCampaigns10,000 / responsePagination needed for more
getMessages100 / requestDefault 50
importContacts30s timeoutPer call
createCampaign1 / hourUnpublished, HARD LIMIT after ban incident

Source: https://selzy.com/en/support/api/common/selzy-api-limits/


🔐 Authentication

All requests require the SELZY_API_KEY environment variable. Pass it as the api_key parameter.

Base URL: https://api.selzy.com/en/api

Important: All methods use GET with query parameters (Selzy API uses GET for all endpoints). URL-encode parameter values when needed.

General Request Pattern

curl "https://api.selzy.com/en/api/{METHOD}?format=json&api_key=$SELZY_API_KEY&{params}"

Response Format:

  • Success: {"result": {...}} or {"result": [...]}
  • Error: {"error": "message", "code": "error_code"}

📋 1. Contact Lists

1.1 Get Lists — getLists

Retrieve all contact lists.

curl "https://api.selzy.com/en/api/getLists?format=json&api_key=$SELZY_API_KEY"

Response:

{
  "result": [
    {"id": 1, "title": "Newsletter subscribers", "count": 15420, "active_contacts": 14800}
  ]
}

1.2 Create List — createList

Create a new contact list.

curl "https://api.selzy.com/en/api/createList?format=json&api_key=$SELZY_API_KEY&title=VIP%20Customers"

Response: {"result": {"id": 12345}}

1.3 Get List Details — getList

Get detailed info about a specific list.

curl "https://api.selzy.com/en/api/getList?format=json&api_key=$SELZY_API_KEY&list_id=12345"

👥 2. Contact Management

2.1 Import Contacts — importContacts

Bulk import contacts into a list.

curl "https://api.selzy.com/en/api/importContacts?format=json&api_key=$SELZY_API_KEY&field_names[]=email&field_names[]=Name&data[][]=john@example.com&data[][]=John&data[][]=jane@example.com&data[][]=Jane&list_ids=12345&overwrite=2"
ParameterDescription
field_names[]Column names: email (required), Name, phone, etc.
data[][]Contact data rows (flat array, fills row by row)
list_idsComma-separated list IDs to add contacts to
overwrite0=skip existing, 1=overwrite all, 2=overwrite empty only

2.2 Subscribe — subscribe

Add a single contact with opt-in control.

curl "https://api.selzy.com/en/api/subscribe?format=json&api_key=$SELZY_API_KEY&list_ids=12345&fields[email]=user@example.com&fields[Name]=Alice&double_optin=3"

double_optin values:

  • 0 = no confirmation
  • 3 = send confirmation email
  • 4 = already confirmed (force subscribe)

2.3 Exclude Contact — exclude

Unsubscribe/remove a contact.

curl "https://api.selzy.com/en/api/exclude?format=json&api_key=$SELZY_API_KEY&contact_type=email&contact=user@example.com"

2.4 Get Contact — getContact

Get contact details by email.

curl "https://api.selzy.com/en/api/getContact?format=json&api_key=$SELZY_API_KEY&email=user@example.com"

2.5 Create Custom Field — createField

Add a custom field for contacts.

curl "https://api.selzy.com/en/api/createField?format=json&api_key=$SELZY_API_KEY&field_name=Company&field_type=text"

field_type options: text, number, date, boolean


📧 3. Email Messages (Templates)

3.1 Create Email Message — createEmailMessage

⚠️ CRITICAL: list_id is REQUIRED ⚠️

Without list_id, Selzy will send to ONLY 1 contact (default behavior). This is a common pitfall that causes campaigns to be sent to wrong recipients.

ALWAYS call getLists first to get the correct list_id and verify contact count BEFORE creating a message.

Create an email template for campaigns.

curl "https://api.selzy.com/en/api/createEmailMessage?format=json&api_key=$SELZY_API_KEY&sender_name=My%20Store&sender_email=news@yourdomain.com&subject=Summer%20Sale%20🔥&body=<h1>Hello!</h1><p>Check%20out%20our%20deals</p>&list_id=12345"
ParameterRequiredDescription
sender_nameYesFrom name
sender_emailYesFrom email (must be verified domain)
subjectYesEmail subject line
bodyYesHTML content (URL-encoded)
list_idYES — CRITICALTarget list ID. MUST be obtained from getLists. Without this, campaign sends to 1 contact only!
langNoLanguage code (en, ru, es, etc.)
text_bodyNoPlain text version for fallback
tagNoCampaign tag for filtering/analytics

Response: {"result": {"message_id": 67890}}

3.2 Update Email Message — updateEmailMessage

Modify an existing email template.

curl "https://api.selzy.com/en/api/updateEmailMessage?format=json&api_key=$SELZY_API_KEY&id=67890&subject=Updated%20Subject"

3.3 Get Message — getMessage

Get email template details.

curl "https://api.selzy.com/en/api/getMessage?format=json&api_key=$SELZY_API_KEY&id=67890"

3.4 List Messages — listMessages

List all email templates with date filter.

curl "https://api.selzy.com/en/api/listMessages?format=json&api_key=$SELZY_API_KEY&date_from=2026-01-01&date_to=2026-02-01"

3.5 Create Email Template — createEmailTemplate

Create a reusable template (separate from messages).

curl "https://api.selzy.com/en/api/createEmailTemplate?format=json&api_key=$SELZY_API_KEY&name=Welcome%20Series&subject=Welcome!&body=<h1>Welcome {{Name}}!</h1>"

3.6 Get Template — getTemplate

Get template details.

curl "https://api.selzy.com/en/api/getTemplate?format=json&api_key=$SELZY_API_KEY&template_id=12345"

🚀 4. Campaigns

4.1 Create Campaign — createCampaign

Create and schedule a campaign.

curl "https://api.selzy.com/en/api/createCampaign?format=json&api_key=$SELZY_API_KEY&message_id=67890&start_time=2026-02-10%2010:00:00&timezone=Europe/Moscow&track_read=1&track_links=1"
ParameterRequiredDescription
message_idYesEmail message ID from createEmailMessage
start_timeNoSchedule time (YYYY-MM-DD HH:MM:SS). Omit for immediate send
timezoneNoTimezone for scheduled send (e.g., Europe/Belgrade)
track_readNoTrack opens (1=yes, 0=no)
track_linksNoTrack clicks (1=yes, 0=no)

Response: {"result": {"campaign_id": 11111}}

4.2 Cancel Campaign — cancelCampaign

Cancel a scheduled campaign before it sends.

curl "https://api.selzy.com/en/api/cancelCampaign?format=json&api_key=$SELZY_API_KEY&campaign_id=11111"

4.3 Get Campaign Status — getCampaignStatus

Check campaign status and progress.

curl "https://api.selzy.com/en/api/getCampaignStatus?format=json&api_key=$SELZY_API_KEY&campaign_id=11111"

Status values: draft, scheduled, sending, analysed, canceled

4.4 Get Campaigns — getCampaigns

List recent campaigns with optional date filter.

curl "https://api.selzy.com/en/api/getCampaigns?format=json&api_key=$SELZY_API_KEY&from=2026-01-01&to=2026-02-24"

Date format: YYYY-MM-DD HH:MM:SS or YYYY-MM-DD


📊 5. Campaign Statistics

5.1 Get Campaign Stats — getCampaignCommonStats

Get comprehensive statistics for a campaign.

curl "https://api.selzy.com/en/api/getCampaignCommonStats?format=json&api_key=$SELZY_API_KEY&campaign_id=11111"

Response:

{
  "result": {
    "total": 15000,
    "sent": 14800,
    "delivered": 14500,
    "read_unique": 4200,
    "read_all": 5100,
    "clicked_unique": 890,
    "clicked_all": 1200,
    "unsubscribed": 12,
    "spam": 3
  }
}

Metrics to calculate:

  • Open Rate = (read_unique / delivered) × 100
  • Click Rate = (clicked_unique / delivered) × 100
  • Bounce Rate = ((sent - delivered) / sent) × 100
  • Unsubscribe Rate = (unsubscribed / delivered) × 100
  • Spam Rate = (spam / delivered) × 100

📮 6. Senders

6.1 Get Sender Emails — getSenderEmails

List all verified sender emails.

curl "https://api.selzy.com/en/api/getSenderEmails?format=json&api_key=$SELZY_API_KEY"

Response:

{
  "result": [
    {
      "id": 8526648,
      "email": "news@yourdomain.com",
      "name": "Your Store",
      "isVerified": true,
      "dkimStatus": "verified",
      "isFreeDomain": false
    }
  ]
}

Note: sender_email in campaigns must be from this verified list.


🎯 Instructions for the Agent

Critical Rules

🚨 SAFETY CHECKLIST (Before Any Campaign Send)

MANDATORY — verify ALL before proceeding:

  • [ ] getLists called → have explicit list_id
  • [ ] Contact count verified → matches expected recipients
  • [ ] If count = 0 or count != expected → STOP and alert user
  • [ ] createEmailMessage includes list_id parameter
  • [ ] User confirmed: list name, count, subject, send time
  • [ ] Explicit "send" or "confirm" received from user
  • [ ] RATE LIMIT CHECK: Last campaign created >1 HOUR ago (HARD LIMIT)
  • [ ] BATCH WARNING: If creating >1 campaign per hour = ACCOUNT BAN RISK

If ANY check fails → DO NOT SEND, ask user first.

CRITICAL: Creating 35 campaigns in a few minutes = ACCOUNT BAN. MAX 1 campaign per HOUR.


  1. NEVER send a campaign without explicit user confirmation. Always show:

- Recipient list name and count (VERIFY this matches expectations) - Subject line - Body summary (first 100 chars) - Send time (immediate or scheduled) - list_id being used

  1. For new campaigns, follow this workflow (MANDATORY):
   1. getLists → GET list_id AND count of contacts
   2. VERIFY: count >= expected recipients (if count=0, STOP and ask)
   3. createEmailMessage → MUST include list_id parameter + confirm subject + content
   4. RATE LIMIT CHECK: If created campaign in last 60s, WAIT before proceeding
   5. createCampaign → confirm timing + recipient count
   6. WAIT for explicit "send" or "confirm" from user

⚠️ BATCH SENDS: If creating multiple campaigns (e.g., for different segments): - Create all createEmailMessage calls first (no rate limit) - Queue createCampaign calls with 1 HOUR delays between each (HARD LIMIT) - NEVER create >1 campaign per hour — instant ban risk - Real incident: 35 campaigns in few minutes = account blocked - Use cron jobs to space campaigns across days if needed

  1. CRITICAL: list_id is REQUIRED

- NEVER create email message without explicit list_id - ALWAYS verify contact count matches expectations before sending - If list_id is missing or count is wrong → STOP and alert user

  1. For statistics requests:

- Always calculate rates as percentages - Compare to industry benchmarks if asked (avg: 20% open, 2.5% click) - Highlight trends (up/down vs previous campaigns)

  1. Handle errors gracefully:

- Explain what went wrong in plain language - Suggest specific fixes - Retry once for rate limiting (add 1s delay)

  1. Security reminders:

- Never log or display the full API key - Remind users that sender_email must be verified - Warn about GDPR/compliance for contact imports

Common Workflows

"Create a campaign for my VIP customers"
1. getLists → find VIP list, confirm count (MUST match expected recipients)
2. If count is wrong → STOP and alert user (DO NOT proceed)
3. Ask: subject, content type (promo/newsletter/event)
4. createEmailMessage → MUST include list_id parameter, show preview
5. createCampaign (omit start_time for immediate)
6. ⚠️ WAIT for "send it" or "confirm" before considering it done
7. Report: campaign_id, status, recipient count (verify matches step 1)
"How did my last campaign perform?"
1. getCampaigns (last 7 days) → get latest campaign_id
2. getCampaignCommonStats → get metrics
3. Calculate: open rate, click rate, bounce rate, unsubscribe rate
4. Present as: "X% opened, Y% clicked, Z% bounced"
5. Optional: compare to industry avg or previous campaign
"Add new subscribers to my newsletter"
1. getLists → find newsletter list
2. Confirm: list name, number of contacts to add
3. importContacts (bulk) OR subscribe (single)
4. Report: success count, skipped count, errors
"Show my contact lists"
1. getLists → retrieve all
2. Present table: Name | Total | Active | Created
3. Offer: "Want to create a new list or add contacts?"
"Schedule a webinar invitation"
1. getLists → confirm audience (GET list_id + count)
2. VERIFY count matches expected recipients
3. Ask: webinar details (title, date, time, link)
4. createEmailMessage with storytelling approach + list_id parameter
5. createCampaign with start_time="2026-02-25 10:00:00" timezone="Europe/Belgrade"
6. Confirm: "Scheduled for Feb 25 at 10:00 AM Belgrade time to {count} recipients"

📖 Real-World Bug Fix Example

❌ WRONG — Campaign sent to 1 person instead of 4

# Missing list_id — Selzy sends to 1 contact by default!
curl "https://api.selzy.com/en/api/createEmailMessage?format=json&api_key=$KEY&sender_name=My+Store&sender_email=me@example.com&subject=Sale&body=<h1>Sale!</h1>"

Result: Campaign #327590492 sent to 1 recipient instead of 4 contacts in list.

✅ CORRECT — Always include list_id

# Step 1: Get lists and verify count
curl "https://api.selzy.com/en/api/getLists?format=json&api_key=$KEY"
# Response: [{"id": 12345, "title": "My first list", "count": 4}]

# Step 2: Create message WITH list_id
curl "https://api.selzy.com/en/api/createEmailMessage?format=json&api_key=$KEY&sender_name=My+Store&sender_email=me@example.com&subject=Sale&body=<h1>Sale!</h1>&list_id=12345"
# Response: {"result": {"message_id": 67890}}

# Step 3: Create campaign
curl "https://api.selzy.com/en/api/createCampaign?format=json&api_key=$KEY&message_id=67890"
# Response: {"result": {"campaign_id": 11111}}

# Result: Campaign sent to ALL 4 contacts ✅

⚠️ API Error Handling

Error ResponseMeaningFix
"error": "Incorrect API key"Wrong/missing API keyCheck SELZY_API_KEY in config
"error": "Access denied"Insufficient permissionsVerify API key has correct scope
"error": "Not found"Resource doesn't existCheck ID (campaign_id, message_id, list_id)
"error": "Bad date-time literal"Wrong date formatUse YYYY-MM-DD HH:MM:SS
HTTP 429Rate limitedWait 1-2 seconds, retry once
"error": "Sender not verified"Email not in verified listUse getSenderEmails, pick verified one

📚 Resources

  • API Reference: https://selzy.com/en/support/api/
  • Getting Started: https://selzy.com/en/support/
  • Sign Up: https://selzy.com/en/registration/
  • Blog: https://selzy.com/en/blog/

🧪 Quick Test Commands

Verify API access:

# Check connection
curl "https://api.selzy.com/en/api/getLists?format=json&api_key=YOUR_KEY"

# Check verified senders
curl "https://api.selzy.com/en/api/getSenderEmails?format=json&api_key=YOUR_KEY"

# Test campaign stats (replace ID)
curl "https://api.selzy.com/en/api/getCampaignCommonStats?format=json&api_key=YOUR_KEY&campaign_id=123456"

Skill Version: 2.0 (Complete) Last Updated: 2026-02-24 Tested Methods: getLists, getSenderEmails, getCampaigns, getCampaignCommonStats, createEmailMessage, createCampaign, getTemplates

平台分布

OpenClaw

78.4%
按下载量换算1,969

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

接触敏感数据

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

安装前确认

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

继续浏览同类 Skills