GitHub Auto Reply

v1.0.0

Smart auto-reply for GitHub Issues with professional customer service

0· 342·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
high confidence
!
Purpose & Capability
The skill is presented as a 'Smart auto-reply' with AI analysis, but the SKILL.md only shows simple heuristics (label checks, basic language detection via substring, static templates) and no actual AI calls or external AI credentials. The stated AI capability (analysis, multi-language intelligence) is not implemented in the provided instructions.
!
Instruction Scope
Instructions are narrowly scoped to creating a GitHub Actions workflow that posts comments on new Issues — that matches the core purpose. However the guide explicitly tells the user to set repository Settings > Actions > Allow all actions, which is broader than needed for a single workflow and increases security risk by permitting arbitrary third-party actions to run in the repo.
Install Mechanism
This is an instruction-only skill with no install steps or code files to download or execute. No install mechanism risk is present.
!
Credentials
No environment variables are declared, but the workflow relies implicitly on GitHub Actions' provided GITHUB_TOKEN and repository action permissions. The SKILL.md does not mention required token/permission scopes (issues: write) or the need to configure workflow permissions. Advising 'Allow all actions' is disproportionate to the stated task and increases exposure to third-party action code.
Persistence & Privilege
The skill does not request 'always' presence, does not modify other skills, and has no persistent installation. It only instructs creating a workflow that runs on issue events — typical and proportionate for the purpose.
What to consider before installing
This skill mostly gives a GitHub Actions workflow to auto-comment on issues — it is coherent with its basic purpose but contains two red flags you should address before use: 1) The README/description promises 'AI analysis' and fast 'AI' replies, but the provided workflow uses only simple heuristics (labels, substring checks) and static templates. If you expect real AI-driven responses you should verify which AI service will run, what credentials it needs, and where model calls occur. As-is there are no AI calls. 2) The instructions recommend enabling 'Allow all actions' in repository settings. That is broader than necessary and increases risk: it allows any third-party GitHub Action to run in your repo. Instead, prefer a least-privilege configuration: allow only specific actions or use the official actions/github-script and ensure workflow permissions restrict GITHUB_TOKEN to the minimum (issues: write). Also explicitly set workflow 'permissions' (e.g., issues: write) so you know what's being granted. Additional practical steps: - Replace placeholder contact@example.com with a valid address you control. - Test the workflow in a non-production/test repository first. - Review the exact templates the workflow will post to avoid leaking internal info. - If you want true AI-based replies, demand explicit code/instructions showing API calls, and review what credentials (API keys/PATs) are required before installing. Given the marketing/implementation mismatch and the insecure permission recommendation, treat this skill as suspicious until those issues are resolved.

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

latestvk971wb2nx1t763b17rhyzyh7nh820mfh

License

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

Comments