The static external-command alerts are Markdown formatting false positives, and the network URLs are expected Prometheus installation or localhost validation examples. The certificate findings reference TLS file paths only; no certificate or private key content is included. No prompt injection, exfiltration intent, or malicious behavior was found in SKILL.md.
The static external-command alerts are Markdown formatting false positives, and the network URLs are expected Prometheus installation or localhost validation examples. The certificate findings reference TLS file paths only; no certificate or private key content is included. No prompt injection, exfiltration intent, or malicious behavior was found in SKILL.md.
Most static detections are false positives caused by Markdown code fences and inline file references, not executable backtick code. One low-risk external dependency remains because the Helm setup command contacts the public Prometheus Community chart repository. The certificate entries are example TLS file paths and do not contain secret material.
1
Files scanned
405
Lines analyzed
3
Review items
0
False positives ignored
Capability review items (1)
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 Helm command contacts an external Prometheus Community chart repository. It is an expected public dependency, but it still creates supply-chain and network trust considerations.
Static command, network, sensitive file, weak crypto, and heuristic findings were reviewed in context. The matches are Markdown examples for Prometheus setup, local API checks, TLS file paths, and alert template syntax. No evidence found of executable code, credential exfiltration, prompt injection, obfuscation, or malicious intent.
The certificate and key findings refer to example Prometheus TLS configuration paths. The file does not contain private key material, certificates, or embedded secrets.
The lines are YAML path references under tls_config. No secret values or credential contents are present in the skill file.
Capability review items (3)
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 skill includes Helm, promtool, and curl commands that users may run during Prometheus setup or validation. These are legitimate operational examples, but users should review targets and namespaces before execution.
The commands are inside Markdown code blocks and align with the skill purpose. There is no evidence that the skill executes them automatically.
The hardcoded URLs point to the official Prometheus community Helm chart repository and localhost Prometheus API endpoints. No external exfiltration endpoint or encoded data transfer was found.
The URL contexts are clear Prometheus installation and validation examples. I found no credential payloads or suspicious remote collection service.
Static Heuristic Was Triggered By Documentation Patterns
The critical combination heuristic combines command snippets, URLs, and TLS path references. In context, these are Prometheus documentation examples without executable skill code.
The suspicious elements exist but are not wired together as code. I found no obfuscation, hidden execution path, or instruction to bypass review.
This is a legitimate Prometheus configuration documentation skill. The static scanner flagged code examples within markdown documentation as executable code, which is a false positive. All detected patterns (external commands, network URLs, certificate paths, crypto algorithms) appear in YAML/bash code blocks showing configuration examples - not actual runtime code. No malicious intent detected. Skill is safe for publication.
1
Files scanned
407
Lines analyzed
0
Review items
5
False positives ignored
Static false positives ignored (5)
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.
Static scanner flagged dangerous combination heuristic triggered by documentation code examples. This is a documentation skill showing Prometheus config examples in YAML and bash code blocks. No actual code execution occurs.
Heuristic triggers on documentation patterns. SKILL.md is purely educational content with YAML/bash examples, not executable code.
Backtick and $() patterns appear in bash command examples within documentation. Not actual shell execution - users would run these commands themselves in their terminal.
All backtick/$ patterns are in code fences showing example commands users would run. No exec() or system() calls in actual skill code.