メニュー
Run an AHK v2 script against the alpha.30+Console fork and capture its output. Executes headlessly with stdout/stderr capture and exit-code reporting. TRIGGER when: user says "run this", "execute", "test run", "try running", "launch script", "check output".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Generate a complete AHK v2 GUI from a natural language description. Creates class-based, mathematically positioned GUIs with proper event binding. TRIGGER when: user says "generate a GUI", "build me a window", "create a dialog", "make a form", "design a settings panel", "build a tool with UI".
COM automation and interop for AHK v2 — driving Excel / Word / WMI / Internet Explorer via IDispatch, COM events, ComValue / SafeArrays, and direct vtable ComCall. Use when automating another application, wiring COM events, or calling a COM interface. TRIGGER when: user says "automate Excel/Word", "COM object", "ComObject", "ComCall", "WMI query", "COM event", "IDispatch", "SafeArray", "ComValue", "VARIANT". Examples: "automate Excel from AHK", "query WMI for processes", "hook IE navigation events"
Native calls and raw memory for AHK v2 — DllCall to Windows/native APIs, Buffer + NumGet/NumPut for structs, StrPut/StrGet, CallbackCreate, and the alpha.30 typed Struct. Use when calling a DLL/WinAPI function, building or reading a struct, or passing a callback to native code. TRIGGER when: user says "DllCall", "call a Windows API", "Buffer", "NumPut/NumGet", "struct", "pointer", "CallbackCreate", "StrGet/StrPut", "marshal", "user32/kernel32". Examples: "call GetCursorPos", "build a RECT struct", "pass a callback to EnumWindows"
Search AHK v2 documentation for a function, method, directive, or concept. Returns relevant documentation excerpts with syntax and examples. TRIGGER when: user says "docs for", "how does X work in AHK", "AHK docs", "look up", "what is the syntax for", "documentation".
Load AHK v2 error diagnosis, debugging, and fix knowledge. Use when diagnosing errors, fixing broken scripts, or debugging unexpected behavior. TRIGGER when: user mentions error, crash, broken, not working, debug, exception, TypeError, UnsetError, ValueError, OSError, syntax error, runtime error, fix, problem, issue, thrown, try, catch, troubleshoot, bug, fail, undefined, wrong output, unexpected behavior. Examples: "fix this error", "script crashes on startup", "UnsetError on line 42", "debug this"
Load AHK v2 GUI knowledge for window creation, layout, controls, events, and dark mode. Use when creating or modifying GUIs, positioning controls, handling events, or applying themes. TRIGGER when: user mentions gui, window, dialog, control, layout, button, ListView, ComboBox, dark mode, OnEvent, OnSize, positioning, resize, menu, toolbar, tab, checkbox, radio, edit, text, statusbar, form, modal, popup, theme, style, color. Examples: "create a GUI", "add a button", "fix overlapping controls", "dark mode window", "resize handler"
| name | ahk-run |
| description | Run an AHK v2 script against the alpha.30+Console fork and capture its output. Executes headlessly with stdout/stderr capture and exit-code reporting. TRIGGER when: user says "run this", "execute", "test run", "try running", "launch script", "check output". |
Execute AHK v2 scripts with the canonical fork interpreter and capture all output.
/ahk-run <file> — runs the script headlessly and returns output.
If no file specified, run the most recently edited .ahk file.
WIN_PATH=$(wslpath -w "$FILE")
timeout 10 "$AHK_EXE" /Headless /ErrorStdOut "$WIN_PATH" \
1>"$CLAUDE_JOB_DIR/ahk_run_out.txt" \
2>"$CLAUDE_JOB_DIR/ahk_run_err.txt"
EXIT_CODE=$?
The fork adds two flags that survive launchers that swallow stderr (VSCode AHK extension, custom runners, scheduled tasks). Use them when a normal run produces no useful output:
CRASH_LOG="$CLAUDE_JOB_DIR/ahk_run_crash.log"
STDERR_FILE="$CLAUDE_JOB_DIR/ahk_run_stderr.txt"
CRASH_LOG_WIN=$(wslpath -w "$CRASH_LOG")
STDERR_FILE_WIN=$(wslpath -w "$STDERR_FILE")
timeout 10 "$AHK_EXE" \
/Headless /ErrorStdOut \
"/CrashLog=$CRASH_LOG_WIN" \
"/StdErrFile=$STDERR_FILE_WIN" \
"$WIN_PATH"
EXIT_CODE=$?
# CRASH_LOG holds [START]/[PARSE]/[ERROR]/[FATAL]/[EXIT] records appended for this run.
# STDERR_FILE holds the byte-exact stderr stream.
Surface both files in the result block when the diagnostic run is used.
─ RUN RESULT ─────────────────────────────────────────────
File: script.ahk
Exit code: 0 (Normal)
─ STDOUT ─────────────────────────────────────────────────
<captured stdout>
─ STDERR ─────────────────────────────────────────────────
<captured stderr, if any>
─ CRASH LOG (if diagnostic mode) ─────────────────────────
<contents of $CRASH_LOG>
| Code | Reason | Meaning |
|---|---|---|
| 0 | Normal | Clean exit |
| 10 | Error | Uncaught script-level exception |
| 11 | Critical/Fatal | Interpreter critical error or SEH fault |
| 12 | Parse | Parse / load failure |
| 13 | Check | check subcommand verdict failed |
| 14 | Test | test subcommand verdict failed |
| 64 | Usage | CLI usage error |
| 124 | (timeout) | Hit our 10-second wrapper (not the AHK process) |
| 130 | ExternalSignal | Ctrl+C / Break / close / logoff / shutdown |
| n | ExitApp(n) | Intentional ExitApp(n) for non-reserved n |
Codes 11 (Critical vs Fatal) and 130 are fork additions. Don't conflate 10 (script throw) with 11 (interpreter fault) — the crash-log reason= field disambiguates them when in doubt.
check /Diag=json first./Headless /ErrorStdOut./Headless to suppress dialogs./ErrorStdOut to put runtime errors on stderr.$CLAUDE_JOB_DIR (never /tmp — parallel jobs collide).