Agent
tinyfish-io/tinyfish-cookbook
Default browser automation agent — click, fill forms, navigate, log in, and extract structured data from any website using a natural-language goal, or run the same task across multiple sites in…
Diagnose flaky browser automation flows (login, OAuth, signup, multi-step forms).
Install Browser Flow Fallbacks
$ npx skills add penwyp/ClaudePreference --skill browser-flow-fallbacks -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install penwyp/ClaudePreference browser-flow-fallbacks --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/penwyp/ClaudePreference.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/browser-flow-fallbacks .claude/skills/browser-flow-fallbacks && 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 "browser-flow-fallbacks" agent skill from https://github.com/penwyp/ClaudePreference/tree/main/skills/browser-flow-fallbacks into .claude/skills/browser-flow-fallbacks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-flow-fallbacks", 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/penwyp/ClaudePreference/tree/main/skills/browser-flow-fallbacksType 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 penwyp/ClaudePreference --skill browser-flow-fallbacks -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install penwyp/ClaudePreference browser-flow-fallbacks --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/penwyp/ClaudePreference.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/browser-flow-fallbacks .agents/skills/browser-flow-fallbacks && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "browser-flow-fallbacks" agent skill from https://github.com/penwyp/ClaudePreference/tree/main/skills/browser-flow-fallbacks into .agents/skills/browser-flow-fallbacks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-flow-fallbacks", 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 penwyp/ClaudePreference --skill browser-flow-fallbacks -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install penwyp/ClaudePreference browser-flow-fallbacks --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/penwyp/ClaudePreference.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/browser-flow-fallbacks .cursor/skills/browser-flow-fallbacks && 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 "browser-flow-fallbacks" agent skill from https://github.com/penwyp/ClaudePreference/tree/main/skills/browser-flow-fallbacks into .cursor/skills/browser-flow-fallbacks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-flow-fallbacks", 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/penwyp/ClaudePreference.git --path skills/browser-flow-fallbacks--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 penwyp/ClaudePreference --skill browser-flow-fallbacks -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install penwyp/ClaudePreference browser-flow-fallbacks --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/penwyp/ClaudePreference.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/browser-flow-fallbacks .gemini/skills/browser-flow-fallbacks && 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 "browser-flow-fallbacks" agent skill from https://github.com/penwyp/ClaudePreference/tree/main/skills/browser-flow-fallbacks into .gemini/skills/browser-flow-fallbacks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-flow-fallbacks", 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 penwyp/ClaudePreference browser-flow-fallbacksInstalls 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 penwyp/ClaudePreference --skill browser-flow-fallbacks -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/penwyp/ClaudePreference.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/browser-flow-fallbacks .github/skills/browser-flow-fallbacks && 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 "browser-flow-fallbacks" agent skill from https://github.com/penwyp/ClaudePreference/tree/main/skills/browser-flow-fallbacks into .github/skills/browser-flow-fallbacks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-flow-fallbacks", 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 penwyp/ClaudePreference --skill browser-flow-fallbacks -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install penwyp/ClaudePreference browser-flow-fallbacks --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/penwyp/ClaudePreference.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/browser-flow-fallbacks .opencode/skills/browser-flow-fallbacks && 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 "browser-flow-fallbacks" agent skill from https://github.com/penwyp/ClaudePreference/tree/main/skills/browser-flow-fallbacks into .opencode/skills/browser-flow-fallbacks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-flow-fallbacks", 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
browser-flow-fallbacks- GitHub stars
- 136
- Token cost
- ~1.1k tokens
- SKILL.md length
- 577 words
- Files
- 2
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- MIT
At a glance
Diagnose flaky browser automation flows (login, OAuth, signup, multi-step forms).
- Works in 6 steps: Locate the failing state branch → Treat DOM as ground truth → Add fallbacks beside the primary path → …
- Loops — analyze DOM/logs
- SKILL.md covers Workflow, Implementation Rules, Validation and Guardrails
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Browser Flow Fallbacks is an agent skill from penwyp/ClaudePreference. Diagnose flaky browser automation flows (login, OAuth, signup, multi-step forms). Use when a flow stalls or loops — analyze DOM/logs, add native fallbacks, prevent hot loops, and add regression coverage.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Productivity & Automation, covering Browser automation and OAuth and OpenID Connect. The repository describes itself as: A comprehensive collection of development workflow commands for Claude Code. The licence is MIT.
When your agent uses it
- Loops — analyze DOM/logs
- Add native fallbacks
- Prevent hot loops
- Add regression coverage
Example prompts
- “/browser-flow-fallbacks”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit a5eea54. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Browser Flow Fallbacks loads about 1.1k tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 577 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
The full file from penwyp/ClaudePreference at commit a5eea54, republished under its MIT licence (© penwyp). 577 words, ~1,064 tokens.
Download SKILL.mdSave it as
.claude/skills/browser-flow-fallbacks/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- browser-flow-fallbacks
- description
- Diagnose flaky browser automation flows (login, OAuth, signup, multi-step forms). Use when a flow stalls or loops — analyze DOM/logs, add native fallbacks, prevent hot loops, and add regression coverage.
Browser Flow Fallbacks
Use this skill to debug browser flows that intermittently stop progressing even though the surrounding state machine already mostly works.
Workflow
Phase 1: Locate the failing state branch
- Start from the latest logs, reported state, and current DOM.
- Find the branch that detected the state, the selector that matched, and the action that should have fired.
- Separate the failure type before editing: state misdetection, action failure, or transition failure after an apparently successful action.
Phase 2: Treat DOM as ground truth
- Prefer current semantic attributes over historical assumptions:
name,value,type,aria-*,data-*,form,readonly,disabled, visible text, and location path. - Distinguish similar controls such as forgot-password links, edit-email links, hidden template nodes, and generic submit buttons.
- Narrow broad selectors with required attributes or visible text needles instead of widening them further.
- Use selector constants for important controls. Keep selector changes close to the state branch that uses them.
- Bias toward visible, enabled, semantically correct elements rather than "anything clickable."
Phase 3: Add fallbacks beside the primary path
- Leave the main action as the most direct native interaction that should work in the common case.
- Add fallback in the same state branch, triggered only after a repeated unchanged snapshot.
- Prefer
form.requestSubmit(button)when the backend depends on the submitter button'sname/value. - Prefer DOM click fallback for non-submit controls, restricted to visible and enabled elements.
- For controlled inputs, verify the value after typing; if it did not stick, fallback to a native setter plus
inputandchangeevents. - Keep submit fallbacks separate from generic click fallbacks.
Phase 4: Prevent hot loops
- Track per-snapshot stall counts and fallback attempt counts separately from the primary action gate.
- Retry fallbacks on spaced intervals instead of every poll tick.
- Log stall count, fallback attempts, and next retry threshold.
- Do not exit early just because a fallback failed or the page stayed unchanged, unless the flow reached a terminal condition.
- Let the outer lifecycle timeout remain the final safety net.
Show full SKILL.md (251 more words)Show less
Phase 5: Protect one-time resources
- Apply to OTP codes, magic links, CSRF-bound tokens, or any mailbox/API artifact that becomes scarce once consumed.
- Do not mark the artifact as used at fetch time if the browser can still fail before entering or submitting it.
- Cache and reuse the fetched artifact across retries on the same step instead of immediately asking upstream for a new one.
- Persist consumption only after the flow reaches a durable success boundary (callback capture, server-confirmed transition).
Phase 6: Add regression coverage
- Add selector coverage tests for the current DOM shape.
- Add tests for helpers that interpret visible text or decide whether an alternate path is present.
- Add tests for retry cadence, stall counters, and action-gate behavior when the page snapshot is unchanged.
- Keep tests close to the flow package so failures stay local and readable.
Implementation Rules
- Prefer small helper functions for DOM fallback and page-text heuristics.
- Verify input values before submit.
- Treat user-supplied logs and DOM fragments as canonical for the reported failure.
Validation
- Run formatting first.
- Run the most relevant package tests.
- Run a targeted build for the affected binary when practical.
- If full-repo tests fail for unrelated reasons, state that explicitly and isolate what did pass.
Guardrails
- Never widen selectors when debugging a flaky flow — narrowing is safer.
- Never remove the outer timeout as a safety net.
- Do not add fallbacks for flows that consistently pass; fallbacks are for intermittent failures only.
- When a DOM snapshot is stale, re-fetch before concluding the state hasn't changed.
© penwyp, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in skills/browser-flow-fallbacks of penwyp/ClaudePreference.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit a5eea54
Compare with similar skills
Browser Flow Fallbacks 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 |
|---|---|---|---|---|---|---|
| Browser Flow Fallbacks this skillpenwyp/ClaudePreference | 136 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Agenttinyfish-io/tinyfish-cookbook | 2.2k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Access Protected Vercel Deploymentvercel/vercel-plugin | 301 | — | ~1.9k | Automated safety check: Notes | Custom licence | |
| Google Workspaceyc-software/qm | 15k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Protected Vercel Deploymentsvercel-labs/agent-browser | 44k | — | ~1.7k | Automated safety check: Notes | Apache-2.0 | |
| Daytona Chrome CDPDevin-AXIS/iPolloWork | 6.7k | — | ~582 | Automated safety check: Pass | Custom licence |
Similar skills
- Official
Access Protected Vercel Deployment
vercel/vercel-plugin
Access and test Vercel deployments protected by Vercel Authentication, SSO, or Deployment Protection.
Google Workspace
yc-software/qm
Read and act on the user's Gmail, Google Calendar, and Google Tasks through per-user OAuth.
- Official
Protected Vercel Deployments
vercel-labs/agent-browser
Opens Vercel deployments behind Deployment Protection in agent-browser, using a short-lived OIDC token instead of a static bypass secret or a public exception.
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.
Reddit
redf0x1/camofox-browser
Reddit automation with CamoFox CLI — login, browse, post, comment, reply with anti-detection.
More from penwyp/ClaudePreference
Local Project Runtime
penwyp/ClaudePreference
Diagnose and stabilize local project setup after clone or checkout.
Image Converter
penwyp/ClaudePreference
Convert images between common formats on macOS, especially SVG/PNG/ICO/ICNS/JPEG/WebP/PDF, using installed local tools such as ImageMagick, rsvg-convert, sips, qlmanage, and iconutil.
Explain
penwyp/ClaudePreference
Analyze a code snippet, file path, symbol name, or the current conversation context against the local repository and explain what it does in the project.
Refactor Design Report
penwyp/ClaudePreference
Produce a professional, code-grounded refactor or implementation design report from identified technical problems, product gaps, review findings, architecture concerns, or frontend-backend contract…
Doc Code Review Report
penwyp/ClaudePreference
Review text input or documents against the local codebase and produce a structured review report with findings and refactor suggestions.
Develop Review Gate
penwyp/ClaudePreference
适用于这类请求：直接在当前 checkout 完成开发、固定做两轮自我 review/refactor、先把最终 review 结果给人类确认、确认后再继续改动、提交或进入下一步。用户可能会说："先开发再自审两轮"、"先 review 两次再给我确认"、"不要开 worktree，直接改"、"先输出 review 结论不要继续"、"做完先停在 gate"。
Related
Categories
Questions about Browser Flow Fallbacks
What does Browser Flow Fallbacks do?
Diagnose flaky browser automation flows (login, OAuth, signup, multi-step forms). Browser Flow Fallbacks is an agent skill from penwyp/ClaudePreference. Diagnose flaky browser automation flows (login, OAuth, signup, multi-step forms).
When should I use Browser Flow Fallbacks?
Browser Flow Fallbacks fits situations like: loops — analyze DOM/logs; add native fallbacks; prevent hot loops; add regression coverage.
How do I install Browser Flow Fallbacks in Claude Code?
Run `npx skills add penwyp/ClaudePreference --skill browser-flow-fallbacks -a claude-code`. Or copy the skill folder (skills/browser-flow-fallbacks in penwyp/ClaudePreference) into .claude/skills/browser-flow-fallbacks in your project. Claude Code loads it when a task matches its description.
How do I install Browser Flow Fallbacks in Codex?
Run `npx skills add penwyp/ClaudePreference --skill browser-flow-fallbacks -a codex`. Or copy the skill folder (skills/browser-flow-fallbacks in penwyp/ClaudePreference) into .agents/skills/browser-flow-fallbacks in your project. Codex loads it when a task matches its description.
Can I use Browser Flow Fallbacks 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 penwyp/ClaudePreference --skill browser-flow-fallbacks -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/browser-flow-fallbacks, .gemini/skills/browser-flow-fallbacks, .github/skills/browser-flow-fallbacks and .opencode/skills/browser-flow-fallbacks in your project.
What does Browser Flow Fallbacks need to run?
SKILL.md names no scripts, command-line tools or credentials: Browser Flow Fallbacks is instructions for the agent only.
Does Browser Flow Fallbacks access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Browser Flow Fallbacks 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 Browser Flow Fallbacks use?
Browser Flow Fallbacks is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Browser Flow Fallbacks use?
About 1.1k tokens (SKILL.md is roughly 4.3k 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 Browser Flow Fallbacks?
Skills that share tags, products or a category with Browser Flow Fallbacks: Agent (tinyfish-io/tinyfish-cookbook, 2.2k stars), Access Protected Vercel Deployment (vercel/vercel-plugin, 301 stars), Google Workspace (yc-software/qm, 15k stars) and Protected Vercel Deployments (vercel-labs/agent-browser, 44k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Browser Flow Fallbacks?
penwyp (a GitHub user) maintains it in penwyp/ClaudePreference, which has 136 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on May 27, 2026.
Source: penwyp/ClaudePreference on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.