fsm-engine

Enforce a finite state machine loop for NVIDIA GPU kernel tuning.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/codes1gn/CroqTuner --skill fsm-engine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fsm-engine
Source: https://github.com/codes1gn/CroqTuner/tree/main/.claude/skills/fsm-engine
Command: npx skills add https://github.com/codes1gn/CroqTuner --skill fsm-engine

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, git, and includes scripts (resource) components.

What problem does it solve?

This Skill solves the challenge of running long, error-prone GPU kernel optimization experiments by enforcing a finite state machine workflow with persistent state, validation gates, and autonomous resume support.

Core Features & Use Cases

  • FSM-Driven Tuning Control: Manages GPU kernel optimization through structured states including profiling, ideation, implementation, measurement, decision, and storage.
  • Experiment Reliability Guardrails: Uses state files, validation scripts, idea deduplication, checkpoints, and compaction summaries to prevent skipped steps and repeated experiments.
  • Use Case: Optimize sparse GEMM kernels on NVIDIA Hopper GPUs by continuously testing data-driven improvements from current best kernels or from scratch baselines while preserving progress across sessions.

Quick Start

Use the fsm-engine skill to start a CroqTuner GPU kernel optimization run from the best existing kernel for the specified shape and data type.

Frequently Asked Questions about fsm-engine

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate long-running GPU kernel optimization loops without losing progress?

A finite state machine workflow automates GPU kernel optimization by enforcing structured states like profiling and measurement, using persistent state files and checkpoints to preserve experiment progress reliably across multiple sessions.

What is the best way to manage state and prevent repeated experiments during sparse GEMM tuning?

Managing sparse GEMM tuning requires validation scripts, idea deduplication, and checkpointing. These guardrails prevent skipped steps and repeated experiments by strictly enforcing a structured finite state machine optimization loop.

Can I resume NVIDIA GPU kernel profiling workflows after an interruption?

Yes, you can resume NVIDIA GPU kernel profiling workflows after interruptions using autonomous resume support. The finite state machine relies on persistent state files and compaction summaries to recover and continue tuning iterations reliably.

Do I need jq and git to run autonomous CUDA kernel tuning scripts?

Yes, you need jq and git installed. These dependencies are required to execute the validation scripts, manage state files, and track persistent experiment data during your automated CUDA kernel tuning workflows.

How does a finite state machine control iterative code generation for GPU tuning?

A finite state machine controls iterative code generation by cycling through defined states: profiling, ideation, implementation, measurement, decision, and storage. This ensures benchmark-driven improvements are validated before advancing to the next optimization phase.