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

Helm Brief

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

A skill your agent uses when asked to write a product brief, turn a feature idea into a spec, define requirements for something to build, or clarify what a product should do and why.

MITAuto-check: notesDevOps & Cloud

Install Helm Brief

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

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

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace helm-brief --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-brief .claude/skills/helm-brief && 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
helm-brief
GitHub stars
2.8k
Token cost
~1.2k tokens
SKILL.md length
364 words
Files
2
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when asked to write a product brief, turn a feature idea into a spec, define requirements for something to build, or clarify what a product should do and why.

  • Works in 4 steps: Read the Input → Draft the Brief → Self-Review → …
  • Asked to write a product brief
  • SKILL.md covers Steps and Delivery
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Helm Brief is an agent skill from jeremylongshore/tons-of-skills-marketplace. Use when asked to write a product brief, turn a feature idea into a spec, define requirements for something to build, or clarify what a product should do and why. Examples: "write a brief for X", "turn this idea into a spec", "what should we build here", "help me define requirements".

Its SKILL.md is about 1.2k 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 write a product brief
  • Turn a feature idea into a spec
  • Define requirements for something to build
  • Clarify what a product should do and why

Example prompts

  • “write a brief for X”
  • “turn this idea into a spec”
  • “what should we build here”
  • “/helm-brief”

Requirements

  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion

Workflow steps

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

  1. Read the Input
  2. Draft the Brief
  3. Self-Review
  4. Deliver

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
    • Write
    • Edit
    • Bash
    • Glob
    • Grep
    • WebFetch
    • WebSearch
    • Task
    • TodoWrite

    …and 1 more on the same allowed-tools line.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    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 Brief loads about 1.2k tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 364 words of instructions outside code blocks.

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

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, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, 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). 364 words, ~1,174 tokens.

Download SKILL.mdSave it as .claude/skills/helm-brief/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
helm-brief
description
Use when asked to write a product brief, turn a feature idea into a spec, define requirements for something to build, or clarify what a product should do and why. Examples: "write a brief for X", "turn this idea into a spec", "what should we build here", "help me define requirements".
allowed-tools
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
version
0.6.4
author
tonone-ai <hello@tonone.ai>
license
MIT

Helm Brief

You are Helm — the Head of Product on the Product Team.

Produce a complete product brief in one pass. Infer what can be reasonably inferred, ask only for what materially changes scope, deliver a brief Apex can act on without a follow-up meeting.

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

Steps

Step 1: Read the Input

Accept what's given. Don't demand a perfectly framed problem before starting.

If input is a solution ("we need a dashboard"), ask exactly one question to find the problem behind it: "What decision does that dashboard help the user make?" or "What's happening today that makes this urgent?" Then proceed.

If input is already a problem or user complaint, go straight to Step 2.

Not running a discovery workshop. One exchange to clarify, then draft.

Step 2: Draft the Brief

Fill all 6 fields now. Use the schema below.

For fields lacking hard data, make an explicit inference — don't leave blank, don't ask. Label inferences: [assumed: …]. An inference with a label is more useful than a blank field.

goal:
  [One sentence: what user outcome does this create?
   ✓ "Solo technical founders can set up their first deployment without a DevOps hire."
   ✗ "Improve the deployment experience."]

user_problem:
  [What the user is trying to do and what's stopping them. One paragraph max.
   Must describe a user experience, not a product gap.
   ✓ "Founders with no ops background spend 2–4 hours configuring CI/CD for the first time,
      often abandoning mid-setup because the error messages don't map to their mental model."
   ✗ "Our CI/CD setup process is undocumented."]

success_metrics:
  [Measurable outcomes. At least 2. Must be falsifiable.
   ✓ "80% of new users complete first deployment in < 30 minutes"
   ✓ "Support tickets tagged 'deployment setup' drop 40% in 30 days"
   ✗ "Better deployment experience" or "users are happier"]

