TestsSûr9292/100
Ci Metrics (PyTorch)
Fallback loader for the canonical PyTorch ci-metrics skill. Use for CI duration, failures, queue times, workflow trends, runner health, or dashboard data only when the canonical instructions are not already loaded and no accessible pytorch/pytorch checkout contains them.
ou envoie-le directement à ton agent.
Installer dans ton projet
$ curl -fsSL https://arboristhree.xyz/cli/install-skill.mjs -o /tmp/arboris-install-skill.mjs && node /tmp/arboris-install-skill.mjs ci-metrics__pytorch-test-infra__claude-skills-5407b1e71df1PyTorch
pytorch/test-infra
Contenu à copier
--- name: ci-metrics description: Fallback loader for the canonical PyTorch ci-metrics skill. Use for CI duration, failures, queue times, workflow trends, runner health, or dashboard data only when the canonical instructions are not already loaded and no accessible pytorch/pytorch checkout contains them. metadata: origin: PyTorch --- # PyTorch CI Metrics Loader The canonical skill is `pytorch/pytorch/.claude/skills/ci-metrics/SKILL.md`; this loader does not count. Choose one instruction source in this order: 1. If the canonical instructions are already loaded in the current agent context, follow them directly. A skill catalog entry alone does not count as loaded instructions. 2. If an accessible `pytorch/pytorch` checkout contains `.claude/skills/ci-metrics/SKILL.md`, read and follow that file, resolving relative paths from its directory. Check the current workspace and already-known checkout locations; do not crawl the filesystem looking for a clone. 3. Otherwise, fetch a fresh temporary copy from `pytorch/pytorch` as shown below. Never reuse a previous download or another vendored copy. ```bash dir=$(mktemp -d) base=https://raw.githubusercontent.com/pytorch/pytorch/main/.claude/skills/ci-metrics curl -fsSL "$base/SKILL.md" -o "$dir/SKILL.md" curl -fsSL "$base/gcx-wrapper.sh" -o "$dir/gcx-wrapper.sh" chmod +x "$dir/gcx-wrapper.sh" && echo "$dir" ``` Read the selected `SKILL.md` as a file and follow it as the authoritative instructions; do not invoke a skill named `ci-metrics` from this loader, because that may select this loader again. For a downloaded copy, resolve paths such as `gcx-wrapper.sh` against the printed directory. If it references a file not fetched above, download it from `$base/<path>`. If any download fails, stop and report the error instead of falling back to stale instructions.
Colle ce Markdown dans ton agent ou utilise les boutons ci-dessus pour l’écrire dans ton projet.
Ce que fait Ci Metrics (PyTorch)
Applique les pratiques du skill ci-metrics__pytorch-test-infra__claude-skills-5407b1e71df1.
Comment utiliser Ci Metrics (PyTorch)
1
Copie le prompt
Un clic copie le prompt packagé (ou l'envoie à ton agent).
2
L'agent installe le skill
Il ajoute le SKILL.md et ses ressources à ton projet.
3
Activation automatique
Le skill s'active dès que le contexte correspond.
Déclencheurs pour Ci Metrics (PyTorch)
Dis simplement à ton agent quelque chose comme :
Applique le skill ci-metrics__pytorch-test-infra__claude-skills-5407b1e71df1 à cette tâche
Utilise ci-metrics__pytorch-test-infra__claude-skills-5407b1e71df1 pour améliorer cette implémentation
Passe en revue ce sujet avec ci-metrics__pytorch-test-infra__claude-skills-5407b1e71df1
Skills liés à Ci Metrics (PyTorch)
Add New Op (Alibaba)
为 MNN 框架新增算子。包含 Schema 定义、形状计算、几何计算、后端实现、单元测试的完整 TDD 流程。分 5 步执行,每步有独立测试标准。ai-regression-testing
Regression testing strategies for AI-assisted development. Sandbox-mode API testing without database dependencies, automated bug-check workflows, and patterns to catch AI blind spots where the same model writes and reviews code. Use when adding regression coverage to AI-assisted code, or when the same model both wrote and reviewed a change.Analyze Test Report (PyTorch)
Analyze torch-tensorrt local test results and drive failures to a fix. Use when the user pastes a test report / summary, asks why tests failed, asks to triage or fix failing tests, or mentions the JUnit/test-summary output from `just tests-report` / `just test-summary`. Covers where the JUnit XMLs live, how to read the consolidated report, how to reproduce a single failure, and how to categorize (real bug vs torch-API change vs OOM/skip vs flake).