Daytona Flow Validator

Daytona Flow Validator is a Quality skill for Claude Code, published by Devin-AXIS in iPolloWork.

4.3K stars825 forkson Devin-AXIS/iPolloWorkAdded 2026/08/20Repository updated 2026/08/20

agent-collaborationagent-skillsai-agentsai-workclaude-codecodexdeepseek-harnessdsh-pluginenterprise-agent-workspacehermes-agentipollowork-pluginipollowork-skillopenclawopencodeopencode-pluginself-evolving-aivisual-editor

Install in seconds

Install Daytona Flow Validator

Copy Daytona Flow Validator into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/Devin-AXIS/iPolloWork/tree/main/.opencode/skills/daytona-flow-validator ~/.claude/skills/daytona-flow-validator

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/Devin-AXIS/iPolloWork.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: .opencode/skills/daytona-flow-validator/SKILL.md in Devin-AXIS/iPolloWork
Installs to: ~/.claude/skills/daytona-flow-validator
Collection: One of 25 skills cataloged from this repository
Category: Quality — 1354 skills

What Daytona Flow Validator does

Daytona Flow Validator validates Daytona Electron and browser flows end-to-end using CDP to drive real user journeys, capture frame-by-frame HTML proof, and repair failures before declaring success. Use it when you need pass/fail evidence for UI features in Daytona or iPolloWork.

Daytona Flow Validator is cataloged under Quality on DirSkills. Daytona Flow Validator comes from a repository tagged agent-collaboration, agent-skills, ai-agents, ai-work and claude-code.

Documentation

README

Excerpt

Daytona Flow Validator

Use this skill to decide whether a Daytona Electron or browser flow actually works. Launching the sandbox is separate. This skill owns the feedback loop.

Core Rule

Never report success from a click, script return value, or recording alone. Validate the same path a human would take, using CDP to drive Chrome or Electron instead of replacing the journey with hidden state changes. Every meaningful action must follow this loop:

Observe with browser_snapshot first.
Act with browser_click or browser_fill against snapshot UIDs whenever possible.
Observe again with browser_snapshot.
Assert the expected URL, text, state, process, network, or file result.
Capture a screenshot checkpoint when the visible state matters.

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Daytona Flow Validator

What else does Devin-AXIS publish alongside Daytona Flow Validator?
Daytona Flow Validator is one of 25 skills that DirSkills catalogs from Devin-AXIS/iPolloWork, the repository it ships in. Its siblings there include Acme Research, Agent-First Screenshots and Browser Automation. Each one is a separate skill with its own page in this directory, installs the same way Daytona Flow Validator does, and is maintained by Devin-AXIS in that same repository. The rest of the collection is listed on the Devin-AXIS/iPolloWork page.
How does Daytona Flow Validator compare to other Quality skills?
Daytona Flow Validator ranks #324 by stars among the 1354 Quality skills in this catalog. The most-starred ones next to it are Benchmark, Benchmark Optimization Loop and API Design Patterns. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Daytona Flow Validator against them. Open each page to compare what they document and how they install.