New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Upgrade Console SDK

by openshift-eng in openshift-eng/ai-helpers

Assists in the upgrade of an OpenShift Console dynamic plugin to the latest Console SDK version.

Apache-2.0Auto-check passedDevelopment

Install Upgrade Console SDK

skills CLI
$ npx skills add openshift-eng/ai-helpers --skill upgrade-console-sdk -a claude-code

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

GitHub CLI
$ gh skill install openshift-eng/ai-helpers upgrade-console-sdk --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/openshift-eng/ai-helpers.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/console/skills/upgrade-console-sdk .claude/skills/upgrade-console-sdk && 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
upgrade-console-sdk
GitHub stars
120
Token cost
~3.6k tokens
SKILL.md length
1,684 words
Files
1
Skills in repo
118
Repo updated
First seen
Licence
Apache-2.0

At a glance

Assists in the upgrade of an OpenShift Console dynamic plugin to the latest Console SDK version.

  • Works in 4 steps: Gather information → Fetch and research breaking changes → Present upgrade plan → …
  • Development work in your project
  • SKILL.md covers Usage, Background knowledge, Reference documentation and Upgrade procedure, plus 1 more section
  • Calls yarn, gh and npm; reaches raw.githubusercontent.com

What it does

Upgrade Console SDK is an agent skill from openshift-eng/ai-helpers. Assists in the upgrade of an OpenShift Console dynamic plugin to the latest Console SDK version.

Its SKILL.md is about 3.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Designed for Claude Code. Requires Node.js, gh CLI, and internet access.

It sits in Development. It works with React. The repository describes itself as: Developer productivity tools for Claude Code & other AI assistants. The licence is Apache-2.0.

When your agent uses it

  • Development work in your project

Example prompts

  • “Use the upgrade-console-sdk skill to assist in the upgrade of an OpenShift Console dynamic plugin to the latest Console SDK version”
  • “/upgrade-console-sdk”

