CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

add

Install one or more Cult UI components into the current project with the shadcn CLI, after reading their docs, then adapt them to the project.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

The body is a tight, well-sequenced install workflow: concrete commands, lockfile-derived runner selection, explicit stop-and-ask checkpoints for risky operations, and a verify-and-report step with real gate results. Its only notable gap is the undefined `<docs-slug>` placeholder in the docs-fetch step.

DimensionReasoningScore

Conciseness

The body is lean and imperative throughout — every line instructs an action ("Grep the catalog case-insensitively", "Never pass --overwrite unless the user asked"), and even the brief rationales ("because init rewrites config and global CSS") are decision-relevant rather than padding. Not below 5 because no section explains concepts Claude already knows or could be tightened without losing information.

5 / 5

Actionability

Guidance is almost fully executable: an explicit runner-selection table from lockfiles, a concrete install command template, a retry-by-URL fallback, and a docs URL pattern. Not 5 because the `<docs-slug>` placeholder in the fetch URL is never defined (its source in the catalog is not stated), leaving a minor gap; not 3 because the guidance is concrete and executable, not pseudocode or high-level hints.

4 / 5

Workflow Clarity

Six clearly sequenced sections with explicit checkpoints and feedback loops: ask before `shadcn init`, ask on ambiguous name matches, show the diff before overwriting, retry by URL on unknown namespace, consult the troubleshooting table on CLI failure, and run type check/build/lint/test gates while "reporting the real results". This matches the top anchor of explicit validation with error recovery.

5 / 5

Progressive Disclosure

The skill is under 50 lines with well-organized numbered sections and no bundle of its own to disclose; the two referenced files (the cult-ui catalog and setup guide) are one level deep, purpose-labeled, and given a clear path-resolution fallback (Glob pattern when the plugin-root path fails). Not below 5 because nothing that belongs in a separate file is inlined and navigation is unambiguous.

5 / 5

Total

19

/

20

Passed

Description

66%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 concise, specific, and clearly anchored to a distinct niche (Cult UI + shadcn CLI), with concrete actions covering install, docs, and adaptation. Its main weakness is the complete absence of a "when to use" trigger clause, which both caps completeness and leaves trigger guidance implicit.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user asks to add, install, or set up Cult UI components (e.g. halo-select, dynamic island) in a project."

Include a few natural synonym phrases users would say — "add component", "component library", "cult-ui" — to broaden trigger term coverage.

Briefly differentiate from sibling skills (e.g. use this to install a known component; use `/cult-ui:find` to discover one) to reduce overlap risk within the plugin.

DimensionReasoningScore

Specificity

Names several concrete actions — "Install one or more Cult UI components… with the shadcn CLI", "after reading their docs", "adapt them to the project" — which matches the anchor for several specific actions with minor gaps. Not 5 because deeper capabilities (retokening, framework adaptation, verification) are absent from the description; not 3 because more than 1–2 concrete actions are listed.

4 / 5

Completeness

The "what" is clear (install Cult UI components via the shadcn CLI, read docs, adapt to the project), but there is no "Use when…" clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because the "when" is entirely absent rather than merely implicit-but-stated.

3 / 5

Trigger Term Quality

"Cult UI components", "shadcn CLI", and "install" are the natural terms a user would say when invoking this skill, giving good keyword coverage. Not 5 because common variations like "add component", "component library", or specific component names are missing; not 3 because the domain and tool keywords are more specific and complete than a single generic phrase.

4 / 5

Distinctiveness Conflict Risk

"Cult UI" and "shadcn CLI" carve a mostly distinct niche with minimal conflict risk against unrelated skills. Not 5 because it could overlap with a generic shadcn-install skill and does not distinguish itself from sibling skills like the referenced `cult-ui:find`; not 3 because the named registry and tool are specific, not broadly generic.

4 / 5

Total

15

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

13

/

16

Passed

Repository

freightCognition/linehaulai-claude-marketplace

Path

plugins/cult-ui/skills/add/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.