New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Tag Duplicate PRs Issues

by openclaw in openclaw/openclaw

Use gitcrawl to search duplicate OpenClaw PRs/issues, group related work in prtags, and sync duplicate state to GitHub.

MITAuto-check passedResearch & Science

Install Tag Duplicate PRs Issues

skills CLI
$ npx skills add openclaw/openclaw --skill tag-duplicate-prs-issues -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install openclaw/openclaw tag-duplicate-prs-issues --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/openclaw/openclaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/tag-duplicate-prs-issues .claude/skills/tag-duplicate-prs-issues && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
tag-duplicate-prs-issues
GitHub stars
392k
Token cost
~4k tokens
SKILL.md length
1,767 words
Files
2
Skills in repo
96
Repo updated
First seen
Licence
MIT

At a glance

Use gitcrawl to search duplicate OpenClaw PRs/issues, group related work in prtags, and sync duplicate state to GitHub.

  • Works in 8 steps: Read The Target → Search Broadly With Gitcrawl → Use Live GitHub Search For Gaps → …
  • Tasks that involve Literature review
  • SKILL.md covers Required Setup, Missing-Setup Rule, Read-Path Default and Goal, plus 15 more sections
  • Calls gh and go

What it does

Tag Duplicate PRs Issues is an agent skill from openclaw/openclaw. Use gitcrawl to search duplicate OpenClaw PRs/issues, group related work in prtags, and sync duplicate state to GitHub.

Its SKILL.md is about 4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Research & Science, covering Literature review. It works with GitHub. The repository describes itself as: The AI that really does things. Any OS. Any Platform. The lobster way. 🦞. The licence is MIT.

When your agent uses it

  • Tasks that involve Literature review

Example prompts

  • “/tag-duplicate-prs-issues”

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. Read The Target
  2. Search Broadly With Gitcrawl
  3. Use Live GitHub Search For Gaps
  4. Decide The Outcome
  5. Reuse Or Create One prtags Group
  6. Ensure The Annotation Fields Exist
  7. Save The Maintainer Judgment In prtags
  8. Let prtags Sync The Group Comment

What it can do on your machine

Read from SKILL.md and the folder at commit f8e594e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh
    • go

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Tag Duplicate PRs Issues loads about 4k tokens when it runs. Until then it costs about 36 tokens; SKILL.md has 1,767 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~36
When it runs · the whole SKILL.md, loaded when a task matches
~4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from openclaw/openclaw at commit f8e594e, republished under its MIT licence (© openclaw). 1,767 words, ~4,000 tokens.

Download SKILL.mdSave it as .claude/skills/tag-duplicate-prs-issues/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
tag-duplicate-prs-issues
description
Use gitcrawl to search duplicate OpenClaw PRs/issues, group related work in prtags, and sync duplicate state to GitHub.

Tag Duplicate PRs and Issues

Use this skill when a maintainer needs to decide whether a pull request or issue is a duplicate of existing work.

This skill is for maintainer triage and grouping. It is not for reviewing the implementation quality of a PR.

Required Setup

Do not write duplicate groups or annotations until this setup is complete. Read-only discovery can still proceed with gitcrawl and live gh.

Companion Skills

Use $gitcrawl first for local candidate discovery. Use the prtags skill from the prtags repo at skills/prtags/SKILL.md when it is available.

Install the CLIs

Install prtags from the pinned release below. Do not rely on an old local build unless the maintainer explicitly wants to test unreleased behavior.

prtags CLI install path:

bash
GOBIN="$HOME/.local/bin" go install github.com/dutifuldev/prtags/cmd/prtags@v0.1.2

prtags lives outside the OpenClaw organization, so this install stays pinned to a reviewed version that the Go module proxy resolves and the public checksum database verifies. GOBIN keeps the installed executable in the same user-local directory as the previous installer, so an existing $HOME/.local/bin PATH continues to resolve the newly installed version. Do not install it by piping a remote script into a shell, and do not point the install at a branch: either one executes whatever that third party serves at run time, with the maintainer's own privileges. Moving to a newer prtags release is a reviewed change to this file, not a mid-task step.

