Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Reddit to PR

v0.1.2

Scan Reddit for pain points in a product’s niche, identify a real user complaint worth fixing, and prepare an approved patch or PR workflow for a target repo...

0· 38·0 current·0 all-time
byRyan McNutt@mcnutt1414
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
!
Purpose & Capability
The skill claims to scan Reddit and prepare/submit fixes to a repository. That legitimately requires filesystem and git access and the ability to interact with remote hosting (e.g., GitHub) or a push-capable git credential. However the skill's manifest declares no required binaries or credentials. Not declaring 'git' (or a code-hosting token) is an incoherence: the actions the skill performs (branch, commit, push, open PR) normally need git and remote auth.
!
Instruction Scope
SKILL.md instructs the agent to read/write {baseDir}/config.json, access an arbitrary repoPath on disk, run git operations, search the web for Reddit posts, extract quotes, and optionally post results to Slack. Those actions broadly match the purpose, but the instructions do not constrain or explicitly document how web access, Reddit scraping, and Slack posting are performed or authenticated. The skill relies on 'existing remote/auth tooling' without declaring what forms of credentials it expects or how the agent will obtain them. It also allows local edits and commits after 'explicit user approval'—this is safer than automatic writes, but the document gives the agent filesystem and network actions that could be risky if approval boundaries are unclear.
Install Mechanism
No install spec and no code files are present; this is instruction-only. That lowers risk because nothing new is written to disk by an installer. The runtime instructions will rely on environment tools already present.
!
Credentials
The manifest requests no environment variables or credentials, yet the skill's operational phases (push, open PR, optionally post to Slack) normally require authentication tokens. The SKILL.md says it 'must not request, create, or install credentials on its own' and that pushes/PR creation require existing tooling, but failing to declare required credentials or binaries (git, network/browser tool, slack token or OpenClaw channel access) is a mismatch that can confuse users and lead to unexpected failures or ad-hoc credential use.
Persistence & Privilege
always:false and user-invocable defaults are appropriate. The skill writes a single config.json into its baseDir for setup state, and scheduling is optional and defaults to 'analyze' for safety. No 'always' privilege or cross-skill modifications are requested.
What to consider before installing
This skill appears to do what it claims, but there are important gaps you should address before installing or running it with real repos: - Expect the skill to read and write a config at {baseDir}/config.json and to operate on whatever path you give as repoPath. Only point it at repositories you trust and where an automated tool is allowed to create branches and make edits. - Ensure the runtime environment has git installed and that remote authentication (SSH agent, credential helper, or platform token) is already configured for any push/PR operations. The skill does not declare these dependencies explicitly. - If you plan to enable 'patch' or 'pr' modes or scheduled runs, prefer 'analyze' as the default and require explicit, per-run approval before any writes. Review the exact approval prompts the skill will present. - If you enable Slack results, confirm how the agent will post (OpenClaw channel id vs Slack token) and avoid giving the skill credentials it did not request in its manifest; prefer OpenClaw-managed channel IDs or an isolated session. - Run initial tests in an isolated environment or a fork of your repo to verify behavior before letting it touch production repositories. What would change this assessment: adding explicit declarations of required binaries (git, curl/browser tool) and required environment variables or supported auth modes (SSH, GITHUB_TOKEN, OpenClaw channel id) would make the skill's requirements proportional and move toward 'benign'. Conversely, any instruction to collect arbitrary credentials or to access paths outside the configured repo would increase risk and could make the skill malicious. If you want, provide the full SKILL.md (untruncated) or confirm how you plan to authenticate pushes/PRs and I can re-evaluate with higher confidence.

Like a lobster shell, security has layers — review code before you run it.

latestvk9738dy0x37hz9zvyykvwbn49583z48j

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments