Ya Run
kzahel/yepanywhere
Launch and drive Yep Anywhere — an isolated dev server plus real browser interaction — and run the repository's check suite.
Launches the iPolloWork Electron app inside a Daytona cloud sandbox with a noVNC desktop, and points to focused skills for server, Chrome, secrets and recordings.
Install Daytona Dev Environment
$ npx skills add Devin-AXIS/iPolloWork --skill daytona-dev -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Devin-AXIS/iPolloWork daytona-dev --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Devin-AXIS/iPolloWork.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.opencode/skills/daytona-dev .claude/skills/daytona-dev && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "daytona-dev" agent skill from https://github.com/Devin-AXIS/iPolloWork/tree/main/.opencode/skills/daytona-dev into .claude/skills/daytona-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "daytona-dev", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Devin-AXIS/iPolloWork/tree/main/.opencode/skills/daytona-devType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Devin-AXIS/iPolloWork --skill daytona-dev -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Devin-AXIS/iPolloWork daytona-dev --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Devin-AXIS/iPolloWork.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.opencode/skills/daytona-dev .agents/skills/daytona-dev && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "daytona-dev" agent skill from https://github.com/Devin-AXIS/iPolloWork/tree/main/.opencode/skills/daytona-dev into .agents/skills/daytona-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "daytona-dev", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Devin-AXIS/iPolloWork --skill daytona-dev -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Devin-AXIS/iPolloWork daytona-dev --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Devin-AXIS/iPolloWork.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.opencode/skills/daytona-dev .cursor/skills/daytona-dev && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "daytona-dev" agent skill from https://github.com/Devin-AXIS/iPolloWork/tree/main/.opencode/skills/daytona-dev into .cursor/skills/daytona-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "daytona-dev", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Devin-AXIS/iPolloWork.git --path .opencode/skills/daytona-dev--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Devin-AXIS/iPolloWork --skill daytona-dev -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Devin-AXIS/iPolloWork daytona-dev --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Devin-AXIS/iPolloWork.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.opencode/skills/daytona-dev .gemini/skills/daytona-dev && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "daytona-dev" agent skill from https://github.com/Devin-AXIS/iPolloWork/tree/main/.opencode/skills/daytona-dev into .gemini/skills/daytona-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "daytona-dev", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Devin-AXIS/iPolloWork daytona-devInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Devin-AXIS/iPolloWork --skill daytona-dev -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Devin-AXIS/iPolloWork.git skills-src && mkdir -p .github/skills && cp -r skills-src/.opencode/skills/daytona-dev .github/skills/daytona-dev && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "daytona-dev" agent skill from https://github.com/Devin-AXIS/iPolloWork/tree/main/.opencode/skills/daytona-dev into .github/skills/daytona-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "daytona-dev", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Devin-AXIS/iPolloWork --skill daytona-dev -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Devin-AXIS/iPolloWork daytona-dev --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Devin-AXIS/iPolloWork.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.opencode/skills/daytona-dev .opencode/skills/daytona-dev && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "daytona-dev" agent skill from https://github.com/Devin-AXIS/iPolloWork/tree/main/.opencode/skills/daytona-dev into .opencode/skills/daytona-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "daytona-dev", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
daytona-dev- GitHub stars
- 6.7k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 515 words
- Files
- 1
- Skills in repo
- 30
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Launches the iPolloWork Electron app inside a Daytona cloud sandbox with a noVNC desktop, and points to focused skills for server, Chrome, secrets and recordings.
- Works in 3 steps: Create and start the sandbox → Get the noVNC URL → Get other URLs
- Starting the iPolloWork Electron app in a Daytona sandbox
- SKILL.md covers Prerequisites, Quick Start, What's Running and Running with Den (full stack), plus 3 more sections
- Calls bash, npx and git
What it does
This skill documents how to run the real iPolloWork Electron app in a Daytona cloud sandbox, using Daytona's XFCE and noVNC desktop stack so you can interact with it from your browser. A helper script, test-on-daytona.sh, takes an optional branch or commit, uses a VNC snapshot, starts noVNC, Vite and Electron, and prints the URLs; if the snapshot is missing, a second script creates it. Afterward you can SSH into the named sandbox or ask Daytona for preview URLs for the noVNC desktop and other services such as the Den web dashboard.
The setup is split into reusable pieces with their own skills: a cloud server and Den flow, two-sandbox Electron plus Den validation, a pass-fail validation loop that collects evidence, standalone Chrome with CDP, a secrets volume for provider keys, real Electron UI tests, and an artifacts volume for screenshots, recordings and PR evidence. You are told to prefer the focused skill when a request names one piece. Prerequisites are the Daytona CLI, installed with Homebrew or from GitHub releases, a Daytona login, and the right organization selected.
When your agent uses it
- Starting the iPolloWork Electron app in a Daytona sandbox
- Getting the noVNC URL to view the app in a browser
- Choosing which focused Daytona skill fits a secrets, Chrome or recording task
Example prompts
- “Spin up the iPolloWork Electron app on Daytona for the feature branch and give me the noVNC link.”
- “Where do I put eval-only provider keys for the Daytona sandbox?”
- “Which Daytona skill should I use to capture screenshots for my pull request?”
Requirements
- Daytona CLI, logged in with the right organization
- The iPolloWork repository with its .devcontainer scripts
Workflow steps
3 steps, taken from the step headings in SKILL.md.
- Create and start the sandbox
- Get the noVNC URL
- Get other URLs
What it can do on your machine
Read from SKILL.md and the folder at commit 71a74ad. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
bashnpxgitpnpmbrew
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Daytona Dev Environment loads about 1.5k tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 515 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 515 words (~1,454 tokens).
“Launch the iPolloWork Electron app in a Daytona cloud sandbox. The real desktop app runs on Daytona's XFCE/noVNC desktop stack and is accessible through your browser.”
- name
- daytona-dev
Files
Just SKILL.md in .opencode/skills/daytona-dev of Devin-AXIS/iPolloWork.
Open the folder on GitHubat commit 71a74ad
Compare with similar skills
Daytona Dev Environment next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Daytona Dev Environment this skillDevin-AXIS/iPolloWork | 6.7k | — | ~1.5k | Automated safety check: Pass | Custom licence | |
| Ya Runkzahel/yepanywhere | 534 | — | ~957 | Automated safety check: Pass | MIT | |
| OpenWork Electron Browser Automationdifferent-ai/openwork | 24k | — | ~780 | Automated safety check: Pass | Custom licence | |
| Frontend Verifyucsandman/marketing-studio | 251 | — | ~2.4k | Automated safety check: Pass | MIT | |
| Electron App Screenshotkeybase/client | 9.3k | — | ~476 | Automated safety check: Pass | BSD-3-Clause | |
| Edge Bringupexeex/edge-cores | 110 | — | ~1.7k | Automated safety check: Notes | Apache-2.0 |
Similar skills
OpenWork Electron Browser Automation
different-ai/openwork
Attaches OpenCode browser tools to the OpenWork Electron dev app through CDP to explore its UI, send a composer task and debug, not to give test verdicts.
Frontend Verify
ucsandman/marketing-studio
Verify frontend changes end to end after editing a web app, instead of manually clicking through pages.
Electron App Screenshot
keybase/client
Takes a screenshot of a running Electron desktop app through playwright-cli over remote debugging, shrinks it and shows it so you can check the UI visually.
Edge Bringup
exeex/edge-cores
Prepare a macOS or Ubuntu machine for edge-e3 development, diagnose missing Verilator/LLVM/Python dependencies, initialize the public repository, and answer or act on the example prompts in the root…
Interactive Testing
Porabuild/Poracode
Run repeatable integration and smoke testing against the real Poracode Electron app through Chrome DevTools Protocol.
More from Devin-AXIS/iPolloWork
All 30 skills in this repoMaintainable Code for iPolloWork
Devin-AXIS/iPolloWork
A code-change gate for the iPolloWork repository: search and reuse first, keep one source of truth, justify every new file or dependency, and audit the change.
Daytona Windows Certificate Test
Devin-AXIS/iPolloWork
Reproduces iPolloWork enterprise TLS behavior in a Daytona Windows sandbox by installing a fake corporate CA and proving the app and its runtimes use the OS trust store.
Build iPolloWork Templates
Devin-AXIS/iPolloWork
Builds a reusable iPolloWork template for Design, Slides or PPT, or HyperFrames Video through conversation, keeping a manifest, reusable variables and a validated package current.
OpenCode Plugin Creator
Devin-AXIS/iPolloWork
Scaffolds an OpenCode plugin for iPolloWork with the right async factory shape, zod-based tool definitions and hook registration, and explains where to place and register it.
Agent-First Screenshots
Devin-AXIS/iPolloWork
Has an agent drive the real app through CDP and capture clean, defect-free product screenshots, gated by DOM, pixel and vision checks in a loop.
Daytona Chrome CDP
Devin-AXIS/iPolloWork
Launches a standalone Chrome or Chromium in a Daytona sandbox and drives it over CDP for web sign-in, OAuth and other flows that should bypass the Electron app.
Related
Categories
Questions about Daytona Dev Environment
What does Daytona Dev Environment do?
Launches the iPolloWork Electron app inside a Daytona cloud sandbox with a noVNC desktop, and points to focused skills for server, Chrome, secrets and recordings. This skill documents how to run the real iPolloWork Electron app in a Daytona cloud sandbox, using Daytona's XFCE and noVNC desktop stack so you can interact with it from your browser.sh, takes an optional branch or commit, uses a VNC snapshot, starts noVNC, Vite and Electron, and prints the URLs; if the snapshot is missing, a second script creates it.
When should I use Daytona Dev Environment?
Daytona Dev Environment fits situations like: starting the iPolloWork Electron app in a Daytona sandbox; getting the noVNC URL to view the app in a browser; choosing which focused Daytona skill fits a secrets, Chrome or recording task.
How do I install Daytona Dev Environment in Claude Code?
Run `npx skills add Devin-AXIS/iPolloWork --skill daytona-dev -a claude-code`. Or copy the skill folder (.opencode/skills/daytona-dev in Devin-AXIS/iPolloWork) into .claude/skills/daytona-dev in your project. Claude Code loads it when a task matches its description.
How do I install Daytona Dev Environment in Codex?
Run `npx skills add Devin-AXIS/iPolloWork --skill daytona-dev -a codex`. Or copy the skill folder (.opencode/skills/daytona-dev in Devin-AXIS/iPolloWork) into .agents/skills/daytona-dev in your project. Codex loads it when a task matches its description.
Can I use Daytona Dev Environment in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Devin-AXIS/iPolloWork --skill daytona-dev -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/daytona-dev, .gemini/skills/daytona-dev, .github/skills/daytona-dev and .opencode/skills/daytona-dev in your project.
What does Daytona Dev Environment need to run?
Going by SKILL.md and its folder, Daytona Dev Environment needs the command-line tools its instructions call (bash, npx, git, pnpm and brew). Our summary lists: Daytona CLI, logged in with the right organization; The iPolloWork repository with its .devcontainer scripts.
Does Daytona Dev Environment access the network?
SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.
Is Daytona Dev Environment safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Daytona Dev Environment use?
Daytona Dev Environment has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Daytona Dev Environment use?
About 1.5k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Daytona Dev Environment?
Skills that share tags, products or a category with Daytona Dev Environment: Ya Run (kzahel/yepanywhere, 534 stars), OpenWork Electron Browser Automation (different-ai/openwork, 24k stars), Frontend Verify (ucsandman/marketing-studio, 251 stars) and Electron App Screenshot (keybase/client, 9.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Daytona Dev Environment?
Devin-AXIS (a GitHub user) maintains it in Devin-AXIS/iPolloWork, which has 6,717 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 6, 2026.
Source: Devin-AXIS/iPolloWork on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.