Back to skill

Security audit

github-skill-publisher

Security checks across malware telemetry and agentic risk

Overview

This GitHub-publishing skill is mostly coherent, but it deserves review because it handles GitHub write tokens, publishes local files publicly, has a privacy-scan gap, and writes activity into memory.

Install only if you are comfortable giving the workflow GitHub write access and publishing the selected directory publicly. Prefer a fine-grained, minimal-scope, short-lived token or GitHub CLI auth, avoid pasting tokens into chat or shell history, manually review the files to publish, run a privacy scan that includes SKILL.md and scripts, and disable or avoid persistent memory logging for repository details unless you explicitly want it.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Tool MisuseTool Parameter Abuse, Chaining Abuse, Unsafe Defaults
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
Findings (7)

Lp3

Medium
Category
MCP Least Privilege
Confidence
95% confidence
Finding
The skill clearly describes capabilities to read local files, access environment variables/tokens, and make outbound network requests to GitHub, yet it declares no permissions. This creates a transparency and consent gap: an agent could perform sensitive file scanning and publish content remotely without an explicit permission boundary, increasing the risk of overreach or accidental data exposure.

Context-Inappropriate Capability

Medium
Confidence
91% confidence
Finding
The skill instructs writing publication activity, commit hashes, and operational details into persistent memory, which is not necessary to complete a one-time GitHub publishing task. Persistent retention of repo activity can create an unnecessary audit trail containing sensitive project metadata, repository identities, or workflow details that may later be exposed or reused out of context.

Missing User Warnings

Medium
Confidence
84% confidence
Finding
The README instructs users to export a GitHub personal access token with write permissions directly in the shell, but gives only minimal cleanup guidance. This increases the chance of credential exposure through shell history, inherited environment variables, process inspection, logs, or accidental reuse during publishing to public repositories.

Vague Triggers

Medium
Confidence
83% confidence
Finding
The trigger conditions include broad everyday phrases such as uploading or publishing to GitHub, which can cause the skill to activate in situations where the user did not intend a full public-release workflow. In this skill, mis-triggering is more dangerous because the documented workflow includes scanning local files and publishing to a public repository.

Credential Access

High
Category
Privilege Escalation
Content
| 私有仓改公开 | `private` topic 残留 | 改完 visibility 立即重设 topics |
| 描述拼接中英混排 | 仓库主页"中英缝合感" | 全部用纯中文一句话 |
| commit message 中文逗号 | zsh 显示"nothing to commit" 误报 | 实际成功,看 git log 确认 |
| 凭据来源失效 | Keychain PAT 读不到、gh CLI 未登录 | 必问用户贴 PAT,只用一次立即清空 |

## 客观挑刺清单(必做项)
Confidence
97% confidence
Finding
Keychain

Tool Parameter Abuse

High
Category
Tool Misuse
Content
发布完一个项目后,必须:
1. `unset GH_TOKEN` —— 凭据立即从环境清空
2. 临时文件 `rm -rf /tmp/xxx-review` —— 不留痕
3. 写 memory:今天推了几个仓、commit hash、踩了什么坑
4. 主动挑刺 + 报告,让用户决定是否继续
Confidence
87% confidence
Finding
rm -rf /

Tool Parameter Abuse

High
Category
Tool Misuse
Content
发布完一个项目后,必须:
1. `unset GH_TOKEN` —— 凭据立即从环境清空
2. 临时文件 `rm -rf /tmp/xxx-review` —— 不留痕
3. 写 memory:今天推了几个仓、commit hash、踩了什么坑
4. 主动挑刺 + 报告,让用户决定是否继续
Confidence
87% confidence
Finding
rm -rf /tmp/

VirusTotal

VirusTotal findings are pending for this skill version.

View on VirusTotal

Static analysis

No suspicious patterns detected.