Requirements

  • Node.js
  • Compatibility (from SKILL.md): Designed for Claude Code. Requires Node.js, gh CLI, and internet access.
  • Pre-approved tools (allowed-tools): Bash(gh api repos/openshift/console/contents/*), Bash(gh api repos/*/releases/tags/*), WebFetch(domain:raw.githubusercontent.com), AskUserQuestion, Bash(yarn npm info *), Bash(npm info *)

Workflow steps

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

  1. Gather information
  2. Fetch and research breaking changes
  3. Present upgrade plan
  4. Execute changes (with user approval)

What it can do on your machine

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

    • Bash(gh api repos/openshift/console/contents/*)
    • Bash(gh api repos/*/releases/tags/*)
    • WebFetch(domain:raw.githubusercontent.com)
    • AskUserQuestion
    • Bash(yarn npm info *)
    • Bash(npm info *)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • yarn
    • gh
    • npm
    • pnpm

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

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • raw.githubusercontent.com

    Also links to:

    • github.com

    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.

  • Compatibility

    Designed for Claude Code. Requires Node.js, gh CLI, and internet access.

    From compatibility in the SKILL.md frontmatter.

Context cost

Upgrade Console SDK loads about 3.6k tokens when it runs. Until then it costs about 29 tokens; SKILL.md has 1,684 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~29
When it runs · the whole SKILL.md, loaded when a task matches
~3.6k

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

The full file from openshift-eng/ai-helpers at commit a627176, republished under its Apache-2.0 licence (© openshift-eng). 1,684 words, ~3,638 tokens.

Download SKILL.mdSave it as .claude/skills/upgrade-console-sdk/SKILL.md (or your agent's skills folder).
name
upgrade-console-sdk
description
Assists in the upgrade of an OpenShift Console dynamic plugin to the latest Console SDK version.
allowed-tools
Bash(gh api repos/openshift/console/contents/*), Bash(gh api repos/*/releases/tags/*), WebFetch(domain:raw.githubusercontent.com), AskUserQuestion, Bash(yarn npm info *), Bash(npm info *)
compatibility
Designed for Claude Code. Requires Node.js, gh CLI, and internet access.
argument-hint
<current-target-version> <new-target-version>
license
Apache-2.0

Upgrade Console Plugin SDK

You are a senior software engineer with expertise in TypeScript, React, and webpack module federation, particularly in the context of OpenShift Console dynamic plugins. Your task is to assist developers in upgrading their Console dynamic plugins to a newer Console SDK version.

Usage

text
# Upgrade a Console plugin from version 4.18 to 4.22
/console:upgrade-console-sdk 4.18 4.22

The current-target-version and new-target-version arguments are mandatory -- when not provided, use the AskUserQuestion tool to gather this information from the user.

Background knowledge

What is OpenShift Console?

OpenShift Console is the web-based UI for Red Hat OpenShift Container Platform. It provides cluster management, workload monitoring, and administrative capabilities. Console is built with React and TypeScript, and is designed as an extensible platform that allows dynamic plugins to add functionality without rebuilding or redeploying the console itself.

How dynamic plugins work

Dynamic plugins use module federation to load plugin code over the network at runtime. This means:

  • Plugins are completely decoupled from the Console application -- they can be built, deployed, and upgraded independently.
  • Plugins are delivered as container images and registered on the cluster via a ConsolePlugin custom resource.
  • At startup, Console discovers enabled plugins and loads their assets (manifest, entry chunk, and exposed module chunks) from the cluster network.
  • Console and plugins share specific modules (React, Redux, PatternFly topology, etc.) at runtime via the Console's share scope. This ensures a single copy of React is running and plugins can use Console-provided hooks and components. Plugins must NOT bundle their own copies of shared modules.
  • Each plugin declares extensions (in console-extensions.json or inline in the bundler configuration file (e.g., webpack.config.ts/rspack.config.ts/rspack.config.mts)) that hook into Console's extension points -- adding pages, navigation items, resource views, dashboard cards, actions, and more.
  • Plugin code is referenced via $codeRef entries that point to exposed modules, which are loaded on demand.
SDK packages

There are two distributable SDK packages plugins depend on:

PackagePurpose
@openshift-console/dynamic-plugin-sdkCore runtime APIs, types, hooks, and components used by plugins at runtime
@openshift-console/dynamic-plugin-sdk-webpackWebpack/Rspack ConsoleRemotePlugin that generates plugin manifests, configures module federation, and manages shared modules

There is also @openshift-console/dynamic-plugin-sdk-internal which exposes additional Console code but has no backwards compatibility guarantees.

SDK package versioning

SDK packages follow a semver scheme where the major and minor version indicates the earliest supported OCP Console version, and the patch version indicates the release of that particular package. For example, 4.22.0 is the initial release targeting Console 4.22. Pre-release versions use the format 4.22.0-prerelease.1.

Shared modules

Console provides specific modules (e.g., React, Redux, routing libraries) to plugins at runtime via the Console's share scope. Plugins should list these as devDependencies (not dependencies) since Console supplies them. The exact list and versions change between Console releases -- when Console upgrades a shared module (e.g., React 17 to 18), all plugins must also upgrade to the matching version, since only one version of each singleton module can be loaded at runtime.

Always fetch the SDK README at runtime to get the current shared modules list.

Plugin metadata

Plugin metadata (consolePlugin object) can be specified in package.json or passed directly to ConsoleRemotePlugin in the bundler configuration file. Key fields:

  • name -- unique plugin identifier, must match the ConsolePlugin resource name on the cluster (must be a valid DNS subdomain name)
  • version -- semver version of the plugin
  • exposedModules -- map of module names to file paths that can be referenced via $codeRef
  • dependencies -- @console/pluginAPI semver range declaring which Console versions the plugin supports (e.g., "^4.21.0")

Reference documentation

The following remote sources are the single source of truth for upgrade information. You MUST fetch and read these at runtime -- do NOT rely on memorized or cached data about version-specific changes. If a fetch fails (e.g., a release notes file doesn't exist yet for a pre-release version, or a rate limit is hit), inform the user and proceed with the data you have.

SDK README (shared modules, versioning, PatternFly compatibility)

Fetch this file to determine shared modules, SDK version mapping, and PatternFly version compatibility:

https://raw.githubusercontent.com/openshift/console/refs/heads/main/frontend/packages/console-dynamic-plugin-sdk/README.md

SDK changelogs

Fetch both of these to identify breaking changes, type changes, deprecations, and new features across versions:

  • https://raw.githubusercontent.com/openshift/console/refs/heads/main/frontend/packages/console-dynamic-plugin-sdk/CHANGELOG-core.md
  • https://raw.githubusercontent.com/openshift/console/refs/heads/main/frontend/packages/console-dynamic-plugin-sdk/CHANGELOG-webpack.md
Release notes

Fetch the release notes for EACH version in the upgrade range (from one version above the current through the target). Release notes document shared module changes, CSS removals, migration guides, and upgrade tips.

Available release notes versions:

!gh api repos/openshift/console/contents/frontend/packages/console-dynamic-plugin-sdk/release-notes --jq '.[].name'

Fetch each relevant version using this URL pattern:

https://raw.githubusercontent.com/openshift/console/refs/heads/main/frontend/packages/console-dynamic-plugin-sdk/release-notes/<version>

Console plugin template (canonical reference implementation)

The console-plugin-template is the canonical reference for a Console dynamic plugin. Fetch its package.json, tsconfig.json, and rspack.config.ts for correct dependency versions, build configuration, and compiler options:

  • https://raw.githubusercontent.com/openshift/console-plugin-template/refs/heads/main/package.json
  • https://raw.githubusercontent.com/openshift/console-plugin-template/refs/heads/main/tsconfig.json
  • https://raw.githubusercontent.com/openshift/console-plugin-template/refs/heads/main/rspack.config.ts

Key patterns to note from the template:

  • SDK packages use dist-tags like 4.21-latest rather than exact versions. Check what dist-tag is current for the target version.
  • The consolePlugin.dependencies field uses a semver range like "@console/pluginAPI": "^4.21.0" to declare Console version compatibility.
  • The template may not always be updated to the very latest in-development SDK version. Cross-reference with the changelogs and release notes for the actual target version.
  • Note in the plugin template repo, rspack.config.ts is used for 4.23/5.0 and later. In previous verisons, webpack.config.ts is used. Both are supported and migration is discretionary. If migrating to rspack and type: "module" is not set in package.json, the configuration file may need to be named rspack.config.mts to avoid ESM to CJS interop overhead.

Upgrade procedure

Follow these steps in order:

Step 1: Gather information
  1. Read the plugin's package.json to understand current SDK versions, shared module versions, and PatternFly versions.
  2. Read the plugin's bundler configuration file to understand the build setup.
  3. Read the plugin's tsconfig.json to check compiler options.
  4. Read console-extensions.json if it exists, to understand extension types in use.
  5. Identify the current and target Console versions from the user's arguments.
  6. Detect the plugin's package manager (see below).
Show full SKILL.md (729 more words)Show less
Detecting the package manager

Determine which package manager the plugin uses by checking these indicators in order:

  1. packageManager field in package.json -- e.g., "packageManager": "yarn@4.13.0" means Yarn Berry (v4). This is the most reliable signal.
  2. Lock file present in the repo root:
    • yarn.lock -- Yarn (check format to distinguish v1 from Berry)
    • package-lock.json -- npm
    • pnpm-lock.yaml -- pnpm
  3. .yarnrc.yml file exists -- indicates Yarn Berry (v2 to v5). Yarn v1 uses .yarnrc (no .yml).
  4. If ambiguous, ask the user.

Use the detected package manager for ALL dependency operations throughout the upgrade:

Package ManagerInstallAdd/upgrade a dep
npmnpm installnpm install <pkg>@<version>
Yarn Classic (v1)yarn installyarn upgrade <pkg>@<version>
Yarn Berry (v2, v3, v4, v5)yarn installyarn up <pkg>@<version>
pnpmpnpm installpnpm update <pkg>@<version>
Step 2: Fetch and research breaking changes
  1. Fetch the SDK README to determine the current shared modules list, PatternFly compatibility table, and SDK version mapping.
  2. Fetch both changelogs (core and webpack) and extract all entries between the current and target versions. Categorize changes as:
    • Breaking -- requires code changes, plugin will not work without them
    • Type breaking -- TypeScript type changes that may cause build failures
    • Deprecated -- still works but should be updated
    • New features -- optional improvements available
  3. Fetch the release notes for each version in the upgrade range. These contain critical information about shared module version changes, CSS removals, and migration guides not always covered in the changelogs.
  4. Fetch the plugin template files to use as a reference for correct dependency versions.
  5. If the upgrade requires major version bumps to shared modules (e.g., React 17 to 18, react-i18next v11 to v16, react-redux v7 to v9), fetch the upstream migration/upgrade guides for those libraries to inform your code migration steps:
    • React: fetch the changelog, then follow links to the relevant upgrade guide (e.g., react.dev/blog/2022/03/08/react-18-upgrade-guide for React 18): https://raw.githubusercontent.com/facebook/react/refs/heads/main/CHANGELOG.md
    • react-i18next: https://raw.githubusercontent.com/i18next/react-i18next/refs/heads/master/CHANGELOG.md
    • react-redux: changelogs are in GitHub release notes. Fetch the relevant major version release (e.g., for v9: gh api repos/reduxjs/react-redux/releases/tags/v9.0.0 --jq .body)
    • PatternFly: fetch the upgrade guide and release highlights from the patternfly-org repo (raw markdown, easier to parse than the website):
      • https://raw.githubusercontent.com/patternfly/patternfly-org/refs/heads/main/packages/documentation-site/patternfly-docs/content/releases/upgrade-guide.md
      • https://raw.githubusercontent.com/patternfly/patternfly-org/refs/heads/main/packages/documentation-site/patternfly-docs/content/releases/release-highlights.md
    • For any other shared module with a major version bump, search for its changelog or migration guide on GitHub/npm
Step 3: Present upgrade plan

Present a clear, versioned upgrade plan to the user that includes:

  1. Summary of breaking changes across the version range, ordered by impact
  2. SDK package version updates -- the exact package.json dependency changes needed
  3. Shared module version updates -- version bumps for shared modules like react, react-i18next, react-redux, redux, redux-thunk, etc. Use the plugin template and release notes as the source of truth for correct versions.
  4. PatternFly version changes -- if a PF major version change is required (refer to the compatibility table in the SDK README)
  5. Build tooling changes -- bundler version requirements, TypeScript version requirements, tsconfig changes
  6. Code migration steps -- specific code changes needed, with before/after examples drawn from the release notes migration guides
  7. Deprecation warnings -- things that still work but should be updated
Step 4: Execute changes (with user approval)

After the user approves the plan, make the changes:

  1. Update package.json SDK and shared module versions
  2. Update tsconfig.json if needed (e.g., jsx compiler option)
  3. Update the bundler configuration file if needed
  4. Apply code migrations for breaking changes
  5. Update console-extensions.json if extension types changed
  6. Run the appropriate install command for the detected package manager to update the lockfile
  7. Attempt a build and fix any remaining issues
  8. Run the plugin's test suite if available to catch regressions

Important notes

  • Always update the @console/pluginAPI semver range in plugin metadata (consolePlugin.dependencies) to match the new target version.
  • Shared modules should be listed as devDependencies (not dependencies) in the plugin's package.json, since Console provides them at runtime.
  • When upgrading across multiple major shared module versions (e.g., React 17 to 18), warn the user about potential runtime behavior changes beyond just type errors.
  • When React has a major version bump, @types/react must also be updated to match. Major @types/react versions introduce their own breaking changes (e.g., v18 removed implicit children from React.FC). Check the plugin template for the correct @types/react version.
  • PatternFly major version upgrades are significant -- recommend the user run the official PF codemods and review the PF upgrade guide.
  • If the plugin uses @openshift-console/dynamic-plugin-sdk-internal, warn that this package has no backwards compatibility guarantees.

© openshift-eng, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugins/console/skills/upgrade-console-sdk of openshift-eng/ai-helpers.

Open the folder on GitHubat commit a627176

Compare with similar skills

Upgrade Console SDK 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.

Upgrade Console SDK compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Upgrade Console SDK this skillopenshift-eng/ai-helpers120—~3.6kAutomated safety check: PassApache-2.0
Vercel Composition Patternssupabase/supabase111k59 repos~726Automated safety check: PassMIT
Electron Multi-Process ArchitectureiOfficeAI/AionUi33k1 repos~1.8kAutomated safety check: PassApache-2.0
Nx Generatenomcopter/react-mosaic4.8k7 repos~1.9kAutomated safety check: PassCustom licence
@pierre/diffs Code Renderingpierrecomputer/pierre6.2k2 repos~803Automated safety check: PassApache-2.0
OpenTUI Terminal Interfacescline/cline70k—~1.9kAutomated safety check: PassApache-2.0

Similar skills

  • Vercel Composition Patterns

    supabase/supabase

    Official

    React composition patterns that scale. An agent skill from supabase/supabase.

    111k GitHub starsUsed in 59 repos~726 tokens
    DevelopmentAuto-check passed

  • Electron Multi-Process Architecture

    iOfficeAI/AionUi

    Tells the agent where new code belongs in an Electron multi-process project and which APIs each process may use, with rules for new bridges, services, agents and workers.

    33k GitHub starsUsed in 1 repo~1.8k tokens
    DevelopmentAuto-check passed

  • Nx Generate

    nomcopter/react-mosaic

    Generate code using nx generators. An agent skill from nomcopter/react-mosaic.

    4.8k GitHub starsUsed in 7 repos~1.9k tokens
    DevelopmentAuto-check passed

  • @pierre/diffs Code Rendering

    pierrecomputer/pierre

    Guides an agent through using @pierre/diffs to render syntax-highlighted files and diffs, and to build editing and review surfaces in React or plain JavaScript.

    6.2k GitHub starsUsed in 2 repos~803 tokens
    DevelopmentAuto-check passed

  • OpenTUI Terminal Interfaces

    cline/cline

    Helps build terminal user interfaces with OpenTUI using its core imperative API or its React and Solid reconcilers, with references for layout, keyboard, animation and testing.

    70k GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check passed

  • Claude Code Skill

    codeaashu/claude-code

    Development conventions and architecture guide for the Claude Code CLI repository.

    3.4k GitHub starsUsed in 1 repo~2.7k tokens
    DevelopmentAuto-check passed

More from openshift-eng/ai-helpers

All 118 skills in this repo

  • Investigate CI Reliability

    openshift-eng/ai-helpers

    Find and independently validate actionable reliability defects across OpenShift release jobs and presubmits, then export portable issue handoffs.

    120 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed

  • Address Review PR

    openshift-eng/ai-helpers

    Fetch and address all PR review comments — categorize by priority, make code changes, post replies, and push.

    120 GitHub stars~2.9k tokensUpdated yesterday
    Auto-check passed

  • Categorize Activity Types

    openshift-eng/ai-helpers

    Categorize Jira issues into Red Hat Sankey Activity Type categories using MCP Jira tools.

    120 GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed

  • Has Review Work

    openshift-eng/ai-helpers

    Decide whether a GitHub PR has unanswered authorized review comments or new required CI failures worth a follow-up agent.

    120 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed

  • Must Gather Analyzer

    openshift-eng/ai-helpers

    Analyze OpenShift must-gather diagnostic data including cluster operators, pods, nodes, and network components.

    120 GitHub stars~2.3k tokensUpdated yesterday
    Auto-check passed

  • Payload Autodl JSON

    openshift-eng/ai-helpers

    Schema for the autodl JSON data file produced by payload-analysis for database ingestion — you must use this skill whenever generating the autodl JSON file

    120 GitHub stars~2.6k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Upgrade Console SDK

What does Upgrade Console SDK do?

Assists in the upgrade of an OpenShift Console dynamic plugin to the latest Console SDK version. Upgrade Console SDK is an agent skill from openshift-eng/ai-helpers. Assists in the upgrade of an OpenShift Console dynamic plugin to the latest Console SDK version.

When should I use Upgrade Console SDK?

Upgrade Console SDK fits situations like: development work in your project.

How do I install Upgrade Console SDK in Claude Code?

Run `npx skills add openshift-eng/ai-helpers --skill upgrade-console-sdk -a claude-code`. Or copy the skill folder (plugins/console/skills/upgrade-console-sdk in openshift-eng/ai-helpers) into .claude/skills/upgrade-console-sdk in your project. Claude Code loads it when a task matches its description.

How do I install Upgrade Console SDK in Codex?

Run `npx skills add openshift-eng/ai-helpers --skill upgrade-console-sdk -a codex`. Or copy the skill folder (plugins/console/skills/upgrade-console-sdk in openshift-eng/ai-helpers) into .agents/skills/upgrade-console-sdk in your project. Codex loads it when a task matches its description.

Can I use Upgrade Console SDK 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 openshift-eng/ai-helpers --skill upgrade-console-sdk -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/upgrade-console-sdk, .gemini/skills/upgrade-console-sdk, .github/skills/upgrade-console-sdk and .opencode/skills/upgrade-console-sdk in your project.

What does Upgrade Console SDK need to run?

Going by SKILL.md and its folder, Upgrade Console SDK needs the command-line tools its instructions call (yarn, gh, npm and pnpm). Our summary lists: Node.js. Its frontmatter pre-approves these tools: Bash(gh api repos/openshift/console/contents/*), Bash(gh api repos/*/releases/tags/*), WebFetch(domain:raw.githubusercontent.com), AskUserQuestion, Bash(yarn npm info *), Bash(npm info *). Compatibility (from SKILL.md): Designed for Claude Code. Requires Node.js, gh CLI, and internet access..

Does Upgrade Console SDK access the network?

SKILL.md names 2 domains. In commands or code: raw.githubusercontent.com; the agent is likely to contact it when it follows the instructions. As links in the text: github.com. This is read from the text; nothing was executed.

Is Upgrade Console SDK 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 Upgrade Console SDK use?

Upgrade Console SDK is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Upgrade Console SDK use?

About 3.6k 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.

What are the alternatives to Upgrade Console SDK?

Skills that share tags, products or a category with Upgrade Console SDK: Vercel Composition Patterns (supabase/supabase, 111k stars), Electron Multi-Process Architecture (iOfficeAI/AionUi, 33k stars), Nx Generate (nomcopter/react-mosaic, 4.8k stars) and @pierre/diffs Code Rendering (pierrecomputer/pierre, 6.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Upgrade Console SDK?

openshift-eng (a GitHub organization) maintains it in openshift-eng/ai-helpers, which has 120 GitHub stars. The repository holds 118 skills in this directory. The repository was last updated on October 6, 2026.

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