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

Lens Extension Publisher

by nevalla in nevalla/lens-resource-map-extension

Gets a Lens Kubernetes-IDE extension ready for release and has the running Lens app publish it, instead of running npm login or npm publish directly.

MITAuto-check passedDevelopment

Install Lens Extension Publisher

skills CLI
$ npx skills add nevalla/lens-resource-map-extension --skill lens-extension-development-publish -a claude-code

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

GitHub CLI
$ gh skill install nevalla/lens-resource-map-extension lens-extension-development-publish --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/nevalla/lens-resource-map-extension.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/lens-extension-development-publish .claude/skills/lens-extension-development-publish && 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
lens-extension-development-publish
GitHub stars
404
Token cost
~764 tokens
SKILL.md length
435 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
MIT

At a glance

Gets a Lens Kubernetes-IDE extension ready for release and has the running Lens app publish it, instead of running npm login or npm publish directly.

  • Works in 5 steps: Read the Publish section of… → Fix what Lens's Publish dialog would… → Check that README.md and description… → …
  • Publishing a new version of a Lens extension
  • SKILL.md covers Never publish with npm yourself and Procedure
  • Calls npm and node

What it does

Explains why npm itself must not be used here: a terminal sign-in cannot pass npm's two-factor check, so publishing fails that way. Lens runs its own npm session instead, signing the user into npm in the browser, confirming two-factor authentication, building the extension and publishing it from there.

Before that happens, the skill checks everything Lens's Publish dialog would otherwise warn about: an SPDX license plus a matching LICENSE file, an author, a repository URL, a bugs URL, the `lens-extension` keyword, and the extension's own icon and banner, all read from `package.json`. Anything only the user can decide, such as the license or where bugs are reported, is asked rather than chosen automatically.

It also checks that `README.md` and the package description still match what the extension does, that the changelog has a heading for the current version, and raises the version first if that version is already published on npm. Once everything checks out, it tells the user to switch to Lens, runs the bundled publish script, and waits as long as it takes for the user to complete and close the Publish dialog.

When your agent uses it

  • Publishing a new version of a Lens extension
  • Checking a Lens extension's package.json before a first release
  • Fixing what Lens's Publish dialog would warn about before publishing
  • Raising an extension's version before a release that's already on npm

Example prompts

  • “Get this Lens extension ready and publish the new version.”
  • “Check my package.json for anything Lens's Publish dialog would flag.”
  • “This version is already on npm — bump it and then publish.”

Requirements

  • Lens running locally
  • A package.json with the required Lens extension fields

Workflow steps

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

  1. Read the Publish section of ~/.k8slens/extensions/extension-development-instructions/README.md, and do what it asks before a first…
  2. Fix what Lens's Publish dialog would warn of, so the user is not stopped there. Check each of these, and fix what is missing
  3. Check that README.md and description still describe what the extension does, that README.md has the link to the extension in Lens the…
  4. Tell the user Lens is about to ask them to publish, and to switch to Lens. Then run, from the extension's directory
  5. Say how it went, as the script printed it: published, failed and why, or closed without publishing. On a failure, fix what the reason…

What it can do on your machine

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

    • npm
    • node

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

  • Network

    No URLs in SKILL.md. Its commands use npm, 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

Lens Extension Publisher loads about 764 tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 435 words of instructions outside code blocks.

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

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 nevalla/lens-resource-map-extension at commit dde5980, republished under its MIT licence (© nevalla). 435 words, ~764 tokens.

