AI Agent Skills

Test harness for Claude Code skill argument substitution — demonstrates capture-block pre-declaration, XML tag referencing, unintentional variable corruption in code blo…

Use this skill whenever the user wants to evaluate, test, or validate an AI agent, decide whether an agent is ready to ship or go live, choose how to grade an agent's an…

Use this skill whenever the user asks for a looping booth, kiosk, trade-show, lobby-screen, or silent background video — including requests phrased as "a video loop for…

Use this skill whenever the user asks to test, validate, UAT, regression-check, or investigate the behaviour of a browser-based application — including Copilot Studio ag…

Use this skill automatically when you feel your code is ready for human review, and whenever writing or reviewing code comments. Ready means the code works and achieves…

Ask Claude Code to make a taste-driven call on something ambiguous — UI polish, prose phrasing, naming, formatting. Use when you'd otherwise guess.

Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fi…

Write clean, readable Pythonic code. Use this skill any time you write or change a Python file.

Use when installing or operating Univer CLI for .univer files, spreadsheets, documents, slides, Base databases, Board canvases, cross-Unit embedding, worktrees, Facade a…

Customize Univer color themes, branded palettes, dark mode, and theme-aware plugin styles across Sheets, Docs, Slides, Bases, Boards, and PDFs. Use when setting an initi…

Use when installing or operating the independent Univer Workspace CLI application (`univer-workspace-cli`) for remote Workspace files, Personal or Team Spaces, task Work…

REQUIRED for any task that involves operating a desktop application — opening apps, clicking buttons, typing into fields, pressing keys, scrolling, dragging, reading wha…

Use when completing frontend or UI work that needs visual verification, before claiming the UI is correct

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and…

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Use when you have a spec or requirements for a multi-step task, before touching code