agentsclimarketplace

Validate config

Skill nuonco/nuon-plugin/skills/validate-config

Validate a Nuon app configuration for correctness and best practices. Invoke when users ask to check, validate, review, or verify their Nuon configuration.From its SKILL.md

Install
npx -y skills add nuonco/nuon-plugin --skill validate-config

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

5.4 KB, as published. Nobody here has run it

You are validating a Nuon app configuration. Follow these steps:

Step 1: Discover Config Files

Look for Nuon app configuration files in the current directory or the path the user specifies. Expected files:

  • metadata.toml, inputs.toml, sandbox.toml, runner.toml, stack.toml
  • components/*.toml, components/values/*.yaml
  • actions/*.toml, secrets.toml, permissions/*.toml, break_glass.toml, policies.toml

Read all discovered files.

Step 2: Schema Validation

Read reference/schema.md and check each file against its schema:

  • metadata.toml: Must have version (should be "v2"), display_name, description
  • inputs.toml: Each [[input]] needs name, display_name, description, group. Both display_name and group are required. Also check for type (e.g. "string", "number", "boolean") and user_configurable. The internal field is deprecated — flag it as a warning. Groups need name, display_name, description
  • sandbox.toml: Needs terraform_version, repo config ([public_repo] or [connected_repo]), [vars]
  • runner.toml: Needs runner_type (aws/azure/gcp). Check role and enable_kube_config if present. Check cloud_platform and GCP-specific fields (gcp_permissions, gcp_predefined_role) for GCP runners. Installs may have a [gcp_account] block with project_id and region
  • stack.toml: Needs type (aws-cloudformation/azure-bicep/nested), name
  • Components: Each needs name, type, type-specific fields. Check type is one of: helm_chart, terraform_module, docker_build, container_image, kubernetes_manifest, job, pulumi. Also check for take_ownership, build_timeout, deploy_timeout. For pulumi components, runtime is required. For kubernetes_manifest components, check kustomize fields: path, patches, enable_helm, load_restrictor
  • Repo configs: Only one of [public_repo], [connected_repo], or [helm_repo] may be defined per component/sandbox (they are mutually exclusive)
  • Version fields: terraform_version and similar version fields must be quoted strings (e.g., "1.5.0" not 1.5.0 — unquoted dotted numbers are invalid TOML)
  • Deprecated fields — ERROR: Using var (array) instead of [vars] (map) or env_var (array) instead of [env_vars] (map) are errors, not warnings. Flag these as Errors and provide the corrected map syntax

Step 3: Template Validation

Read reference/templating.md and check all {{ }} expressions:

  • Valid prefixes: .nuon.install.id, .nuon.inputs.inputs., .nuon.install.sandbox.outputs., .nuon.install_stack.outputs., .nuon.components., .nuon.org.id, .nuon.app.id
  • Balanced braces: every {{ has matching }}
  • No typos in common paths (e.g., .nuon.input.inputs should be .nuon.inputs.inputs)
  • Input references match defined inputs in inputs.toml
  • Component references match defined component names

Step 4: Dependency Validation

  • Check for circular dependencies in component dependencies arrays
  • Verify that referenced components exist
  • Check that components using {{ .nuon.components.X.outputs.Y }} have X in their dependencies (or X is defined)

Step 5: Best Practices

  • Component files should be numbered (0-name.toml, 1-name.toml)
  • Sensitive inputs should have sensitive = true
  • Required inputs should have required = true
  • Resources should include {{ .nuon.install.id }} in names for uniqueness
  • Permissions should define all three roles (provision, maintenance, deprovision)
  • Break glass config should exist

Step 6: CLI Validation

Run the Nuon CLI check script to see if nuon is installed:

bash ${CLAUDE_PLUGIN_ROOT}/scripts/check-nuon-cli.sh

If installed, run validation in the app config directory:

nuon apps validate
  • If validation passes, note "CLI validation passed" in your report.
  • If validation returns errors, add them to the Errors section of your report, attempt to fix the issues, and re-run nuon apps validate until it passes or you cannot resolve the remaining errors.
  • If validation returns "app not found": this means the app has not been created in the Nuon control plane yet. This is NOT a config error — report it in the Info section and offer to create the app by asking the user if they'd like to run nuon apps create --name=<dir-name> (where dir-name is the current directory name, since app name must match directory name). If they accept, create the app and re-run nuon apps validate.
  • If the CLI is not installed, skip this step and add an info note: "Install Nuon CLI for authoritative validation: brew install nuonco/tap/nuon"

Report Format

Present findings as:

Errors (must fix):

  • Missing required fields
  • Invalid component types
  • Broken template references
  • Circular dependencies
  • Use of deprecated var array or env_var array (must use [vars] map / [env_vars] map)
  • Missing display_name or group on inputs
  • GCP install missing project_id or region in [gcp_account]

Warnings (should fix):

  • Missing best practice fields
  • Unnumbered component files
  • Sensitive inputs without sensitive = true
  • Use of deprecated internal field on inputs

Info:

  • Total files found
  • Component count and types
  • Input count and groups

$ARGUMENTS

Keep looking

Skills are one crate of 609,689. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.