Agent skill

Test Flet Apps Dev

A skill your agent uses when testing or debugging Flet apps in maintainer/contributor development mode with local Python package sources and the local Flutter client, including web, desktop…

Apache-2.0Auto-check passedMobile

Install Test Flet Apps Dev

skills CLI

$ npx skills add flet-dev/flet --skill test-flet-apps-dev -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install flet-dev/flet test-flet-apps-dev --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/flet-dev/flet.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/test-flet-apps-dev .claude/skills/test-flet-apps-dev && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "test-flet-apps-dev" agent skill from https://github.com/flet-dev/flet/tree/main/.agents/skills/test-flet-apps-dev into .claude/skills/test-flet-apps-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-flet-apps-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

$skill-installer install https://github.com/flet-dev/flet/tree/main/.agents/skills/test-flet-apps-dev

Type 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.

skills CLI

$ npx skills add flet-dev/flet --skill test-flet-apps-dev -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install flet-dev/flet test-flet-apps-dev --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/flet-dev/flet.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/test-flet-apps-dev .agents/skills/test-flet-apps-dev && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "test-flet-apps-dev" agent skill from https://github.com/flet-dev/flet/tree/main/.agents/skills/test-flet-apps-dev into .agents/skills/test-flet-apps-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-flet-apps-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.

skills CLI

$ npx skills add flet-dev/flet --skill test-flet-apps-dev -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install flet-dev/flet test-flet-apps-dev --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/flet-dev/flet.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/test-flet-apps-dev .cursor/skills/test-flet-apps-dev && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "test-flet-apps-dev" agent skill from https://github.com/flet-dev/flet/tree/main/.agents/skills/test-flet-apps-dev into .cursor/skills/test-flet-apps-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-flet-apps-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

$ gemini skills install https://github.com/flet-dev/flet.git --path .agents/skills/test-flet-apps-dev

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add flet-dev/flet --skill test-flet-apps-dev -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install flet-dev/flet test-flet-apps-dev --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/flet-dev/flet.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/test-flet-apps-dev .gemini/skills/test-flet-apps-dev && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "test-flet-apps-dev" agent skill from https://github.com/flet-dev/flet/tree/main/.agents/skills/test-flet-apps-dev into .gemini/skills/test-flet-apps-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-flet-apps-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.

GitHub CLI

$ gh skill install flet-dev/flet test-flet-apps-dev

Installs 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).

skills CLI

$ npx skills add flet-dev/flet --skill test-flet-apps-dev -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/flet-dev/flet.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/test-flet-apps-dev .github/skills/test-flet-apps-dev && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "test-flet-apps-dev" agent skill from https://github.com/flet-dev/flet/tree/main/.agents/skills/test-flet-apps-dev into .github/skills/test-flet-apps-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-flet-apps-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.

skills CLI

$ npx skills add flet-dev/flet --skill test-flet-apps-dev -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install flet-dev/flet test-flet-apps-dev --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/flet-dev/flet.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/test-flet-apps-dev .opencode/skills/test-flet-apps-dev && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "test-flet-apps-dev" agent skill from https://github.com/flet-dev/flet/tree/main/.agents/skills/test-flet-apps-dev into .opencode/skills/test-flet-apps-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-flet-apps-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: test-flet-apps-dev
GitHub stars: 17k
Token cost: ~1.3k tokens
SKILL.md length: 695 words
Files: 1
Skills in repo: 14
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

A skill your agent uses when testing or debugging Flet apps in maintainer/contributor development mode with local Python package sources and the local Flutter client, including web, desktop…

Works in 2 steps: A Python Flet app/server, run from… → The local Flutter client, run from…
Debugging Flet apps in maintainer/contributor development mode with local Python package sources and the local Flutter client
SKILL.md covers Core model, Start the Python app, Run the local Flutter client and Browser and UI interaction, plus 4 more sections
Calls uv and flutter

What it does

Test Flet Apps Dev is an agent skill from flet-dev/flet. Use when testing or debugging Flet apps in maintainer/contributor development mode with local Python package sources and the local Flutter client, including web, desktop, browser, and computer-use verification workflows.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Mobile, covering Cross-platform mobile apps, Desktop control and Debugging. It works with Flutter, Python and Dart. The repository describes itself as: Build realtime web, mobile and desktop apps in Python only. No frontend experience required. The licence is Apache-2.0.

