Agent skills for Grok Build

Codified expertise for returns authorization, receipt and inspection, disposition decisions, refund processing, fraud detection, and…

Use when scripting, automating, or troubleshooting the YugabyteDB Anywhere (YBA) REST API — the control-plane API for self-managed YBA…

Multi-source literature search, citation verification, strict independent other-citation audits, article-level citation metric tables…

Run hypothesis tests, analyze A/B experiment results, calculate sample sizes, and interpret statistical significance with effect sizes.

Run pull request triage and digest workflows for basher83/Zammad-MCP, including human PR review attention, Renovate/Dependabot dependency…

No-code automation democratizes workflow building.

Transforms text into the absurd, energetic, and metaphorical speaking style of Mikoko Aoi from the Zaregoto series.

Expert knowledge of Godot Engine game development including scene creation, node management, GDScript programming, and project structure.

Expert knowledge of Godot performance optimization, profiling, bottleneck identification, and optimization techniques.

Use CodexBar CLI local cost usage to summarize per-model usage for Codex or Claude, including the current (most recent) model or a full…

ZBrush skill for decimation and normal map baking.

Customize the ZCode desktop app with a wallpaper and translucent UI theme.

Create a well-formatted git commit with conventional commit messages

Use when proxy shows dial tcp timeout or i/o timeout.

Use when browsing available dedicated server options.

Use when renting a new dedicated server.

Use when service fails with Connection refused to database or redis.

Use when publishing or updating a Zeabur template to the marketplace.

This skill should be used when the user asks to "learn ethical hacking", "understand penetration testing lifecycle", "perform…

Explore a codebase to find opportunities for architectural improvement, focusing on making the codebase more testable by deepening shallow…

This skill should be used when the user asks to "create bash scripts", "automate Linux tasks", "monitor system resources", "backup files"…