Install
$ agentstack add skill-tim0-12432-hotkeylessahk-mcp-skill-hotkeyless-ahk-invoke ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ● Network access Used
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
Hotkeyless AHK – Invoke Commands
Send commands to the Hotkeyless AHK HTTP server to control the user's desktop.
Prerequisites
You must know the available commands before invoking anything. If you haven't already, use the hotkeyless-ahk-discovering skill first:
curl -s http://localhost:42800/list
Only invoke commands that appear in the /list response.
Invoking a command
Without parameters
curl -s http://localhost:42800/send/
Example:
curl -s http://localhost:42800/send/OpenBrowser
With parameters
Pass parameters as query string values separated by ?:
curl -s http://localhost:42800/send/?param1?param2
Example:
curl -s http://localhost:42800/send/MoveMouse?500?300
> Note: Parameters are separated by ?, not &. This is specific to Hotkeyless AHK.
Response handling
| Response | Meaning | Action | |-------------|----------------------------------------------|-------------------------------| | success | Command was forwarded to AHK | Confirm to user | | failure | No AHK subscriber or command not found | Check if AHK script is running|
If you receive failure:
- Tell the user the AHK subscriber may not be running
- Suggest they check that the Hotkeyless AHK AutoHotkey script is active
- Do not retry more than once
Configuration
- Default URL:
http://localhost:42800 - The user may specify a different host or port
Rules
- Never guess command names. Only use commands from
/list. - Never invoke
killunless the user explicitly asks to shut down the Hotkeyless AHK server. - Ask before bulk actions. If a task requires more than 5 sequential commands (e.g. gameplay automation), confirm the plan with the user first.
- No feedback loop. You cannot see the screen. If you need visual confirmation of results, tell the user or suggest a screenshot MCP tool.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: tim0-12432
- Source: tim0-12432/HotkeylessAHK-mcp-skill
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.