Agent skill

Frontend Forge Extension Operations

by kubesphere in kubesphere/kubesphere

Runs the lifecycle of FrontendExtension resources in a Kubernetes cluster: create, rebuild, package, publish, unpublish, delete and debug stuck states.

Custom licenceAuto-check passedDevOps & Cloud

Install Frontend Forge Extension Operations

skills CLI
$ npx skills add kubesphere/kubesphere --skill frontend-forge-fe-operations -a claude-code

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

GitHub CLI
$ gh skill install kubesphere/kubesphere frontend-forge-fe-operations --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/kubesphere/kubesphere.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/frontend-forge-fe-operations .claude/skills/frontend-forge-fe-operations && 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
frontend-forge-fe-operations
GitHub stars
17k
Token cost
~3.2k tokens
SKILL.md length
1,032 words
Files
6 (incl. references)
Skills in repo
32
Repo updated
First seen
Licence
Custom licence

At a glance

Runs the lifecycle of FrontendExtension resources in a Kubernetes cluster: create, rebuild, package, publish, unpublish, delete and debug stuck states.

  • Works in 5 steps: Inspect the FE object and status first. → If package state is not Ready, inspect… → If package state is Ready but download… → …
  • Creating or updating a FrontendExtension and checking its package build
  • SKILL.md covers When to use, Quick Entry, Preconditions and Source of truth, plus 7 more sections
  • Calls kubectl and curl

What it does

This skill covers operational work on FrontendExtension (FE) resources in frontend-forge: creating or updating an FE manifest, triggering or inspecting package generation, forcing a rebuild with the rebuild-token annotation, downloading the generated package, and publishing, unpublishing or deleting an extension. It also covers inspecting status, conditions, labels, package and publish Jobs, artifact ConfigMaps and publish targets.

Debugging focuses on package phases such as Packaging, Ready and Failed and on publish phases such as Pending, Running, Succeeded and Failed. Three reference files split the work: lifecycle for create, update and rebuild, api for publish, unpublish, download and listing, and inspection for Jobs, labels and conditions. The skill prefers live cluster state over repo docs, and sends FrontendIntegration runtime JSBundle work to a different skill.

Preconditions are that kubectl points at the target cluster, the FE CRD and its controller are installed, the FE API is available for download and publish calls, the build service is reachable from package Jobs, and publish target data exists.

When your agent uses it

  • Creating or updating a FrontendExtension and checking its package build
  • Forcing a rebuild of an extension package
  • Publishing, unpublishing or deleting an extension
  • Debugging an extension stuck in Packaging or a failed publish Job

Example prompts

  • “Create a FrontendExtension for the dashboard plugin and watch its package Job.”
  • “Force a rebuild of the FE named my-ext using the rebuild-token annotation.”
  • “Why is my FE stuck in Packaging? Inspect the package Job and the controller logs.”
  • “Publish the extension, then unpublish it again and confirm the labels changed.”

Requirements

  • kubectl access to the target cluster
  • The FrontendExtension CRD and its controller installed
  • The FE API, for download, publish and unpublish operations

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Inspect the FE object and status first.
  2. If package state is not Ready, inspect status.conditions, status.packageJob, package Job logs, build-service reachability, and artifact…
  3. If package state is Ready but download fails, inspect status.download, status.artifact.storage, the artifact ConfigMap key, and digest…
  4. If publish or unpublish fails, inspect status.publish or status.unpublish, publisher Job logs, target ConfigMap or Secret contents, and…
  5. If live behavior differs from expected defaults, inspect controller deployment env vars and Helm values before changing the FE.

What it can do on your machine

Read from SKILL.md and the folder at commit 04a29b5. 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:

    • kubectl
    • curl

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use kubectl and curl, which can reach the network depending on how they are called.

    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

Frontend Forge Extension Operations loads about 3.2k tokens when it runs, and up to ~9k if it reads all its reference files. Until then it costs about 140 tokens; SKILL.md has 1,032 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~140
When it runs · the whole SKILL.md, loaded when a task matches
~3.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~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

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,032 words (~3,164 tokens).

