GH Triage

Automatically scans GitHub repos to label, comment, assign, and fix issues and PRs for efficient triage and reporting.

This skill does what it says (triage and automatic small fixes) but be cautious: the code requires a GH_TOKEN (not declared in registry metadata) and will clone repos, run 'npm ci'/'npx' and other commands that can execute code from the target repository or its dependencies. Before installing, do the following: 1) only supply a least-privilege GitHub token (limit to specific repos and to the narrowest scopes needed; if you don't want pushes/PRs, use a read-only token); 2) run the skill in an isolated environment (container or sandbox) because it executes repo code; 3) inspect and verify the skill's code and the repositories you configure; 4) consider disabling or carefully reviewing the auto-fix behavior (commits/pushes) until you trust the environment and token handling; and 5) prefer storing secrets in your host secret store rather than plaintext env files. The metadata inconsistencies (undeclared env vars and use of config.example.json instead of configurable config.json) are additional warnings — treat this as a prototype that needs hardening rather than a drop-in safe tool.

Type: OpenClaw Skill Name: gh-triage Version: 0.1.0 The skill includes a script `auto_fix.js` that clones external repositories and executes `npm ci`, `npm run lint`, and `npm test` within the cloned directory. This design introduces a critical Remote Code Execution (RCE) vulnerability because it allows untrusted code from a triaged repository to execute arbitrary commands on the host system via npm lifecycle scripts or test suites. While these actions are aligned with the stated goal of automated PR fixes, the lack of sandboxing for third-party code execution poses a significant security risk.