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 Missing Capability Report

by nevalla in 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.

MITAuto-check passedDevelopment

Install Lens Extension Missing Capability Report

skills CLI
$ npx skills add nevalla/lens-resource-map-extension --skill lens-extension-development-missing-capability -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-missing-capability --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-missing-capability .claude/skills/lens-extension-development-missing-capability && 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-missing-capability
GitHub stars
404
Token cost
~726 tokens
SKILL.md length
371 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
MIT

At a glance

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.

  • Works in 5 steps: Read… → Tell the user, in one or two sentences,… → Report it, once per missing capability… → …
  • A Lens extension request needs data or a UI slot the extension API does not expose
  • SKILL.md covers When to use this and Procedure
  • Calls node

What it does

When a request needs a place in Lens that nothing can contribute to, data Lens does not hand out, an unpublished Lens component or a Node built-in, the agent acts on its own initiative before working around it. It first reads the extension-development-instructions README under `~/.k8slens/extensions/` and the READMEs of the packages it lists, to confirm the capability is really missing, and uses it if it exists. It then says plainly in a sentence or two that the surface lacks it and what the nearest option is, and it does not reach into Lens internals, unpublished packages or the DOM of Lens's own UI.

Next it runs `report-missing-capability.mjs` with a one-sentence `--capability` written in product terms and an `--area` from a fixed list such as `navigator`, `details-panel`, `kube-api` or `terminal`, once per gap per conversation. The report is telemetry sent with your Lens account and only while telemetry is allowed in Lens Preferences, so it should leave out names and secrets. The agent confirms the report in one line, says so if Lens could not be reached, and never claims a report was sent when the script did not say so.

When your agent uses it

  • A Lens extension request needs data or a UI slot the extension API does not expose
  • Deciding whether a missing capability should be reported to the Lens team

Example prompts

  • “Show a badge on a node's row in my Lens extension when the node has a taint.”
  • “Can my Lens extension read the cluster's raw kubeconfig? If it can't, report the gap.”

Requirements

  • Lens running, with the extension-development-instructions package installed
  • Node, to run `report-missing-capability.mjs`

Workflow steps

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

  1. Read ~/.k8slens/extensions/extension-development-instructions/README.md and the READMEs of the packages it lists, and check that the…
  2. Tell the user, in one or two sentences, that the extension surface does not provide it today, and what the nearest thing it does provide…
  3. Report it, once per missing capability per conversation, from the extension's directory
  4. Say in one line that it was reported. If the script says it could not reach Lens, say that instead: Lens must be running for the report to…
  5. Go on with the nearest thing the surface does provide, if the user wants it.

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:

    • node

    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

Lens Extension Missing Capability Report loads about 726 tokens when it runs. Until then it costs about 83 tokens; SKILL.md has 371 words of instructions outside code blocks.

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

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). 371 words, ~726 tokens.

