verify-content
Run comprehensive quality verification on workshop or demo content using Red Hat standards and validation agents.
Discover DevOps skills, compare source repositories and read the instructions for each workflow.
Run comprehensive quality verification on workshop or demo content using Red Hat standards and validation agents.
Guide for writing effective prompt specifications (specs) for the GPT-5.2 Codex agent. Use when the user asks to "write a prompt spec", "create a system prompt for GPT-5.2", "design a spec for an agent", or "ho...
Write and debug Nushell scripts, pipelines, and commands. Also build Nushell plugins in Rust. Use when working with .nu files, writing Nushell code, converting bash to Nushell, creating custom Nushell commands/...
Guide for creating effective skills that extend agent capabilities with specialized knowledge, workflows, or tool integrations. Use this skill when the user asks to; (1) create a new skill, (2) make a skill, (3...
Rust code quality standards and documentation practices. Use when reviewing Rust code, cleaning up churn, writing docstrings, or following rustdoc conventions.
Query Rust docs and crate APIs from CLI. Use when exploring Rust crates, building API context and codemaps for handoffs, searching rustdoc, or needing crate skeletons. Trigger on "ripdoc", "rust docs", "crate A...
Control kitty terminal via remote protocol and kitty-test-harness; launch panels/windows, send keys, capture screen, manage sockets, and debug remote-control failures when testing TUIs.
ALWAYS use this skill when writing AI documentation. Covers CLAUDE.md, AGENTS.md, system prompts, AI-targeted comments, and architecture docs for AI consumption.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or to...
Design user experiences with usability focus. Use when planning user flows, navigation, forms, error handling, or accessibility. Complements frontend-design (visual) with UX structure.
Write idiomatic Rust code. Use when writing Rust, reviewing Rust code, or refactoring. Covers ownership patterns, error handling, and performance.
Write type-safe TypeScript. Use when writing or reviewing TypeScript code. Covers type safety best practices, avoiding dangerous features (any/as), and proper narrowing techniques.
Write Nix code and manage NixOS/home-manager configurations. Use when writing Nix expressions, flakes, modules, or debugging derivations.
Manage git worktrees with gtr. Use when working on multiple branches in parallel, especially with async agents.
Build UIs with DaisyUI component library. Use when creating interfaces with DaisyUI, styling Tailwind projects with semantic components, or customizing DaisyUI themes.
Build Svelte 5 apps with async svelte and remote functions. Always use this when writing svelte code.
Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has be...
Build TypeScript CLIs with gunshi. Use when creating command-line tools, parsing arguments, or implementing subcommands in TypeScript.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include website...
PRの全フィードバック(CodeQL、Copilotレビュー、手動コメント)を取得し、漏れなく対応する
Skill for research-oriented scientific software development, balancing reproducibility, correctness, and long-term maintainability, with selective engineering rigor.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visu...
Use when analyzing sales performance, customer metrics, inventory health, or generating forecasts.
Use when processing return requests, managing RMAs, or handling refund workflows.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.