Agent skill

Helm Recon

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Product landscape reconnaissance — survey existing briefs, research, strategy, and team output before writing new briefs or dispatching specialists.

MITAuto-check: notesDevOps & Cloud

Install Helm Recon

skills CLI

$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill helm-recon -a claude-code

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

GitHub CLI

$ gh skill install jeremylongshore/tons-of-skills-marketplace helm-recon --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/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/helm-recon .claude/skills/helm-recon && 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/

Paste into Claude Code

Install the "helm-recon" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/helm-recon into .claude/skills/helm-recon/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "helm-recon", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/helm-recon

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill helm-recon -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install jeremylongshore/tons-of-skills-marketplace helm-recon --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/helm-recon .agents/skills/helm-recon && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "helm-recon" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/helm-recon into .agents/skills/helm-recon/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "helm-recon", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill helm-recon -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install jeremylongshore/tons-of-skills-marketplace helm-recon --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/helm-recon .cursor/skills/helm-recon && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "helm-recon" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/helm-recon into .cursor/skills/helm-recon/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "helm-recon", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace.git --path plugins/ai-agency/tonone/skills/helm-recon

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill helm-recon -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install jeremylongshore/tons-of-skills-marketplace helm-recon --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/helm-recon .gemini/skills/helm-recon && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "helm-recon" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/helm-recon into .gemini/skills/helm-recon/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "helm-recon", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install jeremylongshore/tons-of-skills-marketplace helm-recon

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill helm-recon -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/helm-recon .github/skills/helm-recon && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "helm-recon" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/helm-recon into .github/skills/helm-recon/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "helm-recon", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill helm-recon -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install jeremylongshore/tons-of-skills-marketplace helm-recon --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/helm-recon .opencode/skills/helm-recon && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "helm-recon" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/helm-recon into .opencode/skills/helm-recon/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "helm-recon", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: helm-recon
GitHub stars: 2.8k
Token cost: ~1k tokens
SKILL.md length: 287 words
Files: 2
Skills in repo: 3,342
Repo updated: Oct 10, 2026
First seen: Oct 8, 2026
Licence: MIT

At a glance

Product landscape reconnaissance — survey existing briefs, research, strategy, and team output before writing new briefs or dispatching specialists.

Works in 6 steps: Detect Environment → Inventory Product Artifacts → Inventory Research and User Insights → …
Asked to understand the product state
SKILL.md covers Steps and Delivery
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Helm Recon is an agent skill from jeremylongshore/tons-of-skills-marketplace. Product landscape reconnaissance — survey existing briefs, research, strategy, and team output before writing new briefs or dispatching specialists. Use when asked to "understand the product state", "what briefs exist", "what has the team produced", "orient me on this product", or before starting a new product initiative.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `.claude-plugin/plugin.json`).

It sits in DevOps & Cloud, covering Container orchestration. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

Asked to understand the product state
What briefs exist
What has the team produced
Orient me on this product

Example prompts

“understand the product state”
“what briefs exist”
“what has the team produced”
“/helm-recon”

Requirements

Pre-approved tools (allowed-tools): Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion

Workflow steps

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

Detect Environment
Inventory Product Artifacts
Inventory Research and User Insights
Inventory Specialist Output
Identify Gaps
Present Assessment

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. 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:
- Read
- Bash
- Glob
- Grep
- WebFetch
- WebSearch
- AskUserQuestion
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
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

Helm Recon loads about 1k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 287 words of instructions outside code blocks.

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

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NotePre-approves every shell command (allowed-tools: Bash)SKILL.md

allowed-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion

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 jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 287 words, ~1,033 tokens.

Download SKILL.mdSave it as .claude/skills/helm-recon/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: helm-recon
description: Product landscape reconnaissance — survey existing briefs, research, strategy, and team output before writing new briefs or dispatching specialists. Use when asked to "understand the product state", "what briefs exist", "what has the team produced", "orient me on this product", or before starting a new product initiative.
allowed-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
version: 0.6.4
author: tonone-ai <hello@tonone.ai>
license: MIT

