OPC 短视频脚本审核

SKILL内容创作
内容创作 未标注权限 许可证不明确
安装这个技能

审核短视频脚本、判断爆款潜力并给出可执行改稿建议。支持抖音、TikTok、Reels、Shorts、小红书、B站、视频号、快手等平台,可分析 hook、结构、留存、情绪、互动、CTA 和平台适配。发布后还能根据后台数据截图或 CSV 表格做归因复盘,给出下一条内容的优化测试,并沉淀账号专属经验。

一句话选型结论

按资料字段整理

OPC 短视频脚本审核是内容创作类的 Agent Skill,安装方式未标注,权限级别未标注,许可证不明确,有可直接复制的安装命令。技能本质是给模型读的说明书,效果取决于模型与客户端;装完先用一个小任务验证,再放进正式流程。

分类内容创作 安装方式未标注 权限级别未标注权限 许可证许可证不明确
累计安装 未标注 本周 未标注
GitHub 星标 未标注 仓库 未标注
下载量 未标注 技能市场下载数
权限级别 未标注权限 安装前请确认风险范围
许可证 许可证不明确 未说明

安装

未标注
在支持 Skills 的客户端里执行,装完问一句「你有哪些技能」验证
skillhub install user_ccb113d8/opc-short-video-review
  1. 1
    确认客户端支持

    确认你的客户端支持 Skills(Claude、Codex、Cursor 等),并升级到较新的版本。

  2. 2
    拿到技能文件

    执行上面的命令安装;也可以把仓库里的 SKILL.md 手动放进客户端的 skills 目录。

  3. 3
    刷新技能列表

    重新打开客户端,或刷新技能列表,让新放进来的技能被加载。

  4. 4
    验证是否生效

    问一句「你有哪些技能」,确认列表里出现它,再拿一个小任务试跑。

技能档案

内容创作
字段来自技能仓库与公开索引,中文说明由本站标注
作者 / 维护方user_ccb113d8仓库 未标注 · 版本 未标注
宿主客户端未标注技能可被这些客户端加载
安装方式未标注安装包 community
权限级别未标注权限安装前请确认风险范围
许可证未说明许可证不明确,商用前请自行确认条款
仓库可用性available技能仓库当前是否可访问
最近核验未标注上游最后核验时间 · 数据更新 1791737279
正文体量7.4 KBSKILL.md 原文大小,越大说明说明书写得越细

典型使用场景

3 类
按分类整理的常见用法,具体以 SKILL.md 为准
写文章与脚本

按主题产出初稿与分镜脚本。

改稿与润色

把草稿改顺、统一语气。

多平台文案改写

同一内容按平台改成长短不同的版本。

选择建议

装之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有可直接复制的安装命令,不用自己翻文档找入口。

先想清楚的地方

  • 没有标注权限级别,实际能做什么要装好后确认。
  • 许可证不明确,商用或二次分发前先到仓库确认条款。
  • 没有做站内核验,内容以作者仓库为准。
  • 技能只是说明书,实际效果取决于模型与客户端,装完先用小任务试一遍。

更适合

  • 需要在内容创作场景里给模型补一套做法的人。
  • 愿意先读一遍 SKILL.md、确认它会让模型做什么的人。

不太适合

  • 对许可证要求很严、必须明确可商用的人。
  • 只想装完就自动变强、不打算看说明书的人。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
技能权限级别安装方式累计安装宿主客户端安装命令
OPC 短视频脚本审核当前 未标注权限 未标注 未标注 未标注 有
AI 视频生成 调用外部服务 GitHub 仓库 431.3 万 Codex、Claude、Cursor 有
视频帧 联网访问 ClawHub 市场 262.1 万 OpenClaw 有
Markdown 转换器 写入文件 ClawHub 市场 135.3 万 OpenClaw 有
哔哩哔哩全合一 接触敏感数据 ClawHub 市场 64.1 万 OpenClaw 有
Remotion video toolkit 命令行 浏览器控制 ClawHub 市场 63.9 万 OpenClaw 有

SKILL.md 全文

7.4 KB
模型实际读到的说明书原文,来自技能仓库

OPC Short Video Review

Purpose

Use this skill as a closed loop: pre-publish script review -> publish hypothesis -> post-publish data review -> reusable experience. Treat 爆款潜力 as a directional, explainable judgment, not a promise. Every recommendation must say what to change, why it should affect a metric, and how to verify it after publishing.

Runtime Portability

Keep the skill portable across Codex, Claude Code, OpenClaw, Hermes, and similar agents:

  • Use only name and description in required frontmatter. Do not rely on platform-specific metadata to trigger the core workflow.
  • Resolve supporting files relative to the folder containing this SKILL.md. If the runtime cannot access supporting files, answer from this file and ask the user to provide the relevant reference text.
  • Before using shell scripts, confirm the runtime has a local shell and the uploaded file has a local path. If not, parse tables/screenshots manually.
  • Do not auto-write case-library files or make git commits. Return proposed entries first; only persist them when the user explicitly asks.
  • For install paths and packaging notes, read runtime-portability.md.

Mode Selection