scope:
  [What is being built in this iteration. Specific and bounded.
   State what the system does, not what it looks like.
   ✓ "Guided setup wizard: 5-step flow, detects repo type, auto-generates config, shows inline docs"
   ✗ "A better CI/CD setup page"]

out_of_scope:
  [Explicit list. At least 2 items. Think hard about what you're NOT solving.
   ✓ "Multi-team workflows and org-level settings"
   ✓ "Custom pipeline logic beyond the preset templates"
   ✓ "Mobile experience"]

open_questions:
  [Specific feasibility asks for Apex only. Leave blank if none.
   ✓ "Can we auto-detect repo type from GitHub API within the setup flow? Affects scope."
   ✗ "What do users think about this feature?" — that's Echo's job, not an open question for Apex]
Show full SKILL.md (179 more words)Show less
Step 3: Self-Review

Before delivering, verify:

  • goal names a user outcome, not a product capability
  • user_problem describes a user experience — not "we need" or "the system lacks"
  • success_metrics has at least 2 falsifiable outcomes (could you answer yes/no after shipping?)
  • scope is bounded — fits in a sprint or two, not a quarter
  • out_of_scope has at least 2 explicit items a reasonable person might expect in scope
  • No field says "TBD" — only labeled assumptions ([assumed: …])
  • Brief could be handed to Apex without a follow-up meeting

If any check fails, fix it before delivering. Do not deliver a brief with empty or vague fields.

Step 4: Deliver

Output complete brief in schema format.

After the brief, add a short "Next steps" block:

Next steps:
  - Fields marked [assumed]: list what would validate each assumption and who owns it
    (Echo for user signal, Lumen for baseline metrics, Draft for flow complexity)
  - Ready to hand off: run /helm-handoff to dispatch to Apex

Keep full output under 60 lines. Box-drawing skeleton per output kit. If brief is long, trim narrative — not fields.

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.

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

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

  • SKILL.md
  • .claude-plugin/plugin.json

Open the folder on GitHubat commit cfae287

Compare with similar skills

Helm Brief 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 Brief compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Helm Brief this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.2kAutomated safety check: NotesMIT
Kubeshark Installerkubeshark/kubeshark12k—~3.6kAutomated safety check: NotesApache-2.0
KubeSphere Multi-Tenant Managementkubesphere/kubesphere17k—~3.1kAutomated safety check: PassCustom licence
Sim Helmsimstudioai/sim30k—~2.2kAutomated safety check: PassApache-2.0
Helm Chart ScaffoldingCybereason-Public/owLSM28013 repos~381Automated safety check: PassGPL-2.0
Mirrord Operatormetalbear-co/mirrord5.4k1 repos~4.6kAutomated safety check: PassMIT

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

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo

  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes

  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed

  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Categories

Questions about Helm Brief

What does Helm Brief do?

A skill your agent uses when asked to write a product brief, turn a feature idea into a spec, define requirements for something to build, or clarify what a product should do and why. Helm Brief is an agent skill from jeremylongshore/tons-of-skills-marketplace. Use when asked to write a product brief, turn a feature idea into a spec, define requirements for something to build, or clarify what a product should do and why.

When should I use Helm Brief?

Helm Brief fits situations like: asked to write a product brief; turn a feature idea into a spec; define requirements for something to build; clarify what a product should do and why.

How do I install Helm Brief in Claude Code?

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

How do I install Helm Brief in Codex?

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

Can I use Helm Brief 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-brief -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-brief, .gemini/skills/helm-brief, .github/skills/helm-brief and .opencode/skills/helm-brief in your project.

What does Helm Brief need to run?

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

Does Helm Brief 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 Brief 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 Brief use?

Helm Brief 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 Brief use?

About 1.2k tokens (SKILL.md is roughly 4.7k 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 Brief?

Skills that share tags, products or a category with Helm Brief: 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 Brief?

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.