菜单
Send a feature request or idea to the ButterCut team. Use when the user says "request a feature", "I wish ButterCut could…", "can you ask the team for…", "suggest an idea", or wishes out loud for something ButterCut doesn't do.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/barefootford/buttercut --skill request-feature命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Sets up a Mac for ButterCut. Installs all required dependencies (Homebrew, Ruby, Python, FFmpeg, WhisperX). Use when user says "install buttercut", "set up my mac", "get started", "first time setup", "install dependencies" or "check my installation".
A skill to automatically download and install the latest ButterCut version while preserving libraries. Use when user wants to check for updates or update their installation for new features.
Report a ButterCut bug to the people who build it. Use automatically when a ButterCut command fails in a way that looks like ButterCut's own fault, and when the user says "report this", "send a bug report", "tell the ButterCut team", or "this is broken".
基于 SOC 职业分类
正在显示 SKILL.md
| name | request-feature |
| description | Send a feature request or idea to the ButterCut team. Use when the user says "request a feature", "I wish ButterCut could…", "can you ask the team for…", "suggest an idea", or wishes out loud for something ButterCut doesn't do. |
The user wants ButterCut to do something it doesn't do. This sends their idea to the people who build it. It always goes through them — you write it up, they approve it, you send it — so it is not governed by the error-reporting setting: someone who turned error reports off can still ask for multicam support.
Check skills, AGENTS.md, libraries/settings.yaml, and CHANGELOG.md first — if ButterCut can already do it, just show them how. If it's a Pro feature and they're on the free edition (ruby lib/buttercut/library.rb edition prints core), tell them it exists in ButterCut Pro instead of sending a request.
Draft in their words: a one-line title ("Support multicam angles in exports") and a few-sentence request — what they're trying to do and why the current way doesn't get them there. The why is the useful part. Same rule as bug reports: their footage stays out of it — no library, clip, client, or subject names ("a recent two-camera shoot", not "the Hendricks wedding").
Read it back, and only when they approve:
ruby lib/buttercut/report.rb send \
--kind feature \
--title "Support multicam angles in exports" \
--narrative "Shoots weddings with two cameras and syncs them by hand in Resolve after exporting. Wants both angles to land on the timeline already lined up."
If they've saved an email (ruby lib/buttercut/report.rb consent shows it), it rides along automatically so the team can reply. If they haven't and they'd want an answer, offer to add error_report_email: to libraries/settings.yaml.
Then confirm it landed, without promising it'll get built:
"Sent — that's with the ButterCut team now. No promises on timing, but they read every one."
Don't show them the JSON, the UUID, or a status code. If the send failed, say so plainly and offer to try again later.
Developer mode. With .buttercut_mode present, report.rb send refuses. Use --dry-run to see what would go.