Improve UI Audit and Plans
ibelick/ui-skills
Audits one product surface against its own design evidence and writes self-contained implementation plans for another agent, without touching product source.
Standard software engineering workflow for requirement analysis, technical design, and task planning.
$ npx skills add LeoYeAI/openclaw-master-skills --skill spec-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills spec-workflow --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/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/cloudbase/references/spec-workflow .claude/skills/spec-workflow && 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 "spec-workflow" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/cloudbase/references/spec-workflow into .claude/skills/spec-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec-workflow", 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/LeoYeAI/openclaw-master-skills/tree/main/skills/cloudbase/references/spec-workflowType 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 LeoYeAI/openclaw-master-skills --skill spec-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills spec-workflow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/cloudbase/references/spec-workflow .agents/skills/spec-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "spec-workflow" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/cloudbase/references/spec-workflow into .agents/skills/spec-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec-workflow", 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 LeoYeAI/openclaw-master-skills --skill spec-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills spec-workflow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/cloudbase/references/spec-workflow .cursor/skills/spec-workflow && 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 "spec-workflow" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/cloudbase/references/spec-workflow into .cursor/skills/spec-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec-workflow", 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/LeoYeAI/openclaw-master-skills.git --path skills/cloudbase/references/spec-workflow--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 LeoYeAI/openclaw-master-skills --skill spec-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills spec-workflow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/cloudbase/references/spec-workflow .gemini/skills/spec-workflow && 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 "spec-workflow" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/cloudbase/references/spec-workflow into .gemini/skills/spec-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec-workflow", 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 LeoYeAI/openclaw-master-skills spec-workflowInstalls 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 LeoYeAI/openclaw-master-skills --skill spec-workflow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/cloudbase/references/spec-workflow .github/skills/spec-workflow && 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 "spec-workflow" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/cloudbase/references/spec-workflow into .github/skills/spec-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec-workflow", 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 LeoYeAI/openclaw-master-skills --skill spec-workflow -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills spec-workflow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/cloudbase/references/spec-workflow .opencode/skills/spec-workflow && 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 "spec-workflow" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/cloudbase/references/spec-workflow into .opencode/skills/spec-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec-workflow", 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.
spec-workflowStandard software engineering workflow for requirement analysis, technical design, and task planning.
Spec Workflow is an agent skill from LeoYeAI/openclaw-master-skills. Standard software engineering workflow for requirement analysis, technical design, and task planning. Use this skill when developing new features, complex architecture designs, multi-module integrations, or projects involving database/UI design.
Its SKILL.md is about 1.4k 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 Frontend & Design, covering UI design and Planning. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.
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.
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Spec Workflow loads about 1.4k tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 611 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.
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.
The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 611 words, ~1,352 tokens.
.claude/skills/spec-workflow/SKILL.md (or your agent's skills folder).Use this skill for structured development workflow when you need to:
Do NOT use for:
Follow the workflow strictly
interactiveDialog tool when clarification is neededApply EARS requirement syntax
While <optional precondition>, when <optional trigger>, the <system name> shall <system response>Reference UI design rules when needed
ui-design skillUpdate task status
tasks.md fileImportant: You must follow these rules. Each phase must be confirmed by the user before proceeding to the next phase.
If you determine that the user's input is a new requirement, you can work independently following standard software engineering practices. Confirm with user when necessary, and can use interactiveDialog tool to collect information.
Whenever the user inputs a new requirement, to standardize requirement quality and acceptance criteria, you must first understand the problem and requirements clearly. You must confirm with the user before proceeding to the next phase.
First complete the requirements design using EARS (Easy Approach to Requirements Syntax) method. If you determine the requirements involve frontend pages, you must strictly reference ui-design skill. Determine design style and color palette in the requirements phase. You must confirm requirement details with the user. After final confirmation, the requirements are finalized, then proceed to the next phase.
Save to specs/spec_name/requirements.md. After confirming with the user, proceed to the next phase.
Reference format:
# Requirements Document
## Introduction
Requirement description
## Requirements
### Requirement 1 - Requirement Name
**User Story:** User story content
#### Acceptance Criteria
1. Use EARS syntax: While <optional precondition>, when <optional trigger>, the <system name> shall <system response>. For example: When "Mute" is selected, the laptop shall suppress all audio output.
2. ...
...After completing the requirements design, based on the current technical architecture and the confirmed requirements above, design the technical solution. It should be concise but accurately describe the technical architecture (e.g., architecture, tech stack, technology selection, database/interface design, test strategy, security). Use mermaid diagrams when necessary.
Save to specs/spec_name/design.md. You must confirm with the user clearly, then proceed to the next phase.
After completing the technical solution design, based on the requirements document and technical solution, break down specific tasks. You must confirm with the user clearly, then save to specs/spec_name/tasks.md. After confirming with the user, proceed to the next phase and begin formal task execution. You need to update task status in a timely manner. When executing, work as independently and autonomously as possible to ensure efficiency and quality.
Task reference format:
# Implementation Plan
- [ ] 1. Task Information
- Specific things to do
- ...
- _Requirement: Related requirement point numbertasks.md file in real-time© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/cloudbase/references/spec-workflow of LeoYeAI/openclaw-master-skills.
Open the folder on GitHubat commit e5199b5
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in LeoYeAI/openclaw-master-skills, which our catalogue first saw on October 7, 2026.
Spec Workflow 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 |
|---|---|---|---|---|---|---|
| Spec Workflow this skillLeoYeAI/openclaw-master-skills | 2.2k | 1 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Improve UI Audit and Plansibelick/ui-skills | 9.5k | — | ~2k | Automated safety check: Pass | MIT | |
| Design LabNeverSight/learn-skills.dev | 216 | 1 repos | ~7.5k | Automated safety check: Pass | None | |
| UI Skills Routeribelick/ui-skills | 9.5k | 2 repos | ~362 | Automated safety check: Pass | MIT | |
| Orca Chat Visualsstablyai/orca | 87k | — | ~933 | Automated safety check: Pass | MIT | |
| Videoohad6k/emulo | 293 | 1 repos | ~8.3k | Automated safety check: Pass | MIT |
ibelick/ui-skills
Audits one product surface against its own design evidence and writes self-contained implementation plans for another agent, without touching product source.
NeverSight/learn-skills.dev
Conduct design interviews, generate five distinct UI variations in a temporary design lab, collect feedback, and produce implementation plans.
ibelick/ui-skills
Routes UI tasks to the smallest useful set of UI Skills through the ui-skills CLI, picking a category and loading at most three skills before implementing.
stablyai/orca
Show a chart, diagram, timeline, comparison or UI mockup inline in this Orca chat by writing one self-contained HTML file and adding a visual line to your reply.
ohad6k/emulo
A skill your agent uses when a brief has to become a film. An agent skill from ohad6k/emulo.
XiaomiMiMo/MiMo-Code
Entry point to a bundle of product design workflows covering context, research, audits, ideation, URL or image to code, design QA and sharing a prototype.
LeoYeAI/openclaw-master-skills
Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.
LeoYeAI/openclaw-master-skills
Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.
LeoYeAI/openclaw-master-skills
Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.
LeoYeAI/openclaw-master-skills
Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.
LeoYeAI/openclaw-master-skills
Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.
LeoYeAI/openclaw-master-skills
Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.
Categories
Standard software engineering workflow for requirement analysis, technical design, and task planning. Spec Workflow is an agent skill from LeoYeAI/openclaw-master-skills. Standard software engineering workflow for requirement analysis, technical design, and task planning.
Spec Workflow fits situations like: developing new features; complex architecture designs; multi-module integrations; projects involving database/UI design.
Run `npx skills add LeoYeAI/openclaw-master-skills --skill spec-workflow -a claude-code`. Or copy the skill folder (skills/cloudbase/references/spec-workflow in LeoYeAI/openclaw-master-skills) into .claude/skills/spec-workflow in your project. Claude Code loads it when a task matches its description.
Run `npx skills add LeoYeAI/openclaw-master-skills --skill spec-workflow -a codex`. Or copy the skill folder (skills/cloudbase/references/spec-workflow in LeoYeAI/openclaw-master-skills) into .agents/skills/spec-workflow in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LeoYeAI/openclaw-master-skills --skill spec-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/spec-workflow, .gemini/skills/spec-workflow, .github/skills/spec-workflow and .opencode/skills/spec-workflow in your project.
SKILL.md names no scripts, command-line tools or credentials: Spec Workflow is instructions for the agent only.
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.
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.
Spec Workflow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.4k 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.
Skills that share tags, products or a category with Spec Workflow: Improve UI Audit and Plans (ibelick/ui-skills, 9.5k stars), Design Lab (NeverSight/learn-skills.dev, 216 stars), UI Skills Router (ibelick/ui-skills, 9.5k stars) and Orca Chat Visuals (stablyai/orca, 87k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,159 GitHub stars. The repository holds 972 skills in this directory. The repository was last updated on July 20, 2026.
Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.