Agent skill

Qv PR Mine

by tetherto in tetherto/qvac

Show the current user's open PRs across every pod registered under .github/teams/, grouped by merge readiness, with copy-paste Slack ping messages routed to the owning pod's team.

Apache-2.0Auto-check passedAI & LLM Engineering

Install Qv PR Mine

skills CLI
$ npx skills add tetherto/qvac --skill qv-pr-mine -a claude-code

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

GitHub CLI
$ gh skill install tetherto/qvac qv-pr-mine --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/tetherto/qvac.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/qv-pr-mine .claude/skills/qv-pr-mine && 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
qv-pr-mine
GitHub stars
683
Token cost
~1.2k tokens
SKILL.md length
645 words
Files
2
Skills in repo
50
Repo updated
First seen
Licence
Apache-2.0

At a glance

Show the current user's open PRs across every pod registered under .github/teams/, grouped by merge readiness, with copy-paste Slack ping messages routed to the owning pod's team.

  • Works in 5 steps: Run the script with --mode my. The… → Slack-handle validation gate. If the… → Present the grouped output to the user… → …
  • The user asks about their own PRs
  • SKILL.md covers When to use this skill, Prerequisites, Usage and Workflow, plus 3 more sections
  • Calls gh and node

What it does

Qv PR Mine is an agent skill from tetherto/qvac. Show the current user's open PRs across every pod registered under .github/teams/, grouped by merge readiness, with copy-paste Slack ping messages routed to the owning pod's team. Use when the user asks about their own PRs, merge readiness, who to ping, or invokes /qv-pr-mine.

Its SKILL.md is about 1.2k 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 AI & LLM Engineering. It works with Slack and GitHub. The repository describes itself as: Open-source local AI SDK - run AI on-device with no cloud, no API keys. Supports GGUF, RAG, image, music, and video generation, speech-to-text, P2P inference, and more… The licence is Apache-2.0.

When your agent uses it

  • The user asks about their own PRs
  • Merge readiness
  • Invokes /qv-pr-mine

Example prompts

  • “/qv-pr-mine”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Run the script with --mode my. The script uses .agents/skills/_lib/pr-skills/pr-activity.mjs for shared PR state collection and…
  2. Slack-handle validation gate. If the script's stderr contains SLACK_VALIDATION_REQUIRED , run the validation flow before presenting any…
  3. Present the grouped output to the user (stderr contains progress info — ignore it).
  4. For PRs in "needs re-review" or "awaiting review", present the "Slack messages (copy-paste ready)" sections in copy-friendly fenced code…
  5. Offer: "Want me to review any of these before requesting reviews? Provide the PR URL and I'll run /qv-pr-review."

What it can do on your machine

Read from SKILL.md and the folder at commit f874b3a. 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
    • node

    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

Qv PR Mine loads about 1.2k tokens when it runs. Until then it costs about 72 tokens; SKILL.md has 645 words of instructions outside code blocks.

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

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 tetherto/qvac at commit f874b3a, republished under its Apache-2.0 licence (© tetherto). 645 words, ~1,202 tokens.

Download SKILL.mdSave it as .claude/skills/qv-pr-mine/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
qv-pr-mine
description
Show the current user's open PRs across every pod registered under .github/teams/, grouped by merge readiness, with copy-paste Slack ping messages routed to the owning pod's team. Use when the user asks about their own PRs, merge readiness, who to ping, or invokes /qv-pr-mine.
disable-model-invocation
true

My PRs

Cross-pod skill. Surfaces the current user's open PRs in the configured repo and emits copy-paste Slack ping messages. The owning pod for each PR is auto-detected from the touched files against every .github/teams/<pod>.json's ownedPaths, so per-PR ping logic uses the right team automatically — no --pod argument needed.

When to use this skill

Use when:

  • User asks about their own PRs, merge readiness, or who to ping
  • User wants Slack messages to request reviews
  • User invokes /qv-pr-mine

Prerequisites

  • gh CLI installed and authenticated (gh auth status)
  • User must have access to the configured GitHub repository
  • At least one pod metadata file at .github/teams/<pod>.json
  • Per-user Slack handle map at ~/.config/qvac-pr-skills/slack.json (auto-bootstrapped on first run; see workflow step 2)

Usage

bash
node .agents/skills/_lib/pr-skills/pr-status.mjs --mode my

--pod is intentionally omitted: --mode my discovers every pod and routes each PR to its owning pod automatically.

