CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

chameleon-controls-library

Builds UIs with Chameleon web components (ch-*). Use when the user mentions Chameleon, ch- components, or needs enterprise UI patterns like grids, trees, chat, sidebars, accordions, combos, tabs, dialogs, or forms. Also use for: implementing a UI from Figma or images, vibe coding a UI, migrating an existing UI to Chameleon, or auditing Chameleon usage in an application.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Failed to scan

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-structured orchestration skill: a clear phased workflow with an explicit audit-and-fix feedback loop, concrete per-phase file pointers, and clean progressive disclosure into a large, verified reference bundle. The residual issues are small — some redundant linking and table duplication, and the examples reference being under-integrated into the workflow.

DimensionReasoningScore

Conciseness

The body is directive and assumes Claude's competence (no explanations of what web components or shadow DOM are), with tight imperative prose throughout. Minor trimmable bulk remains: the ~35-line ASCII workflow diagram, a category table that duplicates the components index, and a bottom References table repeating links already made inline (components-index.md is linked four times).

4 / 5

Actionability

Gives concrete executable guidance for an instruction-only skill: per-phase "Read [specific file]" instructions, a styling decision tree, and a 7-point audit checklist with cross-references to the exact files to verify against. Minor gap: no inline usage example — references/examples.md exists but is only surfaced in the bottom References table rather than wired into the workflow.

4 / 5

Workflow Clarity

Phases A–H are clearly sequenced with parallelism (A/B), sub-entry points (C1–C5), a designated audit-only entry (C5 → Phase H), and an explicit validation phase: a 7-item checklist covering tags, APIs, slots, styles, best practices, and anti-patterns, plus a fix-and-re-audit feedback loop ("fix the issue (returning to phases D-G as needed) and re-audit until all checks pass"). This matches the anchor-5 example of sequence + validation + error-recovery loop.

5 / 5

Progressive Disclosure

The body is a genuine overview that splits detail across a well-organized bundle (405 files: per-component README/usage/styling, best-practices, installation, and topical guides), with references one level deep, consistently signaled via bolded "Read" markers and inline links. All referenced paths were verified to exist on disk, and navigation is easy despite the large bundle.

5 / 5

Total

18

/

20

Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is a strong match to the top anchors: third-person voice, concrete what-statement, and an explicit multi-clause "Use when" trigger list covering mention-based, task-based (Figma/images, vibe coding), migration, and audit entry points. The only weakness is that component styling/theming — a substantial part of the skill — is not surfaced as a capability.

DimensionReasoningScore

Specificity

Lists several concrete actions — "Builds UIs with Chameleon web components (ch-*)", "implementing a UI from Figma or images", "migrating an existing UI to Chameleon", "auditing Chameleon usage" — but omits styling/theming work that the skill body covers heavily, leaving minor gaps in coverage. Not 3 because it goes well beyond 1-2 actions; not 5 because the primary action is broad and a major capability (component styling) is unstated.

4 / 5

Completeness

Explicitly answers both questions: what ("Builds UIs with Chameleon web components (ch-*)") and when ("Use when the user mentions Chameleon, ch- components..." and "Also use for: implementing a UI from Figma or images, vibe coding a UI, migrating... or auditing"). This mirrors the anchor-5 example structure with concrete trigger phrases.

5 / 5

Trigger Term Quality

Covers natural trigger phrasing comprehensively: "Chameleon", "ch- components", concrete pattern names users would say ("grids, trees, chat, sidebars, accordions, combos, tabs, dialogs, or forms"), plus "Figma", "vibe coding a UI", "migrating", and "auditing". No natural synonym category is missing for this domain.

5 / 5

Distinctiveness Conflict Risk

Clear niche — a specific named component library with a distinctive "ch-*" tag prefix and "Chameleon" name in triggers — so it is unlikely to fire for unrelated UI/framework skills. Conflict risk with generic web-component or design-system skills is minimal because the triggers are name-anchored.

5 / 5

Total

19

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 4 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 4 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

cinthamo/genexus-skills

Path

frontend/chameleon-controls-library/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.