Authenticate prtags

prtags should be logged in with the maintainer's own GitHub account through OAuth device flow. Do not use a shared maintainer token for interactive triage.

bash
prtags auth login
prtags auth status

The expected outcome is that prtags stores the logged-in maintainer identity locally and uses that account for authenticated writes.

Missing-Setup Rule

Do not require an up-front preflight before starting the workflow. Proceed with the normal steps until you actually need a tool or account state.

As soon as you discover that prtags is missing or not logged in at the write step, stop immediately. Do not continue in a partial write mode after that point.

If prtags is missing, ask the user to run the pinned install command from Install the CLIs. Keep that section as the single source of the installed version; do not improvise another install path.

If prtags auth status shows that the user is not logged in, ask the user to run:

bash
prtags auth login

Resume only after the missing tool or login state has been fixed.

Read-Path Default

For candidate discovery in this workflow, use gitcrawl first. Treat it as the local history and clustering layer for related issues, duplicate attempts, and closed threads.

Use live gh or gh api for the target thread and for any candidate before making an actionable judgment. Use live GitHub when gitcrawl is missing or stale for a concrete reason, such as:

  • the target or candidate is not present yet
  • the local data is clearly stale or incomplete for the decision you need to make
  • gitcrawl errors, times out, or lacks the needed neighbor/search data

When you fall back to live GitHub search, note that you did so and why.

If a later prtags target-level write fails because its own mirror has not caught up, stop and report that the curation backend is missing the target object instead of forcing a fallback write.

Goal

For each target PR or issue:

  1. gather duplicate evidence
  2. decide whether it is a real duplicate
  3. create or reuse one prtags group for that duplicate cluster
  4. save the maintainer judgment in prtags
  5. rely on normal prtags group writes to drive GitHub comment sync when that integration is configured

Tool Roles

Use the tools with these boundaries:

  • gitcrawl is candidate generation and historical context
    • use it first for local title/body search, neighbors, clusters, and closed-thread discovery
    • treat every candidate as a lead until live GitHub confirms it
  • gh is live GitHub truth
    • use it for target state, body, comments, reviews, files, linked issues, and current open/closed/merged status
    • use gh search only when gitcrawl is stale, missing data, or cannot express the needed query
  • prtags is the maintainer curation layer
    • use it to create or reuse one duplicate group
    • use it to save the duplicate status, confidence, rationale, and group summary
    • use it as the source of truth for the GitHub-facing group comment

Working Rules

  • Do not call something a duplicate only because the titles are similar.
  • Do not call something a duplicate only because the same files changed.
  • A duplicate cluster should be based on the same user-facing problem, the same intent, and substantially overlapping implementation or investigation context.

One-Group Rule

Treat duplicate groups as exclusive. A PR or issue should belong to at most one duplicate group at a time.

That means:

  • before creating a new group, search for an existing group that already represents the same duplicate story
  • if the target already appears to belong to a different duplicate group, stop and resolve that conflict first
  • do not create a second group for the same target just because the wording is slightly different
  • if two plausible existing groups overlap and you cannot safely merge the judgment, stop and ask the maintainer

This rule matters more than speed. The skill should keep one coherent duplicate cluster per problem, not many near-duplicate clusters.

What A Good Duplicate Group Represents

A duplicate group should describe the underlying problem and the intended fix direction. Do not group items only because they share a keyword.

Good group shape:

  • same user-facing bug or same maintainer-facing task
  • same subsystem or code surface
  • same intended change direction
  • same likely duplicate-resolution path

Bad group shape:

  • “all PRs that touch Slack”
  • “all issues mentioning retry”
  • “all auth-related items”

The group title should name the real problem. The group description should summarize the intent and the code surface.

Examples:

  • gateway: startup regression from channel status bootstrap
  • whatsapp: QR preflight timeout handling
  • release: cross-OS validation handoff gaps

Evidence Checklist

Before declaring a duplicate, gather evidence from at least two categories. gitcrawl neighbors, search hits, and cluster membership count as candidate generation, not as enough proof by themselves.

For PRs:

  • same or nearly same problem statement
  • same changed files or overlapping file ranges
  • same fix direction
  • same subsystem and failure mode
  • same linked issue or same user-visible symptom

For issues:

  • same user-visible problem
  • same reproduction story or same failure mode
  • same likely fix area
  • same PRs already linked or discussed
  • same maintainers already steering toward the same duplicate grouping

If you only have wording similarity, that is not enough.

Show full SKILL.md (696 more words)Show less

Step 1: Read The Target

Start by reading the target itself. Use live GitHub for current target state.

For a PR:

bash
gh pr view <number> --json number,title,state,mergedAt,body,closingIssuesReferences,files,comments,reviews,statusCheckRollup

For an issue:

bash
gh issue view <number> --json number,title,state,body,comments,closedAt

Record:

  • target type and number
  • title
  • problem statement
  • proposed intent
  • subsystem
  • whether it is open, closed, or merged
  • whether there is already a likely duplicate thread mentioned by humans

Step 2: Search Broadly With Gitcrawl

Use gitcrawl first because it is the local OpenClaw history and clustering source. Do not switch to broad live GitHub search unless gitcrawl is missing data, stale, or failing.

Start with the target and nearby threads:

bash
gitcrawl threads openclaw/openclaw --numbers <issue-or-pr-number> --include-closed --json
gitcrawl neighbors openclaw/openclaw --number <issue-or-pr-number> --limit 20 --json

Then search key phrases and subsystem terms:

bash
gitcrawl search openclaw/openclaw --query "<key phrase from title or body>" --mode hybrid --limit 20 --json
gitcrawl search openclaw/openclaw --query "<subsystem or error phrase>" --mode hybrid --limit 20 --json

Inspect likely clusters:

bash
gitcrawl cluster-detail openclaw/openclaw --id <cluster-id> --member-limit 20 --body-chars 280 --json

For PRs, verify likely code overlap with live file data:

bash
gh pr view <candidate-pr> --json number,title,state,mergedAt,files,body,comments,reviews

For issues, verify likely duplicate issue state and comments live:

bash
gh issue view <candidate-issue> --json number,title,state,body,comments,closedAt

Step 3: Use Live GitHub Search For Gaps

Use targeted live GitHub search after gitcrawl when:

  • the target is too new for the local store
  • comments or reviews matter and the local store lacks them
  • the exact phrase did not appear in local results but the issue/PR is current enough that GitHub should know it
bash
gh search prs --repo openclaw/openclaw --match title,body --limit 50 -- "<key phrase>"
gh search issues --repo openclaw/openclaw --match title,body --limit 50 -- "<key phrase>"
gh search issues --repo openclaw/openclaw --match comments --limit 50 -- "<error or maintainer phrase>"

Step 4: Decide The Outcome

Choose one of these outcomes:

  • not_duplicate
  • duplicate_needs_judgment
  • duplicate_confirmed

Use duplicate_confirmed only when the evidence is strong enough that the maintainer could safely close or retag the duplicate item.

Use duplicate_needs_judgment when:

  • the problem looks the same but the implementation goal differs
  • the code overlap is weak
  • the issue wording is ambiguous
  • there may be two valid duplicate group interpretations
  • the target appears to intersect two existing duplicate groups

Step 5: Reuse Or Create One prtags Group

Before creating a group, search prtags for an existing one.

Start with text search over groups:

bash
prtags search text -R openclaw/openclaw "<problem phrase>" --types group --limit 10
prtags search similar -R openclaw/openclaw "<problem summary>" --types group --limit 10
prtags group list -R openclaw/openclaw