“Use this skill for operational work around FrontendExtension resources:”

— opening of SKILL.md by kubesphere, Custom licence
name
frontend-forge-fe-operations

Read the full SKILL.md on GitHub

Files

SKILL.md and 5 other files (references) in skills/frontend-forge-fe-operations of kubesphere/kubesphere.

  • SKILL.md
  • agents/openai.yaml
  • evals/evals.json
  • references/api.md
  • references/inspection.md
  • references/lifecycle.md

Open the folder on GitHubat commit 04a29b5

Compare with similar skills

Frontend Forge Extension Operations 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.

Frontend Forge Extension Operations compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Frontend Forge Extension Operations this skillkubesphere/kubesphere17k—~3.2kAutomated safety check: PassCustom licence
Intrinsic Core Debuggingintrinsic-ai/intrinsic-core553—~3.8kAutomated safety check: NotesApache-2.0
Kubeshark Installerkubeshark/kubeshark12k—~3.6kAutomated safety check: NotesApache-2.0
LangBot Deployment Guidelangbot-app/LangBot18k—~1.2kAutomated safety check: NotesApache-2.0
Openbkn Deployopenbkn-ai/bkn-foundry636—~1.9kAutomated safety check: NotesCustom licence
KubeShark for KubernetesLukasNiessen/kubernetes-skill444—~1.2kAutomated safety check: PassMIT

Similar skills

  • Intrinsic Core Debugging

    intrinsic-ai/intrinsic-core

    Meta-level debugging workflows, architectural layer isolation, and progressive disclosure routing across Envoy ingress, Kubernetes pods, Behavior Trees, ObjectWorld synchronization, ICON real-time…

    553 GitHub stars~3.8k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes
  • Kubeshark Installer

    kubeshark/kubeshark

    Installs and configures Kubeshark on a Kubernetes cluster, choosing between the quick CLI path and a Helm install with custom values.

    12k GitHub stars~3.6k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes
  • LangBot Deployment Guide

    langbot-app/LangBot

    Deploys and configures a LangBot instance with Docker Compose or Kubernetes, covering config.yaml, the Box sandbox runtime, the plugin runtime and the global API key.

    18k GitHub stars~1.2k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes
  • Openbkn Deploy

    openbkn-ai/bkn-foundry

    Deploy or upgrade OpenBKN on a customer-authorized Linux server through the repository's deploy scripts, with preflight checks, explicit confirmation, secret handling, and post-deployment…

    636 GitHub stars~1.9k tokensUpdated today
    DevOps & CloudAuto-check: notes
  • KubeShark for Kubernetes

    LukasNiessen/kubernetes-skill

    Keeps Kubernetes manifests, Helm charts and policies grounded by diagnosing six failure modes, such as insecure defaults and API drift, and loading only matching references.

    444 GitHub stars~1.2k tokensUpdated 25 days ago
    DevOps & CloudAuto-check passed
  • Debug Openshell Cluster

    NVIDIA/OpenShell

    Official

    Debug why an OpenShell gateway deployment is unhealthy, unreachable, or unable to create sandboxes.

    15k GitHub stars~19k tokensUpdated today
    DevOps & CloudAuto-check: notes

More from kubesphere/kubesphere

All 32 skills in this repo
  • Creates and queries KubeSphere users, workspaces and projects and assigns built-in roles, defaulting to least privilege and never deleting anything.

    17k GitHub starsUsed in 1 repo~3.1k tokens
    Auto-check passed
  • KubeSphere ServiceMesh Manager

    kubesphere/kubesphere

    Installs, checks and troubleshoots the KubeSphere ServiceMesh extension (Istio, Kiali, Jaeger), including grayscale release, sidecar injection, topology and tracing issues.

    17k GitHub stars~2.4k tokensUpdated 2 mo ago
    Auto-check passed
  • KubeEye Cluster Inspection

    kubesphere/kubesphere

    Deploys KubeEye on KubeSphere and writes InspectRule and InspectPlan resources to inspect cluster health, then retrieves the inspection reports.

    17k GitHub stars~3.6k tokensUpdated 2 mo ago
    Auto-check passed
  • KubeSphere NodeGroup Operations

    kubesphere/kubesphere

    Queries, creates, updates, binds and troubleshoots NodeGroup resources in the edgewize nodegroup project through a bundled authenticated API script.

    17k GitHub stars~1.9k tokensUpdated 2 mo ago
    Auto-check passed
  • WizTelemetry Platform Service

    kubesphere/kubesphere

    Installs and configures the WizTelemetry Platform Service extension for KubeSphere, the shared API server behind its observability extensions.

    17k GitHub stars~1.8k tokensUpdated 2 mo ago
    Auto-check passed
  • Frontend Forge FI Operations

    kubesphere/kubesphere

    Operates FrontendIntegration resources and the frontend-forge extension with kubectl: create from YAML, update, enable, disable, delete, inspect and troubleshoot builds.

    17k GitHub stars~1.3k tokensUpdated 2 mo ago
    Auto-check passed

