agentleFS
BryceYuuuBryceYuuu/open-workflow-skills/skills/auto-bgm/SKILL.md

auto-bgm

Skill1 starsChanged 2 months agoMITView on GitHub

Analyze scene and pacing to suggest or place background music and apply ducking; music selection remains subjective. Use when the user asks for auto bgm or an equivalent workflow.

  • Installs packages

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 11 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈11

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the user explicitly requests auto bgm, or when the requested outcome clearly matches this workflow.

    line 45
  2. Distinctive:

    Do not activate it merely because the topic is related.

    line 47
  3. Distinctive:

    Treat permissions as capabilities to request or verify, not as permissions automatically granted by installing the skill.

    line 69
  4. Distinctive:

    Verify all expected outputs exist and are readable.

    line 124
  5. Distinctive:

    Verify the source was not unintentionally overwritten.

    line 125
  6. Distinctive:

    Verify structured outputs against their expected schema or invariants.

    line 126
  7. Distinctive:

    Never mark the workflow successful solely because a model produced text.

    line 128
  8. Distinctive:

    Do not invent source facts or claim an external action succeeded without verification.

    line 134
  9. Distinctive:

    If a dependency, credential, connected service, browser session, file, or required permission is unavailable:

    line 141
  10. Distinctive:

    Stop the affected step.

    line 143
  11. Distinctive:

    Do not fabricate a successful result.

    line 146

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Auto BGM / 视频自动配乐

Purpose / 用途

中文

分析视频情绪和节奏,生成或匹配背景音乐并进行 Ducking;选曲质量仍具有主观性和版权约束。

English

Analyze scene and pacing to suggest or place background music and apply ducking; music selection remains subjective.

Status / 状态

  • Workflow status: 🟡 Experimental / Assisted / 实验性 / 辅助型 / 辅助完成
  • Implementation: 📘 Definition only / 仅工作流定义
  • Audit grade: C
  • Quality score: 2.5/5
  • Automation level: L3
  • Category: Content & Media / 内容创作与媒体

Workflow status describes how well the workflow itself is understood. Implementation status separately tells you whether this repository ships runnable code for it. Integration skills still require external services or authorization; experimental skills may need more human review.

Search aliases / 搜索关键词

auto-bgm · Auto BGM · 视频自动配乐 · automatic background music · video BGM · music ducking · 视频配乐 · 自动BGM · AI content automation · content automation · video automation · social media automation · 内容自动化 · 视频自动化

When to use / 何时使用

Use this skill when the user explicitly requests auto bgm, or when the requested outcome clearly matches this workflow.

Do not activate it merely because the topic is related. Confirm the input, desired output, and any consequential external action.

Inputs / 输入

  • Video/audio file or URL
  • Desired language/style/output constraints

Outputs / 输出

  • Content/media outputs
  • Manifest / QA notes

Core stack / 核心工具

Audio analysis / music source / FFmpeg

Permissions / 权限

  • filesystem:read
  • filesystem:write
  • network:optional

Treat permissions as capabilities to request or verify, not as permissions automatically granted by installing the skill.

Workflow / 工作流

  1. Inspect / 检查输入 — Verify source files/data, format, scope, and user constraints.
  2. Plan / 制定计划 — Select the deterministic tools, model calls, and external integrations needed.
  3. Preflight / 运行前检查 — Check dependencies, credentials, permissions, destination paths, and destructive-action risk.
  4. Execute / 执行 — Run the smallest reliable sequence of steps. Prefer deterministic code for calculations, parsing, rendering, and file operations.
  5. Validate / 验证 — Verify output structure, counts, schemas, file readability, test results, or other task-specific invariants.
  6. Review / 审核 — For subjective or consequential outputs, present a reviewable result before external publication, sending, payment, deployment, signing, or irreversible action.
  7. Report / 汇报 — State what was produced, where it was saved, what was verified, and what still needs human review.

Dependency suggestions / 依赖建议

  • macOS: brew install ffmpeg
  • Ubuntu/Debian: sudo apt-get update && sudo apt-get install -y ffmpeg

The Agent Skill itself should remain installable even when optional runtimes are absent. Report missing runtime dependencies instead of silently installing privileged software.

Install / 安装

Inspect before installing

npx skills add BryceYuuu/open-workflow-skills --list

Install this skill into the current project

npx skills add BryceYuuu/open-workflow-skills --skill auto-bgm

Install for a specific supported agent

npx skills add BryceYuuu/open-workflow-skills --skill auto-bgm --agent codex

npx skills is a community ecosystem CLI, not an OpenAI-official installer. Review third-party skills and scripts before granting shell, filesystem, network, or credential access.

Example invocation / 调用示例

中文

使用 auto-bgm 工作流处理我提供的输入。先检查依赖和权限,不覆盖源文件;执行后给我输出路径、验证结果和需要人工审核的部分。

English

Use the auto-bgm workflow for the provided input. Check dependencies and permissions first, preserve the source, validate the result, and report outputs plus any human-review items.

Validation / 验证

At minimum:

  • Verify all expected outputs exist and are readable.
  • Verify the source was not unintentionally overwritten.
  • Verify structured outputs against their expected schema or invariants.
  • Record warnings, skipped steps, external dependencies, and failed checks.
  • Never mark the workflow successful solely because a model produced text.

See references/QUALITY.md for skill-specific quality expectations.

Safety / 安全

  • Do not invent source facts or claim an external action succeeded without verification.
  • Preserve source files unless the user explicitly requests in-place modification.
  • Surface missing dependencies, permissions, credentials, and failed checks clearly.
  • Label generated outputs as candidates or assisted results and require human review before consequential use.

Failure handling / 失败处理

If a dependency, credential, connected service, browser session, file, or required permission is unavailable:

  1. Stop the affected step.
  2. Preserve completed safe outputs.
  3. State exactly what is missing.
  4. Do not fabricate a successful result.
  5. Suggest the minimum next action needed to continue.

Files / 文件

  • SKILL.md — workflow instructions
  • references/QUALITY.md — quality/evaluation guidance
  • tests/cases.yaml — example evaluation cases

Implementation scripts may be added under scripts/ when deterministic execution materially improves reliability.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.