Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

gpu-usage

Sterne3

Forks1

Aktualisiert31. März 2026 um 04:50

Report GPU usage on shared servers — shows which processes occupy each GPU, VRAM percentage, GPU utilization, process owner, elapsed time, and Docker container name. Use this skill when the user asks: "who's using the GPU", "check GPU usage", "is the GPU free", "can I profile", "GPU contention", "VRAM usage", "show GPU processes", "gpu-usage", or any question about GPU availability before profiling.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

poyenc

poyenc/agent-skills

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Netzwerk- und ComputersystemadministratorenInformatik- und Mathematikberufe·SOC 15-1244

Datei-Explorer

2 Dateien

SKILL.md

readonly

name	gpu-usage
description	Report GPU usage on shared servers — shows which processes occupy each GPU, VRAM percentage, GPU utilization, process owner, elapsed time, and Docker container name. Use this skill when the user asks: "who's using the GPU", "check GPU usage", "is the GPU free", "can I profile", "GPU contention", "VRAM usage", "show GPU processes", "gpu-usage", or any question about GPU availability before profiling.
allowed-tools	Bash(python3 * gpu_usage.py *)

GPU Usage Report

Prerequisites

rocm-smi installed and on PATH
Python 3.8+

Workflow

Run the script:

python3 <skill-dir>/scripts/gpu_usage.py --format markdown

Present the output directly — it's a ready-to-display markdown table.

If all GPUs are idle, the script prints "All GPUs are idle."

Use --format json if structured data is needed downstream.

Mehr aus diesem Repository

gleiches Repository

handoff

poyenc/agent-skills

Compact the current conversation into a handoff document so a fresh agent can continue the work without losing context. Use when the user says "handoff", "hand off", "write a handoff", or otherwise asks to checkpoint or wrap up the current work so a new session can pick up seamlessly.

2026-07-133

ck-ci-build

poyenc/agent-skills

Trigger Jenkins CI builds for Composable Kernel pull requests or branches with optional parameter overrides. Use this skill whenever the user wants to trigger a CI build, start a build, kick off CI, rebuild, re-run CI, or launch a Jenkins build for a CK or Composable Kernel PR or branch. Also trigger when the user asks to set CI build parameters, enable/disable specific tests (like FMHA, AITER, FA, pytorch), or wants to check what CI parameters are available for a PR or branch.

2026-06-193

hip-kernel-team

poyenc/agent-skills

Launch and manage a multi-agent team for HIP/GPU kernel development, debugging, and optimization. Configurable roles (Lead, Implementer, Profiler, Researcher) with optional recall-plugin integration and long-running context rotation. Use this skill whenever the user wants to: start a kernel optimization team, launch agents to work on a HIP kernel, create a dev team for GPU kernel work, set up a multi-agent workflow for kernel performance tuning, or resume a previously saved team config. Also trigger when the user says things like "start a team to optimize kernel X", "launch agents for my HIP kernel", "hip-kernel-team load", "resume my kernel team", or "set up a dev team for this GPU kernel".

2026-05-143

ck-ci-report

poyenc/agent-skills

Analyze CI build failures for Composable Kernel pull requests or branches on the Jenkins dashboard. Use this skill whenever the user asks about CI failures, build errors, Jenkins build status, or wants to investigate why a CK PR or branch build failed. Trigger on phrases like "check CI", "why did the build fail", "CI report for PR", "CI report for branch", "check Jenkins", "what failed in PR-XXXX", "what failed on branch X", "build status", "CI dashboard", or "analyze build failure".

2026-05-143

post-review

poyenc/agent-skills

Validate and post inline PR comments from a prior /review output. Spawns a subagent to verify each claim against actual code, drops wrong items, formats confirmed findings as inline comment drafts, and optionally posts them to GitHub. Works with both PR and local branch reviews. Trigger on: "post review", "post comments", "post inline comments", "format review as comments", or "/post-review".

2026-05-133

ck-list-fmha-prs

poyenc/agent-skills

List open pull requests from ROCm/rocm-libraries that are labeled "project: composablekernel" and focused on fused multi-head attention (FMHA) — including kernel code, tests, and CI/infrastructure. Use this skill whenever the user asks about open FMHA PRs, CK attention PRs, composable kernel flash attention pull requests, FMHA test PRs, FMHA CI changes, or wants to see what FMHA-related work is in progress on the rocm-libraries repo. Also trigger when the user asks things like "what PRs touch the attention kernel", "show me open CK FMHA changes", "list MHA pull requests", "what's being worked on for flash attention in CK", "FMHA test PRs", or "FMHA CI changes". Pass `--full-scan` to ignore saved state and re-scan all PRs from scratch.

2026-05-123

name	gpu-usage
description	Report GPU usage on shared servers — shows which processes occupy each GPU, VRAM percentage, GPU utilization, process owner, elapsed time, and Docker container name. Use this skill when the user asks: "who's using the GPU", "check GPU usage", "is the GPU free", "can I profile", "GPU contention", "VRAM usage", "show GPU processes", "gpu-usage", or any question about GPU availability before profiling.
allowed-tools	Bash(python3 * gpu_usage.py *)

GPU Usage Report

Prerequisites

rocm-smi installed and on PATH
Python 3.8+

Workflow

Run the script:

python3 <skill-dir>/scripts/gpu_usage.py --format markdown

Present the output directly — it's a ready-to-display markdown table.

If all GPUs are idle, the script prints "All GPUs are idle."

Use --format json if structured data is needed downstream.