When your agent uses it

Debugging Flet apps in maintainer/contributor development mode with local Python package sources and the local Flutter client
Computer-use verification workflows

Example prompts

“/test-flet-apps-dev”

Requirements

Python 3

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

A Python Flet app/server, run from sdk/python.
The local Flutter client, run from client, when Dart/client or extension code

What it can do on your machine

Read from SKILL.md and the folder at commit 9748de3. 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:
- uv
- flutter
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use uv, which can reach the network depending on how they are called.
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

Test Flet Apps Dev loads about 1.3k tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 695 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~60
When it runs · the whole SKILL.md, loaded when a task matches: ~1.3k

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 flet-dev/flet at commit 9748de3, republished under its Apache-2.0 licence (© flet-dev). 695 words, ~1,340 tokens.

Download SKILL.mdSave it as .claude/skills/test-flet-apps-dev/SKILL.md (or your agent's skills folder).

name: test-flet-apps-dev
description: Use when testing or debugging Flet apps in maintainer/contributor development mode with local Python package sources and the local Flutter client, including web, desktop, browser, and computer-use verification workflows.

Test Flet Apps In Dev Mode

Use this skill when validating a Flet app, example, feature, or bug fix against this repo's local Python packages and/or local Flutter client during maintainer or contributor work.

Core model

Flet dev-mode testing usually has one or two processes:

A Python Flet app/server, run from sdk/python.
The local Flutter client, run from client, when Dart/client or extension code must be tested.

If only Python code changed, uv run flet run ... is often enough. If Dart, Flutter, extension, or transport code changed, run the local Flutter client so the changed Dart code is actually used.

The local Flutter client debug build uses a fixed app-server URL from client/lib/main.dart:

dart

if (kDebugMode) {
  pageUrl = "http://localhost:8550";
}

Therefore, when using the local Flutter client without extra URL arguments, start the Python app on port 8550.

Start the Python app

Run from {repo}/sdk/python:

bash

uv run flet run -w -p 8550 examples/controls/core/interactive_viewer/handling_events/main.py

Adjust the sample path as needed. Use port 8550 when the local Flutter client will connect with its default debug URL. Keep this process running and watch its stdout for Python callback output, tracebacks, and event payloads.

For web-only checks with the packaged web client, open:

text

http://127.0.0.1:8550

Run the local Flutter client

Run these from {repo}/client.

Desktop

Use when validating native desktop behavior on the current host OS:

bash

fvm flutter run -d macos     # macOS
fvm flutter run -d windows   # Windows
fvm flutter run -d linux     # Linux

The debug client defaults to http://localhost:8550 when no app URL argument is provided. Use the platform target that exists on the current machine. Use Computer Use or the relevant platform automation to navigate and interact with the app window.

Flutter web in Chrome

Use when Dart web behavior must be validated in Flutter's default web debug browser:

bash

fvm flutter run -d chrome

This opens a fresh browser connected to the Python app server on port 8550.

Flutter web in another Chromium browser

If the requested browser is not listed by flutter devices, prefer the web server target and open the served URL in that browser:

bash

fvm flutter run -d web-server --web-hostname 127.0.0.1 --web-port 8660
open -a "Brave Browser" http://127.0.0.1:8660

Using CHROME_EXECUTABLE can work, but Flutter may fail to attach its debug websocket in non-default Chromium browsers. Fall back to web-server if that happens.

Browser and UI interaction

For local browser targets (localhost, 127.0.0.1, file://), prefer the in-app browser or the Browser Use plugin when explicitly requested.
Use Computer Use for native desktop apps and external browsers when browser MCP is not the requested tool or cannot control that browser.
For chart/canvas-heavy UI, click/hover coordinates may be necessary because accessibility trees often expose only the HTML canvas container.

Show full SKILL.md (300 more words)Show less

Reading evidence

Always inspect both sides:

Python app stdout: event payloads, user print() calls, Python tracebacks.
Flutter run stdout: client-side event payloads, WebSocket messages, Flutter exceptions, hot reload/restart status.
Browser/app state: the actual rendered UI and any visible error banner.

For client/server protocol bugs, compare the raw outgoing Dart event in Flutter logs with the decoded Python event object in Python logs.

Hot reload and restart

For Flutter client sessions:

Press r for hot reload after many Dart-only edits.
Press R for hot restart if state, initialization, or extension registration may be stale.
Quit with q before final response unless the user explicitly wants the app left running.
Press h for help on other Flutter run key commands.

For Python app sessions, restart uv run flet run ... after Python source or sample changes if the running process does not pick them up.

Troubleshooting

If a sandboxed Flutter command fails trying to write FVM or Flutter cache files such as engine.stamp, rerun the same command with escalation.
If flutter devices does not list Brave/Edge/etc., use flutter run -d web-server and open the URL in the target browser.
If the UI shows a generic Flet error banner, check Python stdout first; the root cause is often a handler exception.
If an event handler indexes a list payload, confirm the empty-list case before treating it as a framework bug.
If the local Flutter client cannot connect, confirm the Python app is running on port 8550 or pass an explicit app URL when the client path supports it.

Finish checklist

Stop long-running app/test sessions unless asked to leave them running.
State exactly which surfaces were tested: packaged web, local Flutter web, desktop target, target browser, or sample-only.
Include the key observed payload/error before and after the fix.
Separate framework bugs from sample-code guard issues.

Files

Just SKILL.md in .agents/skills/test-flet-apps-dev of flet-dev/flet.

Open the folder on GitHubat commit 9748de3

Compare with similar skills

Test Flet Apps Dev 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.

Test Flet Apps Dev compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Test Flet Apps Dev this skillflet-dev/flet	17k	—	~1.3k	Automated safety check: Pass	Apache-2.0	today
Core API Changelibnativeapi/nativeapi	157	—	~2.5k	Automated safety check: Pass	MIT	today
Re Flutterdslsdzc/rev-skills	117	—	~3.5k	Automated safety check: Pass	Apache-2.0	2 days ago
Flutter Pub ReleaseMixinNetwork/flutter-plugins	512	—	~1.3k	Automated safety check: Pass	MIT	1 mo ago
Liquid Glass Widgetssdegenaar/liquid_glass_widgets	711	—	~3.8k	Automated safety check: Pass	MIT	yesterday
Flutter Bloc and Cubitandrewyng/context-hub	14k	—	~998	Automated safety check: Pass	MIT	4 mo ago

Similar skills

Core API Change
libnativeapi/nativeapi
Carry a change to the C++ public API in core/ all the way downstream — design check, header edit, six platform implementations, C ABI + Rust/Dart/C/JS/Python regeneration, per-binding verification…
157 GitHub stars~2.5k tokensUpdated today
MobileAuto-check passed
Re Flutter
dslsdzc/rev-skills
Flutter/Dart AOT 逆向：libapp.so 快照分区解析、符号还原、Dart VM 动态分析。触发词：Flutter、Dart、libapp.so、AOT snapshot、kernelblob、flutterassets、Dart VM
117 GitHub stars~3.5k tokensUpdated 2 days ago
MobileAuto-check passed
Flutter Pub Release
MixinNetwork/flutter-plugins
Prepare and draft a pub.dev release for a package in the flutter-plugins monorepo.
512 GitHub stars~1.3k tokensUpdated 1 mo ago
MobileAuto-check passed
Liquid Glass Widgets
sdegenaar/liquid_glass_widgets
Mastery guide and architectural rules for liquidglasswidgets.
711 GitHub stars~3.8k tokensUpdated yesterday
MobileAuto-check passed
Flutter Bloc and Cubit
andrewyng/context-hub
Helps choose between Bloc and Cubit in Flutter and sets defaults for packages, lifecycle, widget binding and tests.
14k GitHub stars~998 tokensUpdated 4 mo ago
MobileAuto-check passed
Solid
nank1ro/solid
PRIORITY — read this skill FIRST before writing Dart code when pubspec.yaml declares solidannotations or solidgenerator.
165 GitHub stars~3.1k tokensUpdated 1 mo ago
MobileAuto-check passed

More from flet-dev/flet

All 14 skills in this repo

Create Flet Control Integration Tests
flet-dev/flet
A skill your agent uses when asked to create or update integration tests for any Flet control in sdk/python/packages/flet/integrationtests, including visual goldens and interactive behavior tests.
17k GitHub stars~1.4k tokensUpdated today
Auto-check passed
Create Flet Example Projects
flet-dev/flet
A skill your agent uses when asked to create Flet example projects from flat .py files with main.py and pyproject.toml metadata for Gallery/MCP indexing.
17k GitHub stars~2.4k tokensUpdated today
Auto-check passed
Docs Build And Verify
flet-dev/flet
A skill your agent uses when asked to build, preview, or verify the Flet documentation website, including checking for broken links, broken images, and unresolved reST cross-references.
17k GitHub stars~557 tokensUpdated today
Auto-check passed
Docs Conventions
flet-dev/flet
A skill your agent uses when writing or reviewing Flet documentation, including Python docstrings (Google style, reST roles, admonitions), Markdown docs (cross-references, images, code examples)…
17k GitHub stars~1.6k tokensUpdated today
Auto-check passed
Flet Deprecation
flet-dev/flet
A skill your agent uses when adding or changing deprecations for Python controls/APIs in sdk/python/packages/, including V.deprecated fields, deprecated decorators, version lifecycle, and docs…
17k GitHub stars~2.2k tokensUpdated today
Auto-check passed
Flet Release Announcement
flet-dev/flet
Create or update a Flet release announcement blog post from changelog notes, matching existing /blog style.
17k GitHub stars~950 tokensUpdated today
Auto-check passed

Works with

Questions about Test Flet Apps Dev

What does Test Flet Apps Dev do?

A skill your agent uses when testing or debugging Flet apps in maintainer/contributor development mode with local Python package sources and the local Flutter client, including web, desktop…. Test Flet Apps Dev is an agent skill from flet-dev/flet. Use when testing or debugging Flet apps in maintainer/contributor development mode with local Python package sources and the local Flutter client, including web, desktop, browser, and computer-use verification workflows.

When should I use Test Flet Apps Dev?

Test Flet Apps Dev fits situations like: debugging Flet apps in maintainer/contributor development mode with local Python package sources and the local Flutter client; computer-use verification workflows.

How do I install Test Flet Apps Dev in Claude Code?

Run `npx skills add flet-dev/flet --skill test-flet-apps-dev -a claude-code`. Or copy the skill folder (.agents/skills/test-flet-apps-dev in flet-dev/flet) into .claude/skills/test-flet-apps-dev in your project. Claude Code loads it when a task matches its description.

How do I install Test Flet Apps Dev in Codex?

Run `npx skills add flet-dev/flet --skill test-flet-apps-dev -a codex`. Or copy the skill folder (.agents/skills/test-flet-apps-dev in flet-dev/flet) into .agents/skills/test-flet-apps-dev in your project. Codex loads it when a task matches its description.

Can I use Test Flet Apps Dev 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 flet-dev/flet --skill test-flet-apps-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/test-flet-apps-dev, .gemini/skills/test-flet-apps-dev, .github/skills/test-flet-apps-dev and .opencode/skills/test-flet-apps-dev in your project.

What does Test Flet Apps Dev need to run?

Going by SKILL.md and its folder, Test Flet Apps Dev needs the command-line tools its instructions call (uv and flutter). Our summary lists: Python 3.

Does Test Flet Apps Dev access the network?

SKILL.md contains no URLs. Its commands use uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Test Flet Apps Dev 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 Test Flet Apps Dev use?

Test Flet Apps Dev is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Test Flet Apps Dev use?

About 1.3k tokens (SKILL.md is roughly 5.4k 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 Test Flet Apps Dev?

Skills that share tags, products or a category with Test Flet Apps Dev: Core API Change (libnativeapi/nativeapi, 157 stars), Re Flutter (dslsdzc/rev-skills, 117 stars), Flutter Pub Release (MixinNetwork/flutter-plugins, 512 stars) and Liquid Glass Widgets (sdegenaar/liquid_glass_widgets, 711 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Test Flet Apps Dev?

flet-dev (a GitHub organization) maintains it in flet-dev/flet, which has 17,265 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 7, 2026.

Source: flet-dev/flet on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Test Flet Apps Dev

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Test Flet Apps In Dev Mode

Core model

Start the Python app

Run the local Flutter client

Desktop

Flutter web in Chrome

Flutter web in another Chromium browser

Browser and UI interaction

Reading evidence

Hot reload and restart

Troubleshooting

Finish checklist

Files

Compare with similar skills

Similar skills

More from flet-dev/flet

Related

Questions about Test Flet Apps Dev