Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
factory-ai avatar

Verify

  • 72 installs
  • 101 repo stars
  • Updated August 4, 2026
  • factory-ai/factory-plugins

Helps with ai & agent building tasks.

About

verify is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted development.

  • verify
  • AI & Agent Building
  • AI-coding skill

Verify by the numbers

  • 72 all-time installs (skills.sh)
  • Ranked #5,605 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/factory-ai/factory-plugins --skill verify

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs72
repo stars101
Last updatedAugust 4, 2026
Repositoryfactory-ai/factory-plugins

What it does

Helps with ai & agent building tasks.

Files

SKILL.mdMarkdownGitHub ↗

Verify

The orchestrator routed you here. This atom checks the final deliverable against the commitments made at the start of the workflow.

Inputs

You receive:

1. Commitments from the command's parse step -- the promises made about what the deliverable would contain 2. Compose outputs -- the finished artifact(s) and their metadata

Video deliverables

Technical checks

Run ffprobe on the final .mp4:

ffprobe -v quiet -print_format json -show_format -show_streams <video>
CheckPass condition
Exists and playsffprobe exits 0, duration > 0
Resolution1920x1080 (or target resolution)
Pixel formatyuv420p
File sizeUnder 5 MB for GitHub embeds (25 MB hard limit)
DurationMust fall within the compose pacing table's target range for this demo type: 30-45s (single feature), 45-75s (side-by-side comparison), 60-120s (multi-phase). Below the minimum is a failure — re-compose with a lower speed factor or re-capture with more steps.
FilenameIncludes PR number or meaningful identifier

Commitment checks

Walk through each commitment from the parse step:

CommitmentHow to verify
Title cardVideo starts with a static frame showing PR info (check first 5s)
Side-by-side layoutVideo shows two panels with a divider
Showcase polishResolution is 1920x1080, window chrome and rounded corners visible
Keystroke overlayPill overlays appear at interaction points
EffectsEffects matching the committed tier are present (utilitarian: zoom/keystroke; full: spotlight, zoom, callout, keystroke)
Speed noteTitle card mentions playback speed

Content checks

  • Every claim from the "what to prove" analysis has visible evidence in the video
  • Both states (before/after, input/result) appear on screen
  • No dead time longer than 3 seconds without visible activity

Screenshot/snapshot deliverables

For proofs

CheckPass condition
Evidence existsScreenshots/snapshots at every claimed proof point
Environment statedDriver, terminal/browser, OS identified
Conclusion presentEvidence explicitly supports or refutes the claim
Before/after pairedIf comparison, both branches shown at same capture points

For QA reports

CheckPass condition
Step coverageEvery defined test step has a result (PASS/FAIL)
Evidence attachedScreenshots/snapshots at every step
Failures documentedFailed steps have evidence and description
Report structuredMarkdown report follows the QA template

Failure handling

If any check fails:

1. Identify which stage produced the problem (capture or compose) 2. Report the specific failure: "Side-by-side layout was committed but the output is a single panel" 3. Go back to the failed stage and fix it 4. Re-verify after the fix

Do not report a deliverable as complete until every commitment is met.

Output

## Verification

### Technical
- Resolution: 1920x1080 ✓
- Duration: 42s ✓
- Size: 3.2 MB ✓
- Format: yuv420p ✓

### Commitments
- [x] Title card with PR info
- [x] Side-by-side comparison layout
- [x] Showcase hero preset applied
- [x] Keystroke overlay visible

### Content
- [x] Fork creates independent session (visible at 0:18)
- [x] History diverges after fork (visible at 0:32)

All commitments met. Deliverable ready.

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.