Token导航 LogoToken导航TokenDH.com
前端设计敏感数据github未标认证来源可访问许可证需确认审计提醒

vibeskuvibesku 命令行

Agent Skill

vibesku 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

247

周安装

10

GitHub Stars

公开资料未说明

下载量

78
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/ullrai/vibesku-agent --skill vibesku

简介

用于处理 GitHub 仓库、Issue 和 Pull Request,适合协作事项整理。

  • 可在 Codex、Claude 等平台中围绕代码变更进行梳理。
  • 安装命令:npx skills add https://github.com/ullrai/vibesku-agent --skill vibesku。
  • 建议确认仓库访问权限和维护状态后再使用。
  • 注意是否会触发联网或文件操作,避免越权行为。

SKILL.md

VibeSKU CLI

Command-line interface for VibeSKU — AI-powered creative automation that turns product SKU photos into agency-grade e-commerce visuals and marketplace-ready copy in seconds.

What VibeSKU Does

VibeSKU replaces manual creative production for e-commerce teams. Upload a product photo, define brand guidelines, and receive complete multi-format visual sets. Core capabilities: VisionKV™ visual system (complete visual collections from a single product), high-fidelity product restoration (1:1 precision on textures/logos/packaging), multilingual text overlays, and omni-channel format output.

Credit costs: 1K/2K image = 1 credit, 4K image = 2 credits, short video = 5 credits, copy = 1 credit.

Setup

The CLI is bundled at bin/vibesku.js — self-contained Node.js script, zero dependencies (requires Node >= 18).

node <skill-dir>/bin/vibesku.js --help
alias vibesku="node <skill-dir>/bin/vibesku.js"   # optional

Skill Version

For version checks and auto-update workflow, see versioning.md.

Authentication

Two methods, resolved in priority order:

  1. CLI token (vibesku auth login) — browser-based device flow, tokens at ~/.vibesku/config.json
  2. API keyVIBESKU_API_KEY env var > config file key (from vibesku init or vibesku config set-key)
vibesku auth login                # Browser login (recommended)
vibesku init vsk_<key>            # API key for CI/CD

Template Selection Guide

VibeSKU provides 5 templates. Read the corresponding reference file before building the generate command.

NeedTemplateOutputCostReference
Single product image (main photo, banner, poster)ecom-heroIMAGE1-2 cr/imgecom-hero.md
Coordinated detail-page poster setkv-image-setIMAGE1-2 cr/img × sceneskv-image-set.md
Single technical exploded infographicexploded-viewIMAGE1-2 cr/imgexploded-view.md
Clean white-background packshotwhite-backgroundIMAGE1-2 cr/imgwhite-background.md
Product listing copy (title, bullets, description)listingTEXT1 crlisting.md

Decision Tree

User wants visuals?
├── Technical exploded infographic → exploded-view
│   ├── Balanced callouts (default) → labelPlacement: balanced-callout
│   ├── Cleaner visual without labels → labelPlacement: none
│   └── Category-aware environment → backgroundMode: product-matched-scene
├── Marketplace/catalog white-background packshot → white-background
│   ├── Pure white background → backgroundTone: pure-white
│   ├── Softer depth → backgroundTone: soft-white
│   └── Tighter framing → cropMode: close-up
├── Single image (hero/banner/poster) → ecom-hero
│   ├── Product main photo → scenario: MAIN_IMAGE, aspectRatio: 1:1
│   ├── Marketing banner  → scenario: BANNER, aspectRatio: 16:9
│   └── Vertical poster   → scenario: POSTER, aspectRatio: 3:4
└── Multiple coordinated images → kv-image-set
    ├── Full detail page     → scenes: [kv-hero, lifestyle, detail-01, specs-table, ...]
    ├── Quick hero + lifestyle → scenes: [kv-hero, lifestyle]
    └── Brand storytelling   → scenes: [kv-hero, brand-story, user-review]

User wants text?
└── Product listing copy → listing
    ├── Amazon  → templateName: AMAZON_LISTING
    ├── Taobao  → templateName: TAOBAO_DETAIL
    ├── Shopify → templateName: SHOPIFY_DESC
    └── General → templateName: GENERIC

Quick Style Matching (image templates)

Product Typeecom-hero stylekv-image-set styleexploded-view style
Electronics, gadgetstechtech-futurepremium-technical
Luxury, high-endpremiummagazinemorandi-editorial
Food, home goodslifestyleretro-filmlifestyle-soft
Organic, eco-friendlyorganicorganic-naturematerial-focus
Fashion, beautyminimalnordic-minimalstudio-minimal
Kids, sports, boldvibrantcyberpunkauto (recommended)
Artisan, handmadestudiowatercolormaterial-focus
Unsure / let AI decideauto (default)auto (default)auto (default)

Typical Workflow

vibesku auth login                              # 1. Authenticate
vibesku templates                               # 2. Browse templates
vibesku templates info exploded-view            # 3. Inspect template details (optional)
vibesku credits                                 # 4. Check balance
vibesku generate -t ecom-hero \
  -n "Wireless Headphones" \
  -i product.jpg -l logo.png \
  -b "AudioTech"                                # 5. Generate visuals
vibesku status <job-id> --watch                 # 6. Monitor until complete
vibesku refine <output-uuid> -p "brighter bg"   # 7. Refine (optional)
vibesku export <job-id> -o ./output             # 8. Download results

Commands Quick Reference

CommandPurpose
`vibesku auth login\logout\status\refresh`Authentication management
vibesku init <api-key>Initialize with API key
`vibesku config set-key\set-url\show\reset`CLI configuration
vibesku templates [info <id>]List / inspect templates
vibesku generate -t <id> [options]Generate visuals or copy
vibesku refine <output-id> -p <prompt>Refine output with edit instructions
vibesku status <job-id> [--watch]Check job progress
vibesku jobs [-p <page>] [-t <template>]List jobs
vibesku export <job-id> [-o <dir>]Download outputs
vibesku batch <file> [--dry-run]Bulk generation from JSON
`vibesku credits [show\buy\redeem <code>]`Credit management

All commands support --json for machine-readable output. Full details: commands.md

Key Behaviors

  • Asset upload: -i auto-uploads product images; -l uploads logo
  • Modify vs Regenerate: Use vibesku refine <output-id> -p "<instruction>" to edit existing output. Use vibesku generate only for new creations.
  • Full UUID required for refine: Use vibesku status <job-id> --json to get complete output UUIDs (table view truncates them).
  • Agent-friendly output: Prefer --json flag for all commands when used by AI agents.
  • Version drift check (recommended triggers): Compare local VERSION with upstream when any of these happen: unknown template/option error, template mismatch with vibesku templates --json, user asks for newly added capability, or local check is older than 7 days (recommended cadence). If issues occur during execution, prioritize this check before retrying generation/refine commands. Follow versioning.md.
  • Auto-update when outdated (recommended): If upstream version is newer, update skill first, then continue the user task with the updated skill.
  • Watch mode: --watch polls every 5s until all runs complete.
  • Credit tracking: Generation and refine show remaining balance on success.

Environment Variables

VariableDescription
VIBESKU_API_KEYAPI key (overrides config file)
VIBESKU_BASE_URLCustom API URL (overrides config file)
NO_COLORDisable colored output

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

33.88%
按下载量换算26

Claude

32.88%
按下载量换算26

Cursor

21.35%
按下载量换算17

Gemini CLI

9.24%
按下载量换算7

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

敏感数据

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

安装前确认

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

来源信息

继续浏览同类 Skills