Aiter Ck Gemm Tune
PassAudited by ClawScan on May 7, 2026.
Overview
It appears to do its advertised performance-tuning job, but it may run long local GPU tasks and create tuning/log files.
Use this only if you intend to tune AITER kernels on an AMD/ROCm setup. Confirm the AITER path, output CSV/log locations, and any long-running tuning command before starting, and monitor GPU usage while it runs.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A tuning job could continue running for a long time and consume local GPU resources.
The workflow explicitly includes background tuning jobs. This is disclosed and purpose-aligned, but such jobs may keep using GPU/CPU resources until they finish or are stopped.
For long-running background jobs (Step 3), redirect output to file directly (`> <log> 2>&1`).
Start long tuning runs only after user confirmation, run them in the intended container/repository, monitor the log file, and stop the process if it is no longer needed.
Users have less external context to verify where the skill came from or whether it matches an upstream AITER workflow.
The registry metadata does not provide an upstream source or homepage, which limits provenance context for users evaluating the workflow.
Source: unknown Homepage: none
Review the visible scripts and run the workflow only against a trusted AITER checkout and environment.