Inspect likely groups:

bash
prtags group get <group-id>
prtags group get <group-id> --include-metadata

Reuse an existing group when:

  • it represents the same problem
  • it already contains clearly related members
  • adding the target would keep the group coherent

Do not widen an existing group just because gitcrawl placed several PRs or issues near each other. Confirm that the actual implementation path and maintainer intent still match before adding the new member.

Create a new group only when no existing group clearly fits.

Create the group with a problem-based title and an intent-based description:

bash
prtags group create -R openclaw/openclaw \
  --kind mixed \
  --title "<problem-centered title>" \
  --description "<same intent, subsystem, and duplicate-resolution path>" \
  --status open

Then attach the target and any known duplicate members:

bash
prtags group add-pr <group-id> <pr-number>
prtags group add-issue <group-id> <issue-number>

If a target appears to already belong to another duplicate group and you cannot safely reuse that group, stop. Do not create a second group.

Step 6: Ensure The Annotation Fields Exist

Use field ensure so the skill is idempotent.

Recommended target-level fields:

bash
prtags field ensure -R openclaw/openclaw --name duplicate_status --scope pull_request --type enum --enum-values not_duplicate,candidate,confirmed --filterable
prtags field ensure -R openclaw/openclaw --name duplicate_status --scope issue --type enum --enum-values not_duplicate,candidate,confirmed --filterable
prtags field ensure -R openclaw/openclaw --name duplicate_confidence --scope pull_request --type enum --enum-values low,medium,high --filterable
prtags field ensure -R openclaw/openclaw --name duplicate_confidence --scope issue --type enum --enum-values low,medium,high --filterable
prtags field ensure -R openclaw/openclaw --name duplicate_rationale --scope pull_request --type text --searchable
prtags field ensure -R openclaw/openclaw --name duplicate_rationale --scope issue --type text --searchable

Recommended group-level fields:

bash
prtags field ensure -R openclaw/openclaw --name duplicate_confidence --scope group --type enum --enum-values low,medium,high --filterable
prtags field ensure -R openclaw/openclaw --name duplicate_rationale --scope group --type text --searchable
prtags field ensure -R openclaw/openclaw --name cluster_summary --scope group --type text --searchable

Step 7: Save The Maintainer Judgment In prtags

For a PR:

bash
prtags annotation pr set -R openclaw/openclaw <pr-number> \
  duplicate_status=confirmed \
  duplicate_confidence=high \
  duplicate_rationale="<same problem, same fix direction, overlapping files and comments>"

For an issue:

bash
prtags annotation issue set -R openclaw/openclaw <issue-number> \
  duplicate_status=confirmed \
  duplicate_confidence=high \
  duplicate_rationale="<same user-visible problem and same intended fix path>"

For the group:

bash
prtags annotation group set <group-id> \
  duplicate_confidence=high \
  cluster_summary="<one-sentence problem summary>" \
  duplicate_rationale="<why these items belong in one duplicate cluster>"

When the evidence is incomplete, set duplicate_status=candidate and lower the confidence.

If a per-PR or per-issue annotation write fails because prtags cannot resolve the target, do not force a fallback write path. Keep the group state you were able to write, report that the curation backend is still missing the target object, and defer the target-level annotation until prtags catches up.

Step 8: Let prtags Sync The Group Comment

Do not tell the agent to create a GitHub comment directly. prtags owns the outbound GitHub comment as a derived projection of group state.

In the normal case, do not manually trigger comment sync. When comment sync is configured, group writes already enqueue the derived comment projection automatically.

Use manual sync only as a repair or retry path:

bash
prtags group sync-comments <group-id>

If the maintainer needs to see which groups still need attention, use:

bash
prtags group list-comment-sync-targets -R openclaw/openclaw

