Agent skill

Manage Components

by telerik in telerik/kendo-themes

Create or update a Kendo UI component across kendo-themes packages.

No licenceAuto-check passedFrontend & Design

Install Manage Components

skills CLI
$ npx skills add telerik/kendo-themes --skill manage-components -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install telerik/kendo-themes manage-components --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/telerik/kendo-themes.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/manage-components .claude/skills/manage-components && rm -rf skills-src

Use ~/.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/

Facts

Skill name
manage-components
GitHub stars
158
Token cost
~2.3k tokens
SKILL.md length
863 words
Files
2 (incl. references)
Skills in repo
11
Repo updated
First seen
Licence
None found

At a glance

Create or update a Kendo UI component across kendo-themes packages.

  • Works in 12 steps: Derive naming constants → Research a reference component → Create SCSS variables → …
  • The user wants to add a new component
  • SKILL.md covers When to use, Inputs, Procedure — New Component and Procedure — Update Component, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Manage Components is an agent skill from telerik/kendo-themes. Create or update a Kendo UI component across kendo-themes packages. For new components, scaffolds core skeleton with null variables, theme overrides for targeted themes, HTML spec, templates, visual tests, and unit tests. For existing components, audits the current state, produces a change plan, and applies SCSS variable changes, layout/theme updates, HTML spec modifications, and test additions. Use this skill when the user wants to add a new component, update a component's design, change styling values, add new…

Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/update-checklist.md`).

It sits in Frontend & Design, covering CSS and styling, Unit testing and Project scaffolding. The repository describes itself as: Monorepo for SASS-based Kendo UI themes.

When your agent uses it

  • The user wants to add a new component
  • Update a components design
  • Change styling values
  • Align a component with design assets

Example prompts

  • “/manage-components”

Workflow steps

12 steps, taken from the step headings in SKILL.md.

  1. Derive naming constants
  2. Research a reference component
  3. Create SCSS variables
  4. Create SCSS styles, module, and register
  5. Create HTML spec
  6. Create HTML templates
  7. Create visual tests
  8. Create unit test
  9. Validate
  10. Derive naming constants
  11. Audit the current state
  12. Analyze design assets and produce change plan

What it can do on your machine

Read from SKILL.md and the folder at commit 153f3f6. 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

    No scripts in the folder and no shell commands in SKILL.md.

    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

Manage Components loads about 2.3k tokens when it runs, and up to ~3.9k if it reads all its reference files. Until then it costs about 149 tokens; SKILL.md has 863 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~149
When it runs · the whole SKILL.md, loaded when a task matches
~2.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.9k

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

Without a licence we can't republish the file, so here is its outline and opening line. It has 863 words (~2,286 tokens).

“Create or update a Kendo UI component across the monorepo.”

— opening of SKILL.md by telerik
name
manage-components
argument-hint
[component-name] e.g. chip, button, info-bar
metadata.internal
true

Read the full SKILL.md on GitHub

Files

SKILL.md and 1 other file (references) in .github/skills/manage-components of telerik/kendo-themes.

  • SKILL.md
  • references/update-checklist.md

Open the folder on GitHubat commit 153f3f6

Compare with similar skills

Manage Components 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.

Manage Components compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Manage Components this skilltelerik/kendo-themes158—~2.3kAutomated safety check: PassNone
Create ComponentOrange-OpenSource/Orange-Boosted-Bootstrap222—~648Automated safety check: PassMIT
Quasar Skilldskilld-dev/vue-ecosystem-skills181—~1.6kAutomated safety check: PassMIT
Docs LookupProgrammerAnthony/Expert-Coding-Harness235—~640Automated safety check: PassMIT
Frontend Guidelightly-ai/lightly-studio896—~2.9kAutomated safety check: PassApache-2.0
Create ComponentEndava/BEEQ163—~1.5kAutomated safety check: PassApache-2.0

Similar skills

  • Create Component

    Orange-OpenSource/Orange-Boosted-Bootstrap

    Step-by-step workflow for creating a new SCSS and/or JavaScript component in OUDS Web.

    222 GitHub stars~648 tokensUpdated today
    Frontend & DesignAuto-check passed
  • Quasar Skilld

    skilld-dev/vue-ecosystem-skills

    Build, configure, and debug apps with the Quasar framework (quasar npm package, v2.33.1).

    181 GitHub stars~1.6k tokensUpdated 16 days ago
    Frontend & DesignAuto-check passed
  • Docs Lookup

    ProgrammerAnthony/Expert-Coding-Harness

    通过 Context7 MCP 获取库和框架的实时最新文档,而非依赖训练数据,防止 API 幻觉。适用于查询任何库或框架的用法、配置、示例代码。触发词:怎么用、怎么配置、API参考、文档、示例代码、用法、接口、库文档、框架文档、documentation、docs、how to use、API…

    235 GitHub stars~640 tokensUpdated 5 mo ago
    Frontend & DesignAuto-check passed
  • Frontend Guide

    lightly-ai/lightly-studio

    Read before writing or reviewing any frontend code in lightlystudioview - Svelte, TypeScript, or SvelteKit files.

    896 GitHub stars~2.9k tokensUpdated today
    Frontend & DesignAuto-check passed
  • Create Component

    Endava/BEEQ

    Create a new BEEQ StencilJS web component. An agent skill from Endava/BEEQ.

    163 GitHub stars~1.5k tokensUpdated today
    Frontend & DesignAuto-check passed
  • Create Component

    adobe/skills

    Creates complete AEM components with dialog, HTL template, Sling Model, unit tests, and clientlibs.

    196 GitHub stars~4.3k tokensUpdated today
    Testing & QAAuto-check passed

More from telerik/kendo-themes

All 11 skills in this repo
  • Audit Design Tokens

    telerik/kendo-themes

    Audit and report on design token usage (color, spacing, typography, elevation, border-radius) across SCSS packages.

    158 GitHub stars~1.8k tokensUpdated yesterday
    Auto-check passed
  • Kendo Themes

    telerik/kendo-themes

    DEPRECATED — moved to the kendo-design plugin in telerik/ai-plugins (https://github.com/telerik/ai-plugins).

    158 GitHub stars~2.7k tokensUpdated yesterday
    Auto-check passed
  • Manage HTML A11y

    telerik/kendo-themes

    Create or update ARIA accessibility annotations and validate WCAG compliance for a Kendo UI component.

    158 GitHub stars~2k tokensUpdated yesterday
    Auto-check passed
  • Manage HTML Specs

    telerik/kendo-themes

    Create or update an HTML component specification (.spec.tsx) in the HTML package.

    158 GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed
  • Manage HTML Templates

    telerik/kendo-themes

    Create or update reusable HTML templates for a Kendo UI component in the HTML package.

    158 GitHub stars~1.8k tokensUpdated yesterday
    Auto-check passed
  • Manage HTML Tests

    telerik/kendo-themes

    Create or update visual test scenarios for a Kendo UI component in the HTML package.

    158 GitHub stars~1.8k tokensUpdated yesterday
    Auto-check passed

Questions about Manage Components

What does Manage Components do?

Create or update a Kendo UI component across kendo-themes packages. Manage Components is an agent skill from telerik/kendo-themes. Create or update a Kendo UI component across kendo-themes packages.

When should I use Manage Components?

Manage Components fits situations like: the user wants to add a new component; update a components design; change styling values; align a component with design assets.

How do I install Manage Components in Claude Code?

Run `npx skills add telerik/kendo-themes --skill manage-components -a claude-code`. Or copy the skill folder (.github/skills/manage-components in telerik/kendo-themes) into .claude/skills/manage-components in your project. Claude Code loads it when a task matches its description.

How do I install Manage Components in Codex?

Run `npx skills add telerik/kendo-themes --skill manage-components -a codex`. Or copy the skill folder (.github/skills/manage-components in telerik/kendo-themes) into .agents/skills/manage-components in your project. Codex loads it when a task matches its description.

Can I use Manage Components 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 telerik/kendo-themes --skill manage-components -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/manage-components, .gemini/skills/manage-components, .github/skills/manage-components and .opencode/skills/manage-components in your project.

What does Manage Components need to run?

SKILL.md names no scripts, command-line tools or credentials: Manage Components is instructions for the agent only.

Does Manage Components 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 Manage Components 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 Manage Components use?

No licence was found for Manage Components or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.

How many tokens does Manage Components use?

About 2.3k tokens (SKILL.md is roughly 9.1k 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 1.6k tokens, read only when the agent opens those files.

What are the alternatives to Manage Components?

Skills that share tags, products or a category with Manage Components: Create Component (Orange-OpenSource/Orange-Boosted-Bootstrap, 222 stars), Quasar Skilld (skilld-dev/vue-ecosystem-skills, 181 stars), Docs Lookup (ProgrammerAnthony/Expert-Coding-Harness, 235 stars) and Frontend Guide (lightly-ai/lightly-studio, 896 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Manage Components?

telerik (a GitHub organization) maintains it in telerik/kendo-themes, which has 158 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 7, 2026.

Source: telerik/kendo-themes on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.