Most static external command findings are Markdown formatting false positives, and the hardcoded documentation or in-cluster URLs are benign examples. The OpenTelemetry template binds telemetry ports to 0.0.0.0, and the Kiali template uses anonymous authentication with broad namespace visibility. No prompt injection text or malicious exfiltration intent was found.
The Kiali template sets anonymous authentication and grants visibility across all namespaces. If deployed as written, it can expose mesh topology and workload metadata to unauthorized users.
The YAML explicitly sets auth.strategy to anonymous and accessible_namespaces to ** in the same Kiali configuration block. This is a clear insecure default for shared or production clusters.
Capability review items (4)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
The OpenTelemetry template binds a receiver or exporter to 0.0.0.0, which exposes telemetry endpoints on all container interfaces if deployed without network controls. This can be legitimate in Kubernetes, but it needs explicit access restrictions.
The OpenTelemetry template binds a receiver or exporter to 0.0.0.0, which exposes telemetry endpoints on all container interfaces if deployed without network controls. This can be legitimate in Kubernetes, but it needs explicit access restrictions.
The OpenTelemetry template binds a receiver or exporter to 0.0.0.0, which exposes telemetry endpoints on all container interfaces if deployed without network controls. This can be legitimate in Kubernetes, but it needs explicit access restrictions.
The OpenTelemetry template binds a receiver or exporter to 0.0.0.0, which exposes telemetry endpoints on all container interfaces if deployed without network controls. This can be legitimate in Kubernetes, but it needs explicit access restrictions.
Most static external command findings are Markdown formatting false positives, and the hardcoded documentation or in-cluster URLs are benign examples. The OpenTelemetry template binds telemetry ports to 0.0.0.0, and the Kiali template uses anonymous authentication with broad namespace visibility. No prompt injection text or malicious exfiltration intent was found.
The Kiali template sets anonymous authentication and grants visibility across all namespaces. If deployed as written, it can expose mesh topology and workload metadata to unauthorized users.
The YAML explicitly sets auth.strategy to anonymous and accessible_namespaces to ** in the same Kiali configuration block. This is a clear insecure default for shared or production clusters.
Capability review items (4)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
The OpenTelemetry template binds a receiver or exporter to 0.0.0.0, which exposes telemetry endpoints on all container interfaces if deployed without network controls. This can be legitimate in Kubernetes, but it needs explicit access restrictions.
The OpenTelemetry template binds a receiver or exporter to 0.0.0.0, which exposes telemetry endpoints on all container interfaces if deployed without network controls. This can be legitimate in Kubernetes, but it needs explicit access restrictions.
The OpenTelemetry template binds a receiver or exporter to 0.0.0.0, which exposes telemetry endpoints on all container interfaces if deployed without network controls. This can be legitimate in Kubernetes, but it needs explicit access restrictions.
The OpenTelemetry template binds a receiver or exporter to 0.0.0.0, which exposes telemetry endpoints on all container interfaces if deployed without network controls. This can be legitimate in Kubernetes, but it needs explicit access restrictions.
Static analysis reported many high-risk patterns, but most are false positives from Markdown code fences, PromQL expressions, and documentation links. Real publish concerns remain in example manifests that enable anonymous Kiali access, wildcard namespace visibility, broad listener bindings, and insecure telemetry TLS settings.
The Kiali example sets anonymous authentication and wildcard namespace access. If copied into a shared cluster, it can expose mesh topology and service metadata too broadly.
The configuration explicitly uses anonymous access and accessible_namespaces set to a wildcard. This is a clear copy-paste security risk, although it is documentation and not executed by the skill.
Capability review items (2)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
The Linkerd section includes shell commands that install or query mesh observability components. They are legitimate examples but can alter a Kubernetes cluster if copied.
The commands are visible and relevant to the skill purpose. They are not hidden or malicious, but they deserve user review before execution.
Static false positives ignored (4)
These static matches were dismissed by semantic review or matched schema-only tokens, so they are shown for transparency but do not drive the quality score.
False Positive: Markdown Backticks Flagged as Ruby Shell Execution
The reported external command locations are Markdown code fences or inline resource references. The skill contains documentation, not Ruby code that executes shell backticks.
Line review shows Markdown fences and one bash example block. No Ruby runtime, interpolation, or automatic command execution path is present.
False Positive: Weak Cryptography Alerts Match Query Syntax
No weak cryptographic algorithm usage was found. The alerts map to service mesh text, PromQL rate windows, histogram queries, and alert annotations.
The reviewed lines contain observability descriptions and query expressions, not crypto APIs or hashing functions. The scanner appears to match short substrings in normal text.
This skill is a documentation-only guide for service mesh observability. Static analysis flagged 55 patterns, but all are false positives: backtick commands are markdown code blocks (not execution), hardcoded URLs/IPs are configuration examples, and crypto warnings are triggered by YAML config snippets. No actual code execution, network calls, or filesystem operations occur.