CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

proof-video

Capture, edit, inspect, and attach real ClawHub browser proof directly to a GitHub PR, with captions, focused zooms, and clearly separated before/after results.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/proof-video/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a strong, disciplined operational guide: fully executable commands, an explicit multi-phase workflow with real validation checkpoints, and lean prose that assumes competence. The only notable gaps are minor inline detail that could be trimmed or moved to reference files and references that are mentioned rather than clearly signaled.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence — no basic-concept explanations (ffmpeg, Playwright, GitHub attachments are used, not taught) and every section carries project-specific constraints. It is not a 5 because of minor trimmable material: the provenance paragraph about OpenClaw's original skill and the version-sensitive empirical Chromium deviceScaleFactor anecdote, which reads like reference detail inlined in the main flow.

4 / 5

Actionability

Fully executable, copy-paste-ready commands cover the common cases: the runner invocation ("bun run proof:ui -- --runner local --mode feature --scenario .artifacts/proof-scenarios/example.pw.ts --candidate-url http://127.0.0.1:3000"), the ffmpeg transcode command, and the gh attachment command with flags, formats, and the 100 MB limit. Concrete details like accepted extensions ('.mp4', '.mov' or '.webm', never a #alt suffix') and the bare-line player rendering rule go beyond the score-4 anchor's 'minor gaps'.

5 / 5

Workflow Clarity

The sections form a clear sequence — Establish the claim → Capture → Edit → Inspect before publishing → Attach to the PR — with explicit validation checkpoints and feedback loops: "Open every final screenshot and inspect every video across its full timeline", "Re-capture or re-edit anything misleading, blank, clipped or stale", and "Verify the posted comment contains the intended image/video URLs". Failure handling is also explicit ('retain the local media and report the precise failed operation; do not claim publication'), matching the top anchor.

5 / 5

Progressive Disclosure

Good structure: five well-scoped sections at a reasonable length (~80 lines), with pointers to detail files ("See scripts/ui-proof-runtime.mjs for the scenario contract and specs/ui-proof.md for runtime isolation"). It is not a 5 because those references are plain inline code mentions rather than clearly signaled navigation links, no bundle files are provided alongside the skill, and some deep editing detail (zoom/remap/frame-rate mechanics) could live in a reference file.

4 / 5

Total

18

/

20

Passed

Description

63%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and action-oriented, clearly stating what the skill does across its full pipeline, and is reasonably distinct. Its main weaknesses are the absence of any 'Use when…' trigger guidance and the omission of the most natural trigger terms — 'video' and 'screenshot' — which limit discoverability and completeness.

Suggestions

Add an explicit 'Use when…' clause, e.g. 'Use when asked to record video or screenshot proof of a UI change, attach PR evidence, or demonstrate a before/after fix.'

Include the natural trigger words 'video', 'screen recording', and 'screenshot' — the skill's primary output formats — which are currently missing from the description.

Mention the formats/verbs users would naturally say (e.g. 'MP4 clips', 'attach evidence to a pull request') to strengthen keyword coverage and distinctiveness.

DimensionReasoningScore

Specificity

"Capture, edit, inspect, and attach real ClawHub browser proof directly to a GitHub PR, with captions, focused zooms, and clearly separated before/after results" lists multiple concrete actions (capture, edit, inspect, attach) plus output specifics (captions, zooms, before/after separation), covering the pipeline comprehensively. It exceeds the score-4 anchor because there are no meaningful gaps in the action coverage, not merely 'several specific actions with minor gaps'.

5 / 5

Completeness

The 'what' is clearly and specifically answered (capture/edit/inspect/attach proof on a GitHub PR), but there is no 'Use when…' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 2 because the 'what' is concrete rather than vague, and not a 4 because no 'when' is present even weakly.

3 / 5

Trigger Term Quality

Relevant keywords are present ("proof", "browser", "GitHub PR", "captions", "before/after"), but the most natural terms a user would say — "video" (the skill's own name and primary output format) and "screenshot" — are entirely absent. It sits below the score-4 'good keyword coverage, a few natural terms missing' anchor because the missing terms are the most common trigger phrases, not just a few synonyms.

3 / 5

Distinctiveness Conflict Risk

"real ClawHub browser proof directly to a GitHub PR" carves a distinct niche unlikely to trigger for unrelated skills, with only minor overlap risk against generic screenshot/video-capture or PR-review skills. It does not reach 5 because without explicit trigger phrasing, generic requests like 'record a video' or 'take a screenshot' could plausibly match it.

4 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

openclaw/clawhub

Path

.agents/skills/proof-video/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.