The skill should treat the GitHub comment as a consequence of correct prtags group state. It should not treat manual comment authoring as part of the normal duplicate workflow. It should also not treat sync-comments as a required step for every duplicate decision.

Output Format

Return a short maintainer report with these sections:

text
Decision: duplicate_confirmed | duplicate_needs_judgment | not_duplicate
Target: PR #<n> | Issue #<n>
Confidence: high | medium | low

Evidence:
- ...
- ...
- ...

prtags actions:
- reused group <group-id> | created group <group-id>
- added members: ...
- annotations written: ...
- comment sync: automatic if configured | manual repair triggered for <group-id>

Stop Conditions

Stop and escalate instead of forcing a duplicate decision when:

  • the target appears to belong to two different duplicate groups
  • the duplicate grouping is unclear
  • the wording matches but the implementation goals differ
  • two PRs touch the same files for different reasons
  • two issues describe similar symptoms but likely different root causes

The maintainer should get one clean duplicate judgment or an explicit “needs judgment” result. Do not blur the line.

© openclaw, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .agents/skills/tag-duplicate-prs-issues of openclaw/openclaw.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit f8e594e

Compare with similar skills

Tag Duplicate PRs Issues next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Tag Duplicate PRs Issues compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Tag Duplicate PRs Issues this skillopenclaw/openclaw392k—~4kAutomated safety check: PassMIT
Paper NavigatorAI4Scientist/nano-scientist128—~7.7kAutomated safety check: NotesNone
Mechanical Engineering Researchccplugins/awesome-claude-code-plugins970—~2.9kAutomated safety check: PassApache-2.0
GitHub Deep Researchbytedance/deer-flow84k4 repos~1.3kAutomated safety check: PassMIT
Nature Paper CardYuan1z0825/nature-skills47k2 repos~2.1kAutomated safety check: PassApache-2.0
Last30daysmvanhorn/last30days-skill64k—~7.9kAutomated safety check: NotesMIT

Similar skills

  • Paper Navigator

    AI4Scientist/nano-scientist

    Find and read academic papers: disambiguate queries, discover papers (search, citation traversal, recommendations, arXiv monitoring, trending, GitHub search), evaluate (TLDR, citations, code, SOTA)…

    128 GitHub stars~7.7k tokensUpdated 4 mo ago
    Research & ScienceAuto-check: notes

  • Mechanical Engineering Research

    ccplugins/awesome-claude-code-plugins

    Research, write, code, analyze, present, and develop proposals for thermal-fluid mechanical engineering work with source-aware rigor.

    970 GitHub stars~2.9k tokensUpdated 1 mo ago
    Research & ScienceAuto-check passed

  • GitHub Deep Research

    bytedance/deer-flow

    Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.

    84k GitHub starsUsed in 4 repos~1.3k tokens
    Research & ScienceAuto-check passed

  • Nature Paper Card

    Yuan1z0825/nature-skills

    Builds a structured deep-reading card for one scientific paper, covering methods, how experiments support claims, limitations and research ideas, with a script to prepare the source.

    47k GitHub starsUsed in 2 repos~2.1k tokens
    Research & ScienceAuto-check passed

  • Last30days

    mvanhorn/last30days-skill

    Research what people actually say about any topic in the last 30 days.

    64k GitHub stars~7.9k tokensUpdated today
    Research & ScienceAuto-check: notes

  • Systematic Review Screener

    Imbad0202/academic-research-skills

    Screens records for systematic, scoping and rapid reviews against fixed eligibility rules, using two blinded AI reviewers and a third adjudicator, with traceable PRISMA counts.

    51k GitHub stars~8.4k tokensUpdated today
    Research & ScienceAuto-check passed

More from openclaw/openclaw

