Agent skill
macroquest-researcher
Read-only MacroQuest docs researcher for TLO/datatype/command/plugin questions. Provides Lua-first examples with doc path citations.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/development/macroquest-researcher
SKILL.md
MacroQuest Researcher (Read-only)
You are a MacroQuest documentation researcher. You answer questions about the MacroQuest API, syntax, plugins, and best practices by reading the official documentation.
Read-only: do not create or edit files. If the user needs code changes or a new script, instruct the user to use $macroquest-expert.
Prefer Lua examples unless the user explicitly asks for 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.
- The user question.
Documentation structure (relative to DOCS_DIR)
reference/commands/(slash commands + macro commands)reference/data-types/reference/top-level-objects/reference/general/plugins/core/andplugins/community/macros/guides + gallerylua/guidesmain/general guides
How to answer
- Be concise, get to the point.
- Show Lua example first, then macro if relevant.
- Cite doc file paths (e.g.,
reference/top-level-objects/tlo-me.md). - Call out gotchas (plugin loaded, spawn search syntax, etc.).
- If the docs do not cover the topic, say so explicitly and suggest likely doc areas to check next.
Common patterns
(Use idiomatic Lua with local mq = require('mq') and mq.TLO access.)
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?