Workflow

  1. Run the script with --mode my. The script uses .agents/skills/_lib/pr-skills/pr-activity.mjs for shared PR state collection and ~/.config/qvac-pr-skills/config.json for repo/stale settings when available.

  2. Slack-handle validation gate. If the script's stderr contains SLACK_VALIDATION_REQUIRED <N>, run the validation flow before presenting any output to the user:

    a. Read ~/.config/qvac-pr-skills/slack.json. b. For each login in pendingReview, present the proposed handle to the user via AskQuestion so they can confirm or correct. Use one question per pending login. Show the GitHub login and the proposed handle as the option label, e.g. <github-login> -> <proposed-handle>. Provide options: "keep proposed", "edit (then prompt for new handle)". Do NOT inline any names from the proposed map into commentary, examples, or follow-up text. c. For any logins the user chose to edit, ask one follow-up question per login for the corrected handle as free text. d. Apply corrections to state.map, set state.pendingReview = [], save the file (atomic write). e. Re-run the script. The marker should no longer fire.

  3. Present the grouped output to the user (stderr contains progress info — ignore it).

  4. For PRs in "needs re-review" or "awaiting review", present the "Slack messages (copy-paste ready)" sections in copy-friendly fenced code blocks so the user can paste directly into Slack.

  5. Offer: "Want me to review any of these before requesting reviews? Provide the PR URL and I'll run /qv-pr-review."

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

Output groups

  1. Ready to merge — has both team member and team lead approval (per the PR's owning pod's team)
  2. Needs re-review — a reviewer's approval was dismissed (new commits); shows who to re-request
  3. Awaiting review — missing approvals; shows who to ping
  4. No pod matched — touched files don't match any .github/teams/<pod>.json ownedPaths; ping logic is skipped (rare; usually means the user's PR is outside the pod system)

Each non-empty group of PRs needing pings includes ready-to-copy Slack messages with @-mentions and PR links sourced from ~/.config/qvac-pr-skills/slack.json (falling back to @<github-login> when a handle is not yet mapped).

Per-PR pod resolution

