tester_skill

Manage GitHub issues by listing, filtering, spawning fix agents, creating PRs, and tracking review comments using the authenticated gh CLI.

Key things to consider before installing: - The SKILL.md requires the gh CLI and a GitHub token (GITHUB_TOKEN), but the skill metadata does not declare these — confirm the author/source and why metadata omits these requirements. - Understand exactly what spawn_subagent does in your agent environment: will sub-agents push commits, open PRs, or run arbitrary code? Ask for explicit limits and review/approval steps. - If you try it, use a least-privilege token (PAT) scoped only to the repositories needed (avoid using a full user token), and prefer a machine/service account rather than your personal account. - Require manual approval or merge protections in GitHub so PRs opened by the skill cannot be merged automatically without human review. - Ask the publisher for source code or provenance (why is there no homepage/source), and request that the skill metadata be corrected to list required binaries and credentials. - If you cannot verify these points, avoid granting it GitHub credentials or enable model-driven autonomous actions until you have tighter controls.

Type: OpenClaw Skill Name: tester Version: 1.0.0 The skill is classified as suspicious due to a significant prompt injection vulnerability pattern identified in `SKILL.md`. The `spawn_subagent` instruction demonstrates passing unsanitized, user-controlled data (GitHub issue `title` and `description`) directly into a sub-agent's `task` string. This allows an attacker to craft malicious issue content to potentially manipulate the sub-agent's behavior. Additionally, the instruction to `export GITHUB_TOKEN` highlights a sensitive secret management practice, which, while necessary for functionality, poses a risk if not handled securely by the agent or user.