Impeccable
bestofjs/bestofjs
A skill your agent uses when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a…
Expert at analyzing the quality and effectiveness of Claude Code components (agents, skills, commands, hooks).
Install Analyzing Component Quality
$ npx skills add aiskillstore/marketplace --skill analyzing-component-quality -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install aiskillstore/marketplace analyzing-component-quality --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/aiskillstore/marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/c0ntr0lledcha0s/analyzing-component-quality .claude/skills/analyzing-component-quality && 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 "analyzing-component-quality" agent skill from https://github.com/aiskillstore/marketplace/tree/main/skills/c0ntr0lledcha0s/analyzing-component-quality into .claude/skills/analyzing-component-quality/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyzing-component-quality", 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/aiskillstore/marketplace/tree/main/skills/c0ntr0lledcha0s/analyzing-component-qualityType 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 aiskillstore/marketplace --skill analyzing-component-quality -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install aiskillstore/marketplace analyzing-component-quality --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aiskillstore/marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/c0ntr0lledcha0s/analyzing-component-quality .agents/skills/analyzing-component-quality && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "analyzing-component-quality" agent skill from https://github.com/aiskillstore/marketplace/tree/main/skills/c0ntr0lledcha0s/analyzing-component-quality into .agents/skills/analyzing-component-quality/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyzing-component-quality", 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 aiskillstore/marketplace --skill analyzing-component-quality -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install aiskillstore/marketplace analyzing-component-quality --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aiskillstore/marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/c0ntr0lledcha0s/analyzing-component-quality .cursor/skills/analyzing-component-quality && 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 "analyzing-component-quality" agent skill from https://github.com/aiskillstore/marketplace/tree/main/skills/c0ntr0lledcha0s/analyzing-component-quality into .cursor/skills/analyzing-component-quality/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyzing-component-quality", 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/aiskillstore/marketplace.git --path skills/c0ntr0lledcha0s/analyzing-component-quality--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 aiskillstore/marketplace --skill analyzing-component-quality -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install aiskillstore/marketplace analyzing-component-quality --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aiskillstore/marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/c0ntr0lledcha0s/analyzing-component-quality .gemini/skills/analyzing-component-quality && 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 "analyzing-component-quality" agent skill from https://github.com/aiskillstore/marketplace/tree/main/skills/c0ntr0lledcha0s/analyzing-component-quality into .gemini/skills/analyzing-component-quality/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyzing-component-quality", 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 aiskillstore/marketplace analyzing-component-qualityInstalls 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 aiskillstore/marketplace --skill analyzing-component-quality -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/aiskillstore/marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/c0ntr0lledcha0s/analyzing-component-quality .github/skills/analyzing-component-quality && 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 "analyzing-component-quality" agent skill from https://github.com/aiskillstore/marketplace/tree/main/skills/c0ntr0lledcha0s/analyzing-component-quality into .github/skills/analyzing-component-quality/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyzing-component-quality", 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 aiskillstore/marketplace --skill analyzing-component-quality -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install aiskillstore/marketplace analyzing-component-quality --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aiskillstore/marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/c0ntr0lledcha0s/analyzing-component-quality .opencode/skills/analyzing-component-quality && 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 "analyzing-component-quality" agent skill from https://github.com/aiskillstore/marketplace/tree/main/skills/c0ntr0lledcha0s/analyzing-component-quality into .opencode/skills/analyzing-component-quality/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyzing-component-quality", 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
analyzing-component-quality- GitHub stars
- 430
- Token cost
- ~3.7k tokens
- SKILL.md length
- 697 words
- Files
- 4 (incl. scripts, references)
- Skills in repo
- 1,108
- Repo updated
- First seen
- Licence
- None found
At a glance
Expert at analyzing the quality and effectiveness of Claude Code components (agents, skills, commands, hooks).
- Works in 9 steps: Description Clarity (1-5) → Tool Permissions (1-5) → Auto-Invoke Triggers (1-5) → …
- Tasks that involve UX design
- SKILL.md covers Important Assumptions, Your Expertise, When to Use This Skill and Quality Dimensions, plus 9 more sections
- Runs Python scripts from its folder; calls python
What it does
Analyzing Component Quality is an agent skill from aiskillstore/marketplace. Expert at analyzing the quality and effectiveness of Claude Code components (agents, skills, commands, hooks). Assumes component is already technically valid. Evaluates description clarity, tool permissions, auto-invoke triggers, security, and usability to provide quality scores and improvement suggestions.
Its SKILL.md is about 3.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts and reference files (for example `references/quality-standards.md`, `scripts/quality-scorer.py` and `skill-report.json`).
It sits in Frontend & Design, covering UX design. The repository describes itself as: Security-audited skills for Claude, Codex & Claude Code. One-click install, quality verified.
When your agent uses it
- Tasks that involve UX design
Example prompts
- “/analyzing-component-quality”
Requirements
- Python 3
- Pre-approved tools (allowed-tools): Read, Grep, Glob, Bash
Workflow steps
9 steps, taken from the step headings in SKILL.md.
- Description Clarity (1-5)
- Tool Permissions (1-5)
- Auto-Invoke Triggers (1-5)
- Security Review (1-5)
- Usability (1-5)
- Read Component
- Score Each Dimension
- Identify Specific Issues
- Provide Concrete Improvements
What it can do on your machine
Read from SKILL.md and the folder at commit ad8daf7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadGrepGlobBash
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python
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
Analyzing Component Quality loads about 3.7k tokens when it runs, and up to ~6.6k if it reads all its reference files. Until then it costs about 84 tokens; SKILL.md has 697 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: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Read, Grep, Glob, Bash
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
Without a licence we can't republish the file, so here is its outline and opening line. It has 697 words (~3,745 tokens).
“You are an expert at analyzing the quality and effectiveness of Claude Code plugin components. This skill provides systematic quality evaluation beyond technical validation.”
- name
- analyzing-component-quality
- allowed-tools
- Read, Grep, Glob, Bash
- version
- 1.0.0
Files
SKILL.md and 3 other files (scripts, references) in skills/c0ntr0lledcha0s/analyzing-component-quality of aiskillstore/marketplace.
- SKILL.md
- references/quality-standards.md
- scripts/quality-scorer.py
- skill-report.json
Open the folder on GitHubat commit ad8daf7
Compare with similar skills
Analyzing Component Quality 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 |
|---|---|---|---|---|---|---|
| Analyzing Component Quality this skillaiskillstore/marketplace | 430 | — | ~3.7k | Automated safety check: Notes | None | |
| Impeccablebestofjs/bestofjs | 3.1k | 27 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Interface Design for Dashboards and Appsholaboss-ai/holaOS | 11k | 3 repos | ~6k | Automated safety check: Pass | MIT | |
| Animategrowupanand/ConvoForm | 101 | 6 repos | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| Migrate Content Iadocker/docs | 4.7k | — | ~5.1k | Automated safety check: Pass | Apache-2.0 | |
| UX WalkthroughXiaoMi/hiui | 877 | — | ~1.3k | Automated safety check: Pass | MIT |
Similar skills
Interface Design for Dashboards and Apps
holaboss-ai/holaOS
Pushes an agent past generic defaults when designing dashboards, admin panels, SaaS apps and tools, with attention to structure, type, navigation and how data is shown.
Animate
growupanand/ConvoForm
Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight.
- Official
Migrate Content Ia
docker/docs
Handle Hugo docs information-architecture moves: discover old vs new URLs, add front matter aliases (Phase 1), update in-repo links (Phase 2), interactive List 2 resolution and fragment validation…
UX Walkthrough
XiaoMi/hiui
体验走查 skill。适用于代码库、URL、截图三种输入，输出结构化体验问题报告，并同步生成本地 docx 报告。触发词：体验走查、UX review、交互走查、界面审查、体验问题。
Color Audit
rome-os/rome
Audit a design system's color palette against measurable color-science disciplines — WCAG/APCA contrast of declared token pairs, perceptual (OKLCH) ramp uniformity, color-blindness safety of…
More from aiskillstore/marketplace
All 1,108 skills in this repoCode Stats
aiskillstore/marketplace
Analyze codebase with tokei (fast line counts by language) and difft (semantic AST-aware diffs).
File Search
aiskillstore/marketplace
Modern file and content search using fd, ripgrep (rg), and fzf.
Data Processing
aiskillstore/marketplace
Process JSON with jq and YAML/TOML with yq. An agent skill from aiskillstore/marketplace.
Doc Scanner
aiskillstore/marketplace
Scans for project documentation files (AGENTS.md, CLAUDE.md, GEMINI.md, COPILOT.md, CURSOR.md, WARP.md, and 15+ other formats) and synthesizes guidance.
Find Replace
aiskillstore/marketplace
Modern find-and-replace using sd (simpler than sed) and batch replacement patterns.
Investigating Codebases
aiskillstore/marketplace
Automatically activated when user asks how something works, wants to understand unfamiliar code, needs to explore a new codebase, or asks questions like "where is X implemented?", "how does Y…
Related
Categories
Questions about Analyzing Component Quality
What does Analyzing Component Quality do?
Expert at analyzing the quality and effectiveness of Claude Code components (agents, skills, commands, hooks). Analyzing Component Quality is an agent skill from aiskillstore/marketplace. Expert at analyzing the quality and effectiveness of Claude Code components (agents, skills, commands, hooks).
When should I use Analyzing Component Quality?
Analyzing Component Quality fits situations like: tasks that involve UX design.
How do I install Analyzing Component Quality in Claude Code?
Run `npx skills add aiskillstore/marketplace --skill analyzing-component-quality -a claude-code`. Or copy the skill folder (skills/c0ntr0lledcha0s/analyzing-component-quality in aiskillstore/marketplace) into .claude/skills/analyzing-component-quality in your project. Claude Code loads it when a task matches its description.
How do I install Analyzing Component Quality in Codex?
Run `npx skills add aiskillstore/marketplace --skill analyzing-component-quality -a codex`. Or copy the skill folder (skills/c0ntr0lledcha0s/analyzing-component-quality in aiskillstore/marketplace) into .agents/skills/analyzing-component-quality in your project. Codex loads it when a task matches its description.
Can I use Analyzing Component Quality 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 aiskillstore/marketplace --skill analyzing-component-quality -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/analyzing-component-quality, .gemini/skills/analyzing-component-quality, .github/skills/analyzing-component-quality and .opencode/skills/analyzing-component-quality in your project.
What does Analyzing Component Quality need to run?
Going by SKILL.md and its folder, Analyzing Component Quality needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3. Its frontmatter pre-approves these tools: Read, Grep, Glob, Bash.
Does Analyzing Component Quality 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 Analyzing Component Quality safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. 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 Analyzing Component Quality use?
No licence was found for Analyzing Component Quality or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Analyzing Component Quality use?
About 3.7k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.9k tokens, read only when the agent opens those files.
What are the alternatives to Analyzing Component Quality?
Skills that share tags, products or a category with Analyzing Component Quality: Impeccable (bestofjs/bestofjs, 3.1k stars), Interface Design for Dashboards and Apps (holaboss-ai/holaOS, 11k stars), Animate (growupanand/ConvoForm, 101 stars) and Migrate Content Ia (docker/docs, 4.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Analyzing Component Quality?
aiskillstore (a GitHub organization) maintains it in aiskillstore/marketplace, which has 430 GitHub stars. The repository holds 1,108 skills in this directory. The repository was last updated on October 7, 2026.
Source: aiskillstore/marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.