AGENT SKILL
video-prep-skill
暂无简介
- License 许可
- MIT
- 最近更新
- 2026-10-21
- Stars
- ★ 0
- Forks
- 0
02 资源文件 28
- 参考文档.github/workflows/ci.yml417 B
- 其他.gitignore46 B
- 脚本bin/video-prep-skill.js1.6 KB
- 参考文档CHANGELOG.md1.0 KB
- 参考文档CONTRIBUTING.md188 B
- 参考文档docs/CLAIM_CHECKLIST.md465 B
- 参考文档docs/EXAMPLES.md376 B
- 参考文档docs/ORCHESTRATION.md725 B
- 参考文档docs/PRD.md896 B
- 参考文档docs/RELEASE_CANDIDATE.md328 B
- 参考文档docs/RELEASE_CHECKLIST.md469 B
- 参考文档docs/TASKS.md647 B
- 参考文档examples/sample-brief.json2.3 KB
- 参考文档fixtures/malformed-scripts-repo/package.json332 B
- 参考文档fixtures/malformed-scripts-repo/README.md121 B
- 参考文档fixtures/readme-fallback-repo/README.md209 B
- 许可证LICENSE1.0 KB
- 参考文档package-lock.json348 B
- 参考文档package.json1.3 KB
- 参考文档README.md4.1 KB
- 脚本scripts/check-task-status.mjs1.6 KB
- 脚本scripts/package-smoke.js852 B
- 脚本scripts/validate.sh76 B
- 参考文档SECURITY.md181 B
- 脚本src/core.js10.0 KB
- 脚本test/cli.test.js4.7 KB
- 脚本test/core.test.js11.0 KB
- 脚本test/task-status.test.js2.8 KB
03 SKILL.md 正文
Video Prep Skill
When To Use
Use this skill when an agent needs to prepare a practical launch, demo, or walkthrough video from a software repository. It is best for short scripts, release teasers, demo prep, and repo-to-content workflows.
Required Inputs
- A local repository path.
- Optional audience and desired viewer outcome.
- Optional format selection:
textorjson.
Tools
- Local filesystem read access.
- Node.js 20 or newer.
- No network access is required.
Side-Effect Boundaries
The skill is read-only. It must not publish video, post to social platforms, edit the target repository, create branches, or call external media APIs. Any external action requires a separate explicit approval step.
Workflow
- Use the first generated demo command when one is present; otherwise run the CLI manually and inspect its output.
- Run the CLI against the target repo.
- Check that every claim in the brief maps to repository evidence.
- Remove or rewrite weak claims before recording.
- Run the target repo's listed verification commands before mentioning them in public copy.
The generated brief names only non-empty smoke, test, check, or build
package scripts found in the target repository. Do not turn an absent or
malformed script into a command claim; retain the CLI/manual fallback instead.
Examples
node bin/video-prep-skill.js fixtures/sample-repo --format text
node bin/video-prep-skill.js ../my-tool --audience "open source maintainers" --outcome "run the smoke test"
Validation
Run:
npm run check
npm test
npm run smoke