Overlap Check
PassAudited by ClawScan on May 1, 2026.
Overview
This instruction-only skill appears benign: it uses the GitHub CLI to check for duplicate issues or PRs before posting, with bounded searches and guidance to ask the user when duplicates are found.
This skill is reasonable for avoiding duplicate GitHub issues or PRs. Before installing, make sure you are comfortable with the agent running `gh` searches/views in the target repository and using the currently authenticated GitHub CLI account for those read-only checks.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The agent may query GitHub for existing issues or PRs before posting on your behalf.
The skill instructs the agent to run GitHub CLI searches automatically before creating issues or PRs; the commands are disclosed, read-oriented, limited to the target repo, and aligned with the stated purpose.
gh search issues --repo OWNER/REPO "KEYWORDS" --limit 5 --json number,title,state,comments gh search prs --repo OWNER/REPO "KEYWORDS" --limit 5 --json number,title,state,comments
Confirm the target repository is correct and review any duplicate matches before deciding whether to create a new thread or comment on an existing one.
If your GitHub CLI is authenticated, the skill's checks may use your GitHub account permissions to read repository issue or PR details.
These GitHub CLI commands can use the current `gh` login and therefore may read issue or PR information available to that account, including private repository data if the user has access.
Open the thread: `gh issue view NUMBER --repo OWNER/REPO` or `gh pr view NUMBER`
Use the intended GitHub account and repository context when invoking this skill, especially for private repositories.