Hook Development for Claude Code Plugins
anthropics/claude-plugins-official
Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.
Install the LibreUIUX-Claude-Code plugin pack the way a user does, into a clean Claude Code config and a clean Grok Build home, prove every plugin validates, installs and loads its components, and…
MITAuto-check passed
Install Verify Libreuiux
$ npx skills add HermeticOrmus/LibreUIUX-Claude-Code --skill verify-libreuiux -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install HermeticOrmus/LibreUIUX-Claude-Code verify-libreuiux --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/HermeticOrmus/LibreUIUX-Claude-Code.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.grok/skills/verify-libreuiux .claude/skills/verify-libreuiux && 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 "verify-libreuiux" agent skill from https://github.com/HermeticOrmus/LibreUIUX-Claude-Code/tree/main/.grok/skills/verify-libreuiux into .claude/skills/verify-libreuiux/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-libreuiux", 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/HermeticOrmus/LibreUIUX-Claude-Code/tree/main/.grok/skills/verify-libreuiuxType 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 HermeticOrmus/LibreUIUX-Claude-Code --skill verify-libreuiux -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install HermeticOrmus/LibreUIUX-Claude-Code verify-libreuiux --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/HermeticOrmus/LibreUIUX-Claude-Code.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.grok/skills/verify-libreuiux .agents/skills/verify-libreuiux && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "verify-libreuiux" agent skill from https://github.com/HermeticOrmus/LibreUIUX-Claude-Code/tree/main/.grok/skills/verify-libreuiux into .agents/skills/verify-libreuiux/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-libreuiux", 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 HermeticOrmus/LibreUIUX-Claude-Code --skill verify-libreuiux -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install HermeticOrmus/LibreUIUX-Claude-Code verify-libreuiux --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/HermeticOrmus/LibreUIUX-Claude-Code.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.grok/skills/verify-libreuiux .cursor/skills/verify-libreuiux && 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 "verify-libreuiux" agent skill from https://github.com/HermeticOrmus/LibreUIUX-Claude-Code/tree/main/.grok/skills/verify-libreuiux into .cursor/skills/verify-libreuiux/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-libreuiux", 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/HermeticOrmus/LibreUIUX-Claude-Code.git --path .grok/skills/verify-libreuiux--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 HermeticOrmus/LibreUIUX-Claude-Code --skill verify-libreuiux -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install HermeticOrmus/LibreUIUX-Claude-Code verify-libreuiux --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/HermeticOrmus/LibreUIUX-Claude-Code.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.grok/skills/verify-libreuiux .gemini/skills/verify-libreuiux && 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 "verify-libreuiux" agent skill from https://github.com/HermeticOrmus/LibreUIUX-Claude-Code/tree/main/.grok/skills/verify-libreuiux into .gemini/skills/verify-libreuiux/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-libreuiux", 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 HermeticOrmus/LibreUIUX-Claude-Code verify-libreuiuxInstalls 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 HermeticOrmus/LibreUIUX-Claude-Code --skill verify-libreuiux -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/HermeticOrmus/LibreUIUX-Claude-Code.git skills-src && mkdir -p .github/skills && cp -r skills-src/.grok/skills/verify-libreuiux .github/skills/verify-libreuiux && 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 "verify-libreuiux" agent skill from https://github.com/HermeticOrmus/LibreUIUX-Claude-Code/tree/main/.grok/skills/verify-libreuiux into .github/skills/verify-libreuiux/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-libreuiux", 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 HermeticOrmus/LibreUIUX-Claude-Code --skill verify-libreuiux -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install HermeticOrmus/LibreUIUX-Claude-Code verify-libreuiux --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/HermeticOrmus/LibreUIUX-Claude-Code.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.grok/skills/verify-libreuiux .opencode/skills/verify-libreuiux && 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 "verify-libreuiux" agent skill from https://github.com/HermeticOrmus/LibreUIUX-Claude-Code/tree/main/.grok/skills/verify-libreuiux into .opencode/skills/verify-libreuiux/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-libreuiux", 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
verify-libreuiux- GitHub stars
- 112
- Token cost
- ~1.5k tokens
- SKILL.md length
- 652 words
- Files
- 7
- Skills in repo
- 15
- Repo updated
- First seen
- Licence
- MIT
At a glance
Install the LibreUIUX-Claude-Code plugin pack the way a user does, into a clean Claude Code config and a clean Grok Build home, prove every plugin validates, installs and loads its components, and…
- Proving a LibreUIUX-Claude-Code PRs Done-when
- SKILL.md covers Launch, Doctor, Drive and Evidence, plus 2 more sections
- Calls claude and python3
- Checking that a plugin change still installs in both CLIs
What it does
Verify Libreuiux is an agent skill from HermeticOrmus/LibreUIUX-Claude-Code. Install the LibreUIUX-Claude-Code plugin pack the way a user does, into a clean Claude Code config and a clean Grok Build home, prove every plugin validates, installs and loads its components, and keep the transcripts. Use when proving a LibreUIUX-Claude-Code PR's Done-when, checking that a plugin change still installs in both CLIs, or reproducing an install bug.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files (for example `features/README.md`, `features/install-claude-code.md` and `features/install-grok-build.md`).
The repository describes itself as: UI/UX system for Claude Code: 71 plugins, 93 agents, 74 skills. Design mastery, archetypal design, accessibility, and frontend workflows in one validated plugin marketplace. The licence is MIT.
When your agent uses it
- Proving a LibreUIUX-Claude-Code PRs Done-when
- Checking that a plugin change still installs in both CLIs
- Reproducing an install bug
Example prompts
- “/verify-libreuiux”
Requirements
- Python 3
What it can do on your machine
Read from SKILL.md and the folder at commit 41a968c. 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:
claudepython3
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
Verify Libreuiux loads about 1.5k tokens when it runs. Until then it costs about 96 tokens; SKILL.md has 652 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 HermeticOrmus/LibreUIUX-Claude-Code at commit 41a968c, republished under its MIT licence (© HermeticOrmus). 652 words, ~1,482 tokens.
Download SKILL.mdSave it as
.claude/skills/verify-libreuiux/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.- name
- verify-libreuiux
- description
- Install the LibreUIUX-Claude-Code plugin pack the way a user does, into a clean Claude Code config and a clean Grok Build home, prove every plugin validates, installs and loads its components, and keep the transcripts. Use when proving a LibreUIUX-Claude-Code PR's Done-when, checking that a plugin change still installs in both CLIs, or reproducing an install bug.
Verify LibreUIUX-Claude-Code
LibreUIUX-Claude-Code is a plugin library, not a running app: 71 plugins under plugins/, published as the libreuiux marketplace. Its user surface is the install. A user adds this repo as a plugin marketplace in Claude Code or Grok Build, installs plugins from it (or runs ./setup.sh from a clone), and then uses the skills, commands, agents and hooks those plugins bring. This skill drives that path in throwaway configs, so a proof never touches your own Claude Code config or Grok home.
Helper (executable, bash; needs claude, grok, jq and git): .grok/skills/verify-libreuiux/bin/control-libreuiux
B=.grok/skills/verify-libreuiux/bin/control-libreuiux
$B --help
$B doctor # worth driving? CLIs, head, manifests in sync
$B run # every plugins, both CLIs, prove each loaded; one JSON result
$B run --only design-mastery # the same for the plugins a change touched
$B run --pr 12 --expect <sha> # the same on a PR head, fetched into a scratch clone
$B install --claude --only design-mastery # a fresh run that keeps its clean config for the next steps
$B details design-mastery # component inventory in the latest run (both CLIs)
$B setup --list # ./setup.sh inside the latest run's clean configs
$B check # scripts/check.sh, the repo's one check command
$B cleanup # drop every run's scratch; the evidence staysJSON on stdout, progress on stderr, exit 1 on any failed proof. Everything the helper writes lives under VERIFY_LIBREUIUX_HOME (default ~/.local/share/verify-libreuiux): runs/<stamp>-<head8>/ (or <stamp>-pr<N>-<head8>) holds scratch/ and evidence/, and runs/latest points at the newest run.
Launch
- There is no server. Launching is starting a run: a run folder with an empty Claude Code config (
CLAUDE_CONFIG_DIR) and an empty Grok home (GROK_HOME), both underscratch/. - The tree under test is the checkout the helper sits in. With
--pr Nit is a scratch clone ofrefs/pull/N/headfetched fromorigin, and--expect <sha>refuses any other head. - Claude Code adds the tree as the
libreuiuxmarketplace and installs<plugin>@libreuiux. Grok adds the checkout as a marketplace named after its folder, then installs<plugin>@<folder>. - Ready when the marketplace add exits 0:
evidence/claude-marketplace-add.logandevidence/grok-marketplace-add.log(orgrok-install.log) end inexit 0. - Teardown:
runremoves its own scratch when it finishes. Afterinstall, runcleanupwhen you are done withdetailsandsetup.
Doctor
$B doctorclaude,grok: the CLI versions on PATH. Empty means that CLI is missing.marketplace,claude_plugins,grok_plugins: what the manifests in this checkout declare (grok_pluginsis null when the repo root is the plugin).grok_manifest_in_sync:python3 scripts/sync-grok-manifest.py --checkpasses.head,dirty: the commit under test, and whether the checkout has uncommitted changes. A dirty tree is reported, not refused; say so in the proof.worth_driving: falsemeans stop and fix the reported field first.
Drive
Match the change to a feature in features/README.md and drive every entry point that feature file lists. run is the whole install path at once: it adds the marketplace in both CLIs, installs the selected plugins, reads back claude plugin list --json and grok plugin list --json, and writes each plugin's component inventory from claude plugin details and grok plugin details. result.json reports per CLI what was wanted, what is enabled or installed, what is missing, and any Claude Code load errors. ok is true only when nothing is missing and nothing failed to load.
For a change to one plugin, run --only <plugin> is the proof; for a change to the manifests, setup.sh or anything shared, run with no --only.
Show full SKILL.md (204 more words)Show less
Evidence
evidence/<step>.logfor every command: the command line, its output andexit N.evidence/claude-list.jsonandevidence/grok-list.json: what the clean configs hold after the install.evidence/details-claude-<plugin>.txtandevidence/details-grok-<plugin>.txt: the skills, commands, agents and hooks each plugin brings.evidence/result.json: the verdict fields above, with the head and PR it ran on.
Proof standards: drive the real user path (add the marketplace, then install), never copy files into a plugins folder. Capture the action and the resulting state: the install log and the list and details read back from the clean config. A green scripts/check.sh is the repo's check, not the proof of a Done-when that names a user path: drive that path too. When a Done-when names a command a plugin brings, show that the command is in the plugin's details.
Cleanup
$B cleanupRemoves scratch/ (the clean configs and any PR clone) from every run, and nothing else. It never touches your own Claude Code config or Grok home, because no command here ran with them. The evidence stays under runs/ until you delete it.
Helpers
bin/control-libreuiux: the commands above.--helpprints them.scripts/check.sh(repo root): the one check command CI runs on every pull request and on push tomain.scripts/check.shvalidates every plugin with--strict.
© HermeticOrmus, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 6 other files in .grok/skills/verify-libreuiux of HermeticOrmus/LibreUIUX-Claude-Code.
- SKILL.md
- bin/control-libreuiux
- features/README.md
- features/install-claude-code.md
- features/install-grok-build.md
- features/plugin-components.md
- features/setup-script.md
Open the folder on GitHubat commit 41a968c
Compare with similar skills
Verify Libreuiux 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 |
|---|---|---|---|---|---|---|
| Verify Libreuiux this skillHermeticOrmus/LibreUIUX-Claude-Code | 112 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Hook Development for Claude Code Pluginsanthropics/claude-plugins-official | 38k | 10 repos | ~4.1k | Automated safety check: Notes | Apache-2.0 | |
| Claude Code Agent Developmentanthropics/claude-plugins-official | 38k | 7 repos | ~2.8k | Automated safety check: Pass | Apache-2.0 | |
| Claude Code Skill Developer Guidediet103/claude-code-infrastructure-showcase | 10k | 11 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Plugin Settings Patternanthropics/claude-plugins-official | 38k | 7 repos | ~3k | Automated safety check: Pass | Apache-2.0 | |
| MCP Integration for Pluginsanthropics/claude-plugins-official | 38k | 11 repos | ~3.1k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
- Official
Claude Code Agent Development
anthropics/claude-plugins-official
Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.
Claude Code Skill Developer Guide
diet103/claude-code-infrastructure-showcase
A guide to creating and managing Claude Code skills with auto-activation: skill-rules.json triggers, hooks, enforcement levels, YAML frontmatter and progressive disclosure.
- Official
Plugin Settings Pattern
anthropics/claude-plugins-official
Shows how Claude Code plugins keep per-project settings and state in .claude/plugin-name.local.md files with YAML frontmatter and a markdown body.
- Official
MCP Integration for Plugins
anthropics/claude-plugins-official
Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.
Git Guardrails Claude Code
fossasia/eventyay-interpretation
Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute.
More from HermeticOrmus/LibreUIUX-Claude-Code
All 15 skills in this repoDeployment Pipeline Design
HermeticOrmus/LibreUIUX-Claude-Code
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration.
Multi Cloud Architecture
HermeticOrmus/LibreUIUX-Claude-Code
Design multi-cloud architectures using a decision framework to select and integrate services across AWS, Azure, and GCP.
Archetypal Combinations
HermeticOrmus/LibreUIUX-Claude-Code
Rules and worked examples for combining an archetype (structure and behavior) with a Major Arcana card (color and mood) into one coherent design system.
Langchain Architecture
HermeticOrmus/LibreUIUX-Claude-Code
Design LLM applications using the LangChain framework with agents, memory, and tool integration patterns.
Brand Systems
HermeticOrmus/LibreUIUX-Claude-Code
Brand identity building blocks: positioning, personality, archetypes, logo systems, color palettes, type pairing, voice, and guidelines documentation.
Design Principles
HermeticOrmus/LibreUIUX-Claude-Code
Core visual design principles (visual hierarchy, Gestalt grouping, composition, balance, contrast, white space, color, typography) with UI fixes, a checklist, and deep-dive references.
Questions about Verify Libreuiux
What does Verify Libreuiux do?
Install the LibreUIUX-Claude-Code plugin pack the way a user does, into a clean Claude Code config and a clean Grok Build home, prove every plugin validates, installs and loads its components, and…. Verify Libreuiux is an agent skill from HermeticOrmus/LibreUIUX-Claude-Code. Install the LibreUIUX-Claude-Code plugin pack the way a user does, into a clean Claude Code config and a clean Grok Build home, prove every plugin validates, installs and loads its components, and keep the transcripts.
When should I use Verify Libreuiux?
Verify Libreuiux fits situations like: proving a LibreUIUX-Claude-Code PRs Done-when; checking that a plugin change still installs in both CLIs; reproducing an install bug.
How do I install Verify Libreuiux in Claude Code?
Run `npx skills add HermeticOrmus/LibreUIUX-Claude-Code --skill verify-libreuiux -a claude-code`. Or copy the skill folder (.grok/skills/verify-libreuiux in HermeticOrmus/LibreUIUX-Claude-Code) into .claude/skills/verify-libreuiux in your project. Claude Code loads it when a task matches its description.
How do I install Verify Libreuiux in Codex?
Run `npx skills add HermeticOrmus/LibreUIUX-Claude-Code --skill verify-libreuiux -a codex`. Or copy the skill folder (.grok/skills/verify-libreuiux in HermeticOrmus/LibreUIUX-Claude-Code) into .agents/skills/verify-libreuiux in your project. Codex loads it when a task matches its description.
Can I use Verify Libreuiux 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 HermeticOrmus/LibreUIUX-Claude-Code --skill verify-libreuiux -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/verify-libreuiux, .gemini/skills/verify-libreuiux, .github/skills/verify-libreuiux and .opencode/skills/verify-libreuiux in your project.
What does Verify Libreuiux need to run?
Going by SKILL.md and its folder, Verify Libreuiux needs the command-line tools its instructions call (claude and python3). Our summary lists: Python 3.
Does Verify Libreuiux 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 Verify Libreuiux 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 Verify Libreuiux use?
Verify Libreuiux is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Verify Libreuiux use?
About 1.5k tokens (SKILL.md is roughly 5.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 Verify Libreuiux?
Skills that share tags, products or a category with Verify Libreuiux: Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Claude Code Agent Development (anthropics/claude-plugins-official, 38k stars), Claude Code Skill Developer Guide (diet103/claude-code-infrastructure-showcase, 10k stars) and Plugin Settings Pattern (anthropics/claude-plugins-official, 38k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Verify Libreuiux?
HermeticOrmus (a GitHub user) maintains it in HermeticOrmus/LibreUIUX-Claude-Code, which has 112 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 4, 2026.
Source: HermeticOrmus/LibreUIUX-Claude-Code on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.