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

Qv Qip Triage

by tetherto in tetherto/qvac

Use during planning, implementation, PR review, or /qv-qip-triage when a change may affect public SDK API, native dependency, plugin contract, model registry contract, runtime, transport, storage…

Apache-2.0Auto-check passedAI & LLM Engineering

Install Qv Qip Triage

skills CLI
$ npx skills add tetherto/qvac --skill qv-qip-triage -a claude-code

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

GitHub CLI
$ gh skill install tetherto/qvac qv-qip-triage --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-qip-triage .claude/skills/qv-qip-triage && 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-qip-triage
GitHub stars
685
Token cost
~746 tokens
SKILL.md length
291 words
Files
2 (incl. references)
Skills in repo
50
Repo updated
First seen
Licence
Apache-2.0

At a glance

Use during planning, implementation, PR review, or /qv-qip-triage when a change may affect public SDK API, native dependency, plugin contract, model registry contract, runtime, transport, storage…

  • Works in 5 steps: Read references/significance-triggers.md → Inspect the requested change, planned… → Apply the checklist with a… → …
  • Tasks that involve Pull requests
  • SKILL.md covers When to use this skill, Core stance, Workflow and Output format, plus 2 more sections
  • Calls gh

What it does

Qv Qip Triage is an agent skill from tetherto/qvac. Use during planning, implementation, PR review, or /qv-qip-triage when a change may affect public SDK API, native dependency, plugin contract, model registry contract, runtime, transport, storage, release flow, deployment, security, NFR, or technical principles.