Product Reconnaissance

You are Helm — the head of product on the Product Team. Map product landscape before writing briefs or dispatching specialists.

Steps

Step 0: Detect Environment

Scan for product and research artifacts:

bash

find . -name "*.md" | xargs grep -l "brief\|persona\|OKR\|roadmap\|strategy\|positioning" 2>/dev/null | head -20
ls docs/ research/ product/ briefs/ strategy/ 2>/dev/null

Step 1: Inventory Product Artifacts

Read and summarize:

Existing briefs — any files matching brief*.md, helm-brief*.md, or a briefs/ directory
Roadmaps — roadmap docs, now/next/later plans, quarterly plans
OKRs — objective/key-result documents, metric definitions
Strategy memos — vision docs, strategic narratives, bet-sizing documents
Competitive analysis — competitor comparisons, positioning 2x2s

Step 2: Inventory Research and User Insights

Read and summarize:

Personas — existing user persona cards or segment definitions
JTBD statements — jobs-to-be-done frameworks, user stories
Interview summaries — research synthesis, user feedback reports
Feedback data — NPS reports, support ticket themes, churn analysis
Analytics summaries — funnel reports, retention data, metric dashboards

Step 3: Inventory Specialist Output

Check what each product specialist has produced:

Specialist	Check For
Echo	Persona cards, interview reports, feedback synthesis
Lumen	Metrics frameworks, funnel analyses, A/B test results
Draft	User flows, wireframes, IA documents
Form	Brand guides, design systems, logo/color specs
Crest	Roadmaps, competitive analyses, OKRs
Pitch	Positioning statements, messaging frameworks, launch plans
Surge	Growth experiments, retention playbooks, PLG strategies

Step 4: Identify Gaps

For each category above, note:

What exists — artifact name and approximate freshness
What's missing — gaps that would block brief writing
What's stale — artifacts older than 3 months or out of sync with current state

Step 5: Present Assessment

Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.

## Product Reconnaissance

**Product:** [name] | **Stage:** [0→1 / growth / scaling / mature]

### Artifacts Inventory
| Area           | Status  | Last Updated | Notes |
|----------------|---------|--------------|-------|
| Briefs         | [✓/✗/~] | [date]       | [N] found |
| Roadmap        | [✓/✗/~] | [date]       | [horizon] |
| OKRs           | [✓/✗/~] | [date]       | [quarter] |
| Personas       | [✓/✗/~] | [date]       | [N] found |
| Research       | [✓/✗/~] | [date]       | [N] found |
| Competitive    | [✓/✗/~] | [date]       | [N] found |

### Key Insights from Existing Work
[2-4 bullet points — the most important things already known]

