Agent skill

Docs Build And Verify

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.

Apache-2.0Auto-check passed

Install Docs Build And Verify

skills CLI

$ npx skills add flet-dev/flet --skill docs-build-and-verify -a claude-code

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

GitHub CLI

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

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 docs-build-and-verify -a codex

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

GitHub CLI

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

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

GitHub CLI

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

--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 docs-build-and-verify -a gemini-cli

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

GitHub CLI

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

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 docs-build-and-verify -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/docs-build-and-verify .github/skills/docs-build-and-verify && 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 "docs-build-and-verify" agent skill from https://github.com/flet-dev/flet/tree/main/.agents/skills/docs-build-and-verify into .github/skills/docs-build-and-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-build-and-verify", 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 docs-build-and-verify -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 docs-build-and-verify --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/docs-build-and-verify .opencode/skills/docs-build-and-verify && 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 "docs-build-and-verify" agent skill from https://github.com/flet-dev/flet/tree/main/.agents/skills/docs-build-and-verify into .opencode/skills/docs-build-and-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-build-and-verify", 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: docs-build-and-verify
GitHub stars: 17k
Token cost: ~557 tokens
SKILL.md length: 139 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 asked to build, preview, or verify the Flet documentation website, including checking for broken links, broken images, and unresolved reST cross-references.

Verify the Flet documentation website
SKILL.md covers Prerequisites, Build, Check Broken Links and Check Broken Images, plus 1 more section
Calls yarn, nvm and python3
Including checking for broken links

What it does

Docs Build And Verify is an agent skill from flet-dev/flet. Use when asked to build, preview, or verify the Flet documentation website, including checking for broken links, broken images, and unresolved reST cross-references.

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

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

Verify the Flet documentation website
Including checking for broken links
Unresolved reST cross-references

Example prompts

“/docs-build-and-verify”

Requirements

Python 3
Node.js

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:
- yarn
- nvm
- python3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use yarn, 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

Docs Build And Verify loads about 557 tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 139 words of instructions outside code blocks.

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

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). 139 words, ~557 tokens.

