AC douyin-guoxue-volcengine-pipeline
Create and publish Chinese metaphysics / guoxue / I Ching short videos for Douyin using a verified multi-shot pipeline: Volcengine image generation + Volcengine video generation + Edge TTS dubbing + ffmpeg stitching + Douyin publish + backend verification. Use when the user wants 国学/易经/卦象/乾卦/坤卦/泰卦 style short videos, especially when they want 3-second shot changes instead of a single looping shot, AI-assisted visual generation, or a reusable Douyin production workflow. 中文：用于抖音国学/易经/卦象短视频的多镜头生产发布流程，包含火山文生图、火山图生视频、Edge TTS 配音、ffmpeg 合成、抖音发布和后台回查。适用于“做一条乾卦/坤卦/泰卦视频”“3秒换镜头”“国学短视频自动生成并发布”等请求。
As a process C 57/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Create and publish Chinese metaphysics / guoxue / I Ching short vi… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 57/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 16 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 38 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 813 tokens
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -4Absolute local paths (C:\Users, /home/…): not portable
- +1No license
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +3Description length 593: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 38 items
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.