Other skills

用户要给视频做封面、要封面大字，或要标题和封面一起出时用：读文稿提炼卖点，给几组标题与封面文案，用户挑定后按视频画幅生成封面图，放进这个视频的候选素材。每句都由视频兑现。只要标题或简介、不要封面时用起标题与写简介。需要视频的转写。

The English summary is being prepared. Showing the original description.

一两个人对着镜头说话的录音要剪成能发布的视频时用：去掉口癖、长停顿、录废重来的部分和离题的话，在几遍重录里挑一遍，收紧句间停顿，把最有力的原话挪到开头，再按需要加放大强调、B-roll、竖屏取景和配乐闪避。需要视频的转写。只想从长视频里挑几段短视频时用切短视频。

The English summary is being prepared. Showing the original description.

视频的转写要校对或润色时用：改错字与误听，统一术语与专名，补正标点与分句，写回同一份转写，词的时间不变。做译文之前先做这一步；已经建好的原文字幕层写回时跟着改字。默认不改语法、不删口癖、不精简；去掉口癖与停顿是剪辑，不在这里做。不用于润色与视频无关的文章或纯文本。

The English summary is being prepared. Showing the original description.

用户要把视频的转写或字幕翻译成另一种语言、做双语字幕，或更新原文改动后过期的译文时用：逐句翻译写成视频里的译文文档，再放到画面上、按需导出。有媒体时「翻译」默认指字幕翻译。不用于翻译与视频无关的文章、文档或一段纯文本；对话里没有视频或字幕、又看不出指的是什么时先问一次。

The English summary is being prepared. Showing the original description.

用户有一个长视频（访谈、讲座、直播回放、口播），想从中切出几支能单独发布的短视频时用：读转写找出最值得发的话题，每个话题从开头的钩子剪到讲完，建成可编辑的子视频，用户在编辑器里接着调；几支、每支多长可以交给你按话题定。需要视频的转写。不用于按主题从零做一个新的短视频，也不用于把整段口播剪干净（用剪口播）。

The English summary is being prepared. Showing the original description.

用户要为准备发布的视频起标题、要几个标题候选、再来一批或照某个再来几个，或要写视频简介（视频页标题下的说明文字、章节列表、标签）时用。写给发布视频的人：吸引人，并且每句都由视频兑现。需要视频的转写。不用于给文章起标题等与视频无关的写作。

The English summary is being prepared. Showing the original description.

视频里有几个人说话、要区分是谁在说或给说话人标名字时用：没区分说话人的文稿按声纹重新转录并区分，再从文稿与来源信息里找证据给每位起真名，写回转写的 speakers。只改说话人，不改正文的字。只有一个人说话、或用户只要校对错字时不用。

The English summary is being prepared. Showing the original description.

Turn incoming reports, external PRs and alerts into evidence-based decisions and agent-ready briefs. Use when: intake arrives. For accepted work, use Plan.

The English summary is being prepared. Showing the original description.

Maintain the official OpenMeld Changelog from repository evidence. Use when deciding whether a change needs a Changelog entry, writing or publishing an entry, preparing release notes, validating generated Changelog files, or historically backfilling missing changes.

The English summary is being prepared. Showing the original description.

Use when diagnosing a Wake that failed, stalled, or produced no visible reply — dispatch, setup handoff, or reply-path issues. Routes to the deterministic trace evidence path.

The English summary is being prepared. Showing the original description.

Use when deciding whether an OpenMeld change needs a Changelog entry, writing or publishing an entry, preparing release notes, validating Changelog projections, or historically backfilling missing changes.

The English summary is being prepared. Showing the original description.

Use when the user asks how clueless works, what its commands or levels are, or types /clueless-help.

The English summary is being prepared. Showing the original description.

Use when the user explicitly cannot review the output in the current domain, says they do not understand it or will copy-paste without checking, or requests clueless mode. Examples: "I know nothing about this", "не разбираюсь", "сделай за меня". Brevity, "make it nice", and delegation alone do not establish a knowledge gap.

The English summary is being prepared. Showing the original description.

Coordinate multi-step work across services the user has authorized through Aident Loadout, using live action schemas, connection checks, cost preflight, and explicit approval for side effects.

The English summary is being prepared. Showing the original description.

Operate Gas City through its own doors: Mayor, doctor and native run state. Use when: Gas City is selected or a gc run looks stuck.

The English summary is being prepared. Showing the original description.

Tear down a competitor's repo or product into a feature inventory and adoption choices. Use when: comparing us to another tool or asking what to steal.

The English summary is being prepared. Showing the original description.

Measure whether a skill helps by comparing runs with and without it. Use when: reading skill A/B results or deciding to keep, revise or remove one.

The English summary is being prepared. Showing the original description.

Drive one accepted change through implementation and checks to done, with one fresh review only where a mistake is costly. Use when: asked to run or orchestrate work through RPI.

The English summary is being prepared. Showing the original description.

Freshly judge whether a finished change and its claims meet original acceptance: PASS, FAIL or NOT_PROVEN. Use when: asked for a go/no-go, sign-off or independent verdict.

The English summary is being prepared. Showing the original description.

Find how a rollout plan could fail before committing to it. Use when: asked what could go wrong or to poke holes in a plan.

The English summary is being prepared. Showing the original description.

Pick the next work in an epic or bead graph; closed is not proven. Use when: asked what is next or whether an epic is done.

The English summary is being prepared. Showing the original description.

Coordinate several workers: what idle agents do next, which finished work gets checked first, how to recover a dead one. Use when: managing multiple agents.

The English summary is being prepared. Showing the original description.

Compare independent opinions from several models or contexts without inflating agreement. Use when: wanting a second opinion or debate, or summarizing several reviewers' results.

The English summary is being prepared. Showing the original description.

Write source-checked docs, READMEs, change descriptions and handoffs. Use when: documenting a change, leaving or resuming a handoff, or drafting a questionnaire for someone else.

The English summary is being prepared. Showing the original description.