Download SKILL.mdSave it as .claude/skills/docs-build-and-verify/SKILL.md (or your agent's skills folder).

name: docs-build-and-verify
description: Use when asked to build, preview, or verify the Flet documentation website, including checking for broken links, broken images, and unresolved reST cross-references.

Docs Build and Verification

Prerequisites

Node.js 24 is required, matching what CI runs:

bash

nvm use 24

Build

Full production build (includes broken link detection):

bash

cd website && yarn build

Dev server with hot reload:

bash

cd website && yarn start

Regenerate API data and sidebars only (no Docusaurus build):

bash

cd website && yarn crocodocs:generate

Check Broken Links

yarn build reports both, but only broken links fail the build. Docusaurus defaults onBrokenAnchors to warn and docusaurus.config.js does not override it, so a broken anchor scrolls past in the log and still ships - grep the build output for Broken anchor rather than trusting the exit code.

Check Broken Images

Run this after yarn build to find images referenced in HTML that don't exist:

bash

cd website && python3 -c "
import re, os, glob

build_dir = 'build'
img_re = re.compile(r'<img[^>]+src=\"(/[^\"]+)\"', re.IGNORECASE)
broken = []

for html_file in sorted(glob.glob(f'{build_dir}/docs/**/index.html', recursive=True)):
    page = html_file.replace(build_dir + '/', '').replace('/index.html', '')
    content = open(html_file).read()
    for match in img_re.finditer(content):
        src = match.group(1)
        if src.startswith('http') or src.startswith('data:'):
            continue
        file_path = os.path.join(build_dir, src.lstrip('/'))
        if not os.path.exists(file_path):
            broken.append((page, src))

if broken:
    print(f'Found {len(broken)} broken images:')
    for page, src in broken:
        print(f'  {page}: {src}')
else:
    print('No broken images found!')
"

Check Unresolved reST Cross-References

After building, check for reST roles that failed to resolve and appear as raw text:

bash

cd website && grep -r ':attr:\|:class:\|:meth:\|:func:' build/docs/ --include='*.html' -l

If any files are listed, those pages have unresolved cross-references that render as plain text instead of links.

Files

Just SKILL.md in .agents/skills/docs-build-and-verify of flet-dev/flet.

Open the folder on GitHubat commit 9748de3

Compare with similar skills

Docs Build And Verify 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.

Docs Build And Verify compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Docs Build And Verify this skillflet-dev/flet	17k	—	~557	Automated safety check: Pass	Apache-2.0	today
Langfuse Previewslangfuse/langfuse	35k	—	~2.8k	Automated safety check: Notes	Custom licence	today
Upload Element Previewsremotion-dev/remotion	62k	—	~265	Automated safety check: Pass	Custom licence	today
Windmill Dev Page Previewwindmill-labs/windmill	18k	—	~1.8k	Automated safety check: Pass	Custom licence	yesterday
Docs Learn PR Previewnetdata/netdata	81k	—	~2k	Automated safety check: Pass	GPL-3.0	today
Previewblotcms/blot	2k	—	~649	Automated safety check: Pass	AGPL-3.0	today

Similar skills

Langfuse Previews
langfuse/langfuse
Use Langfuse's disposable per-PR previews at pr-N.preview.langfuse.com (synthetic data only).
35k GitHub stars~2.8k tokensUpdated today
AI & LLM EngineeringAuto-check: notes
Upload Element Previews
remotion-dev/remotion
Official
Upload a Remotion Element's preview assets to remotion.media and replace local preview URLs.
62k GitHub stars~265 tokensUpdated today
Media & CreativeAuto-check passed
Windmill Dev Page Preview
windmill-labs/windmill
Opens the Windmill dev page to preview a flow, script or app, choosing between proxy and direct mode and deciding whether the agent or the runtime starts the wmill dev server.
18k GitHub stars~1.8k tokensUpdated yesterday
DevelopmentAuto-check passed
Docs Learn PR Preview
netdata/netdata
Use only when the user explicitly asks to build, run, preview, inspect, or validate learn.netdata.cloud locally using the contents of a PR or documentation branch before merge.
81k GitHub stars~2k tokensUpdated today
DevOps & CloudAuto-check passed
Preview
blotcms/blot
Run this git worktree's code in its own local server at https://slot-local.blot (slots a-e) so the operator can see and click through it while the main stack keeps running.
2k GitHub stars~649 tokensUpdated today
DevelopmentAuto-check passed
Add Block Preview
simstudioai/sim
Gate a block's visibility — ship an unreleased block as a preview (hidden until revealed via AppConfig/env), reveal it to admins/orgs, GA it, or kill-switch a shipped block
30k GitHub stars~1.3k tokensUpdated today
Auto-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 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
Flet Validation
flet-dev/flet
A skill your agent uses whenever editing validation for Python controls in sdk/python/packages/: adding/changing constrained properties, Raises: ValueError docstrings, beforeupdate() checks, raise…
17k GitHub stars~1.9k tokensUpdated today
Auto-check passed

Questions about Docs Build And Verify

What does Docs Build And Verify do?

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 Build And Verify is an agent skill from flet-dev/flet. Use when asked to build, preview, or verify the Flet documentation website, including checking for broken links, broken images, and unresolved reST cross-references.

When should I use Docs Build And Verify?

Docs Build And Verify fits situations like: verify the Flet documentation website; including checking for broken links; unresolved reST cross-references.

How do I install Docs Build And Verify in Claude Code?

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

How do I install Docs Build And Verify in Codex?

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

Can I use Docs Build And Verify 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 docs-build-and-verify -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/docs-build-and-verify, .gemini/skills/docs-build-and-verify, .github/skills/docs-build-and-verify and .opencode/skills/docs-build-and-verify in your project.

What does Docs Build And Verify need to run?

Going by SKILL.md and its folder, Docs Build And Verify needs the command-line tools its instructions call (yarn, nvm and python3). Our summary lists: Python 3; Node.js.

Does Docs Build And Verify 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 Docs Build And Verify 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 Docs Build And Verify use?

Docs Build And Verify 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 Docs Build And Verify use?

About 557 tokens (SKILL.md is roughly 2.2k 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 Docs Build And Verify?

Skills that share tags, products or a category with Docs Build And Verify: Langfuse Previews (langfuse/langfuse, 35k stars), Upload Element Previews (remotion-dev/remotion, 62k stars), Windmill Dev Page Preview (windmill-labs/windmill, 18k stars) and Docs Learn PR Preview (netdata/netdata, 81k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Docs Build And Verify?

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 Docs Build And Verify

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Docs Build and Verification

Prerequisites

Build

Check Broken Links

Check Broken Images

Check Unresolved reST Cross-References

Files

Compare with similar skills

Similar skills

More from flet-dev/flet

Questions about Docs Build And Verify