For each of the user's PRs, the script:

  1. Lists the touched files via the GitHub API.
  2. Walks the discovered pods (one per .github/teams/*.json) and picks the first one whose ownedPaths contains any touched path as a prefix. The walk order is readdir order of .github/teams/.
  3. Uses that pod's leads, members, and Slack handles for the PR's "needs approval" / "ping" semantics.

If a PR touches files spanning multiple pods, the first match wins. This is fine for the typical case where a PR is owned by a single team. If two pods commonly share files, rename one of them in .github/teams/ so the desired pod sorts first.

Maintaining the Slack map

The script auto-fills new entries from gh api users/<login> when:

  • the file does not yet exist (first run on this machine), OR
  • a new login appears in any .github/teams/<pod>.json that is not yet in the map.

Newly seeded logins land in pendingReview and trigger the validation gate above on the next --mode my run. Edit ~/.config/qvac-pr-skills/slack.json directly at any time to update handles; the file is per-user and never committed.

© tetherto, Apache-2.0. 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/qv-pr-mine of tetherto/qvac.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit f874b3a

Compare with similar skills

Qv PR Mine 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.

Qv PR Mine compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Qv PR Mine this skilltetherto/qvac683—~1.2kAutomated safety check: PassApache-2.0
Token Meter Communicationsplunk/token-meter114—~1.1kAutomated safety check: PassMIT
Async Communication Etiquetteaiming-lab/MetaClaw3.5k—~224Automated safety check: PassMIT
Token Meter Intakesplunk/token-meter114—~1.4kAutomated safety check: WarnMIT
Building LoopsPostHog/posthog40k—~3.6kAutomated safety check: PassCustom licence
Report Indicator Changesowid/etl159—~2.6kAutomated safety check: PassMIT

Similar skills

  • Token Meter Communication

    splunk/token-meter

    A skill your agent uses when a Token Meter task will produce Slack, GitHub, release, contributor, or user-facing status communication.

    114 GitHub stars~1.1k tokensUpdated 2 days ago
    AI & LLM EngineeringAuto-check passed
  • A skill your agent uses when writing messages in async channels (Slack, GitHub issues, email threads) where the reader may not have context and cannot ask follow-up questions immediately.

    3.5k GitHub stars~224 tokensUpdated 4 mo ago
    AI & LLM EngineeringAuto-check passed
  • Token Meter Intake

    splunk/token-meter

    A skill your agent uses when a Token Meter Slack or GitHub request needs contextual intake, clarification, triage, acknowledgment, or closure.

    114 GitHub stars~1.4k tokensUpdated 2 days ago
    AI & LLM EngineeringAuto-check: warnings
  • Building Loops

    PostHog/posthog

    Official

    Build a Loop for PostHog Desktop: a workflow that creates an AI task each time its trigger fires, optionally followed by a Slack or email notification with the task's result.

    40k GitHub stars~3.6k tokensUpdated today
    Productivity & AutomationAuto-check passed
  • Draft a short update message to a topic-owner reviewer after landing substantial dataset or chart changes on staging.

    159 GitHub stars~2.6k tokensUpdated today
    Data & AnalyticsAuto-check passed
  • Composio

    ComposioHQ/composio

    Route and complete Composio work across Composio For You and Composio Platform.

    30k GitHub starsUsed in 1 repo~1.7k tokens
    Productivity & AutomationAuto-check passed

More from tetherto/qvac

All 50 skills in this repo
  • Creates a Solutions page in the QVAC documentation website from a real use case, generalizing the case into reusable guidance and registering the page in the site navigation.

    683 GitHub stars~2.8k tokensUpdated today
    Auto-check passed
  • Qv Docs Update

    tetherto/qvac

    Updates the docs website after a change to the SDK or CLI. An agent skill from tetherto/qvac.

    683 GitHub stars~11k tokensUpdated today
    Auto-check passed
  • Qv Agent Stack Sync

    tetherto/qvac

    Plan and prepare the QVAC agent-stack release cascade across @qvac/inference, @qvac/sdk, @qvac/cli, @qvac/ai-sdk-provider, @qvac/opencode-plugin, and @qvac/openclaw-plugin.

    683 GitHub stars~2k tokensUpdated today
    Auto-check passed
  • Run the deterministic code-quality audit, turn related findings into contextual remediation groups, prepare approval-gated Asana proposals, reconcile recurring runs, or configure twice-monthly…

    683 GitHub stars~1.6k tokensUpdated today
    Auto-check passed
  • Review C++ changes for string parameter and call-site efficiency conventions (std::stringview, std::string&&, const std::string&, const char, and TransparentStringMap lookup).

    683 GitHub stars~702 tokensUpdated today
    Auto-check passed
  • Qv Addon Changelog

    tetherto/qvac

    Generate changelog entries for a target add-on package. An agent skill from tetherto/qvac.

    683 GitHub stars~1.7k tokensUpdated today
    Auto-check passed

Works with

Questions about Qv PR Mine

What does Qv PR Mine do?

Show the current user's open PRs across every pod registered under .github/teams/, grouped by merge readiness, with copy-paste Slack ping messages routed to the owning pod's team. Qv PR Mine is an agent skill from tetherto/qvac.github/teams/, grouped by merge readiness, with copy-paste Slack ping messages routed to the owning pod's team.

When should I use Qv PR Mine?

Qv PR Mine fits situations like: the user asks about their own PRs; merge readiness; invokes /qv-pr-mine.

How do I install Qv PR Mine in Claude Code?

Run `npx skills add tetherto/qvac --skill qv-pr-mine -a claude-code`. Or copy the skill folder (.agents/skills/qv-pr-mine in tetherto/qvac) into .claude/skills/qv-pr-mine in your project. Claude Code loads it when a task matches its description.

How do I install Qv PR Mine in Codex?

Run `npx skills add tetherto/qvac --skill qv-pr-mine -a codex`. Or copy the skill folder (.agents/skills/qv-pr-mine in tetherto/qvac) into .agents/skills/qv-pr-mine in your project. Codex loads it when a task matches its description.

Can I use Qv PR Mine 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 tetherto/qvac --skill qv-pr-mine -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/qv-pr-mine, .gemini/skills/qv-pr-mine, .github/skills/qv-pr-mine and .opencode/skills/qv-pr-mine in your project.

What does Qv PR Mine need to run?

Going by SKILL.md and its folder, Qv PR Mine needs the command-line tools its instructions call (gh and node).

Does Qv PR Mine 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 Qv PR Mine 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 Qv PR Mine use?

Qv PR Mine is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Qv PR Mine use?

About 1.2k tokens (SKILL.md is roughly 4.8k 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 Qv PR Mine?

Skills that share tags, products or a category with Qv PR Mine: Token Meter Communication (splunk/token-meter, 114 stars), Async Communication Etiquette (aiming-lab/MetaClaw, 3.5k stars), Token Meter Intake (splunk/token-meter, 114 stars) and Building Loops (PostHog/posthog, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Qv PR Mine?

tetherto (a GitHub organization) maintains it in tetherto/qvac, which has 683 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on October 9, 2026.

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