Agent skill

Pytorch Clickhouse

Load this FIRST whenever working with PyTorch CI data (any pytorch/ org repo), the torchci/HUD codebase, or the PyTorch HUD ClickHouse database.

Custom licenceAuto-check passedDatabases

Install Pytorch Clickhouse

skills CLI

$ npx skills add pytorch/test-infra --skill pytorch-clickhouse -a claude-code

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

GitHub CLI

$ gh skill install pytorch/test-infra pytorch-clickhouse --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/pytorch/test-infra.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/pytorch-clickhouse .claude/skills/pytorch-clickhouse && 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/

Paste into Claude Code

Install the "pytorch-clickhouse" agent skill from https://github.com/pytorch/test-infra/tree/main/.claude/skills/pytorch-clickhouse into .claude/skills/pytorch-clickhouse/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pytorch-clickhouse", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/pytorch/test-infra/tree/main/.claude/skills/pytorch-clickhouse

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add pytorch/test-infra --skill pytorch-clickhouse -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install pytorch/test-infra pytorch-clickhouse --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/pytorch/test-infra.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/pytorch-clickhouse .agents/skills/pytorch-clickhouse && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "pytorch-clickhouse" agent skill from https://github.com/pytorch/test-infra/tree/main/.claude/skills/pytorch-clickhouse into .agents/skills/pytorch-clickhouse/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pytorch-clickhouse", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add pytorch/test-infra --skill pytorch-clickhouse -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install pytorch/test-infra pytorch-clickhouse --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/pytorch/test-infra.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/pytorch-clickhouse .cursor/skills/pytorch-clickhouse && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "pytorch-clickhouse" agent skill from https://github.com/pytorch/test-infra/tree/main/.claude/skills/pytorch-clickhouse into .cursor/skills/pytorch-clickhouse/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pytorch-clickhouse", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/pytorch/test-infra.git --path .claude/skills/pytorch-clickhouse

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add pytorch/test-infra --skill pytorch-clickhouse -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install pytorch/test-infra pytorch-clickhouse --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/pytorch/test-infra.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/pytorch-clickhouse .gemini/skills/pytorch-clickhouse && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "pytorch-clickhouse" agent skill from https://github.com/pytorch/test-infra/tree/main/.claude/skills/pytorch-clickhouse into .gemini/skills/pytorch-clickhouse/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pytorch-clickhouse", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install pytorch/test-infra pytorch-clickhouse

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add pytorch/test-infra --skill pytorch-clickhouse -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/pytorch/test-infra.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/pytorch-clickhouse .github/skills/pytorch-clickhouse && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "pytorch-clickhouse" agent skill from https://github.com/pytorch/test-infra/tree/main/.claude/skills/pytorch-clickhouse into .github/skills/pytorch-clickhouse/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pytorch-clickhouse", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add pytorch/test-infra --skill pytorch-clickhouse -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install pytorch/test-infra pytorch-clickhouse --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/pytorch/test-infra.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/pytorch-clickhouse .opencode/skills/pytorch-clickhouse && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "pytorch-clickhouse" agent skill from https://github.com/pytorch/test-infra/tree/main/.claude/skills/pytorch-clickhouse into .opencode/skills/pytorch-clickhouse/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pytorch-clickhouse", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: pytorch-clickhouse
GitHub stars: 113
Token cost: ~2.8k tokens
SKILL.md length: 1,316 words
Files: 2 (incl. references)
Skills in repo: 11
Repo updated: Oct 8, 2026
First seen: Oct 7, 2026
Licence: Custom licence

At a glance

Load this FIRST whenever working with PyTorch CI data (any pytorch/ org repo), the torchci/HUD codebase, or the PyTorch HUD ClickHouse database.

Works in 3 steps: List: get_clickhouse_queries_resource →… → Inspect params:… → Run:…
Investigating CI/trunk failures
SKILL.md covers Start here (once per session), pytorch-hud — curated triage…, pytorch-hud — curated named… and clickhouse-mcp — raw SQL,…, plus 3 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Pytorch Clickhouse is an agent skill from pytorch/test-infra. Load this FIRST whenever working with PyTorch CI data (any pytorch/ org repo), the torchci/HUD codebase, or the PyTorch HUD ClickHouse database. Covers the two MCP servers that reach this data — pytorch-hud (curated no-SQL triage plus ~145 pre-tuned named queries) and clickhouse-mcp (raw SQL, schema introspection, EXPLAIN, query optimization) — including which tool to reach for, the data model, and how to debug and speed up queries. Use when investigating CI/trunk failures, flaky or disabled tests, queue times…

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

