qv-skill-list
Skill697 starsChanged 18 days agoApache-2.0View on GitHub
Catalog of all repo qv-* custom skills with one-line purpose and when-to-use. Use when the user asks what skills exist, which skill to use, how to invoke a skill, or invokes /qv-skill-list.
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
All custom repo skills live under .agents/skills/ and use the qv- prefix.
- Distinctive: line 22
When unsure which skill fits, scan the tables below or ask: *"which qv skill should I use for …?"*
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
QVAC Custom Skills Catalog
All custom repo skills live under .agents/skills/ and use the qv- prefix. Invoke with /qv-<name> in chat.
Not listed here (by design):
setup— repo-wide bootstrap (/setup); copies shared config frompackages/ocr-ggml/.agent/into.claude/and.cursor/.packages/ocr-ggml/.agent/skills/— framework skills (orchestrate,release,ci-validate,commit-trace,review); installed by/setup, notqv-*prefixed.
How to invoke
| Mode | Behavior |
| Auto-invokable | No disable-model-invocation in frontmatter — the agent may load the skill when your request matches the description. |
| Manual only | disable-model-invocation: true or agents/openai.yaml with allow_implicit_invocation: false — invoke explicitly with /qv-<name> (or ask the agent to run that skill). |
When unsure which skill fits, scan the tables below or ask: "which qv skill should I use for …?"
PR workflow (cross-pod)
| Skill | Purpose | Use when |
qv-pr-review | Deep PR review: gitflow, CI, format, code quality, security; posts a PENDING GitHub review with inline comments. | Reviewing any PR, given a PR URL, or follow-up from a pod status/my skill. Manual: /qv-pr-review |
qv-pr-test | Plan and run local PR validation; discovers packages/scripts, recommends test tier, analyzes results. | Testing a PR locally before merge. Manual: /qv-pr-test |
qv-pr-mine | Your open PRs across all pods, merge readiness, Slack ping messages for reviewers. | "What are my PRs?", merge readiness, who to ping. Manual: /qv-pr-mine |
DevOps pod
| Skill | Purpose | Use when |
qv-devops-pr-create | PR titles and bodies for CI/CD, composite actions, automation, IaC. | Creating a DevOps PR. Manual: /qv-devops-pr-create |
qv-devops-pr-review | /qv-pr-review plus GitHub Actions security audit (pinning, permissions, OIDC, secrets). | Reviewing PRs that touch DevOps paths. Manual: /qv-devops-pr-review |
qv-devops-pr-status | Team DevOps PR dashboard: re-review, stale, needs-review, conflicts. | DevOps pod PR queue health. Manual: /qv-devops-pr-status |
qv-devops-why-my-pr-not | Diagnose missing CI checks or merge blockers (labels, CODEOWNERS, approvals). | "Why aren't checks running?" / "Why can't I merge?" Manual: /qv-devops-why-my-pr-not |
qv-devops-daily-update | Slack standup (Done / Planned / Blockers) from PRs, reviews, CI. | DevOps EOD or standup. Manual: /qv-devops-daily-update |
qv-mobile-test-dispatch | Start an addon mobile (Device Farm) test and pick the right prebuild source; where the Android/iOS and C++ logs are. | "Run mobile tests for X" / "test my native change on a device" / reading a mobile failure. Manual: /qv-mobile-test-dispatch |
SDK pod
| Skill | Purpose | Use when |
qv-sdk-pr-create | PR descriptions for SDK pod packages (sdk, cli, rag, logging, error). | Creating an SDK pod PR; may chain to backmerge. Auto |
qv-sdk-pr-status | Team SDK pod PR dashboard. | SDK pod PR queue. Manual: /qv-sdk-pr-status |
qv-sdk-changelog | Changelogs for SDK pod packages (tag-based GitFlow). | Release prep, CHANGELOG_LLM.md. Auto |
qv-sdk-backmerge | Open backmerge PR (release version bump + changelog → main). | After SDK release PR; often chained from qv-sdk-pr-create. Auto |
qv-release-train | Release a whole dependency chain from one branch and one publish run. | Engine + SDK + agent stack moving together. Auto |
qv-sdk-e2e-create | Scaffold e2e tests in packages/sdk/e2e for new/changed public APIs. | Adding consumer-facing SDK APIs. Auto |
qv-sdk-update-models | Regen SDK models.ts from live registry and open a [mod] PR; optional provider/python cascade. | After registry model updates; /qv-sdk-update-models. Manual |
qv-agent-stack-sync | Plan / draft-cascade / promote the SDK → CLI → AI SDK provider → OpenCode + OpenClaw release chain. | Agent-stack release prep; /qv-agent-stack-sync --plan. Auto |
Addon pod (native inference / decoder / OCR)
| Skill | Purpose | Use when |
qv-addon-changelog | Changelog entries for a target add-on package. | Add-on release prep. Auto |
qv-addon-pr-create | PR descriptions for non-SDK inference addons, decoder, OCR. | "Prepare PR description" for an addon. Auto |
qv-addon-release-notes | Release notes for addon packages. | Addon release notes. Auto |
Registry server
| Skill | Purpose | Use when |
qv-registry-autobase-patterns | Autobase, HyperDB, multi-writer patterns, replication debugging. | Registry server, Autobase/HyperDB schemas, Corestore issues. Auto |
Documentation website
| Skill | Purpose | Use when |
qv-docs-solution-create | Solutions pages: generalize a supported use case into a docs page and register it in the site navigation. | A real developer, company, or partner scenario should become reusable documentation. Manual: /qv-docs-solution-create |
Developer diary and standup
| Skill | Purpose | Use when |
qv-dev-diary-setup | Opt-in local dev diary (~/.config/qvac-pr-skills/). | Enable diary, diary --init, configure capture. Manual: /qv-dev-diary-setup |
qv-dev-diary | Read, inspect, append diary entries. | View today's log, add notes after setup. Manual: /qv-dev-diary |
qv-daily-work-update | Personal EOD update from diary + GitHub + PR state (+ optional Asana). | Personal standup / "what did I do today". Manual: /qv-daily-work-update |
qv-asana-sync | Look up and update Asana tasks (status, comments, PR links). | Sync Asana task, move status, validate config. Manual: /qv-asana-sync |
Code quality
| Skill | Purpose | Use when |
qv-quality-reporting | Run deterministic quality analysis, triage cohesive debt groups, and prepare approval-gated Asana proposals. | Initial debt triage, recurring quality review, or twice-monthly reporting setup. Manual: /qv-quality-reporting |
Ecosystem and compliance
| Skill | Purpose | Use when |
qv-holepunch-dev | Holepunch/P2P/Bare/Pear API discovery via docs.pears.com and gh. | Hypercore, Hyperswarm, Autobase, Bare, Pear development. Auto |
qv-notice-generate | NOTICE files and third-party attributions for monorepo packages. | License compliance, release NOTICE updates. Auto |
Documentation site
| Skill | Purpose | Use when |
qv-docs-update | Updates the docs website after a change to the SDK or CLI. | You added or changed a feature and the docs need to catch up. Manual: /qv-docs-update |
Architecture proposals (QIP)
| Skill | Purpose | Use when |
qv-qip-triage | Conservatively checks whether a change clearly needs a QIP before deeper implementation. | Planning or implementing contract, cross-package, delivery, or principle-impacting work; PR review. Auto |
qv-qip-create | Drafts a Slack Canvas-ready QIP from a clear proposal or fuzzy idea. | Creating a QIP, shaping alternatives, consequences, and people to consult. Manual: /qv-qip-create |
qv-qip-review | Reviews a QIP for approval readiness, consequences, principle conflicts, and consultation coverage. | Reviewing a QIP draft before posting or approval. Auto |
Rule nudge: .cursor/rules/qip-triage.mdc
Quick picker
| You want to… | Skill |
| Review any PR | qv-pr-review |
| Review a DevOps/CI PR | qv-devops-pr-review |
| Test a PR locally | qv-pr-test |
| See your open PRs | qv-pr-mine |
| SDK team PR board | qv-sdk-pr-status |
| DevOps team PR board | qv-devops-pr-status |
| Why CI/merge is blocked | qv-devops-why-my-pr-not |
| Run mobile tests on a device | qv-mobile-test-dispatch |
| Write SDK PR body | qv-sdk-pr-create |
| Sync SDK models.ts from registry | qv-sdk-update-models |
| Write addon PR body | qv-addon-pr-create |
| SDK release changelog | qv-sdk-changelog |
| Addon release changelog | qv-addon-changelog |
| Backmerge after SDK release | qv-sdk-backmerge |
| Release engine + SDK + agent stack together | qv-release-train |
| Sync CLI/provider/OpenCode/OpenClaw to SDK | qv-agent-stack-sync |
| New SDK e2e tests | qv-sdk-e2e-create |
| Registry Autobase/HyperDB help | qv-registry-autobase-patterns |
| Publish a Solutions page from a use case | qv-docs-solution-create |
| Holepunch stack help | qv-holepunch-dev |
| Generate NOTICE files | qv-notice-generate |
| Update the docs website after an SDK/CLI change | qv-docs-update |
| Check if a QIP is needed | qv-qip-triage |
| Draft a QIP | qv-qip-create |
| Review a QIP | qv-qip-review |
| Triage code-quality debt | qv-quality-reporting |
| List all skills | qv-skill-list (this file) |
In this repository56 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/agent-integrations.mdcCursor rule
- .cursor/rules/cpp/string-api-conventions.mdcCursor rule
- .cursor/rules/devops/main.mdcCursor rule
- .cursor/rules/no-remote-code-execution.mdcCursor rule
- .cursor/rules/qip-triage.mdcCursor rule
- .cursor/rules/sdk/commit-and-pr-format.mdcCursor rule
- .cursor/rules/sdk/error-handling.mdcCursor rule
- .cursor/rules/sdk/first-class-product-parity.mdcCursor rule
- .cursor/rules/sdk/main.mdcCursor rule
- .cursor/rules/sdk/public-constants-contract.mdcCursor rule
- .cursor/rules/sdk/request-lifecycle-primitives.mdcCursor rule
- .cursor/rules/sdk/sdk-pod-packages.mdcCursor rule
- .cursor/rules/sdk/skill-authoring-guidelines.mdcCursor rule
- cpp-string-api-reviewSkill
- qv-addon-changelogSkill
- qv-addon-pr-createSkill
- qv-addon-release-notesSkill
- qv-agent-stack-syncSkill
- qv-asana-syncSkill
- qv-daily-work-updateSkill
- qv-dev-diary-setupSkill
- qv-dev-diarySkill
- qv-devops-daily-updateSkill
- qv-devops-pr-createSkill
- qv-devops-pr-reviewSkill
- qv-devops-pr-statusSkill
- qv-devops-runner-queueSkill
- qv-devops-why-my-pr-notSkill
- qv-docs-solution-createSkill
- qv-docs-updateSkill
- qv-holepunch-devSkill
- qv-merge-guard-wireSkill
- qv-mobile-test-dispatchSkill
- qv-notice-generateSkill
- qv-pr-mineSkill
- qv-pr-reviewSkill
- qv-pr-testSkill
- qv-qip-createSkill
- qv-qip-reviewSkill
- qv-qip-triageSkill
- qv-quality-reportingSkill
- qv-registry-autobase-patternsSkill
- qv-release-trainSkill
- qv-sdk-backmergeSkill
- qv-sdk-changelogSkill
- qv-sdk-e2e-createSkill
- qv-sdk-inference-versionSkill
- qv-sdk-pr-createSkill
- qv-sdk-pr-statusSkill
- qv-sdk-update-modelsSkill
- setupSkill
- setupSkill
- qv-nx-ciSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.