AF vss-summarize-video
Use to summarize a recorded video via the LVS summarization microservice (HITL-gated) with a VLM fallback. Not for report generation or live RTSP captioning.
Use to summarize a recorded video via the LVS summarization microservice (HITL-gated) with a VLM fallback.
As a process F 50/100 · Will not run — References files that are not bundled: references/video-summarization-debugging.md, references/video-summarization-api.md, references/video-summarization-deployment.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/video-summarization-debugging.md - warning
missing-refreference to a missing file: references/video-summarization-api.md - warning
missing-refreference to a missing file: references/video-summarization-deployment.md - warning
missing-refreference to a missing file: references/video-summarization-environment-variables.md - warning
missing-refreference to a missing file: references/hitl-prompts.md - warning
missing-refreference to a missing file: references/end-to-end-example.md - warning
missing-refreference to a missing file: assets/video-summarization.env.example - note
edit-residuethe text marks something as outdated (lines 249): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 50/100
- 0Tools and files. 7 referenced file(s) missing: references/video-summarization-debugging.md, references/video-summarization-api.md, references/video-summarization-deployment.md
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 26 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 4583 tokens
- 85Steps. 45 steps, 1 vague phrases
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 18 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (3 tags): a typed call is more reliable
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
- +5Description has no quoted example phrases that should trigger the skill
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 157: enough signal without eating the budget
- +4Structure: 20 headings
- +3Step-by-step instructions: 45 items
- +4Has examples (4 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.