### Gaps Before Brief Writing
- [BLOCKING] [gap that must be filled first]
- [USEFUL] [gap that would help but isn't blocking]

### Recommended Next Step
[Which specialist to dispatch first, and why]

Delivery

If output exceeds the 40-line CLI budget, invoke /atlas-report with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.

Files

SKILL.md and 1 other file in plugins/ai-agency/tonone/skills/helm-recon of jeremylongshore/tons-of-skills-marketplace.

SKILL.md
.claude-plugin/plugin.json

Open the folder on GitHubat commit cfae287

Compare with similar skills

Helm Recon 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.

Helm Recon compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Helm Recon this skilljeremylongshore/tons-of-skills-marketplace	2.8k	—	~1k	Automated safety check: Notes	MIT	yesterday
Kubeshark Installerkubeshark/kubeshark	12k	—	~3.6k	Automated safety check: Notes	Apache-2.0	yesterday
KubeSphere Multi-Tenant Managementkubesphere/kubesphere	17k	—	~3.1k	Automated safety check: Pass	Custom licence	2 mo ago
Sim Helmsimstudioai/sim	30k	—	~2.2k	Automated safety check: Pass	Apache-2.0	today
Helm Chart ScaffoldingCybereason-Public/owLSM	280	13 repos	~381	Automated safety check: Pass	GPL-2.0	3 days ago
Mirrord Operatormetalbear-co/mirrord	5.4k	1 repos	~4.6k	Automated safety check: Pass	MIT	today

Similar skills

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
KubeSphere Multi-Tenant Management
kubesphere/kubesphere
Creates and queries KubeSphere users, workspaces and projects and assigns built-in roles, defaulting to least privilege and never deleting anything.
17k GitHub stars~3.1k tokensUpdated 2 mo ago
DevOps & CloudAuto-check passed
Sim Helm
simstudioai/sim
Install, upgrade, and operate the Sim Helm chart on Kubernetes.
30k GitHub stars~2.2k tokensUpdated today
DevOps & CloudAuto-check passed
Helm Chart Scaffolding
Cybereason-Public/owLSM
Comprehensive guidance for creating, organizing, and managing Helm charts for packaging and deploying Kubernetes applications.
280 GitHub starsUsed in 13 repos~381 tokens
DevOps & CloudAuto-check passed
Mirrord Operator
metalbear-co/mirrord
Help users install and configure the mirrord Operator for team/enterprise environments.
5.4k GitHub starsUsed in 1 repo~4.6k tokens
DevOps & CloudAuto-check passed
Kubeshark KFL2 Filter Reference
kubeshark/kubeshark
Syntax reference for KFL2, the CEL-based display filter language used to search Kubernetes network traffic captured by Kubeshark, loaded before any filter is written.
12k GitHub stars~3.6k tokensUpdated yesterday
DevOps & CloudAuto-check passed

Questions about Helm Recon

What does Helm Recon do?

Product landscape reconnaissance — survey existing briefs, research, strategy, and team output before writing new briefs or dispatching specialists. Helm Recon is an agent skill from jeremylongshore/tons-of-skills-marketplace. Product landscape reconnaissance — survey existing briefs, research, strategy, and team output before writing new briefs or dispatching specialists.

When should I use Helm Recon?

Helm Recon fits situations like: asked to understand the product state; what briefs exist; what has the team produced; orient me on this product.

How do I install Helm Recon in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill helm-recon -a claude-code`. Or copy the skill folder (plugins/ai-agency/tonone/skills/helm-recon in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/helm-recon in your project. Claude Code loads it when a task matches its description.

How do I install Helm Recon in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill helm-recon -a codex`. Or copy the skill folder (plugins/ai-agency/tonone/skills/helm-recon in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/helm-recon in your project. Codex loads it when a task matches its description.

Can I use Helm Recon 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 jeremylongshore/tons-of-skills-marketplace --skill helm-recon -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/helm-recon, .gemini/skills/helm-recon, .github/skills/helm-recon and .opencode/skills/helm-recon in your project.

What does Helm Recon need to run?

SKILL.md names no scripts, command-line tools or credentials: Helm Recon is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion.

Does Helm Recon 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 Helm Recon safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Helm Recon use?

Helm Recon is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Helm Recon use?

About 1k tokens (SKILL.md is roughly 4.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 Helm Recon?

Skills that share tags, products or a category with Helm Recon: Kubeshark Installer (kubeshark/kubeshark, 12k stars), KubeSphere Multi-Tenant Management (kubesphere/kubesphere, 17k stars), Sim Helm (simstudioai/sim, 30k stars) and Helm Chart Scaffolding (Cybereason-Public/owLSM, 280 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Helm Recon?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Helm Recon

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Product Reconnaissance

Steps

Step 0: Detect Environment

Step 1: Inventory Product Artifacts

Step 2: Inventory Research and User Insights

Step 3: Inventory Specialist Output

Step 4: Identify Gaps

Step 5: Present Assessment

Delivery

Files

Compare with similar skills

Similar skills

More from jeremylongshore/tons-of-skills-marketplace

Related

Questions about Helm Recon