Skip to content

aiskillstore/marketplace / skills/92bilal26/helm-chart-architect

helm-chart-architect

Verified

Design production-grade Helm charts through architectural reasoning rather than pattern retrieval. Activate when designing new Helm charts for Kubernetes deployments, evaluating chart architecture, making decisions about component packaging, or reviewing charts for extensibility and maintainability. Guides decision-making about dependencies, lifecycle hooks, configuration surface, and multi-environment deployment through context-specific reasoning rather than generic best practices.

FileKindSize
SKILL.mdskill md19.5 KB
skill-report.jsonconfig24.3 KB

skill-report.json

View on GitHub
{
  "schema_version": "2.0",
  "meta": {
    "generated_at": "2026-07-05T15:19:13.890Z",
    "slug": "92bilal26-helm-chart-architect",
    "source_url": "https://github.com/92Bilal26/TaskPilotAI/tree/main/.claude/skills/helm-chart-architect",
    "source_ref": "main",
    "model": "codex",
    "analysis_version": "3.0.0",
    "source_type": "community",
    "content_hash": "e0bb5a218b228b705d33f5428fdc95518d46cd839d8d3d2bbd0c1472088f079a",
    "tree_hash": "f67cee42a01e53e97f9a1bb9d8def7727a2700ad264999884a11ef5813ec403a",
    "provenance": {
      "model_effective": "codex",
      "fallback_chain": [
        {
          "agent": "codex",
          "outcome": "success"
        }
      ],
      "analysis_version": "3.0.0"
    }
  },
  "skill": {
    "name": "helm-chart-architect",
    "description": "Design Helm charts through guided architecture questions for Kubernetes applications. The skill covers dependencies, hooks, values, environments, extensibility, and operator experience.",
    "summary": "Architect Helm charts with clear dependency, lifecycle, and values decisions.",
    "icon": "📦",
    "version": "1.0.1",
    "author": "92Bilal26",
    "license": "MIT",
    "tags": [
      "helm",
      "kubernetes",
      "devops",
      "platform-engineering",
      "chart-design"
    ],
    "supported_tools": [
      "claude",
      "codex",
      "claude-code"
    ],
    "risk_factors": [
      "external_commands",
      "network"
    ],
    "category": "devops"
  },
  "security_audit": {
    "risk_level": "safe",
    "is_blocked": false,
    "safe_to_publish": true,
    "analysis_status": "ok",
    "summary": "The static findings are false positives caused by Markdown inline code, YAML fences, public Helm repository examples, and design questions. No prompt injection, data exfiltration intent, or executable automation was found in SKILL.md.",
    "remediation": [],
    "risk_factor_evidence": [
      {
        "factor": "external_commands",
        "evidence": [
          {
            "file": "SKILL.md",
            "line_start": 213,
            "line_end": 213
          },
          {
            "file": "SKILL.md",
            "line_start": 218,
            "line_end": 228
          },
          {
            "file": "SKILL.md",
            "line_start": 228,
            "line_end": 230
          },
          {
            "file": "SKILL.md",
            "line_start": 230,
            "line_end": 247
          },
          {
            "file": "SKILL.md",
            "line_start": 247,
            "line_end": 248
          },
          {
            "file": "SKILL.md",
            "line_start": 248,
            "line_end": 254
          },
          {
            "file": "SKILL.md",
            "line_start": 254,
            "line_end": 257
          },
          {
            "file": "SKILL.md",
            "line_start": 257,
            "line_end": 289
          },
          {
            "file": "SKILL.md",
            "line_start": 289,
            "line_end": 289
          },
          {
            "file": "SKILL.md",
            "line_start": 315,
            "line_end": 317
          },
          {
            "file": "SKILL.md",
            "line_start": 317,
            "line_end": 320
          },
          {
            "file": "SKILL.md",
            "line_start": 320,
            "line_end": 325
          },
          {
            "file": "SKILL.md",
            "line_start": 325,
            "line_end": 353
          },
          {
            "file": "SKILL.md",
            "line_start": 353,
            "line_end": 356
          },
          {
            "file": "SKILL.md",
            "line_start": 356,
            "line_end": 420
          },
          {
            "file": "SKILL.md",
            "line_start": 420,
            "line_end": 432
          }
        ]
      },
      {
        "factor": "network",
        "evidence": [
          {
            "file": "SKILL.md",
            "line_start": 221,
            "line_end": 221
          },
          {
            "file": "SKILL.md",
            "line_start": 225,
            "line_end": 225
          }
        ]
      }
    ],
    "static_findings": [
      {
        "id": "external_commands:SKILL.md:213:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 213,
        "line_end": 213,
        "snippet": "Not every deployment needs Redis or PostgreSQL. Use Helm's `condition` and `tags` mechanisms in Char"
      },
      {
        "id": "external_commands:SKILL.md:218:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 218,
        "line_end": 228,
        "snippet": "```yaml"
      },
      {
        "id": "external_commands:SKILL.md:228:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 228,
        "line_end": 230,
        "snippet": "```"
      },
      {
        "id": "external_commands:SKILL.md:230:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 230,
        "line_end": 247,
        "snippet": "Operators can then set `postgresql.enabled: false` if they use managed RDS instead."
      },
      {
        "id": "external_commands:SKILL.md:247:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 247,
        "line_end": 248,
        "snippet": "- Schema migrations: Use `IF NOT EXISTS` checks"
      },
      {
        "id": "external_commands:SKILL.md:248:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 248,
        "line_end": 254,
        "snippet": "- Data loading: Use `ON CONFLICT ... DO NOTHING` or skip if already present"
      },
      {
        "id": "external_commands:SKILL.md:254:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 254,
        "line_end": 257,
        "snippet": "```yaml"
      },
      {
        "id": "external_commands:SKILL.md:257:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 257,
        "line_end": 289,
        "snippet": "```"
      },
      {
        "id": "external_commands:SKILL.md:289:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 289,
        "line_end": 289,
        "snippet": "Use `Chart.yaml`'s `kubeVersion` and a `values.schema.json` file to validate configuration before re"
      },
      {
        "id": "external_commands:SKILL.md:315:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 315,
        "line_end": 317,
        "snippet": "```yaml"
      },
      {
        "id": "external_commands:SKILL.md:317:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 317,
        "line_end": 320,
        "snippet": "```"
      },
      {
        "id": "external_commands:SKILL.md:320:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 320,
        "line_end": 325,
        "snippet": "```yaml"
      },
      {
        "id": "external_commands:SKILL.md:325:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 325,
        "line_end": 353,
        "snippet": "```"
      },
      {
        "id": "external_commands:SKILL.md:353:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 353,
        "line_end": 356,
        "snippet": "```yaml"
      },
      {
        "id": "external_commands:SKILL.md:356:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 356,
        "line_end": 420,
        "snippet": "```"
      },
      {
        "id": "external_commands:SKILL.md:420:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 420,
        "line_end": 432,
        "snippet": "```"
      },
      {
        "id": "network:SKILL.md:221:hardcoded-url",
        "category": "network",
        "severity": "low",
        "pattern": "Hardcoded URL",
        "file": "SKILL.md",
        "line_start": 221,
        "line_end": 221,
        "snippet": "repository: https://charts.bitnami.com/bitnami"
      },
      {
        "id": "network:SKILL.md:225:hardcoded-url",
        "category": "network",
        "severity": "low",
        "pattern": "Hardcoded URL",
        "file": "SKILL.md",
        "line_start": 225,
        "line_end": 225,
        "snippet": "repository: https://charts.bitnami.com/bitnami"
      },
      {
        "id": "blocker:SKILL.md:129:system-reconnaissance",
        "category": "blocker",
        "severity": "low",
        "pattern": "System reconnaissance",
        "file": "SKILL.md",
        "line_start": 129,
        "line_end": 129,
        "snippet": "How does this chart help operators avoid these mistakes?"
      },
      {
        "id": "blocker:SKILL.md:293:system-reconnaissance",
        "category": "blocker",
        "severity": "low",
        "pattern": "System reconnaissance",
        "file": "SKILL.md",
        "line_start": 293,
        "line_end": 293,
        "snippet": "- Numeric values are in valid ranges (replicaCount > 0, not negative)"
      },
      {
        "id": "blocker:SKILL.md:406:system-reconnaissance",
        "category": "blocker",
        "severity": "low",
        "pattern": "System reconnaissance",
        "file": "SKILL.md",
        "line_start": 406,
        "line_end": 407,
        "snippet": "- **Values schema**: Validate GPU count is positive integer, training parameters are valid"
      }
    ],
    "finding_verdicts": [
      {
        "id": "external_commands:SKILL.md:213:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.94,
        "reason": "The line uses Markdown inline code for Helm Chart.yaml keys, not executable Ruby or shell syntax. It is guidance prose with no command invocation path."
      },
      {
        "id": "external_commands:SKILL.md:218:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.94,
        "reason": "This starts a YAML example block for Helm dependencies. It does not instruct the agent to execute the contents as shell code."
      },
      {
        "id": "external_commands:SKILL.md:228:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.94,
        "reason": "This is a Markdown code fence boundary, not a backtick execution construct. No command is present at this location."
      },
      {
        "id": "external_commands:SKILL.md:230:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.94,
        "reason": "The line references a Helm values key in inline Markdown code. It describes operator configuration and does not execute user input."
      },
      {
        "id": "external_commands:SKILL.md:247:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.94,
        "reason": "The inline code describes an idempotent SQL pattern for migrations. It is not Ruby backtick execution or a shell command."
      },
      {
        "id": "external_commands:SKILL.md:248:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.94,
        "reason": "The inline code describes SQL conflict handling in documentation. It is not executable shell syntax in the skill."
      },
      {
        "id": "external_commands:SKILL.md:254:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.94,
        "reason": "This starts a YAML snippet for Helm hook annotations. The Markdown fence is documentation, not command execution."
      },
      {
        "id": "external_commands:SKILL.md:257:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.94,
        "reason": "This is a Markdown fence in a documentation example. The surrounding content discusses hook design and contains no shell execution instruction."
      },
      {
        "id": "external_commands:SKILL.md:289:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.94,
        "reason": "The line uses inline Markdown code for Chart.yaml and values.schema.json filenames. It is file naming guidance, not executable code."
      },
      {
        "id": "external_commands:SKILL.md:315:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.94,
        "reason": "This begins a YAML documentation example. Static analysis confused the Markdown fence with execution syntax."
      },
      {
        "id": "external_commands:SKILL.md:317:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.94,
        "reason": "This is the end of a Markdown YAML example. It contains no command, interpreter call, or user-controlled execution."
      },
      {
        "id": "external_commands:SKILL.md:320:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.94,
        "reason": "This begins another YAML example for values documentation. It is static prose and cannot execute by itself."
      },
      {
        "id": "external_commands:SKILL.md:325:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.94,
        "reason": "This Markdown fence closes a documentation block. No shell command or backtick execution behavior is present."
      },
      {
        "id": "external_commands:SKILL.md:353:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.94,
        "reason": "This starts a YAML example for hook deletion policy. It is instructional chart configuration, not runtime command execution."
      },
      {
        "id": "external_commands:SKILL.md:356:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.94,
        "reason": "This is a Markdown fence around chart documentation. The skill contains no mechanism that runs the fenced text."
      },
      {
        "id": "external_commands:SKILL.md:420:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.94,
        "reason": "This begins an invocation prompt example in Markdown. It is user guidance and does not cause shell execution."
      },
      {
        "id": "network:SKILL.md:221:hardcoded-url",
        "verdict": "false_positive",
        "confidence": 0.9,
        "reason": "The URL is the public Bitnami Helm repository used in an example Chart.yaml dependency. It is not an automatic network request or data exfiltration endpoint."
      },
      {
        "id": "network:SKILL.md:225:hardcoded-url",
        "verdict": "false_positive",
        "confidence": 0.9,
        "reason": "The URL is repeated as a public Helm chart repository example for Redis. It does not transmit local data or credentials."
      },
      {
        "id": "blocker:SKILL.md:129:system-reconnaissance",
        "verdict": "false_positive",
        "confidence": 0.9,
        "reason": "The line asks how chart design helps operators avoid mistakes. It is operational design guidance, not host or system reconnaissance."
      },
      {
        "id": "blocker:SKILL.md:293:system-reconnaissance",
        "verdict": "false_positive",
        "confidence": 0.9,
        "reason": "The line discusses validating numeric chart values such as replica count. It does not inspect the local system or collect environment details."
      },
      {
        "id": "blocker:SKILL.md:406:system-reconnaissance",
        "verdict": "false_positive",
        "confidence": 0.9,
        "reason": "The line describes validating GPU count in values schema for an example workload. It does not perform reconnaissance or request system data."
      }
    ],
    "semantic_findings": [],
    "critical_findings": [],
    "high_findings": [],
    "medium_findings": [],
    "low_findings": [],
    "dangerous_patterns": [],
    "files_scanned": 1,
    "total_lines": 435,
    "audit_model": "codex",
    "audited_at": "2026-07-05T15:19:13.890Z",
    "agent_auto_install_policy": "allowed",
    "manual_install_policy": "allowed"
  },
  "content": {
    "user_title": "Design Production Helm Chart Architecture",
    "value_statement": "Teams often copy Helm examples that do not match their operational constraints. This skill guides chart architecture through dependencies, hooks, values, environments, and operator needs.",
    "seo_keywords": [
      "Claude",
      "Codex",
      "Claude Code",
      "Helm chart architect",
      "Helm charts",
      "Kubernetes deployments",
      "DevOps automation",
      "values.yaml design",
      "Helm lifecycle hooks",
      "Kubernetes platform engineering"
    ],
    "actual_capabilities": [
      "Guides component and dependency decisions for Helm chart architecture.",
      "Evaluates when to use subcharts, external services, or independent charts.",
      "Reviews lifecycle hooks for idempotence, safety, and operational value.",
      "Designs values.yaml as an operator-facing configuration contract.",
      "Plans multi-environment chart behavior for dev, staging, and production.",
      "Identifies extensibility points such as sidecars, annotations, and extra volumes."
    ],
    "limitations": [
      "Does not generate a complete chart without project-specific requirements.",
      "Does not validate live clusters or run Helm commands by itself.",
      "Does not replace security review of rendered Kubernetes manifests.",
      "Depends on accurate input about teams, dependencies, and environments."
    ],
    "use_cases": [
      {
        "title": "Design a New Service Chart",
        "description": "Create a chart architecture for a microservice with clear dependencies, values, hooks, and environment behavior.",
        "target_user": "Application engineers"
      },
      {
        "title": "Standardize Platform Patterns",
        "description": "Define library chart boundaries, security defaults, and reusable templates for many application teams.",
        "target_user": "Platform engineers"
      },
      {
        "title": "Review Chart Maintainability",
        "description": "Assess whether an existing chart is extensible, understandable, and ready for production operations.",
        "target_user": "DevOps leads"
      }
    ],
    "prompt_templates": [
      {
        "title": "Start a Chart Design",
        "scenario": "Beginner request for a new application chart.",
        "prompt": "Use the Helm Chart Architect skill to design a Helm chart for my application. Ask me for missing requirements before proposing architecture."
      },
      {
        "title": "Choose Dependency Strategy",
        "scenario": "Intermediate request about managed services and subcharts.",
        "prompt": "Use the Helm Chart Architect skill to compare subcharts, external services, and independent charts for my dependencies."
      },
      {
        "title": "Review Lifecycle Hooks",
        "scenario": "Advanced request for install, upgrade, and test behavior.",
        "prompt": "Use the Helm Chart Architect skill to review lifecycle hooks for migrations, validation, smoke tests, and deletion behavior."
      },
      {
        "title": "Plan Enterprise Chart Governance",
        "scenario": "Advanced request for multi-team platform standards.",
        "prompt": "Use the Helm Chart Architect skill to design chart governance across platform, application, DevOps, and security teams."
      }
    ],
    "output_examples": [
      {
        "input": "A team needs a Helm chart for a FastAPI service with PostgreSQL, Redis, and separate production requirements.",
        "output": [
          "A component map that separates critical services, optional services, and external dependencies.",
          "A dependency strategy that uses local subcharts in development and managed services in production.",
          "A values design that exposes replicas, resources, external endpoints, and extension points."
        ]
      },
      {
        "input": "A platform team wants reusable Helm patterns for several application teams.",
        "output": [
          "A recommendation to separate library charts from application charts.",
          "Clear ownership boundaries for platform defaults, application logic, and environment values.",
          "A review checklist for security context, probes, labels, and operator documentation."
        ]
      },
      {
        "input": "An existing chart has complex hooks and confusing values.",
        "output": [
          "A hook review focused on idempotence, failure behavior, and deletion policies.",
          "A simplified values contract that removes unclear options and documents important decisions.",
          "Operational checks that help users diagnose failed installs and upgrades."
        ]
      }
    ],
    "best_practices": [
      "Provide project requirements, dependency ownership, and environment differences before asking for architecture.",
      "Review the proposed values contract with the operators who will deploy the chart.",
      "Validate recommendations with Helm lint, schema checks, and rendered manifest review."
    ],
    "anti_patterns": [
      "Do not ask for a generic chart template without explaining operational constraints.",
      "Do not expose every internal chart detail as a values option.",
      "Do not rely on hooks that fail when they run more than once."
    ],
    "faq": [
      {
        "question": "Does this skill create Helm chart files?",
        "answer": "It focuses on architecture decisions first. It can guide chart structure, but complete files need project details."
      },
      {
        "question": "Can it help with existing charts?",
        "answer": "Yes. It can review chart coupling, values design, hooks, dependencies, and operator experience."
      },
      {
        "question": "Does it require access to my Kubernetes cluster?",
        "answer": "No. The skill reasons from requirements and chart content. It does not inspect live clusters."
      },
      {
        "question": "What inputs should I provide?",
        "answer": "Provide components, dependencies, environments, team ownership, security rules, and known operational failures."
      },
      {
        "question": "Can it support AI or GPU workloads?",
        "answer": "Yes. The skill includes an example for LLM fine-tuning, GPU scheduling, queues, and training parameters."
      },
      {
        "question": "How should I verify its recommendations?",
        "answer": "Use Helm lint, values schema validation, rendered manifest review, and operational smoke tests."
      }
    ]
  },
  "file_structure": [
    {
      "name": "SKILL.md",
      "type": "file",
      "path": "SKILL.md",
      "lines": 435
    }
  ]
}
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall