← Plugin catalog
Developer Tools

Nexo YAML Iron

NSC Labs v2026.1.1

Kubernetes relationship review

Create a free account to save this plugin.

From the developer

Declared capabilities

  • Local
  • Read-only
  • Structured output

Not specified in the available declarations: limitations, pricing & account requirements.

Onboarding example

Review this Kubernetes YAML and explain established relationships and unknown evidence.
Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 22, 2026. Package observed Nov 21, 2026.

View package source →

Description

From the marketplace listing

Nexo YAML Iron reviews supplied Kubernetes YAML locally on macOS ARM64. It preserves established relationship findings and explicit unknowns, with detailed facts, joins, gaps and Ingress routes available for inspection. Supported declaration kinds are Pod, Deployment, ReplicaSet, StatefulSet, DaemonSet, Job, CronJob, Service, Ingress, ConfigMap, Secret, ServiceAccount, PersistentVolumeClaim and Namespace. Coverage concerns supported relationships and fields, not full schema validation or runtime health. ConfigMap text and exact references can be explained; Secret payloads and binary values remain opaque in structured output. It does not contact a cluster or change manifests. This release has no telemetry collection or production 7T interpretation.

Language: English · Automatically detected from descriptions.

What changed

· 4 observations

Capabilities & instructions

Full description changed from “established Service, Deployment, or Ingress relationship findings and explicit uncertainty. Use detailed inspection only when deeper evidence is needed. Do...” to “declared workload, Service, Ingress or resource-reference relationships and explicit unknown evidence. Use detailed...

View comparison →
Capabilities & instructions

Full description changed from “Review declared Kubernetes Service, Deployment, and Ingress relationships with deterministic findings and explicit uncertainty.” to “Review declared Kubernetes workload, Service, Ingress and resource-reference relationships with deterministic evidence and explicit unknowns.”. Default...

View comparison →

Technical updates · 1

Package or technical metadata updated

View technical comparison →

Similar plugins

Finding similar plugins… Results will appear here automatically.

Browse plugins →

Keywords

Files & skills

File archives

Plugin package47 files · 1.44 MBBrowse files →
Skill instructions
inspect-kubernetes-relationships4.72 KB

View saved version →

---
name: inspect-kubernetes-relationships
description: Review supplied local Kubernetes YAML with Nexo YAML Iron when the user needs declared workload, Service, Ingress or resource-reference relationships and explicit unknown evidence. Use detailed inspection for underlying facts and joins. Do not use this as evidence of live cluster state, policy compliance or runtime health.
---

# Review Kubernetes Relationships

Use the executable bundled with this plugin as the authoritative analyzer. Explain
its structured results without computing, filling, relabeling or replacing Nexo
state from intuition. This release requires local execution on macOS ARM64.

## Locate the executable

Use `${PLUGIN_ROOT}/scripts/nexo-yaml-iron` when the host supplies a resolved plugin
root. If that variable is not defined, derive the root from the actual installed
location of this file: `skills/inspect-kubernetes-relationships/SKILL.md` is two
levels below it. Use that absolute root with `/scripts/nexo-yaml-iron`. Do not
substitute a same-named command from PATH or a development checkout.

If the host cannot execute local programs or the platform is unsupported, explain
the compatibility requirement and stop rather than guessing a result.

## Run the review

For a manifest path explicitly supplied or authorized by the user:

```sh
"${PLUGIN_ROOT}/scripts/nexo-yaml-iron" review <path>
```

If the user supplies YAML text, use the host's local file tools to place the exact
text in a temporary YAML file before invoking the executable. Preserve its document
boundaries and values. Do not add a namespace, rewrite fields or scan unrelated
files. Redact credential values before they are supplied; opaque output is not
redaction of content already sent to an AI host. Do not split oversized input to
bypass the 512 KiB file budget.

Present this compact Review result first, preserving established findings and
explicit unknowns. No reported finding is not a safety or completeness verdict.

## Coverage

Supported declaration kinds are Pod, Deployment, ReplicaSet, StatefulSet,
DaemonSet, Job, CronJob, Service, Ingress, ConfigMap, Secret, ServiceAccount,
PersistentVolumeClaim and Namespace. Coverage concerns supported fields and
relationships, not complete Kubernetes semantics. Keep actual workload kinds and
namespace-qualified identifiers attached to the explanation.

ConfigMap text, key references, container environment sources, mounts, volumes,
ServiceAccounts and named resource dependencies can be inspected where supported.
Explain only supplied text and established reference relationships. Do not infer
runtime environment expansion or precedence. Secret payloads and binary values
remain opaque in structured output; do not ask for real credentials.

Unsupported kinds or fields remain outside coverage. Init-container port evidence
is unknown in this slice. Missing supplied declarations do not prove cluster absence.

## Detailed inspection

Use Inspect when the user needs underlying evidence, complete joins or a deeper
view of ambiguous Service-port/backend evidence:

```sh
"${PLUGIN_ROOT}/scripts/nexo-yaml-iron" inspect <path> --format json
```

Review is a compact projection and does not enumerate every established
relationship. Preserve relevant Inspect evidence when Review omits a summary.
Use `--format ndjson` only when row-oriented output is useful. Add `--snapshot`,
`--partition` or `--namespace` only for requested artifact coordinates; these flags
do not supply a missing manifest namespace or establish live cluster state.

## Explain the evidence

- Preserve findings, unknowns, source keys, namespaces, route bindings and gap cases.
- A known witness can coexist with residual unknowns. Do not erase either one.
- An unknown does not establish a negative finding. A removed gap does not prove repair.
- Explain ConfigMap references from supplied facts; do not invent unseen values.
- If a diagram helps or the user requests one, show a small relevant relationship

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.

Release notes

Adds the 14-kind application declaration roster and rebuilt hardened macOS ARM64 runtime. Preserves per-field and per-port unknown evidence, deterministic dependency ordering, scoped identities and bounded inputs. Expands workload and resource-reference inspection while keeping Secret payloads opaque. Includes binary-use terms and dependency notices. Telemetry and experimental 7T interpretation are not enabled. Review remains a compact projection; use Inspect for detailed evidence and coverage limits.

Declared in the saved package. Remote tools may change independently.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package author
NSC Labs
Keywords
See keywords
Commerce declaration
Does not support commerceThis does not establish whether access is free or paid.

Declared capabilities

  • Local
  • Read-only
  • Structured output

Package observed Nov 21, 2026.

Technical details
First seen
Sep 30, 2026 · 22:02 UTC
Last seen
Nov 22, 2026 · 00:00 UTC
Latest observed change
Oct 31, 2026 · 12:10 UTC
Collection status
Collected

plugins_6aa1b27bfa9481919ddf8e2ec393c495

Download plugin data (JSON)

Plugin details: served from cache. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.