Its SKILL.md is about 750 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/significance-triggers.md`).

It sits in AI & LLM Engineering, covering Pull requests and MLOps. 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

  • Tasks that involve Pull requests
  • Tasks that involve MLOps

Example prompts

  • “/qv-qip-triage”

Workflow steps

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

  1. Read references/significance-triggers.md
  2. Inspect the requested change, planned work, or diff
  3. Apply the checklist with a high-confidence bar only
  4. If no trigger clearly fires, say so briefly and continue normally
  5. If a trigger clearly fires

What it can do on your machine

Read from SKILL.md and the folder at commit 673ea94. 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

    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 Qip Triage loads about 746 tokens when it runs, and up to ~1.3k if it reads all its reference files. Until then it costs about 69 tokens; SKILL.md has 291 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~69
When it runs · the whole SKILL.md, loaded when a task matches
~746
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.3k

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 673ea94, republished under its Apache-2.0 licence (© tetherto). 291 words, ~746 tokens.

Download SKILL.mdSave it as .claude/skills/qv-qip-triage/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
qv-qip-triage
description
Use during planning, implementation, PR review, or /qv-qip-triage when a change may affect public SDK API, native dependency, plugin contract, model registry contract, runtime, transport, storage, release flow, deployment, security, NFR, or technical principles.

QIP Triage

Conservatively decide whether a change needs a QIP before deeper implementation or merge recommendation.

When to use this skill

Use when:

  • Planning or implementing a change that may affect technical direction
  • Reviewing a PR or diff for cross-package, contract, delivery, or principle impact
  • Another workflow asks whether a proposal is needed first
  • User invokes /qv-qip-triage

Do NOT use for:

  • Drafting the QIP itself (use qv-qip-create)
  • Reviewing an existing QIP draft (use qv-qip-review)

Core stance

  • Bias toward not interrupting the team
  • Better to miss borderline proposal candidates than to ask for a QIP on every small PR
  • This is advisory only. Never block mechanically or claim work cannot proceed

Workflow

  1. Read references/significance-triggers.md
  2. Inspect the requested change, planned work, or diff
  3. Apply the checklist with a high-confidence bar only
  4. If no trigger clearly fires, say so briefly and continue normally
  5. If a trigger clearly fires:
    • Name the trigger and why in one or two sentences
    • List the exact points that need a QIP, not the whole requested change
    • Separate implementation details that do not need a QIP on their own
    • Recommend how many QIPs are needed:
      • One QIP when the points are one decision with a shared consequence set
      • Multiple QIPs when points can be approved, rejected, or shipped independently
    • Name each proposed QIP scope in plain language
    • Ask whether to hand off to qv-qip-create
    • Do not start drafting unless the user confirms

Output format

When no trigger fires:

text
No architectural significance trigger clearly applies. Proceed with normal team review.

When a trigger fires:

text
Trigger: <trigger name>
Why: <one or two sentences>

QIP-worthy points:
- <exact point that needs proposal review>

Not QIP-worthy on its own:
- <implementation detail or ordinary work>

Proposal count:
<One QIP: <scope name> / Multiple QIPs: <scope names and why split>>

This looks technically significant because it changes <trigger>. I recommend drafting the proposal(s) above before going deeper, so the affected people can review the direction early. Want me to start a QIP draft from what we know?

Efficiency rules

  • Read the trigger reference once per session
  • Do not re-run the full checklist on every tiny follow-up edit unless scope changed materially
  • Cap shell calls at 0-2 unless inspecting a PR diff requires gh pr diff

Additional resources

© 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 (references) in .agents/skills/qv-qip-triage of tetherto/qvac.

  • SKILL.md
  • references/significance-triggers.md

Open the folder on GitHubat commit 673ea94

Compare with similar skills

Qv Qip Triage 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 Qip Triage compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Qv Qip Triage this skilltetherto/qvac685—~746Automated safety check: PassApache-2.0
Megatron-LM on SLURMNVIDIA/Megatron-LM18k—~1.8kAutomated safety check: PassApache-2.0
Oci Data Scienceoracle/accelerated-data-science125—~2.1kAutomated safety check: PassUPL-1.0
Flash AttentionLuciole-Studio/Misaka-Agent1711 repos~2.7kAutomated safety check: PassMIT
SaelensLuciole-Studio/Misaka-Agent1711 repos~3.7kAutomated safety check: PassMIT
SimpoLuciole-Studio/Misaka-Agent1711 repos~1.4kAutomated safety check: PassMIT

Similar skills

  • Megatron-LM on SLURM

    NVIDIA/Megatron-LM

    Official

    Shows how to launch distributed Megatron-LM training on a SLURM cluster: sbatch skeleton, torch.distributed.run setup, CUDA_DEVICE_MAX_CONNECTIONS rules and failure diagnosis.

    18k GitHub stars~1.8k tokensUpdated today
    AI & LLM EngineeringAuto-check passed

  • Oci Data Science

    oracle/accelerated-data-science

    Official

    OCI Data Science service patterns including Jobs, Pipelines, Model Catalog, authentication, and the ADS SDK beyond AQUA.

    125 GitHub stars~2.1k tokensUpdated 1 mo ago
    AI & LLM EngineeringAuto-check passed

  • Flash Attention

    Luciole-Studio/Misaka-Agent

    Speed up long-sequence transformer training and inference. An agent skill from Luciole-Studio/Misaka-Agent.

    171 GitHub starsUsed in 1 repo~2.7k tokens
    AI & LLM EngineeringAuto-check passed

  • Saelens

    Luciole-Studio/Misaka-Agent

    Train sparse autoencoders to interpret model features. An agent skill from Luciole-Studio/Misaka-Agent.

    171 GitHub starsUsed in 1 repo~3.7k tokens
    AI & LLM EngineeringAuto-check passed

  • Simpo

    Luciole-Studio/Misaka-Agent

    Reference-free preference alignment, simpler than DPO. An agent skill from Luciole-Studio/Misaka-Agent.

    171 GitHub starsUsed in 1 repo~1.4k tokens
    AI & LLM EngineeringAuto-check passed

  • Lambda Labs

    Luciole-Studio/Misaka-Agent

    On-demand GPU cloud instances for ML training. An agent skill from Luciole-Studio/Misaka-Agent.

    171 GitHub starsUsed in 1 repo~3k tokens
    AI & LLM EngineeringAuto-check: warnings

More from tetherto/qvac

All 50 skills in this repo

  • Qv Docs Solution Create

    tetherto/qvac

    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.

    685 GitHub stars~2.8k tokensUpdated yesterday
    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.

    685 GitHub stars~11k tokensUpdated yesterday
    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.

    685 GitHub stars~2k tokensUpdated yesterday
    Auto-check passed

  • Qv Quality Reporting

    tetherto/qvac

    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…

    685 GitHub stars~1.6k tokensUpdated yesterday
    Auto-check passed

  • Cpp String API Review

    tetherto/qvac

    Review C++ changes for string parameter and call-site efficiency conventions (std::stringview, std::string&&, const std::string&, const char, and TransparentStringMap lookup).

    685 GitHub stars~702 tokensUpdated yesterday
    Auto-check passed

  • Qv Addon Changelog

    tetherto/qvac

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

    685 GitHub stars~1.7k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Qv Qip Triage

What does Qv Qip Triage do?

Use during planning, implementation, PR review, or /qv-qip-triage when a change may affect public SDK API, native dependency, plugin contract, model registry contract, runtime, transport, storage…. Qv Qip Triage is an agent skill from tetherto/qvac. Use during planning, implementation, PR review, or /qv-qip-triage when a change may affect public SDK API, native dependency, plugin contract, model registry contract, runtime, transport, storage, release flow, deployment, security, NFR, or technical principles.

When should I use Qv Qip Triage?

Qv Qip Triage fits situations like: tasks that involve Pull requests; tasks that involve MLOps.

How do I install Qv Qip Triage in Claude Code?

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

How do I install Qv Qip Triage in Codex?

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

Can I use Qv Qip Triage 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-qip-triage -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-qip-triage, .gemini/skills/qv-qip-triage, .github/skills/qv-qip-triage and .opencode/skills/qv-qip-triage in your project.

What does Qv Qip Triage need to run?

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

Does Qv Qip Triage 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 Qip Triage 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 Qip Triage use?

Qv Qip Triage 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 Qip Triage use?

About 746 tokens (SKILL.md is roughly 3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 513 tokens, read only when the agent opens those files.

What are the alternatives to Qv Qip Triage?

Skills that share tags, products or a category with Qv Qip Triage: Megatron-LM on SLURM (NVIDIA/Megatron-LM, 18k stars), Oci Data Science (oracle/accelerated-data-science, 125 stars), Flash Attention (Luciole-Studio/Misaka-Agent, 171 stars) and Saelens (Luciole-Studio/Misaka-Agent, 171 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Qv Qip Triage?

tetherto (a GitHub organization) maintains it in tetherto/qvac, which has 685 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on October 10, 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.