agentsclimarketplace

Github label scout

Skill baronguyen001/ai-automation-skills/skills/github-label-scout

8 production-tested Claude skills: automation, Gemini cost/structured output, OSS bounty scouting, ML validation.

Install
npx -y skills add baronguyen001/ai-automation-skills --skill github-label-scout

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Scan a public GitHub repo for open issues carrying a given label and drop the ones already taken - skips pull requests returned by the issues endpoint and any issue with assignees - using the public REST API with no token required. Use for find github issues by label, good first issue scout, skip assigned issues, github issue triage, or open source contribution finder.

SKILL.md

2.6 KB, as published. Nobody here has run it

GitHub Label Scout

Use this skill when a user wants to find claimable open issues in a public repo by label - "good first issue", "help wanted", "bug" - without wasting time on issues someone already owns. It hits the public REST API, filters out the pull requests the issues endpoint mixes in, and skips anything with an assignee so you only see open lanes. No token is needed for low volume; set one in the env only to raise the rate limit.

When to invoke

  • User says: "find issues by label" / "good first issue scout" / "skip assigned issues" / "open-source contribution finder"
  • Code in the conversation uses: GitHub issue triage, label filtering, or contribution discovery.

When NOT to invoke

  • The user wants paid bounty boards (use [[algora-bounty-scout]] for that).
  • The user already has one specific issue and only needs implementation help.

Concrete example

User input:

Show me unassigned "good first issue" tickets in octocat/Hello-World.

Output:

# Copy assets/scout.py into your project, then:
from scout import scout_label

for row in scout_label("octocat/Hello-World", "good first issue"):
    print(f"#{row['number']} {row['title']} ({row['comments']} comments) {row['url']}")
# #142 Fix typo in README (1 comments) https://github.com/octocat/Hello-World/issues/142
# #156 Add retry to client (0 comments) https://github.com/octocat/Hello-World/issues/156

The helper reads an optional GITHUB_TOKEN from the environment purely to raise the rate limit; it works unauthenticated.

Pattern to apply

  1. Query GET /repos/{owner}/{repo}/issues?state=open&labels=<label>.
  2. Drop any item that has a pull_request key - the issues endpoint returns PRs too.
  3. Skip any issue with a non-empty assignees array (assignee-first rule: assigned = already taken).
  4. Return number, title, URL, and comment count so you can prioritize.
  5. Add GITHUB_TOKEN from env only for rate-limit headroom; never hardcode a token.

Reference: assets/scout.py.

Source

Distilled from production use across the author's automation projects. v1.0.0. See also: [[algora-bounty-scout]], [[pr-body-formatter]].

→ Build the full runnable bot with Trawlkit.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.