Download SKILL.mdSave it as .claude/skills/lens-extension-development-publish/SKILL.md (or your agent's skills folder).
name
lens-extension-development-publish
description
Publish the Lens extension to npm, through Lens's own Publish dialog. Use whenever the user asks to publish or release the extension, instead of running npm login or npm publish.
user_invocable
true

Lens extension development: publish

Your job: get the extension ready to publish, then have the running Lens publish it, and say how it went.

Never publish with npm yourself

Do not run npm login or npm publish, and do not ask the user to run them. A sign-in in your shell does not get through npm's two-factor checks, and the publish fails. Lens publishes in an npm session of its own: it signs the user in to npm in the browser, checks the account has two-factor authentication, builds the extension and publishes it.

Procedure

  1. Read the Publish section of ~/.k8slens/extensions/extension-development-instructions/README.md, and do what it asks before a first publish, such as checking the package name is free.

  2. Fix what Lens's Publish dialog would warn of, so the user is not stopped there. Check each of these, and fix what is missing:

    • license in package.json names an SPDX license, and a matching LICENSE file is there.
    • author in package.json names who the author is.
    • repository in package.json names where the source is.
    • bugs in package.json names where users report problems.
    • keywords in package.json has lens-extension.
    • lensExtension.icon in package.json names an icon of the extension's own.
    • lensExtension.banner in package.json names a banner of the extension's own.

    Ask the user where only they can decide, such as the license, the author, or where users report problems. Do not choose for them.

  3. Check that README.md and description still describe what the extension does, that README.md has the link to the extension in Lens the instructions' Keep the README, the changelog and the description current names, and that CHANGELOG.md has a heading for the version in package.json. If that version is on npm already (npm view <name>@<version> version prints it), raise the version first.

  4. Tell the user Lens is about to ask them to publish, and to switch to Lens. Then run, from the extension's directory:

    node ~/.k8slens/extensions/extension-development-instructions/publish-extension.mjs --ai-tool claude-code

    Lens opens Publish in its window. The user confirms there, signs in to npm in the browser if asked, and approves the publish. The script waits until the user closes Publish, so give it as long as it takes.

  5. Say how it went, as the script printed it: published, failed and why, or closed without publishing. On a failure, fix what the reason names, if it is yours to fix, and offer to try again. If the script could not reach Lens, ask the user to click Publish in Lens instead: on the toolbar of the terminal the extension is developed in, or on its details tab. Never say it was published when the script did not say so.

© nevalla, MIT. 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 .claude/skills/lens-extension-development-publish of nevalla/lens-resource-map-extension.

Open the folder on GitHubat commit dde5980

Compare with similar skills

Lens Extension Publisher 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.

Lens Extension Publisher compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Lens Extension Publisher this skillnevalla/lens-resource-map-extension404—~764Automated safety check: PassMIT
Releasengrok/ngrok-operator272—~2.7kAutomated safety check: PassMIT
Remotion Bits Releaseav/remotion-bits490—~1.2kAutomated safety check: PassNone
Cline CLI Release Publishercline/cline70k—~3.4kAutomated safety check: WarnApache-2.0
Releasehyhmrright/brooks-lint1.5k—~1.2kAutomated safety check: PassMIT
TS SDK Authormindfold-ai/Trellis15k—~6.1kAutomated safety check: PassMIT

Similar skills

  • Release

    ngrok/ngrok-operator

    Automates the ngrok-operator release process: gathers PR data, classifies changes by component (container, Helm chart, CRDs chart), generates changelogs, updates version files, and prepares the…

    272 GitHub stars~2.7k tokensUpdated 6 days ago
    DevelopmentAuto-check passed

  • Remotion Bits Release

    av/remotion-bits

    Runs the full release of the remotion-bits package: version bump, changelog, registry build, release commit, GitHub release, docs deploy and npm publish.

    490 GitHub stars~1.2k tokensUpdated 25 days ago
    DevelopmentAuto-check passed

  • Cline CLI Release Publisher

    cline/cline

    Walks through releasing the Cline CLI package to npm: release notes, version bump, matching git tag, and either the GitHub workflow or a local publish.

    70k GitHub stars~3.4k tokensUpdated today
    DevelopmentAuto-check: warnings

  • Release

    hyhmrright/brooks-lint

    Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG…

    1.5k GitHub stars~1.2k tokensUpdated 6 days ago
    DevelopmentAuto-check passed

  • TS SDK Author

    mindfold-ai/Trellis

    Design, build, verify, and publish production-grade TypeScript SDKs as npm packages inside a pnpm monorepo.

    15k GitHub stars~6.1k tokensUpdated 11 days ago
    DevelopmentAuto-check passed

  • ClawRouter Release Checklist

    BlockRunAI/ClawRouter

    Walks the agent through every ClawRouter release step in order, from the version bump and changelog entry to build, tests, npm publish, git tag and GitHub release.

    6.6k GitHub stars~1.4k tokensUpdated 5 days ago
    DevelopmentAuto-check passed

More from nevalla/lens-resource-map-extension

  • Lens Extension Missing Capability Report

    nevalla/lens-resource-map-extension

    Tells the user when a request needs something the Lens extension surface does not offer, reports the gap to Lens, and carries on with the nearest supported option.

    404 GitHub stars~726 tokensUpdated 4 days ago
    Auto-check passed

  • Lens Extension Dependency Sync

    nevalla/lens-resource-map-extension

    Aligns a Lens extension's package.json ranges with the dependency versions bundled in the running Lens build, then reinstalls and rebuilds.

    404 GitHub stars~709 tokensUpdated 4 days ago
    Auto-check passed

  • Lens Extension Idea Menu

    nevalla/lens-resource-map-extension

    Propose starter prompts for this Lens extension based on the host's current extension-development-instructions.

    404 GitHub stars~665 tokensUpdated 4 days ago
    Auto-check passed

Works with

Categories

Questions about Lens Extension Publisher

What does Lens Extension Publisher do?

Gets a Lens Kubernetes-IDE extension ready for release and has the running Lens app publish it, instead of running npm login or npm publish directly. Explains why npm itself must not be used here: a terminal sign-in cannot pass npm's two-factor check, so publishing fails that way. Lens runs its own npm session instead, signing the user into npm in the browser, confirming two-factor authentication, building the extension and publishing it from there.

When should I use Lens Extension Publisher?

Lens Extension Publisher fits situations like: publishing a new version of a Lens extension; checking a Lens extension's package.json before a first release; fixing what Lens's Publish dialog would warn about before publishing; raising an extension's version before a release that's already on npm.

How do I install Lens Extension Publisher in Claude Code?

Run `npx skills add nevalla/lens-resource-map-extension --skill lens-extension-development-publish -a claude-code`. Or copy the skill folder (.claude/skills/lens-extension-development-publish in nevalla/lens-resource-map-extension) into .claude/skills/lens-extension-development-publish in your project. Claude Code loads it when a task matches its description.

How do I install Lens Extension Publisher in Codex?

Run `npx skills add nevalla/lens-resource-map-extension --skill lens-extension-development-publish -a codex`. Or copy the skill folder (.claude/skills/lens-extension-development-publish in nevalla/lens-resource-map-extension) into .agents/skills/lens-extension-development-publish in your project. Codex loads it when a task matches its description.

Can I use Lens Extension Publisher 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 nevalla/lens-resource-map-extension --skill lens-extension-development-publish -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lens-extension-development-publish, .gemini/skills/lens-extension-development-publish, .github/skills/lens-extension-development-publish and .opencode/skills/lens-extension-development-publish in your project.

What does Lens Extension Publisher need to run?

Going by SKILL.md and its folder, Lens Extension Publisher needs the command-line tools its instructions call (npm and node). Our summary lists: Lens running locally; A package.json with the required Lens extension fields.

Does Lens Extension Publisher access the network?

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

Is Lens Extension Publisher 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 Lens Extension Publisher use?

Lens Extension Publisher is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Lens Extension Publisher use?

About 764 tokens (SKILL.md is roughly 3.1k 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 Lens Extension Publisher?

Skills that share tags, products or a category with Lens Extension Publisher: Release (ngrok/ngrok-operator, 272 stars), Remotion Bits Release (av/remotion-bits, 490 stars), Cline CLI Release Publisher (cline/cline, 70k stars) and Release (hyhmrright/brooks-lint, 1.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Lens Extension Publisher?

nevalla (a GitHub user) maintains it in nevalla/lens-resource-map-extension, which has 404 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 6, 2026.

Source: nevalla/lens-resource-map-extension on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.