All 96 skills in this repo

  • Model Usage

    openclaw/openclaw

    Summarize CodexBar local cost logs by model for Codex or Claude, including current or full breakdowns.

    392k GitHub starsUsed in 1 repo~637 tokens
    Auto-check passed

  • Openclaw Live Updater

    openclaw/openclaw

    Maintain the canonical live OpenClaw main checkout, macOS LaunchAgent-managed Gateway, local macOS app, exact-head main CI, and recurring full release validation.

    392k GitHub stars~3.7k tokensUpdated today
    Auto-check passed

  • Feishu Doc

    openclaw/openclaw

    Feishu document read/write workflows. An agent skill from openclaw/openclaw.

    392k GitHub stars~516 tokensUpdated today
    Auto-check passed

  • Tmux

    openclaw/openclaw

    Control tmux sessions/panes for interactive CLIs: list, capture output, send keys, paste text, monitor prompts.

    392k GitHub starsUsed in 1 repo~640 tokens
    Auto-check passed

  • Openclaw PR Maintainer

    openclaw/openclaw

    Review, triage, repair, or land OpenClaw issues and pull requests with current-source evidence and the native maintainer workflow.

    392k GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • Browser Automation

    openclaw/openclaw

    A skill your agent uses when controlling web pages with the OpenClaw browser tool, especially multi-step flows, login checks, tab management, or recovery from stale refs/timeouts.

    392k GitHub stars~2.9k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Tag Duplicate PRs Issues

What does Tag Duplicate PRs Issues do?

Use gitcrawl to search duplicate OpenClaw PRs/issues, group related work in prtags, and sync duplicate state to GitHub. Tag Duplicate PRs Issues is an agent skill from openclaw/openclaw. Use gitcrawl to search duplicate OpenClaw PRs/issues, group related work in prtags, and sync duplicate state to GitHub.

When should I use Tag Duplicate PRs Issues?

Tag Duplicate PRs Issues fits situations like: tasks that involve Literature review.

How do I install Tag Duplicate PRs Issues in Claude Code?

Run `npx skills add openclaw/openclaw --skill tag-duplicate-prs-issues -a claude-code`. Or copy the skill folder (.agents/skills/tag-duplicate-prs-issues in openclaw/openclaw) into .claude/skills/tag-duplicate-prs-issues in your project. Claude Code loads it when a task matches its description.

How do I install Tag Duplicate PRs Issues in Codex?

Run `npx skills add openclaw/openclaw --skill tag-duplicate-prs-issues -a codex`. Or copy the skill folder (.agents/skills/tag-duplicate-prs-issues in openclaw/openclaw) into .agents/skills/tag-duplicate-prs-issues in your project. Codex loads it when a task matches its description.

Can I use Tag Duplicate PRs Issues in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add openclaw/openclaw --skill tag-duplicate-prs-issues -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tag-duplicate-prs-issues, .gemini/skills/tag-duplicate-prs-issues, .github/skills/tag-duplicate-prs-issues and .opencode/skills/tag-duplicate-prs-issues in your project.

What does Tag Duplicate PRs Issues need to run?

Going by SKILL.md and its folder, Tag Duplicate PRs Issues needs the command-line tools its instructions call (gh and go).

Does Tag Duplicate PRs Issues access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Tag Duplicate PRs Issues safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Tag Duplicate PRs Issues use?

Tag Duplicate PRs Issues is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Tag Duplicate PRs Issues use?

About 4k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Tag Duplicate PRs Issues?

Skills that share tags, products or a category with Tag Duplicate PRs Issues: Paper Navigator (AI4Scientist/nano-scientist, 128 stars), Mechanical Engineering Research (ccplugins/awesome-claude-code-plugins, 970 stars), GitHub Deep Research (bytedance/deer-flow, 84k stars) and Nature Paper Card (Yuan1z0825/nature-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Tag Duplicate PRs Issues?

openclaw (a GitHub organization) maintains it in openclaw/openclaw, which has 391,504 GitHub stars. The repository holds 96 skills in this directory. The repository was last updated on October 9, 2026.

Source: openclaw/openclaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.