Works with

Categories

Questions about Frontend Forge Extension Operations

What does Frontend Forge Extension Operations do?

Runs the lifecycle of FrontendExtension resources in a Kubernetes cluster: create, rebuild, package, publish, unpublish, delete and debug stuck states. This skill covers operational work on FrontendExtension (FE) resources in frontend-forge: creating or updating an FE manifest, triggering or inspecting package generation, forcing a rebuild with the rebuild-token annotation, downloading the generated package, and publishing, unpublishing or deleting an extension. It also covers inspecting status, conditions, labels, package and publish Jobs, artifact ConfigMaps and publish targets.

When should I use Frontend Forge Extension Operations?

Frontend Forge Extension Operations fits situations like: creating or updating a FrontendExtension and checking its package build; forcing a rebuild of an extension package; publishing, unpublishing or deleting an extension; debugging an extension stuck in Packaging or a failed publish Job.

How do I install Frontend Forge Extension Operations in Claude Code?

Run `npx skills add kubesphere/kubesphere --skill frontend-forge-fe-operations -a claude-code`. Or copy the skill folder (skills/frontend-forge-fe-operations in kubesphere/kubesphere) into .claude/skills/frontend-forge-fe-operations in your project. Claude Code loads it when a task matches its description.

How do I install Frontend Forge Extension Operations in Codex?

Run `npx skills add kubesphere/kubesphere --skill frontend-forge-fe-operations -a codex`. Or copy the skill folder (skills/frontend-forge-fe-operations in kubesphere/kubesphere) into .agents/skills/frontend-forge-fe-operations in your project. Codex loads it when a task matches its description.

Can I use Frontend Forge Extension Operations 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 kubesphere/kubesphere --skill frontend-forge-fe-operations -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/frontend-forge-fe-operations, .gemini/skills/frontend-forge-fe-operations, .github/skills/frontend-forge-fe-operations and .opencode/skills/frontend-forge-fe-operations in your project.

What does Frontend Forge Extension Operations need to run?

Going by SKILL.md and its folder, Frontend Forge Extension Operations needs the command-line tools its instructions call (kubectl and curl). Our summary lists: kubectl access to the target cluster; The FrontendExtension CRD and its controller installed; The FE API, for download, publish and unpublish operations.

Does Frontend Forge Extension Operations access the network?

SKILL.md contains no URLs. Its commands use curl, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Frontend Forge Extension Operations 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 Frontend Forge Extension Operations use?

Frontend Forge Extension Operations has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Frontend Forge Extension Operations use?

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

What are the alternatives to Frontend Forge Extension Operations?

Skills that share tags, products or a category with Frontend Forge Extension Operations: Intrinsic Core Debugging (intrinsic-ai/intrinsic-core, 553 stars), Kubeshark Installer (kubeshark/kubeshark, 12k stars), LangBot Deployment Guide (langbot-app/LangBot, 18k stars) and Openbkn Deploy (openbkn-ai/bkn-foundry, 636 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Frontend Forge Extension Operations?

kubesphere (a GitHub organization) maintains it in kubesphere/kubesphere, which has 17,060 GitHub stars. The repository holds 32 skills in this directory. The repository was last updated on July 15, 2026.

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