Most high static secret detections are scanner regex definitions rather than embedded credentials. Real risks remain around .env scanning, redaction gaps, outbound marketplace submissions, sibling-directory command execution, and public repository publication.
The scanner treats .env files as text inputs while walking a user-supplied tree. That is audit-related, but it can process sensitive environment files and should redact output.
The audit script stores the matched source line in Finding.text and prints it in normal and JSON output. If a real key is found, the raw value can appear in logs or reports.
The code directly captures and prints full matched lines while scanning for API keys and private keys. The audit purpose is legitimate, but secret values should be masked.
Capability review items (14)
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 command references ../../skill-package and a user-supplied absolute path. It can execute code outside the skill directory, so the filesystem boundary risk is real.
python3 ../../skill-package/scripts/skill_package.py build /absolute/path/to/skill --mode public
The build command references ../../skill-package and writes a public package from a user-supplied source path. The sibling-directory execution risk is real.
The validator command references ../skill-creator outside the skill package. It assumes a trusted sibling path and could execute unintended local code.
The fenced block instructs running a local Python audit command on a user-supplied skill path. External command execution is explicit and should require user approval.
The script imports urllib and later uses it for outbound marketplace submissions. This enables transmission of repository URLs and optional user notes.
This posts the repository URL and optional notes to the Skillstore API. The endpoint is legitimate for the workflow, but it is real external transmission.
Most high static secret detections are scanner regex definitions rather than embedded credentials. Real risks remain around .env scanning, redaction gaps, outbound marketplace submissions, sibling-directory command execution, and public repository publication.
The scanner treats .env files as text inputs while walking a user-supplied tree. That is audit-related, but it can process sensitive environment files and should redact output.
The audit script stores the matched source line in Finding.text and prints it in normal and JSON output. If a real key is found, the raw value can appear in logs or reports.
The code directly captures and prints full matched lines while scanning for API keys and private keys. The audit purpose is legitimate, but secret values should be masked.
Capability review items (14)
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 command references ../../skill-package and a user-supplied absolute path. It can execute code outside the skill directory, so the filesystem boundary risk is real.
python3 ../../skill-package/scripts/skill_package.py build /absolute/path/to/skill --mode public
The build command references ../../skill-package and writes a public package from a user-supplied source path. The sibling-directory execution risk is real.
The validator command references ../skill-creator outside the skill package. It assumes a trusted sibling path and could execute unintended local code.
The fenced block instructs running a local Python audit command on a user-supplied skill path. External command execution is explicit and should require user approval.
The script imports urllib and later uses it for outbound marketplace submissions. This enables transmission of repository URLs and optional user notes.
This posts the repository URL and optional notes to the Skillstore API. The endpoint is legitimate for the workflow, but it is real external transmission.
Most secret-pattern and Markdown static hits are false positives from scanner signatures or formatting. Real risks remain in outbound marketplace submissions, public GitHub publishing commands, relative helper script execution, and audit output that can reveal matched secret lines.
The audit script stores matched line text and prints it in reports. When a real secret is detected, logs or JSON output can reveal the secret-bearing line.
The code copies matching line text into Finding.text and emits findings through JSON and console output. The scanner targets secret patterns, so a true positive can leak the detected secret value.
Capability review items (14)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
This command block copies files, creates commits, and pushes a public GitHub repository. If run on the wrong artifact, it can publish unintended content.
The command executes packaging helpers through parent-directory paths outside the skill root. In a different install layout, that can execute unexpected local code.
python3 ../../skill-package/scripts/skill_package.py build /absolute/path/to/skill --mode public
The command executes packaging helpers through parent-directory paths outside the skill root. In a different install layout, that can execute unexpected local code.
The command executes a validator through a parent-directory path outside the skill root. In a different install layout, that can execute unexpected local code.
This command block instructs the agent to run a local Python audit script against a user-supplied skill path. The command is intended, but it requires trusting the local script and path.
The urllib request code supports outbound POST requests to marketplace endpoints. It is intentional, but it creates a real external data-sharing surface.
The urllib request code supports outbound POST requests to marketplace endpoints. It is intentional, but it creates a real external data-sharing surface.
with urllib.request.urlopen(request, timeout=30) as response:
The urllib request code supports outbound POST requests to marketplace endpoints. It is intentional, but it creates a real external data-sharing surface.
The script posts the repository URL and optional notes to the Skillstore endpoint. This is expected publishing behavior, but it transmits user-provided data externally.
The script posts listing request content and optional email to the SkillMap feedback endpoint. This is expected, but it shares user-provided data with a third party.
Static false positives ignored (1)
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.
The static analyzer reported many high and critical patterns, but most are false positives from markdown backticks, marketplace URLs, regex definitions, and words such as SKILL.md. Confirmed risks are intentional: scripts read local skill files and submit user-provided repository or contact details to public marketplace endpoints, so use requires user consent and endpoint verification.
The submit script posts repository URLs, notes, optional email addresses, and listing messages to Skillstore and SkillMap endpoints. This is expected for the skill, but it can disclose user-provided project and contact details if run without clear consent.
The code directly builds JSON payloads and sends POST requests to fixed external marketplace URLs. The behavior matches the skill purpose, so the risk is disclosure through intended operation rather than hidden exfiltration.
The audit script walks a user-supplied skill directory, reads text-like files, and prints detected secret-like lines. This is legitimate audit behavior, but findings may expose sensitive snippets in terminal logs or captured output.
The filesystem traversal and output of matching lines are explicit in the script. The code does not send this data over the network, but local output exposure is a real operational concern.
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.
Many external-command findings occur in fenced documentation examples and marketplace notes. They are not executed by the skill automatically, but users should review commands before running publishing steps such as git, rsync, gh, and Python scripts.
The cited locations are markdown instructions or URL notes, not runtime shell execution. The only risk is if a user voluntarily runs documented commands without verifying paths and destinations.
Secret and Environment Access Patterns Are Scanner Definitions
The reported private-key, API-key, dotenv, and SSH-file hits appear inside regex pattern definitions for the audit scanner. No evidence found that the script reads environment variables, imports dotenv, or contains real secret material.
The suspicious strings are compiled regular expressions used to detect secrets in other files. The script imports os for directory walking, but does not access os.environ or load dotenv files as configuration.
The weak-cryptography alerts point to descriptions, markdown references, argparse setup, or marketplace text. No evidence found of MD5, SHA1, DES, RC4, or other weak cryptographic operations in the cited files.
Manual review of the cited lines found user-facing text and parser construction, not cryptographic API calls. The scanner likely matched substrings such as md in SKILL.md or marketplace wording.
The path traversal findings are caused by documentation examples using relative paths to neighboring local tooling. They are not used in code to open attacker-controlled paths, although users should adjust paths for their own workspace.
The ../ sequences occur in markdown command examples, not in a file-access implementation. The actual audit script resolves the supplied root path and walks that directory intentionally.
This skill is a legitimate security audit and marketplace publishing tool. Static analysis detected 126 patterns that are primarily false positives: (1) Pattern definitions in public_skill_audit.py designed to detect secrets were flagged as containing secrets, (2) Markdown backticks in documentation were misidentified as Ruby shell execution, (3) Public API endpoints for marketplace submission were flagged as hardcoded URLs. The skill performs local file auditing, makes outbound HTTP requests to public marketplace APIs, and uses shell commands for git operations - all appropriate for its intended purpose.
5
Files scanned
574
Lines analyzed
4
Review items
4
False positives ignored
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.
Static analyzer flagged 73 instances of 'Ruby/shell backtick execution' in SKILL.md and references/marketplaces.md. These are markdown code block delimiters showing bash command examples, not actual Ruby code execution. All flagged lines are in documentation files demonstrating workflow commands.
Verified file contents are markdown documentation with backtick-delimited code blocks, not Ruby source code. No executable Ruby files exist in the repository.
Static Scanner False Positive - Pattern Definitions Detected as Threats
The public_skill_audit.py script contains regex patterns to detect secrets (SSH keys, API tokens, AWS keys). Static analysis flagged these pattern definitions as actual security threats. The script is a security detector, not a source of vulnerabilities.
Code review confirms lines 47-60 define HIGH_PATTERNS and MEDIUM_PATTERNS arrays containing compiled regex objects for secret detection, not actual secret values.
Public API endpoints for Skillstore (skillstore.io/api/submit) and SkillMap (skillmaps.net/v1/feedback) were flagged as hardcoded URLs. These are documented public marketplace submission endpoints required for the skill's core functionality.
URLs point to documented public API endpoints verified in references/marketplaces.md. No authentication credentials are embedded.
Multiple files were flagged for 'weak cryptographic algorithm'. These are false positives from pattern matching on documentation text and file extensions, not actual cryptographic implementations.
No cryptographic libraries imported or used. Flags triggered by text patterns in documentation, not actual crypto code.