It sits in Databases, covering Deep learning, Data warehousing and MCP servers. It works with PyTorch, ClickHouse, Model Context Protocol and SQL. The repository describes itself as: This repository hosts code that supports the testing infrastructure for the PyTorch organization. For example, this repo hosts the logic to track disabled tests and slow tests…

When your agent uses it

Investigating CI/trunk failures
Job/workflow/runner status
Optimizing any ClickHouse query against HUD data — even if the MCP servers arent named explicitly

Example prompts

“/pytorch-clickhouse”

Workflow steps

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

List: get_clickhouse_queries_resource → catalog of names (e.g. master_commit_red, queue_times_historical, commit_jobs_query, flaky_tests).
Inspect params: get_clickhouse_query_params_resource(query_name) → {params: {name: Type}, tests: [...]}. Doubles as a data-model hint.
Run: query_clickhouse_resource(query_name, parameters) — parameters is a JSON string matching those params.

What it can do on your machine

Read from SKILL.md and the folder at commit 71b3093. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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

Pytorch Clickhouse loads about 2.8k tokens when it runs, and up to ~6.3k if it reads all its reference files. Until then it costs about 176 tokens; SKILL.md has 1,316 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~176
When it runs · the whole SKILL.md, loaded when a task matches: ~2.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~6.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

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,316 words (~2,837 tokens).

“Two MCP servers reach the same PyTorch HUD ClickHouse backend — the only ClickHouse you have access to. Pick by task:”

— opening of SKILL.md by pytorch, Custom licence

name: pytorch-clickhouse

Read the full SKILL.md on GitHub

Files

SKILL.md and 1 other file (references) in .claude/skills/pytorch-clickhouse of pytorch/test-infra.

SKILL.md
references/clickhouse-perf.md

Open the folder on GitHubat commit 71b3093

Compare with similar skills

Pytorch Clickhouse 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.

Pytorch Clickhouse compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Pytorch Clickhouse this skillpytorch/test-infra	113	—	~2.8k	Automated safety check: Pass	Custom licence	today
Semantic Analystsidequery/sidemantic	129	—	~982	Automated safety check: Pass	AGPL-3.0	yesterday
Modelersidequery/sidemantic	129	—	~4.2k	Automated safety check: Pass	Apache-2.0	yesterday
Optimize Clickhouse SQLFrankChen021/datastoria	327	—	~1.2k	Automated safety check: Pass	Custom licence	2 mo ago
Triaging Warehouse Sync TicketsPostHog/posthog	40k	—	~6.3k	Automated safety check: Warn	Custom licence	today
Aurora Dsqlaws/agent-toolkit-for-aws	2.8k	—	~9.6k	Automated safety check: Pass	Apache-2.0	yesterday

Similar skills

Semantic Analyst
sidequery/sidemantic
Answer analytical, KPI, metric, trend, cohort, and business-performance questions through a Sidemantic semantic layer.
129 GitHub stars~982 tokensUpdated yesterday
DatabasesAuto-check passed
Modeler
sidequery/sidemantic
Build, validate, and manage semantic models using Sidemantic.
129 GitHub stars~4.2k tokensUpdated yesterday
DatabasesAuto-check passed
Optimize Clickhouse SQL
FrankChen021/datastoria
Optimize slow queries, analyze SQL performance, and collect evidence for expensive workloads.
327 GitHub stars~1.2k tokensUpdated 2 mo ago
DatabasesAuto-check passed
Triaging Warehouse Sync Tickets
PostHog/posthog
Official
Debug a customer's data warehouse source, schema, or table from a support ticket, using PostHog's own production data.
40k GitHub stars~6.3k tokensUpdated today
DatabasesAuto-check: warnings
Aurora Dsql
aws/agent-toolkit-for-aws
Official
Provisions and manages Aurora DSQL clusters, connects via psql or DSQL Connectors, manages schemas, runs queries, migrates from MySQL, diagnoses query plans, and develops apps on serverless…
2.8k GitHub stars~9.6k tokensUpdated yesterday
Backend & APIsAuto-check passed
AWS Storage
aws/agent-toolkit-for-aws
Official
Selects, investigates, and compares AWS object, file, and block storage services, and answers cost, performance, configuration, security, and troubleshooting questions about storage services.
2.8k GitHub stars~5.8k tokensUpdated yesterday
DatabasesAuto-check passed

More from pytorch/test-infra

