Trace NVCF helmfile stack deployments and dependencies from helmfile.d sources.
npx skills add https://github.com/NVIDIA/nvcf --skill nvcf-explore-stack
Please help me install this Agent Skill. Skill: nvcf-explore-stack Source: https://github.com/NVIDIA/nvcf/tree/main/ai-tooling/dev/skills/nvcf-explore-stack Command: npx skills add https://github.com/NVIDIA/nvcf --skill nvcf-explore-stack
Navigate and explain the NVCF self-hosted stack inside the monorepo. Maps helmfile releases to their charts, image-source subtrees, helm hooks, namespaces, and needs: dependency chains. Reads deploy/stacks/self-managed/helmfile.d/*.yaml.gotmpl as the source of truth for ordering and versions, with deployment-sequence.md and deployment-dependencies.yaml as enrichment, and imports.yaml for upstream provenance. Use when a user or developer asks "what deploys X", "what does X depend on", "what hooks run for X", "walk me through deployment order", "which subtree do I edit to change X", "what namespaces does the stack use", or mentions stack topology, helmfile stages, deployment DAG, or dependency map. Always cite the source file path so the user can verify.
Identify releases, charts, image sources, hooks, and namespaces for a given stack. Determine deployment order, dependencies, and ownership across monorepo layers. Assist onboarding by explaining stack topology and provenance with explicit file citations.
Ask it to explain what deploys a release X by tracing deploy/stacks/self-managed/helmfile.d/*.yaml.gotmpl and enrichment files, citing exact source paths.
High-intent search queries and answers about installing and using this skill.
Determine deployment order by tracing helmfile.d/*.yaml.gotmpl sources combined with deployment-sequence.md enrichment files. This maps the deployment DAG, showing the exact sequence and dependency chains required to orchestrate the stack.
Find helm hooks and namespaces by querying the helmfile.d gotmpl sources and enrichment files for the target release. This reveals the specific hooks executed during deployment and the namespaces the stack utilizes across the monorepo.
You can identify the correct image-source subtree by tracing the release through helmfile.d configurations and imports.yaml. This points to the exact upstream provenance and monorepo directory you need to edit to modify the image.
The best way to map dependencies is by analyzing helmfile.d gotmpl files with imports.yaml for upstream provenance. This provides a complete dependency map and traces the origin of all components within the deployment topology.
Yes, the stack topology tracer always cites the exact source file paths, such as helmfile.d gotmpl files and imports.yaml. This allows you to manually verify the deployment ordering, hooks, and dependency chains within the monorepo.
henrycashe26Standardize repository agent configurations for issue tracking, triage labels, and domain documentation.
VoltDBAutomate VoltDB cluster deployment and configuration on Kubernetes with Helm and Terraform.
cosmonic-labsEnforce Helm chart conventions for consistent Kubernetes deployments.
ollieb89Initialize, template, test, and package Helm charts for Kubernetes applications.