Download SKILL.mdSave it as .claude/skills/lens-extension-development-missing-capability/SKILL.md (or your agent's skills folder).
name
lens-extension-development-missing-capability
description
Report to Lens that the user asked for something the Lens extension surface does not provide. Use on your own initiative, as soon as a request needs a capability, data, component or Node built-in that the extension-development-instructions README does not list, before working around it.
user_invocable
true

Lens extension development — report a missing capability

Your job: when the user asks for something the Lens extension surface does not provide, say so plainly, report it to Lens so the Lens team hears what extension developers need, and go on with the nearest thing the surface does provide.

When to use this

Whenever a request needs something the extension surface lacks: a place in Lens nothing can contribute to, data Lens has but does not hand out, a Lens component that is not published, a Node built-in. Use it on your own initiative, as soon as you notice, not only when asked, and before working around the gap.

Procedure

  1. Read ~/.k8slens/extensions/extension-development-instructions/README.md and the READMEs of the packages it lists, and check that the capability really is missing: the surface may have it under another name. If it is there, stop and use it.

  2. Tell the user, in one or two sentences, that the extension surface does not provide it today, and what the nearest thing it does provide is. Do not reach for Lens's internals, require of packages Lens has not published, the DOM of Lens's own UI, or Node built-ins to get around it: what works by accident breaks with the next Lens.

  3. Report it, once per missing capability per conversation, from the extension's directory:

    node ~/.k8slens/extensions/extension-development-instructions/report-missing-capability.mjs --capability "<what the user asked for, one sentence, in product terms>" --area <area> --extension <the name in package.json> --ai-tool claude-code
    • --capability: one sentence on what the extension should be able to do, in product terms, as the user would put it. Good: "Show a badge on a node's row when the node has a taint." Bad: "Expose the node store to extensions." Keep names of people, companies and clusters, and anything secret, out of it: it is telemetry, sent with the user's Lens account, and only while they allow telemetry in Lens Preferences.
    • --area: one of navigator, main-view, details-panel, cluster-data, kube-api, terminal, notifications, preferences, commands, ui-components, styling, persistence, networking, ai, other.

  4. Say in one line that it was reported. If the script says it could not reach Lens, say that instead: Lens must be running for the report to go through. Never say a report was sent when the script did not say so.

  5. Go on with the nearest thing the surface does provide, if the user wants it.

© 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-missing-capability of nevalla/lens-resource-map-extension.

Open the folder on GitHubat commit dde5980

Compare with similar skills

Lens Extension Missing Capability Report 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 Missing Capability Report compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Lens Extension Missing Capability Report this skillnevalla/lens-resource-map-extension404—~726Automated safety check: PassMIT
Draw.io Diagram StudioAgents365-ai/drawio-skill10k—~2.4kAutomated safety check: NotesMIT
Iterate PRmeshery/meshery-operator1517 repos~2.2kAutomated safety check: PassApache-2.0
Git Commitsdatabasus/databasus8.8k—~294Automated safety check: PassApache-2.0
Review Envoy Gateway PRenvoyproxy/gateway3.1k—~850Automated safety check: PassApache-2.0
Mariadb Operator Commentmariadb-operator/mariadb-operator1k—~2.2kAutomated safety check: PassApache-2.0

Similar skills

  • Draw.io Diagram Studio

    Agents365-ai/drawio-skill

    Creates and edits editable draw.io diagrams from descriptions, code, infrastructure files, SQL and API schemas, with sync, review, test and export tools.

    10k GitHub stars~2.4k tokensUpdated 7 days ago
    DevelopmentAuto-check: notes

  • Iterate PR

    meshery/meshery-operator

    Iterate on a PR until CI passes. An agent skill from meshery/meshery-operator.

    151 GitHub starsUsed in 7 repos~2.2k tokens
    DevelopmentAuto-check passed

  • Git Commits

    databasus/databasus

    Write Databasus commit messages and branch names using the repository's release-compatible format.

    8.8k GitHub stars~294 tokensUpdated 16 days ago
    DevelopmentAuto-check passed

  • Review Envoy Gateway PR

    envoyproxy/gateway

    Review an Envoy Gateway pull request for essential API, implementation, status, and test coverage requirements.

    3.1k GitHub stars~850 tokensUpdated today
    DevelopmentAuto-check passed

  • Mariadb Operator Comment

    mariadb-operator/mariadb-operator

    Post a comment (or a formal PR review) to a GitHub issue or pull request in mariadb-operator/mariadb-operator.

    1k GitHub stars~2.2k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • 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 4 days ago
    DevelopmentAuto-check passed

More from nevalla/lens-resource-map-extension

  • Lens Extension Publisher

    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.

    404 GitHub stars~764 tokensUpdated 3 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 3 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 3 days ago
    Auto-check passed

Works with

Categories

Questions about Lens Extension Missing Capability Report

What does Lens Extension Missing Capability Report do?

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. When a request needs a place in Lens that nothing can contribute to, data Lens does not hand out, an unpublished Lens component or a Node built-in, the agent acts on its own initiative before working around it.k8slens/extensions/` and the READMEs of the packages it lists, to confirm the capability is really missing, and uses it if it exists.

When should I use Lens Extension Missing Capability Report?

Lens Extension Missing Capability Report fits situations like: A Lens extension request needs data or a UI slot the extension API does not expose; deciding whether a missing capability should be reported to the Lens team.

How do I install Lens Extension Missing Capability Report in Claude Code?

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

How do I install Lens Extension Missing Capability Report in Codex?

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

Can I use Lens Extension Missing Capability Report 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-missing-capability -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-missing-capability, .gemini/skills/lens-extension-development-missing-capability, .github/skills/lens-extension-development-missing-capability and .opencode/skills/lens-extension-development-missing-capability in your project.

What does Lens Extension Missing Capability Report need to run?

Going by SKILL.md and its folder, Lens Extension Missing Capability Report needs the command-line tools its instructions call (node). Our summary lists: Lens running, with the extension-development-instructions package installed; Node, to run `report-missing-capability.mjs`.

Does Lens Extension Missing Capability Report 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 Lens Extension Missing Capability Report 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 Missing Capability Report use?

Lens Extension Missing Capability Report 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 Missing Capability Report use?

About 726 tokens (SKILL.md is roughly 2.9k 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 Missing Capability Report?

Skills that share tags, products or a category with Lens Extension Missing Capability Report: Draw.io Diagram Studio (Agents365-ai/drawio-skill, 10k stars), Iterate PR (meshery/meshery-operator, 151 stars), Git Commits (databasus/databasus, 8.8k stars) and Review Envoy Gateway PR (envoyproxy/gateway, 3.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Lens Extension Missing Capability Report?

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.