OpenHarness End-to-End Evals
HKUDS/OpenHarness
Validates OpenHarness features by running real multi-turn agent loops with live LLM calls against an unfamiliar codebase, checking actual tool execution.
Create or update Flet control screenshots and GIFs that are generated from integration tests and shown in docs.
Install Update Flet Control Doc Gifs
$ npx skills add flet-dev/flet --skill update-flet-control-doc-gifs -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install flet-dev/flet update-flet-control-doc-gifs --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/flet-dev/flet.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/update-flet-control-doc-gifs .claude/skills/update-flet-control-doc-gifs && 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 "update-flet-control-doc-gifs" agent skill from https://github.com/flet-dev/flet/tree/main/.agents/skills/update-flet-control-doc-gifs into .claude/skills/update-flet-control-doc-gifs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-flet-control-doc-gifs", 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/flet-dev/flet/tree/main/.agents/skills/update-flet-control-doc-gifsType 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 flet-dev/flet --skill update-flet-control-doc-gifs -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install flet-dev/flet update-flet-control-doc-gifs --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/flet-dev/flet.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/update-flet-control-doc-gifs .agents/skills/update-flet-control-doc-gifs && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "update-flet-control-doc-gifs" agent skill from https://github.com/flet-dev/flet/tree/main/.agents/skills/update-flet-control-doc-gifs into .agents/skills/update-flet-control-doc-gifs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-flet-control-doc-gifs", 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 flet-dev/flet --skill update-flet-control-doc-gifs -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install flet-dev/flet update-flet-control-doc-gifs --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/flet-dev/flet.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/update-flet-control-doc-gifs .cursor/skills/update-flet-control-doc-gifs && 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 "update-flet-control-doc-gifs" agent skill from https://github.com/flet-dev/flet/tree/main/.agents/skills/update-flet-control-doc-gifs into .cursor/skills/update-flet-control-doc-gifs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-flet-control-doc-gifs", 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/flet-dev/flet.git --path .agents/skills/update-flet-control-doc-gifs--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 flet-dev/flet --skill update-flet-control-doc-gifs -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install flet-dev/flet update-flet-control-doc-gifs --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/flet-dev/flet.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/update-flet-control-doc-gifs .gemini/skills/update-flet-control-doc-gifs && 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 "update-flet-control-doc-gifs" agent skill from https://github.com/flet-dev/flet/tree/main/.agents/skills/update-flet-control-doc-gifs into .gemini/skills/update-flet-control-doc-gifs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-flet-control-doc-gifs", 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 flet-dev/flet update-flet-control-doc-gifsInstalls 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 flet-dev/flet --skill update-flet-control-doc-gifs -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/flet-dev/flet.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/update-flet-control-doc-gifs .github/skills/update-flet-control-doc-gifs && 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 "update-flet-control-doc-gifs" agent skill from https://github.com/flet-dev/flet/tree/main/.agents/skills/update-flet-control-doc-gifs into .github/skills/update-flet-control-doc-gifs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-flet-control-doc-gifs", 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 flet-dev/flet --skill update-flet-control-doc-gifs -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install flet-dev/flet update-flet-control-doc-gifs --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/flet-dev/flet.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/update-flet-control-doc-gifs .opencode/skills/update-flet-control-doc-gifs && 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 "update-flet-control-doc-gifs" agent skill from https://github.com/flet-dev/flet/tree/main/.agents/skills/update-flet-control-doc-gifs into .opencode/skills/update-flet-control-doc-gifs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-flet-control-doc-gifs", 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
update-flet-control-doc-gifs- GitHub stars
- 17k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 579 words
- Files
- 1
- Skills in repo
- 14
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Create or update Flet control screenshots and GIFs that are generated from integration tests and shown in docs.
- Works in 3 steps: Locate the example-backed integration… → Prefer extending an existing interaction… → Build the visual sequence with…
- Working on sdk/python/packages/flet/integrationtests/examples
- SKILL.md covers Workflow, Naming, Docs Update Rules and Verification Checklist, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Update Flet Control Doc Gifs is an agent skill from flet-dev/flet. Create or update Flet control screenshots and GIFs that are generated from integration tests and shown in docs. Use when working on sdk/python/packages/flet/integrationtests/examples, refreshing static or interactive golden screenshots, or replacing old example media images or GIFs with generated test assets.
Its SKILL.md is about 1.2k 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 Testing & QA, covering Integration testing. It works with Python. 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
- Working on sdk/python/packages/flet/integrationtests/examples
- Refreshing static
- Interactive golden screenshots
- Replacing old example media images
Example prompts
- “/update-flet-control-doc-gifs”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Locate the example-backed integration test under sdk/python/packages/flet/integration_tests/examples.
- Prefer extending an existing interaction test instead of creating a second flow test.
- Build the visual sequence with deterministic states
What it can do on your machine
Read from SKILL.md and the folder at commit 3710aff. 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
Update Flet Control Doc Gifs loads about 1.2k tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 579 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 flet-dev/flet at commit 3710aff, republished under its Apache-2.0 licence (© flet-dev). 579 words, ~1,223 tokens.
Download SKILL.mdSave it as
.claude/skills/update-flet-control-doc-gifs/SKILL.md (or your agent's skills folder).- name
- update-flet-control-doc-gifs
- description
- Create or update Flet control screenshots and GIFs that are generated from integration tests and shown in docs. Use when working on `sdk/python/packages/flet/integration_tests/examples`, refreshing static or interactive golden screenshots, or replacing old example media images or GIFs with generated test assets.
Update Flet Control Doc Gifs
Use this skill after the integration test structure is already in place and the task is to capture doc-ready screenshots or interactive GIF states from integration tests.
Workflow
- Locate the example-backed integration test under
sdk/python/packages/flet/integration_tests/examples. - Prefer extending an existing interaction test instead of creating a second flow test.
- Build the visual sequence with deterministic states:
- set
page.enable_screenshots = True - set
theme_modewhen visuals matter - set fixed page size before screenshots
- prefer finding controls by visible text or other stable user-facing content; add a
keyonly when there is no reliable human-facing locator - call
pump_and_settle()after each interaction
- Capture only states that are visually meaningful:
- before interaction
- hover state
- popup/menu/dialog open
- reopened state that proves persistence
- single static screenshots when one frame is enough for docs
- do not keep screenshots taken after a click if the UI closes and the state is not visible
- Use
assert_screenshot(...)for regular golden screenshots andcreate_gif([...], "<flow_name>", duration=...)only when the docs benefit from an animated flow.
- Prefer storing only asserted or docs-facing states as named screenshots; keep intermediate hover/click frames in memory and pass them directly to
create_gif(...)when they do not need standalone golden files.
- Update docs to use the generated screenshot or GIF, not an old media asset from
examples/.../media, when the integration-test asset is now the better docs artifact. - Update docs references to point at the intended generated screenshot or GIF path, but do not copy generated assets into
website/static/docs/test-images/...as part of this workflow.
Naming
- Use short screenshot names that describe visible states, for example
before_click,hover_popup,popup_open,checked_item_reopened. - Use one flow GIF name per control/example, for example
app_bar_flow. - Use descriptive static screenshot names when the asset is docs-facing, for example
image_for_docs,popup_open, orchecked_item_reopened. - Give the integration test a behavior-based name such as
test_actions_and_popup_menu; avoid placeholder names liketest_basicwhen the test covers a specific flow. - Keep screenshot names stable because they become golden filenames.
Show full SKILL.md (252 more words)Show less
Docs Update Rules
- Control docs usually point to generated assets through
frontMatter.example_images. - If a docs page still has
example_imagespointing at example media instead of generated test images, update that front matter first so the page has a single source of truth for screenshots and GIFs. - When a docs page has multiple example sections, add the generated screenshot or GIF directly under the matching
CodeExampleblock so each visual stays paired with the example it demonstrates. - If a docs page still uses
frontMatter.example_media + '/old.png'orfrontMatter.example_media + '/old.gif', replace it withfrontMatter.example_images + '/<asset>'when the generated integration-test asset is the new source of truth. - Generated screenshots and GIFs from integration tests are commonly stored at
sdk/python/packages/flet/integration_tests/examples/.../golden/macos/<control>/. - Do not copy generated screenshots or GIFs into
website/static/docs/test-images/...as part of this skill. Keep the work limited to tests and docs references unless the user explicitly asks for a copy.
Verification Checklist
- The interaction test still reflects the example behavior.
- Every screenshot included in a GIF is visibly different and useful.
- The GIF duration is intentional; prefer shorter loops for hover/click flows unless the interaction needs more time.
- The docs front matter points to the generated test-images location rather than stale example media paths.
- The docs page references the new screenshot or GIF path.
- The generated screenshot or GIF exists in the integration-test golden directory at the path implied by the test names.
- Remove or stop referencing obsolete media screenshots or GIFs only when the new generated asset fully replaces them.
References
sdk/python/packages/flet/integration_tests/examplessdk/python/packages/flet/integration_tests/examples/controls/material/test_alert_dialog.pysdk/python/packages/flet/integration_tests/examples/controls/material/test_app_bar.pywebsite/docs/controls
© flet-dev, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/update-flet-control-doc-gifs of flet-dev/flet.
Open the folder on GitHubat commit 3710aff
Compare with similar skills
Update Flet Control Doc Gifs 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 |
|---|---|---|---|---|---|---|
| Update Flet Control Doc Gifs this skillflet-dev/flet | 17k | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| OpenHarness End-to-End EvalsHKUDS/OpenHarness | 16k | 1 repos | ~2.1k | Automated safety check: Notes | MIT | |
| Godot E2ERandallLiuXin/GodotMaker | 550 | 1 repos | ~3.9k | Automated safety check: Pass | Custom licence | |
| JS-in-HTML Testingliaohch3/claude-tap | 3.3k | — | ~924 | Automated safety check: Pass | MIT | |
| Run Integration Testsvalkey-io/valkey-search | 145 | — | ~511 | Automated safety check: Pass | BSD-3-Clause | |
| Temporal Python Testingwshobson/agents | 40k | 12 repos | ~1.2k | Automated safety check: Pass | MIT |
Similar skills
Godot E2E
RandallLiuXin/GodotMaker
Write and run E2E (end-to-end) game tests using the godot-e2e framework.
JS-in-HTML Testing
liaohch3/claude-tap
Tests JavaScript embedded in an HTML file in two layers: pytest checks of the logic ported to Python, and Playwright runs in a real browser for the DOM.
Run Integration Tests
valkey-io/valkey-search
Run or troubleshoot Valkey Search C++ and Python integration tests, including focused development runs, full-suite verification, and packaging/build or runtime failure classification.
Temporal Python Testing
wshobson/agents
Test Temporal workflows with pytest, time-skipping, and mocking strategies.
Integration Testing
s-morgan-jeffries/apple-mail-fast-mcp
A skill your agent uses when setting up, running, or debugging integration tests against real Apple Mail.
More from flet-dev/flet
All 14 skills in this repoCreate 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.
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.
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.
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)…
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…
Flet Release Announcement
flet-dev/flet
Create or update a Flet release announcement blog post from changelog notes, matching existing /blog style.
Related
Works with
Categories
Questions about Update Flet Control Doc Gifs
What does Update Flet Control Doc Gifs do?
Create or update Flet control screenshots and GIFs that are generated from integration tests and shown in docs. Update Flet Control Doc Gifs is an agent skill from flet-dev/flet. Create or update Flet control screenshots and GIFs that are generated from integration tests and shown in docs.
When should I use Update Flet Control Doc Gifs?
Update Flet Control Doc Gifs fits situations like: working on sdk/python/packages/flet/integrationtests/examples; refreshing static; interactive golden screenshots; replacing old example media images.
How do I install Update Flet Control Doc Gifs in Claude Code?
Run `npx skills add flet-dev/flet --skill update-flet-control-doc-gifs -a claude-code`. Or copy the skill folder (.agents/skills/update-flet-control-doc-gifs in flet-dev/flet) into .claude/skills/update-flet-control-doc-gifs in your project. Claude Code loads it when a task matches its description.
How do I install Update Flet Control Doc Gifs in Codex?
Run `npx skills add flet-dev/flet --skill update-flet-control-doc-gifs -a codex`. Or copy the skill folder (.agents/skills/update-flet-control-doc-gifs in flet-dev/flet) into .agents/skills/update-flet-control-doc-gifs in your project. Codex loads it when a task matches its description.
Can I use Update Flet Control Doc Gifs 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 update-flet-control-doc-gifs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/update-flet-control-doc-gifs, .gemini/skills/update-flet-control-doc-gifs, .github/skills/update-flet-control-doc-gifs and .opencode/skills/update-flet-control-doc-gifs in your project.
What does Update Flet Control Doc Gifs need to run?
SKILL.md names no scripts, command-line tools or credentials: Update Flet Control Doc Gifs is instructions for the agent only.
Does Update Flet Control Doc Gifs 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 Update Flet Control Doc Gifs 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 Update Flet Control Doc Gifs use?
Update Flet Control Doc Gifs 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 Update Flet Control Doc Gifs use?
About 1.2k tokens (SKILL.md is roughly 4.9k 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 Update Flet Control Doc Gifs?
Skills that share tags, products or a category with Update Flet Control Doc Gifs: OpenHarness End-to-End Evals (HKUDS/OpenHarness, 16k stars), Godot E2E (RandallLiuXin/GodotMaker, 550 stars), JS-in-HTML Testing (liaohch3/claude-tap, 3.3k stars) and Run Integration Tests (valkey-io/valkey-search, 145 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Update Flet Control Doc Gifs?
flet-dev (a GitHub organization) maintains it in flet-dev/flet, which has 17,305 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 9, 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.