All 11 skills in this repo

Migrate Workflow Ec2 To Osdc
pytorch/test-infra
Step-by-step playbook for migrating a pytorch/pytorch .github/workflows/.yml from EC2 to OSDC (ARC) runners — covers both dial-up and 100% opt-in patterns, with the inputs that must be plumbed…
113 GitHub stars~2k tokensUpdated today
Auto-check passed
R2 Outage Toggle
pytorch/test-infra
Disable or re-enable Cloudflare R2 (download-r2.pytorch.org) usage in managev2.py during R2 outages.
113 GitHub stars~1.5k tokensUpdated today
Auto-check passed
Release Cherry Pick Missing Reverts
pytorch/test-infra
Find reverts that landed on pytorch/pytorch main but are missing from a release branch (release/X.Y) because the reverted commit was already shipped in a release candidate, and open one cherry-pick…
113 GitHub stars~2.6k tokensUpdated today
Auto-check passed
Release Create Tracker Issue
pytorch/test-infra
Generate (and optionally open) a PyTorch release tracker / cherry-pick tracking issue from a release announcement, like https://github.com/pytorch/pytorch/issues/180506.
113 GitHub stars~2.7k tokensUpdated today
Auto-check passed
Release Create Validation Issue
pytorch/test-infra
Generate a PyTorch release validation checklist issue by pulling open/closed issues from a GitHub milestone and cherry-picks from a release tracker issue.
113 GitHub stars~2.2k tokensUpdated today
Auto-check passed
Release Go Live Binary Build Matrix
pytorch/test-infra
Update tools/scripts/generatebinarybuildmatrix.py when a PyTorch release goes live.
113 GitHub stars~1.7k tokensUpdated today
Auto-check passed

Works with

Questions about Pytorch Clickhouse

What does Pytorch Clickhouse do?

Load this FIRST whenever working with PyTorch CI data (any pytorch/ org repo), the torchci/HUD codebase, or the PyTorch HUD ClickHouse database. Pytorch Clickhouse is an agent skill from pytorch/test-infra. Load this FIRST whenever working with PyTorch CI data (any pytorch/ org repo), the torchci/HUD codebase, or the PyTorch HUD ClickHouse database.

When should I use Pytorch Clickhouse?

Pytorch Clickhouse fits situations like: investigating CI/trunk failures; job/workflow/runner status; optimizing any ClickHouse query against HUD data — even if the MCP servers arent named explicitly.

How do I install Pytorch Clickhouse in Claude Code?

Run `npx skills add pytorch/test-infra --skill pytorch-clickhouse -a claude-code`. Or copy the skill folder (.claude/skills/pytorch-clickhouse in pytorch/test-infra) into .claude/skills/pytorch-clickhouse in your project. Claude Code loads it when a task matches its description.

How do I install Pytorch Clickhouse in Codex?

Run `npx skills add pytorch/test-infra --skill pytorch-clickhouse -a codex`. Or copy the skill folder (.claude/skills/pytorch-clickhouse in pytorch/test-infra) into .agents/skills/pytorch-clickhouse in your project. Codex loads it when a task matches its description.

Can I use Pytorch Clickhouse 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 pytorch/test-infra --skill pytorch-clickhouse -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pytorch-clickhouse, .gemini/skills/pytorch-clickhouse, .github/skills/pytorch-clickhouse and .opencode/skills/pytorch-clickhouse in your project.

What does Pytorch Clickhouse need to run?

SKILL.md names no scripts, command-line tools or credentials: Pytorch Clickhouse is instructions for the agent only.

Does Pytorch Clickhouse access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Pytorch Clickhouse 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 Pytorch Clickhouse use?

Pytorch Clickhouse has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Pytorch Clickhouse use?

About 2.8k tokens (SKILL.md is roughly 11k 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 3.4k tokens, read only when the agent opens those files.

What are the alternatives to Pytorch Clickhouse?

Skills that share tags, products or a category with Pytorch Clickhouse: Semantic Analyst (sidequery/sidemantic, 129 stars), Modeler (sidequery/sidemantic, 129 stars), Optimize Clickhouse SQL (FrankChen021/datastoria, 327 stars) and Triaging Warehouse Sync Tickets (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 Pytorch Clickhouse?

pytorch (a GitHub organization) maintains it in pytorch/test-infra, which has 113 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 8, 2026.

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

Install Pytorch Clickhouse

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Files

Compare with similar skills

Similar skills

More from pytorch/test-infra

Related

Questions about Pytorch Clickhouse