ma-agents 3.4.9 → 3.5.0

package/.opencode/skills/csharp-best-practices/SKILL.md

@@ -1,278 +0,0 @@
----
-name: C# Best Practices
-description: Comprehensive C# coding standards covering modern C# (C# 10-12), async/await, LINQ, dependency injection basics, nullable reference types, and testing conventions.
----
-# C# Best Practices
-
-Coding standards for modern C# (C# 10+) across .NET 6 through .NET 8+. This skill covers language-level patterns. Framework-specific patterns (ASP.NET Core middleware, EF Core, Blazor) belong in future skills.
-
-## 1. Naming Conventions
-
-**Rule:** Use consistent naming to maximize code readability and tooling support.
-
-| Element | Convention | Example |
-|---------|-----------|---------|
-| Namespace | PascalCase, match folder | `MyApp.Services` |
-| Class / Struct / Record | PascalCase | `CustomerService` |
-| Interface | `I` + PascalCase | `ICustomerService` |
-| Method | PascalCase | `GetCustomerAsync` |
-| Property | PascalCase | `FirstName` |
-| Local variable | camelCase | `customerCount` |
-| Parameter | camelCase | `customerId` |
-| Private field | `_` + camelCase | `_logger` |
-| Constant | PascalCase | `MaxRetryCount` |
-| Enum type | PascalCase singular | `OrderStatus` |
-| Enum member | PascalCase | `OrderStatus.Pending` |
-| Async method | suffix `Async` | `SaveAsync` |
-
-## 2. Code Organization
-
-**Rule:** One type per file; namespace matches folder path.
-
-- File-scoped namespace declaration (C# 10+): `namespace MyApp.Services;` — no extra indentation level.
-- Organize types in the order: constants, fields, constructors, properties, methods (public first, then private).
-- Use `global using` directives in a dedicated `GlobalUsings.cs` file to eliminate repetitive `using` statements project-wide.
-- Prefer `record` types for immutable data containers; use `record struct` for small value-type data.
-
-## 3. Nullable Reference Types
-
-**Rule:** Enable NRT project-wide and treat warnings as errors.
-
-```xml
-<Nullable>enable</Nullable>
-<TreatWarningsAsErrors>true</TreatWarningsAsErrors>
-```
-
-- Never use `!` (null-forgiving) to silence warnings without a documented reason.
-- Use `string?` for intentionally nullable references; non-nullable types must be initialized before use.
-- Initialize fields in the constructor or use `required` members (C# 11+) to enforce initialization at the call site.
-
-```csharp
-public class Order
-{
-    public required string CustomerId { get; init; }
-    public string? Notes { get; init; }
-}
-```
-
-## 4. Modern C# Language Features
-
-### 4.1 Primary Constructors (C# 12)
-
-Use primary constructors for classes and structs that primarily capture injected dependencies.
-
-```csharp
-public class OrderService(IOrderRepository repository, ILogger<OrderService> logger)
-{
-    public async Task<Order?> GetAsync(int id, CancellationToken ct)
-    {
-        logger.LogInformation("Getting order {Id}", id);
-        return await repository.FindAsync(id, ct);
-    }
-}
-```
-
-### 4.2 Collection Expressions (C# 12)
-
-Prefer collection expressions over explicit constructors for collection initialization.
-
-```csharp
-// Preferred
-int[] ids = [1, 2, 3];
-List<string> names = ["Alice", "Bob"];
-
-// Also valid for spread
-int[] combined = [..ids, 4, 5];
-```
-
-### 4.3 Raw String Literals (C# 11)
-
-Use raw string literals for JSON, SQL, or multi-line strings to avoid escaping.
-
-```csharp
-var json = """
-    {
-        "name": "Alice",
-        "age": 30
-    }
-    """;
-```
-
-### 4.4 Pattern Matching
-
-Use pattern matching to simplify type checks and conditional logic.
-
-```csharp
-// Type patterns
-string Describe(object obj) => obj switch
-{
-    int n when n > 0 => "positive integer",
-    int n            => "non-positive integer",
-    string s         => $"string: {s}",
-    null             => "null",
-    _                => "other"
-};
-
-// List patterns (C# 11)
-bool IsFirstTwo(int[] arr) => arr is [var first, var second, ..];
-```
-
-### 4.5 Records and Record Structs
-
-Use `record` for immutable reference-type DTOs and value objects. Use `readonly record struct` for small immutable value types that benefit from stack allocation.
-
-```csharp
-// Reference-type record (class semantics, heap allocated)
-public record Address(string Street, string City, string PostalCode);
-
-// with-expressions for non-destructive mutation
-var updated = original with { City = "New York" };
-
-// Value-type record (struct semantics, stack allocated)
-public readonly record struct Point(double X, double Y);
-
-// Mutable record struct — only when mutation is explicitly needed
-public record struct Range(int Start, int End);
-```
-
-Choose `readonly record struct` over `record` when: the data is small (2-4 fields), frequently allocated in hot paths, and value semantics (equality by value, copied on assignment) are correct.
-
-### 4.6 File-Scoped Types (C# 11)
-
-Use the `file` access modifier to restrict a type's visibility to the single file where it is declared. This is useful for implementation detail types that should not leak into other files.
-
-```csharp
-// Only visible within this .cs file — cannot be used from any other file
-file class OrderValidator
-{
-    public bool IsValid(Order order) => order.CustomerId is not null;
-}
-
-// Also applies to records, structs, interfaces, delegates
-file record struct ValidationResult(bool IsValid, string? Error);
-```
-
-Use `file`-scoped types for: helper classes private to a single implementation file, source generators' internal scaffolding, and avoiding name collisions across files without polluting `internal` scope.
-
-## 5. Async/Await
-
-**Rule:** Use async all the way up the call stack; never block on async code.
-
-- Prefer `async Task` / `async Task<T>` over returning naked `Task`.
-- Never use `async void` except for event handlers; use `async Task` instead.
-- Always propagate `CancellationToken` from public API boundaries down to I/O calls.
-- Prefer `ConfigureAwait(false)` in library code where the calling context does not matter.
-- Use `ValueTask<T>` when a method frequently returns a synchronous result (hot-path optimization); default to `Task<T>` for simplicity.
-
-```csharp
-// Correct — async all the way, CancellationToken propagated, ConfigureAwait in library code
-public async Task<Order?> FindOrderAsync(int id, CancellationToken ct = default)
-{
-    return await _repository.GetByIdAsync(id, ct).ConfigureAwait(false);
-}
-
-// Correct — multiple I/O operations with cancellation
-public async Task<IReadOnlyList<Order>> GetActiveOrdersAsync(CancellationToken ct = default)
-{
-    var orders = await _repository.ListAsync(ct).ConfigureAwait(false);
-    return orders.Where(o => o.IsActive).ToList();
-}
-
-// Wrong — blocks the thread pool, risks deadlock
-public Order? FindOrder(int id) => FindOrderAsync(id).Result;
-```
-
-## 6. LINQ
-
-**Rule:** Prefer method syntax; be aware of deferred execution.
-
-- Use method syntax (`Where`, `Select`, `FirstOrDefault`) over query syntax for consistency with the rest of the codebase.
-- LINQ queries execute lazily — materialize with `.ToList()`, `.ToArray()`, or `.ToDictionary()` when the result will be enumerated more than once or when you need a stable snapshot.
-- Avoid LINQ inside tight loops on large collections; profile before assuming LINQ is a bottleneck.
-- For in-memory filtering on large datasets, consider `AsSpan()` or `ArrayPool<T>` instead of repeated LINQ queries.
-
-```csharp
-// Materialize when enumerating multiple times
-var activeOrders = orders.Where(o => o.IsActive).ToList();
-
-// Avoid multiple enumeration of IEnumerable
-foreach (var order in activeOrders) { /* ... */ }
-int count = activeOrders.Count;
-```
-
-## 7. Error Handling
-
-**Rule:** Use structured exception handling; reserve exceptions for truly exceptional conditions.
-
-- Define a domain exception hierarchy derived from a base exception: `AppException : Exception`.
-- Use the Result pattern for expected failure cases (validation, not-found) where exceptions are expensive overhead.
-- For HTTP APIs, structure error responses using ProblemDetails (RFC 9457) — the language-level concern is ensuring your exceptions carry enough data to produce one; the middleware that converts them belongs in a future `csharp-aspnet-patterns` skill.
-- Never swallow exceptions silently; always log or rethrow.
-
-```csharp
-// Result pattern for expected failures
-public record Result<T>(T? Value, string? Error)
-{
-    public bool IsSuccess => Error is null;
-    public static Result<T> Ok(T value) => new(value, null);
-    public static Result<T> Fail(string error) => new(default, error);
-}
-
-// Exception hierarchy
-public class AppException(string message) : Exception(message);
-public class NotFoundException(string entity, object id)
-    : AppException($"{entity} with id '{id}' was not found.");
-```
-
-## 8. Dependency Injection
-
-**Rule:** Favor constructor injection; choose service lifetimes deliberately.
-
-- Constructor injection is the standard pattern — inject only what the type needs.
-- **Singleton:** One instance for the application lifetime. Use for stateless services and configuration.
-- **Scoped:** One instance per request (web) or operation scope. Use for database contexts and unit-of-work patterns.
-- **Transient:** New instance per resolution. Use for lightweight, stateless utilities.
-- Never inject a Scoped or Transient service into a Singleton — this causes captive dependency bugs.
-
-```csharp
-// Registration via IServiceCollection (Microsoft.Extensions.DependencyInjection)
-// Works in console apps, workers, ASP.NET Core, and any .NET host
-IServiceCollection services = new ServiceCollection();
-services.AddSingleton<IConfigService, ConfigService>();
-services.AddScoped<IOrderService, OrderService>();
-services.AddTransient<IEmailFormatter, EmailFormatter>();
-```
-
-## 9. Testing
-
-**Rule:** Follow Arrange-Act-Assert; use framework-agnostic patterns.
-
-- Name tests: `MethodName_StateUnderTest_ExpectedBehavior`.
-- Arrange all preconditions, act on the system under test, assert the single observable outcome.
-- Major test frameworks: xUnit (most popular for .NET), NUnit, MSTest — choose based on team preference.
-- Popular assertion libraries: FluentAssertions, Shouldly. Popular mock libraries: NSubstitute, Moq.
-- Avoid test logic that depends on execution order; each test must be independent.
-
-```csharp
-// xUnit example (patterns apply to NUnit/MSTest)
-public class OrderServiceTests
-{
-    [Fact]
-    public async Task GetAsync_ExistingId_ReturnsOrder()
-    {
-        // Arrange
-        var repository = Substitute.For<IOrderRepository>();
-        var logger = Substitute.For<ILogger<OrderService>>();
-        repository.FindAsync(1, Arg.Any<CancellationToken>())
-            .Returns(new Order { Id = 1 });
-        var sut = new OrderService(repository, logger);
-
-        // Act
-        var result = await sut.GetAsync(1, CancellationToken.None);
-
-        // Assert
-        result.Should().NotBeNull();
-        result!.Id.Should().Be(1);
-    }
-}
-```

package/.opencode/skills/cyber-generate-certs/SKILL.md

@@ -1,27 +0,0 @@
----
-name: cyber-generate-certs
-description: Generate self-signed certificates using the self-signed-cert skill
-type: skill
-triggers:
-  - "generate certs"
-  - "generate certificates"
----
-
-# workflow-generate-certs.md
-# Secure Certificate Generation Workflow
-
-Automated workflow for generating self-signed certificates using the `self-signed-cert` skill.
-
-## Instructions
-1.  **Load Skill**: Activate the `self-signed-cert` skill instructions.
-2.  **Requirement Analysis**: Determine common name (CN) and Subject Alternative Names (SANs).
-3.  **Execution**:
-    - **Linux/macOS**:
-        - `bash scripts/generate-cert.sh root my-internal-ca`
-        - `bash scripts/generate-cert.sh cert my-service localhost`
-    - **Windows**:
-        - `.\scripts\generate-cert.ps1 -Type root -Name my-internal-ca`
-        - `.\scripts\generate-cert.ps1 -Type cert -Name my-service -Dns localhost`
-4.  **Packaging**: Provide instructions for importing the cert into trust stores (OS, Browsers) or mounting in Kubernetes secrets.
-5.  **Security**: Ensure private keys are stored with restricted permissions (600).
-6.  **Rotation**: Offer a schedule for certificate renewal.

package/.opencode/skills/cyber-generate-certs/bmad-skill-manifest.yaml

@@ -1,3 +0,0 @@
-type: skill
-name: cyber-generate-certs
-module: ma-skills

package/.opencode/skills/cyber-immunity-estimation/SKILL.md

@@ -1,29 +0,0 @@
----
-name: cyber-immunity-estimation
-description: Assess overall security posture and immunity against common attack vectors
-type: skill
-triggers:
-  - "immunity estimation"
-  - "security posture"
----
-
-# workflow-immunity-estimation.md
-# Cyber Immunity Estimation Workflow
-
-Assesses the overall security posture and 'immunity' of the system against common attack vectors.
-
-## Instructions
-1.  **Attack Surface Analysis**: Identify all entry points (APIs, UI, SSH, 3rd party integrations).
-2.  **Control Verification**:
-    - Authentication/Authorization presence.
-    - Encryption in transit and at rest.
-    - Secret management maturity (Hardcoded vs Vault).
-3.  **Posture Scoring**: Rate 1-10 on:
-    - Code quality/Sanitization.
-    - Dependency health.
-    - Infrastructure hardening.
-    - Visibility/Logging.
-4.  **Immunity Report**:
-    - Summarize major gaps.
-    - Provide a roadmap for reach 'Immunity Level 5' (Robust).
-5.  **Verification**: Recommend automated regression tests for security controls.

package/.opencode/skills/cyber-immunity-estimation/bmad-skill-manifest.yaml

@@ -1,3 +0,0 @@
-type: skill
-name: cyber-immunity-estimation
-module: ma-skills

package/.opencode/skills/cyber-security-audit/SKILL.md

@@ -1,27 +0,0 @@
----
-name: cyber-security-audit
-description: Comprehensive security audit of infrastructure and application configuration
-type: skill
-triggers:
-  - "security audit"
-  - "run security audit"
----
-
-# workflow-security-audit.md
-# Comprehensive Security Audit Workflow
-
-Deep-dive audit of infrastructure and application configuration.
-
-## Instructions
-1.  **Infrastructure Audit**:
-    - **K8s**: Check for privileged containers, missing network policies, root users.
-    - **Docker**: Check for exposed ports, unnecessary packages in images.
-2.  **Code Audit**:
-    - Static Analysis (SAST) for common patterns (SQLi, XSS).
-    - Check for insecure defaults in frameworks.
-3.  **Identity Audit**:
-    - Review ServiceAccount permissions (RBAC).
-    - Check for hard-coded credentials.
-4.  **Final Recommendation**: 
-    - Provide a prioritized list of hardening tasks.
-    - Propose CIDCD guardrails.

package/.opencode/skills/cyber-security-audit/bmad-skill-manifest.yaml

@@ -1,3 +0,0 @@
-type: skill
-name: cyber-security-audit
-module: ma-skills

package/.opencode/skills/cyber-vault-secrets/SKILL.md

@@ -1,28 +0,0 @@
----
-name: cyber-vault-secrets
-description: Manage secrets, policies, and authentication in HashiCorp Vault
-type: skill
-triggers:
-  - "vault secrets"
-  - "manage vault"
----
-
-# workflow-vault-secrets.md
-# HashiCorp Vault Secret Management Workflow
-
-This workflow guides the agent through managing secrets, policies, and authentication in HashiCorp Vault.
-
-## Instructions
-1.  **Check Connection**: Verify `vault status` and authentication.
-2.  **Secret Creation/Update**:
-    - `vault kv put secret/{path} {key}={value}`
-    - Ensure secrets are never logged or echoed in plain text.
-3.  **Policy Management**:
-    - Define HCL policies for restricted access.
-    - `vault policy write {name} {policy_file}`
-4.  **Integration**:
-    - Manage Kubernetes auth method: `vault auth enable kubernetes`
-    - Setup Vault Agent injector configurations.
-5.  **Audit**:
-    - Check for expired tokens or orphaned secrets.
-    - Review access logs if available.

package/.opencode/skills/cyber-vault-secrets/bmad-skill-manifest.yaml

@@ -1,3 +0,0 @@
-type: skill
-name: cyber-vault-secrets
-module: ma-skills

package/.opencode/skills/cyber-verify-docker-users/SKILL.md

@@ -1,23 +0,0 @@
----
-name: cyber-verify-docker-users
-description: Audit Docker images for proper user management and least privilege
-type: skill
-triggers:
-  - "verify docker users"
-  - "docker user audit"
----
-
-# verify-docker-users.md
-# Docker User & Hardening Verification Workflow
-
-This workflow guides the Cyber agent through auditing Docker images for proper user management and least privilege.
-
-## Instructions
-1.  **Inspect Metadata**:
-    - Use the `docker-hardening-verification` skill.
-    - Run: `bash skills/docker-hardening-verification/scripts/verify-hardening.sh {image_name}`.
-2.  **Audit Result Analysis**:
-    - **UID Check**: Confirm the defined user is non-zero.
-    - **Permissive Files**: Scan for world-writable files in common paths (/tmp, /etc, /var).
-3.  **Governance Check**: Ensure the image follows OpenShift/hardened cluster requirements (no root, arbitrary UID support).
-4.  **Reporting**: provide a high-level summary of hardening quality and mandatory fixes.

package/.opencode/skills/cyber-verify-docker-users/bmad-skill-manifest.yaml

@@ -1,3 +0,0 @@
-type: skill
-name: cyber-verify-docker-users
-module: ma-skills

package/.opencode/skills/cyber-verify-image-signature/SKILL.md

@@ -1,22 +0,0 @@
----
-name: cyber-verify-image-signature
-description: Verify Docker image signatures for supply chain security
-type: skill
-triggers:
-  - "verify image signature"
-  - "check image signature"
----
-
-# verify-image-signature.md
-# Docker Image Signature Verification Workflow
-
-This workflow guides the Cyber agent through verifying that a Docker image has been properly signed.
-
-## Instructions
-1.  **Identify Image**: Get the image name and digest.
-2.  **Locate Public Key**: Obtain the public key or certificate used for signing.
-3.  **Execute Verification**:
-    - Use `cosign verify --key {public_key} {image_digest}`.
-    - Check the output for valid signatures.
-4.  **Policy Compliance**: Verify if the signing entity (certificate CN) matches the expected trusted authorities.
-5.  **Report**: Alert the user if the image is unsigned or the signature is invalid.

package/.opencode/skills/cyber-verify-image-signature/bmad-skill-manifest.yaml

@@ -1,3 +0,0 @@
-type: skill
-name: cyber-verify-image-signature
-module: ma-skills

package/.opencode/skills/cyber-vulnerability-scan/SKILL.md

@@ -1,28 +0,0 @@
----
-name: cyber-vulnerability-scan
-description: Orchestrate comprehensive vulnerability scanning across tech stacks
-type: skill
-triggers:
-  - "vulnerability scan"
-  - "run vulnerability scan"
----
-
-# workflow-vulnerability-scan.md
-# ma-agents Vulnerability Scan Orchestration
-
-Orchestrates multiple security-focused skills from the `ma-agents` package to provide a comprehensive security scan.
-
-## Instructions
-1.  **Select Scanners**: Based on project tech stack, trigger:
-    - **JS/TS**: `js-ts-security-skill`
-    - **Python**: `python-security-skill`
-    - **Docker**: `verify-hardened-docker-skill`
-2.  **Run Tools**:
-    - Execute `npm audit` or `yarn audit`.
-    - Run `pip-audit` for Python environments.
-    - Run `trivy image {image}` for containers.
-3.  **Aggregate Results**: Collect all findings into a unified report.
-4.  **Prioritization**: Rank vulnerabilities by CVSS score and exploitability.
-5.  **Remediation**:
-    - Propose version upgrades.
-    - Propose configuration hardening steps.

package/.opencode/skills/cyber-vulnerability-scan/bmad-skill-manifest.yaml

@@ -1,3 +0,0 @@
-type: skill
-name: cyber-vulnerability-scan
-module: ma-skills

package/.opencode/skills/devops-configure-infrastructure/SKILL.md

@@ -1,27 +0,0 @@
----
-name: devops-configure-infrastructure
-description: Define and configure core infrastructure components in Kubernetes
-type: skill
-triggers:
-  - "configure infrastructure"
-  - "infrastructure configuration"
----
-
-# workflow-configure-infrastructure.md
-# Infrastructure Configuration Workflow
-
-This workflow focuses on defining and configuring core infrastructure components in a Kubernetes environment.
-
-## Instructions
-1.  **Storage Definition**:
-    - Define `PersistentVolume` (PV) with appropriate access modes and storage classes.
-    - Define `PersistentVolumeClaim` (PVC) for application workloads.
-2.  **Networking**:
-    - Configure `Service` type `LoadBalancer` or `Ingress` controllers.
-    - Define `NetworkPolicies` for secure communication.
-3.  **Disconnected Environments**:
-    - Provide templates for local storage provisioners (e.g., hostPath, Local Persistent Volumes).
-    - Configure static IP assignments for on-prem load balancers.
-4.  **Validation**:
-    - Verify binding status: `kubectl get pv,pvc`
-    - Verify endpoint availability: `kubectl get endpoints`

package/.opencode/skills/devops-configure-infrastructure/bmad-skill-manifest.yaml

@@ -1,3 +0,0 @@
-type: skill
-name: devops-configure-infrastructure
-module: ma-skills

package/.opencode/skills/devops-disconnected-deployment/SKILL.md

@@ -1,27 +0,0 @@
----
-name: devops-disconnected-deployment
-description: Deploy applications in air-gapped or restricted on-prem environments
-type: skill
-triggers:
-  - "disconnected deployment"
-  - "air-gapped deployment"
----
-
-# workflow-disconnected-deployment.md
-# Disconnected Environment Deployment Workflow
-
-Strategies and actions for deploying applications in air-gapped or restricted on-prem environments.
-
-## Instructions
-1.  **Dependency Gathering**:
-    - Identify all required container images.
-    - Export images: `docker save {image_list} | gzip > images.tar.gz`
-    - Package Helm charts: `helm package {chart_path}`
-2.  **Target Readiness**:
-    - Verify local registry availability.
-    - Import images: `docker load < images.tar.gz`
-3.  **Deployment**:
-    - Use `--set image.repository={local_registry}/{repo}` for Helm.
-    - Verify offline connectivity between components.
-4.  **Troubleshooting**:
-    - Check for 'ImagePullBackOff' due to incorrect registry paths.

package/.opencode/skills/devops-disconnected-deployment/bmad-skill-manifest.yaml

@@ -1,3 +0,0 @@
-type: skill
-name: devops-disconnected-deployment
-module: ma-skills

package/.opencode/skills/devops-docker-compose-setup/SKILL.md

@@ -1,26 +0,0 @@
----
-name: devops-docker-compose-setup
-description: Multi-container orchestration using Docker Compose for development and on-prem
-type: skill
-triggers:
-  - "docker compose setup"
-  - "docker compose"
----
-
-# workflow-docker-compose-setup.md
-# Docker Compose Management Workflow
-
-This workflow handles multi-container orchestration using Docker Compose, optimized for development and on-prem deployments.
-
-## Instructions
-1.  **Define Services**: Map application components to Docker services.
-2.  **Environment Sync**: Setup `.env` file management for different environments (on-prem, dev).
-3.  **Disconnected Operations**:
-    - Build images with `--pull=false` if registry is unavailable.
-    - Use local image tags.
-4.  **Orchestration**:
-    - Setup dependencies with `depends_on` and health checks.
-    - Configure volumes for persistence.
-5.  **Execution**:
-    - `docker-compose up -d`
-    - `docker-compose ps`

package/.opencode/skills/devops-docker-compose-setup/bmad-skill-manifest.yaml

@@ -1,3 +0,0 @@
-type: skill
-name: devops-docker-compose-setup
-module: ma-skills

package/.opencode/skills/devops-manage-helm/SKILL.md

@@ -1,28 +0,0 @@
----
-name: devops-manage-helm
-description: Create and manage Helm charts and Helm umbrellas for complex systems
-type: skill
-triggers:
-  - "manage helm"
-  - "helm chart"
----
-
-# workflow-manage-helm.md
-# Helm Management Workflow
-
-This workflow handles the creation and management of Helm charts and Helm umbrellas for complex systems.
-
-## Instructions
-1.  **Analyze System**: Determine if a single chart or an umbrella chart (multiple sub-charts) is needed.
-2.  **Chart Creation**: 
-    - `helm create {chart_name}`
-    - Structure for disconnected environments: Ensure all chart dependencies are bundled (vendorized).
-3.  **Helm Umbrella Setup**:
-    - Configure `Chart.yaml` with sub-chart dependencies.
-    - Setup `values.yaml` to override sub-chart values.
-4.  **On-prem Optimization**:
-    - Prepare `chart-save` and `chart-load` routines for air-gapped systems.
-    - Configure local registry mirrors.
-5.  **Validation**:
-    - `helm lint {chart_path}`
-    - `helm template {chart_path}`

package/.opencode/skills/devops-manage-helm/bmad-skill-manifest.yaml

@@ -1,3 +0,0 @@
-type: skill
-name: devops-manage-helm
-module: ma-skills