macroquest-expert
Provides expert guidance on creating, debugging, and maintaining MacroQuest scripts.
Install
mkdir -p .claude/skills/macroquest-expert && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12834" && unzip -o skill.zip -d .claude/skills/macroquest-expert && rm skill.zipInstalls to .claude/skills/macroquest-expert
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
MacroQuest code expert for creating/editing/debugging Lua scripts and .mac macros. Lua-first, plugin-safe, docs-backed.Key capabilities
- →Create Lua scripts
- →Edit Lua scripts and `.mac` macros
- →Debug Lua scripts and `.mac` macros
- →Refactor macros and Lua scripts
- →Check required plugins at script start
- →Consult documentation for syntax
How it works
The skill creates, edits, and debugs Lua scripts and `.mac` macros, prioritizing Lua, checking plugins, consulting documentation, and providing run instructions.
Inputs & outputs
When to use macroquest-expert
- →Write new Lua script
- →Debug .mac macro
- →Check required plugins
About this skill
MacroQuest Expert (Code)
You are an expert MacroQuest developer. You handle code tasks: creating, editing, debugging, and refactoring macros and Lua scripts.
Prefer Lua for new code unless the user explicitly requests macro language.
Inputs you should look for
- DOCS_DIR (path to mq_docs). If absent and you are in this docs repo, assume DOCS_DIR is the repo root.
- LUA_DIR and/or MACROS_DIR for write targets (may be outside the repo).
- Installation name (Live/Test/EMU), if provided.
- The requested behavior + any constraints (class, group/raid, required plugins, triggers, etc.).
If a path is “not configured” or contains path\to, do not write there—ask the user to provide a real path.
Best practices (non-negotiable)
- Check required plugins once at script start (
mq.TLO.Plugin('X').IsLoaded()). - Do not guess syntax—consult docs when uncertain.
- Use correct spawn search syntax (
reference/general/spawn-search.md). - Avoid infinite loops without escape conditions and include a reasonable
mq.delay(...).
Lua file structure (preferred)
- Create scripts at:
LUA_DIR/<scriptname>/init.lua - Run with:
/lua run <scriptname>
Output requirements
When you finish:
- List files created/modified (full paths).
- Explain what the code does.
- Provide exact run instructions.
- Call out any required plugins and how the script behaves when missing plugins.
External paths / permissions
If writing outside the repo (common for MacroQuest installs), remind the user to start Codex with:
--add-dir <LUA_DIR>and/or--add-dir <MACROS_DIR>:contentReference[oaicite:9]{index=9}
When not to use it
- →When the user explicitly requests macro language but Lua is preferred
- →When a path is 'not configured' or contains `path\to` for writing
- →When guessing syntax instead of consulting documentation
Limitations
- →Prefers Lua for new code unless macro language is explicitly requested
- →Requires `mq.TLO.Plugin('X').IsLoaded()` to check required plugins
- →Avoids infinite loops without escape conditions and includes `mq.delay(...)`
How it compares
This skill provides expert assistance for MacroQuest scripting, adhering to best practices like plugin checks and documentation consultation, unlike ad-hoc script creation.
Compared to similar skills
macroquest-expert side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| macroquest-expert (this skill) | 0 | 7mo | No flags | Advanced |
| godot | 1,044 | 5mo | Review | Intermediate |
| unreal-engine-cpp-pro | 43 | 4mo | No flags | Advanced |
| clojure-write | 16 | 3mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
godot
bfollington
This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.
unreal-engine-cpp-pro
sickn33
Expert guide for Unreal Engine 5.x C++ development, covering UObject hygiene, performance patterns, and best practices.
clojure-write
metabase
Guide Clojure and ClojureScript development using REPL-driven workflow, coding conventions, and best practices. Use when writing, developing, or refactoring Clojure/ClojureScript code.
llvm-tooling
gmh5225
Expertise in LLVM tooling development including Clang plugins, LLDB debugger extensions, Clangd/LSP, and LibTooling. Use this skill when building source code analysis tools, refactoring tools, debugger extensions, or IDE integrations.
superpowers-workflow
anthonylee991
Enforces a disciplined workflow for coding, debugging, refactoring, and automation: brainstorm -> plan -> implement with verification (prefer TDD) -> review -> finish. Use for almost any non-trivial change.
cursor-debug-bundle
jeremylongshore
Debug AI suggestions and code generation in Cursor. Triggers on "debug cursor ai", "cursor suggestions wrong", "bad cursor completion", "cursor ai debug". Use when debugging issues or troubleshooting. Trigger with phrases like "cursor debug bundle", "cursor bundle", "cursor".