Choose the workflow from the user's input:

  1. Script Audit: draft script, outline, title, cover, storyboard, or multiple variants.
  2. Variant Comparison: multiple hooks, covers, titles, openings, scripts, or CTAs.
  3. Post-Publish Data Review: analytics screenshot, CSV export, table, or reported metrics.
  4. Cross-Platform Adaptation: adapting one script between Douyin/TikTok/Reels/Shorts/Xiaohongshu/Bilibili/Video Channels/Kuaishou.
  5. Experience Accumulation: summarizing lessons, updating account-specific calibration, or comparing many past videos.

If the stage is genuinely unclear, ask whether the user wants pre-publish review, variant comparison, or post-publish review. Otherwise proceed with explicit assumptions.

Context Checklist

Gather only what changes the recommendation:

  • Platform, account/niche, target audience, account stage, product/offer, desired goal, target duration, script/shot list, cover/title/caption, production constraints.
  • For data review: views, impressions/reach, duration, average watch time, retention, completion rate, likes, comments, shares, saves, follows, profile clicks, link clicks, conversions, traffic source, publish time, cover/title, and original script.
  • If account history exists, read case-library/calibration-notes.md before scoring. If the file is absent or empty, say the judgment is based on general priors.

Script Audit

Use this workflow for new scripts and variants:

  1. Read content-platform-profiles.md for the target content platform.
  2. Read script-audit-rubric.md.
  3. If calibration notes exist for the account/niche, use them to adjust the generic rubric.
  4. Return the report using review-report-template.md.
  5. Include at least one direct rewrite. For weak scripts, prioritize the first 3 seconds and the core promise before polishing style.
  6. End with a publish hypothesis: the metric that should move if the recommendation is right.

Do not give fake precision such as "爆款率 67%". Prefer a potential band, confidence level, and biggest uncertainty. A numeric score is allowed only as a rough internal scorecard.

Variant Comparison

Use this workflow when the user provides multiple hooks, titles, covers, scripts, endings, or CTAs:

  1. Read variant-testing.md.
  2. Compare variants side by side against the user's platform and goal.
  3. Give a clear winner or a fused version; do not average everything into a bland compromise.
  4. Design a measurable test with the primary metric, sample rule, and what decision to make afterward.

Data Review

Use this workflow after publishing:

  1. Read data-review-playbook.md.
  2. If a CSV path is available and shell execution is allowed, run the metrics helper from the skill directory:
python3 scripts/analyze_metrics.py <path-to-csv>
  1. Normalize raw counts into rates and compare against the account's own baseline first. The helper provides batch medians and initial signals, but final attribution still requires script/platform context.
  2. Connect metric behavior back to exact script choices: hook, promise, pacing, proof, emotion, interaction design, CTA, or platform packaging.
  3. Separate script causes from non-script causes such as cover, title, edit, audio, publish time, platform trend, or randomness.
  4. Return next tests, not just an explanation of what happened.

Experience Loop

When there is a script review, prepare a case entry with status 待回收数据. When data returns, update the same entry with status 已复盘. Use case-entry-template.md and experience-bank.md.

Persistence rules:

  • If the user asks only for advice, include the proposed case entry in the answer but do not write files.
  • If the user asks to save/update experience, append to case-library/cases.md and update case-library/calibration-notes.md only when the lesson has evidence.
  • Mark one-video findings as low-confidence hypotheses.
  • Preserve failed tests and contradictions; they are useful calibration data.

Output Principles

  • Lead with a verdict and bottleneck.
  • Give concrete rewrites, not generic "更抓人".
  • Tie every recommendation to a metric: retention, completion, like, comment, share/save, follow, lead, or conversion.
  • Optimize for the user's stated goal; a sales video and a pure reach video should not be judged by the same weights.
  • Protect creator voice. Sharpen the script without turning every account into the same viral template.
  • Never guarantee virality, revenue, distribution, or algorithmic outcomes.

Resource Index

  • runtime-portability.md: install and compatibility notes for Codex, Claude Code, OpenClaw, Hermes.
  • content-platform-profiles.md: content platform differences and cross-posting rules.
  • script-audit-rubric.md: scoring dimensions and rewrite moves.
  • variant-testing.md: hook/title/script comparison and A/B test design.
  • data-review-playbook.md: metric diagnosis and next-test logic.
  • experience-bank.md: evidence-based lesson format.
  • review-report-template.md: pre-publish report template.
  • case-entry-template.md: case-library entry template.
  • analyze_metrics.py: CSV metric normalization helper.

常见问题

5 问
答案由本站依据条目字段整理
OPC 短视频脚本审核怎么安装?

在支持 Skills 的客户端里执行:skillhub install user_ccb113d8/opc-short-video-review。安装方式为未标注。装完刷新技能列表或重开客户端。

OPC 短视频脚本审核支持哪些客户端?

资料没有标注宿主客户端,但只要客户端支持 Skills(Claude、Codex、Cursor 等),一般都能加载。

OPC 短视频脚本审核权限高吗,安全吗?

权限级别为未标注权限。安装前先看它会读取或写入哪些内容。

OPC 短视频脚本审核收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于技能本身和所用的模型或客户端,正式使用前按作者说明确认。

OPC 短视频脚本审核用什么许可证?

许可证标注为 未说明(许可证不明确)。商用或二次分发前请到仓库确认条款原文。

热门专题

按场景挑技能
全部专题 →

技能内容以作者仓库为准;分类、权限级别与许可证状态的中文说明为中文整理,最近核验 未标注。