nite/video-edit-planner-skill
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: emphasize non-mandatory workflow, support transcription-only use case

Browse Source 
SKILL.md:
- Workflow header: explicit statement that every step is optional
  Example: transcription-only → Steps 1,2,4,5 and stop
- When to Use: add standalone transcription as valid use case
- Don't use for: remove 'pure audio-only transcription' exclusion
- Verification checklist: each item tagged with which step it belongs to
  and whether it can be skipped (e.g. Step 3/8 skip for transcription-only)
This commit is contained in:
nite
2026-07-14 12:21:51 +08:00
parent e56723a68f
commit 5e844d17ec
1 changed files with 15 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
SKILL.md
+15 -10
View File
@@ -28,11 +28,14 @@ The skill is **agent-driven, not scripted**: it provides tools (transcription, c
- User asks "help me edit this video" or "what parts should I cut from this recording."
- User needs to understand video content beyond what the transcript alone reveals.
- User wants an iterative dialogue to refine an edit plan over multiple turns.
- User only needs audio transcription from a video file (extract audio tracks to text). This is a valid standalone use case — not every session requires the full workflow.
**Don't use for:** actual video editing/rendering (this skill plans, it does not produce video files), or pure audio-only transcription.
**Don't use for:** actual video editing/rendering (this skill plans and transcribes, it does not produce rendered video files).
## Workflow
**Every step is optional.** The steps below describe the full end-to-end workflow, but the agent should only execute the steps relevant to the user's request. For example, if the user only wants transcription, execute Steps 1, 2, 4, 5 and stop — no editing goal, frame extraction, vision analysis, or edit plan is needed. Use the user's request to determine which steps apply; do not force the full pipeline when it is not needed.
### Step 1 — Check dependencies
Before any processing, verify the environment. Missing dependencies must be **installed only with explicit user consent**.
@@ -336,12 +339,14 @@ This creates an isolated venv with `funasr`, `torch`, `torchaudio`. If the user
## Verification checklist
- [ ] All dependencies (ffmpeg, uv, python3) confirmed present or user declined.
- [ ] Video path and audio track index confirmed.
- [ ] User's editing goal understood.
- [ ] Transcription completed or reused from cache.
- [ ] Index file initialized at `<video_dir>/<video_stem>.vedit.db`.
- [ ] All extracted clips and frames recorded in the index.
- [ ] Vision analysis performed where needed.
- [ ] Edit plan produced as Markdown table with overall recommendation.
- [ ] User invited to iterate.
Check only the items relevant to the steps actually executed. Not all items apply to every session.
- [ ] Dependencies (ffmpeg, uv, python3) confirmed present or user declined. *(Step 1 — always required)*
- [ ] Video path and audio track index(es) confirmed. *(Step 2 — always required)*
- [ ] User's editing goal understood. *(Step 3 — skip if user only wants transcription)*
- [ ] Transcription completed for all requested tracks, or reused from cache. *(Step 4)*
- [ ] Index file initialized at `<video_dir>/<video_stem>.vedit.db`. *(Step 5 — always required when any processing is done)*
- [ ] All extracted clips and frames recorded in the index. *(Step 6 — only if frames were extracted)*
- [ ] Vision analysis performed where needed. *(Step 7 — only if frames were extracted)*
- [ ] Edit plan produced as Markdown table with overall recommendation. *(Step 8 — skip if user only wants transcription)*
- [ ] User invited to iterate. *(Step 9)*