Agent skill

Frontend Build Timing Audit

by openops-cloud in openops-cloud/openops

Detects and diagnoses chunk-evaluation timing bugs in the Vite/rolldown production build of react-ui (works-in-dev / broken-in-build i18n regressions, missing UI labels, module-scope t()…

Custom licenceAuto-check passedFrontend & Design

Install Frontend Build Timing Audit

skills CLI
$ npx skills add openops-cloud/openops --skill frontend-build-timing-audit -a claude-code

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

GitHub CLI
$ gh skill install openops-cloud/openops frontend-build-timing-audit --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/openops-cloud/openops.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/frontend-build-timing-audit .claude/skills/frontend-build-timing-audit && 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/

Facts

Skill name
frontend-build-timing-audit
GitHub stars
1.1k
Token cost
~2.3k tokens
SKILL.md length
1,031 words
Files
10 (incl. scripts)
Skills in repo
2
Repo updated
First seen
Licence
Custom licence

At a glance

Detects and diagnoses chunk-evaluation timing bugs in the Vite/rolldown production build of react-ui (works-in-dev / broken-in-build i18n regressions, missing UI labels, module-scope t()…

  • Works in 2 steps: Source layer: never call t() at module… → Bundler layer: declare
  • Editing react-ui
  • SKILL.md covers When to use, The bug pattern (mental model), Workflows and Key facts to remember, plus 1 more section
  • Runs JavaScript scripts from its folder; calls node and npx

What it does

Frontend Build Timing Audit is an agent skill from openops-cloud/openops. Detects and diagnoses chunk-evaluation timing bugs in the Vite/rolldown production build of react-ui (works-in-dev / broken-in-build i18n regressions, missing UI labels, module-scope t() anti-patterns). Use when editing react-ui, ui-components, shared, vite.config.ts, package.json sideEffects, or i18n setup; or when a user reports blank labels in build/docker/staging/prod.

Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including scripts (for example `baseline.json` and `reference.md`).

It sits in Frontend & Design, covering Internationalization, MCP servers and Containers. It works with Vite, React, npm and Docker. The repository describes itself as: The batteries-included, No-Code FinOps automation platform, with the AI you trust.

When your agent uses it

  • Editing react-ui
  • Package.json sideEffects
  • A user reports blank labels in build/docker/staging/prod

Example prompts

  • “Use the frontend-build-timing-audit skill to detect and diagnoses chunk-evaluation timing bugs in the Vite/rolldown production build of react-ui…”
  • “/frontend-build-timing-audit”

Requirements

  • Node.js
  • Docker

Workflow steps

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

  1. Source layer: never call t() at module top level. Use
  2. Bundler layer: declare

What it can do on your machine

Read from SKILL.md and the folder at commit 00010ec. 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

    Ships 7 files in scripts/ (JavaScript), which the agent can run.

    Shell commands in SKILL.md call:

    • node
    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx, 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

Frontend Build Timing Audit loads about 2.3k tokens when it runs. Until then it costs about 102 tokens; SKILL.md has 1,031 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~102
When it runs · the whole SKILL.md, loaded when a task matches
~2.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); the scripts in this folder are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,031 words (~2,325 tokens).

“The OpenOps frontend has hit production-only i18n regressions caused by a subtle interaction between Vite 8 + rolldown's chunk splitting and i18next's lazy initialization. This skill bundles the tooling we used to diagnose and prevent those bugs.”

— opening of SKILL.md by openops-cloud, Custom licence
name
frontend-build-timing-audit

Read the full SKILL.md on GitHub

Files

SKILL.md and 9 other files (scripts) in .claude/skills/frontend-build-timing-audit of openops-cloud/openops.

  • SKILL.md
  • baseline.json
  • reference.md
  • scripts/anti-patterns.config.mjs
  • scripts/bundle-diff.mjs
  • scripts/check-regression.mjs
  • scripts/find-toplevel-init-calls.mjs
  • scripts/lib/analyze.mjs
  • scripts/snapshot.mjs
  • scripts/update-baseline.mjs

Open the folder on GitHubat commit 00010ec

Compare with similar skills

Frontend Build Timing Audit 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.

Frontend Build Timing Audit compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Frontend Build Timing Audit this skillopenops-cloud/openops1.1k—~2.3kAutomated safety check: PassCustom licence
Project Releaseswimmwatch/cloakbrowser-mcp161—~1.9kAutomated safety check: PassMIT
Devcontainer Devstacklok/toolhive-studio170—~3.8kAutomated safety check: NotesApache-2.0
Project Docs Maintainerswimmwatch/cloakbrowser-mcp161—~569Automated safety check: PassMIT
Managing MCP IndexComfy-Org/workflow_templates1.3k—~1.9kAutomated safety check: NotesMIT
Oneclickvirtoneclickvirt/oneclickvirt372—~1.1kAutomated safety check: PassGPL-3.0

Similar skills

  • Project Release

    swimmwatch/cloakbrowser-mcp

    Prepare, publish, verify, or recover a cloakbrowser-mcp release only when the user explicitly requests release work.

    161 GitHub stars~1.9k tokensUpdated 6 days ago
    Agent WorkflowsAuto-check passed
  • Devcontainer Dev

    stacklok/toolhive-studio

    Spin up and interact with ToolHive Studio's containerized dev environment (Xvfb + noVNC + DinD).

    170 GitHub stars~3.8k tokensUpdated today
    Agent WorkflowsAuto-check: notes
  • Project Docs Maintainer

    swimmwatch/cloakbrowser-mcp

    Maintain, organize, consolidate, or audit the cloakbrowser-mcp documentation set only when the user explicitly requests project documentation maintenance or an authorized public change requires it.

    161 GitHub stars~569 tokensUpdated 6 days ago
    DevelopmentAuto-check passed
  • Managing MCP Index

    Comfy-Org/workflow_templates

    Builds and maintains templates/index.mcp.json for Comfy Cloud MCP tools.

    1.3k GitHub stars~1.9k tokensUpdated today
    Frontend & DesignAuto-check: notes
  • Oneclickvirt

    oneclickvirt/oneclickvirt

    OneClickVirt operations skill for managing containers, virtual machines, provider nodes, health checks, and metrics through MCP.

    372 GitHub stars~1.1k tokensUpdated 6 days ago
    DevOps & CloudAuto-check passed
  • Official

    Audit a documentation site for agent-friendliness: discovery, markdown delivery, crawlability, semantic structure, machine-readable surfaces, and content legibility.

    4.7k GitHub stars~1.8k tokensUpdated yesterday
    Frontend & DesignAuto-check passed

More from openops-cloud/openops

  • React

    openops-cloud/openops

    A skill your agent uses when creating or editing frontend React code in react-ui or ui-components packages.

    1.1k GitHub stars~1.7k tokensUpdated today
    Auto-check passed

Questions about Frontend Build Timing Audit

What does Frontend Build Timing Audit do?

Detects and diagnoses chunk-evaluation timing bugs in the Vite/rolldown production build of react-ui (works-in-dev / broken-in-build i18n regressions, missing UI labels, module-scope t()…. Frontend Build Timing Audit is an agent skill from openops-cloud/openops. Detects and diagnoses chunk-evaluation timing bugs in the Vite/rolldown production build of react-ui (works-in-dev / broken-in-build i18n regressions, missing UI labels, module-scope t() anti-patterns).

When should I use Frontend Build Timing Audit?

Frontend Build Timing Audit fits situations like: editing react-ui; package.json sideEffects; A user reports blank labels in build/docker/staging/prod.

How do I install Frontend Build Timing Audit in Claude Code?

Run `npx skills add openops-cloud/openops --skill frontend-build-timing-audit -a claude-code`. Or copy the skill folder (.claude/skills/frontend-build-timing-audit in openops-cloud/openops) into .claude/skills/frontend-build-timing-audit in your project. Claude Code loads it when a task matches its description.

How do I install Frontend Build Timing Audit in Codex?

Run `npx skills add openops-cloud/openops --skill frontend-build-timing-audit -a codex`. Or copy the skill folder (.claude/skills/frontend-build-timing-audit in openops-cloud/openops) into .agents/skills/frontend-build-timing-audit in your project. Codex loads it when a task matches its description.

Can I use Frontend Build Timing Audit 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 openops-cloud/openops --skill frontend-build-timing-audit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/frontend-build-timing-audit, .gemini/skills/frontend-build-timing-audit, .github/skills/frontend-build-timing-audit and .opencode/skills/frontend-build-timing-audit in your project.

What does Frontend Build Timing Audit need to run?

Going by SKILL.md and its folder, Frontend Build Timing Audit needs JavaScript for the scripts in its folder and the command-line tools its instructions call (node and npx). Our summary lists: Node.js; Docker.

Does Frontend Build Timing Audit access the network?

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

Is Frontend Build Timing Audit 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Frontend Build Timing Audit use?

Frontend Build Timing Audit has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Frontend Build Timing Audit use?

About 2.3k tokens (SKILL.md is roughly 9.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 Frontend Build Timing Audit?

Skills that share tags, products or a category with Frontend Build Timing Audit: Project Release (swimmwatch/cloakbrowser-mcp, 161 stars), Devcontainer Dev (stacklok/toolhive-studio, 170 stars), Project Docs Maintainer (swimmwatch/cloakbrowser-mcp, 161 stars) and Managing MCP Index (Comfy-Org/workflow_templates, 1.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Frontend Build Timing Audit?

openops-cloud (a GitHub organization) maintains it in openops-cloud/openops, which has 1,075 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 8, 2026.

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