T09 · Insecure Skill Coding Practices
- Location
SKILL.md:34- Finding
Public Gist Publication Is the Default Without a Sensitive-Data Review
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill does what it says, but it defaults agents toward publishing arbitrary content to a public GitHub Gist without a required sensitive-data check or confirmation step.
Review this skill carefully before installing. Use it only for content you have intentionally reviewed for public sharing, prefer secret Gists for non-public material, and never include tokens, credentials, private logs, customer data, or internal context. Store the GitHub token with the least necessary scope and rotate it if it may have been exposed.
SKILL.md:34Public Gist Publication Is the Default Without a Sensitive-Data Review
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
git clone https://github.com/PsiClawOps/gist-share ~/.openclaw/skills/gist-share
### 2. Create a GitHub Personal Access Token (PAT)
1. Go to [github.com/settings/tokens](https://github.com/settings/tokens)
2. Click **"Generate new token (classic)"**
The skill requires a GitHub Personal Access Token in the environment, which is a legitimate operational need, but it normalizes credential setup without any handling guidance, least-privilege notes beyond the scope name, or warnings about leaking the token through command output, logs, or downstream gist content. In an agent context, environment-provided secrets are especially sensitive because other tools or prompts may inadvertently expose them.
## Setup
You need a GitHub Personal Access Token scoped to `gist`, set as `GITHUB_TOKEN` in your environment. Ask your agent to walk you through creating one if you haven't already.
---
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
git clone https://github.com/PsiClawOps/gist-share ~/.openclaw/skills/gist-share
### 2. Create a GitHub Personal Access Token (PAT)
1. Go to [github.com/settings/tokens](https://github.com/settings/tokens)
2. Click **"Generate new token (classic)"**
The README explicitly instructs the agent to create a public GitHub Gist and emphasizes that it is readable by anyone, but it does not provide a prominent warning against posting secrets, credentials, personal data, or internal context. In an agent skill, this is risky because users may hand off arbitrary runtime context, and the default example encourages publication to a world-readable URL.
The skill explicitly encourages posting arbitrary content to a public GitHub Gist and emphasizes that it is readable by anyone, but it does not provide a prominent warning against publishing sensitive data such as credentials, internal reports, logs, or user information. In an agent setting, this increases the risk of accidental data exfiltration because operators may treat the skill as a general-purpose sharing mechanism without understanding the permanence and public exposure of the output.