Phone Harness
ShawnPana/phone-harness
Control the user's phone - an iPhone through the Mac's iPhone Mirroring window, an Android over adb, a rented cloud Android, or a cloud iPhone over HTTPS: open apps, tap, type, swipe, read the screen.
Turn a decision the user cannot fully answer into a Markdown questionnaire for the one person who can - filled in async, or together over a meeting.
Install Maestro Questionnaire
$ npx skills add ReinaMacCredy/maestro --skill maestro-questionnaire -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ReinaMacCredy/maestro maestro-questionnaire --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ReinaMacCredy/maestro.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/plugins/skills/maestro-questionnaire .claude/skills/maestro-questionnaire && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "maestro-questionnaire" agent skill from https://github.com/ReinaMacCredy/maestro/tree/main/src/plugins/skills/maestro-questionnaire into .claude/skills/maestro-questionnaire/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maestro-questionnaire", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ReinaMacCredy/maestro/tree/main/src/plugins/skills/maestro-questionnaireType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ReinaMacCredy/maestro --skill maestro-questionnaire -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ReinaMacCredy/maestro maestro-questionnaire --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ReinaMacCredy/maestro.git skills-src && mkdir -p .agents/skills && cp -r skills-src/src/plugins/skills/maestro-questionnaire .agents/skills/maestro-questionnaire && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "maestro-questionnaire" agent skill from https://github.com/ReinaMacCredy/maestro/tree/main/src/plugins/skills/maestro-questionnaire into .agents/skills/maestro-questionnaire/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maestro-questionnaire", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ReinaMacCredy/maestro --skill maestro-questionnaire -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ReinaMacCredy/maestro maestro-questionnaire --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ReinaMacCredy/maestro.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/src/plugins/skills/maestro-questionnaire .cursor/skills/maestro-questionnaire && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "maestro-questionnaire" agent skill from https://github.com/ReinaMacCredy/maestro/tree/main/src/plugins/skills/maestro-questionnaire into .cursor/skills/maestro-questionnaire/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maestro-questionnaire", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ReinaMacCredy/maestro.git --path src/plugins/skills/maestro-questionnaire--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ReinaMacCredy/maestro --skill maestro-questionnaire -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ReinaMacCredy/maestro maestro-questionnaire --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ReinaMacCredy/maestro.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/src/plugins/skills/maestro-questionnaire .gemini/skills/maestro-questionnaire && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "maestro-questionnaire" agent skill from https://github.com/ReinaMacCredy/maestro/tree/main/src/plugins/skills/maestro-questionnaire into .gemini/skills/maestro-questionnaire/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maestro-questionnaire", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ReinaMacCredy/maestro maestro-questionnaireInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ReinaMacCredy/maestro --skill maestro-questionnaire -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ReinaMacCredy/maestro.git skills-src && mkdir -p .github/skills && cp -r skills-src/src/plugins/skills/maestro-questionnaire .github/skills/maestro-questionnaire && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "maestro-questionnaire" agent skill from https://github.com/ReinaMacCredy/maestro/tree/main/src/plugins/skills/maestro-questionnaire into .github/skills/maestro-questionnaire/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maestro-questionnaire", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ReinaMacCredy/maestro --skill maestro-questionnaire -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ReinaMacCredy/maestro maestro-questionnaire --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ReinaMacCredy/maestro.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/src/plugins/skills/maestro-questionnaire .opencode/skills/maestro-questionnaire && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "maestro-questionnaire" agent skill from https://github.com/ReinaMacCredy/maestro/tree/main/src/plugins/skills/maestro-questionnaire into .opencode/skills/maestro-questionnaire/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maestro-questionnaire", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
maestro-questionnaire- GitHub stars
- 233
- Token cost
- ~946 tokens
- SKILL.md length
- 525 words
- Files
- 1
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- MIT
At a glance
Turn a decision the user cannot fully answer into a Markdown questionnaire for the one person who can - filled in async, or together over a meeting.
- Works in 3 steps: Who is it going to? Ask, in one… → What do you need back? Ask, in one… → Write the questionnaire. Draft questions…
- Vietnamese phrasings such as phỏng vấn đi
- SKILL.md covers Document structure, Context, How to answer and Anything else?
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Maestro Questionnaire is an agent skill from ReinaMacCredy/maestro. Turn a decision the user cannot fully answer into a Markdown questionnaire for the one person who can - filled in async, or together over a meeting. Also triggers on Vietnamese phrasings such as phỏng vấn đi, phỏng vấn tôi, interview tôi.
Its SKILL.md is about 950 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Mobile, covering Mobile testing and debugging. The repository describes itself as: Local-first coordination for human and agent work: durable work, decisions, dispatches, evidence, and prompt-first methods, powered by TypeScript and Bun. The licence is MIT.
When your agent uses it
- Vietnamese phrasings such as phỏng vấn đi
- Tasks that involve Mobile testing and debugging
Example prompts
- “/maestro-questionnaire”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Who is it going to? Ask, in one exchange, the recipient's role,
- What do you need back? Ask, in one exchange, the specific decisions
- Write the questionnaire. Draft questions aimed at the gap from steps
What it can do on your machine
Read from SKILL.md and the folder at commit 2412403. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Maestro Questionnaire loads about 946 tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 525 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from ReinaMacCredy/maestro at commit 2412403, republished under its MIT licence (© ReinaMacCredy). 525 words, ~946 tokens.
Download SKILL.mdSave it as
.claude/skills/maestro-questionnaire/SKILL.md (or your agent's skills folder).- name
- maestro-questionnaire
- description
- Turn a decision the user cannot fully answer into a Markdown questionnaire for the one person who can - filled in async, or together over a meeting. Also triggers on Vietnamese phrasings such as phỏng vấn đi, phỏng vấn tôi, interview tôi.
- review-date
- 2026-11-28
<!-- maestro-skill-version: dev --><!-- adapted from Matt Pocock's to-questionnaire -->maestro-questionnaire
Turn something the user cannot answer alone into a questionnaire: a Markdown document they hand to one person to fill in async, or fill out together over a meeting. The recipient holds knowledge the user lacks; the questionnaire pulls it out of them. Read-only toward code; any tier may use it.
Grill the send, not the subject. Interview the user only about the send, which they can always answer: who it goes to, and what they need back. The questions in the document then target the gap between what the recipient knows and what the user needs.
Who is it going to? Ask, in one exchange, the recipient's role, expertise, and relationship to the user. This fixes the questionnaire's tone and how much context it must carry. Done when you know who the recipient is and what they know that the user does not.
What do you need back? Ask, in one exchange, the specific decisions or facts the user cannot resolve alone and needs from this person. Done when you have a concrete list of what the user must walk away able to do or decide.
Write the questionnaire. Draft questions aimed at the gap from steps 1 and 2, following the Document structure below. When an active bundle owns the decision, write it to
.maestro/bundle/<bundle-id>/QUESTIONNAIRE-<slug>.md, record the wait asmaestro work note <id> "blocked: questionnaire <slug> sent to <role>", and set the bundle's NOTES.md Next Action to the return of the answers; otherwise writequestionnaire-<slug>.mdin the current directory. Report the path. Done when the file exists and every item the user named in step 2 is covered by a question.
When the answers come back, they are settled forks: record each as
maestro decision draft "<answer>" --rationale "<why, per <recipient>>" --work <id>
then maestro decision lock <id>, and clear the Next Action. The filled
questionnaire is the evidence the decision cites.
Show full SKILL.md (207 more words)Show less
Document structure
Frame the document as a discovery questionnaire: the user lacks context,
the recipient holds it. Order questions most-important-first, since async
means you may only get one pass, and group them under ## headings by theme
once there are more than a handful. Write it using the template below.
<questionnaire-template><Questionnaire title>
Purpose: why this questionnaire exists and the decision riding on it.
From: <the user> To: <the recipient> How your answers will be
used: <where they go>
Context
One paragraph orienting a recipient who was not in the user's head. Enough to answer well, not a page.
How to answer
Deadline and rough effort. Partial answers and "I don't know" are useful; flag anything you are unsure of rather than skipping it.
<Theme heading>
One ## section per theme. Under each, its questions, most-important-first.
Every question is one idea, never compound, with an answer stub directly
beneath, and a one-line why this matters only where the question could be
misread or invite a throwaway answer.
<question-example>
### What load is the system expected to handle at launch?Why this matters: it decides whether we provision for burst traffic now or defer it.
</question-example>Anything else?
A closing catch-all: anything we did not ask that we should know?
</questionnaire-template>© ReinaMacCredy, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in src/plugins/skills/maestro-questionnaire of ReinaMacCredy/maestro.
Open the folder on GitHubat commit 2412403
Compare with similar skills
Maestro Questionnaire next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Maestro Questionnaire this skillReinaMacCredy/maestro | 233 | — | ~946 | Automated safety check: Pass | MIT | |
| Phone HarnessShawnPana/phone-harness | 3.2k | — | ~7.7k | Automated safety check: Pass | MIT | |
| Maa Issue Log AnalysisMaaAssistantArknights/MaaAssistantArknights | 24k | — | ~4k | Automated safety check: Pass | AGPL-3.0 | |
| Mobile QAtloncorp/tlon-apps | 107 | — | ~2.4k | Automated safety check: Pass | MIT | |
| Store Listing Screenshotstherxmv/Telegram-Themer | 119 | — | ~2.5k | Automated safety check: Pass | None | |
| Androidyang1ming/android-harness | 176 | — | ~259 | Automated safety check: Pass | MIT |
Similar skills
Maa Issue Log Analysis
MaaAssistantArknights/MaaAssistantArknights
分析 MaaAssistantArknights 上游仓库公开 Issue（https://github.com/MaaAssistantArknights/MaaAssistantArknights/issues/...
Mobile QA
tloncorp/tlon-apps
Run a mobile QA checklist on a physical Android device over adb for tlon-apps, then triage what fails into fixes.
Store Listing Screenshots
therxmv/Telegram-Themer
Generate TelegramThemer's Play Store listing images — capture the 8 required app screenshots on a running emulator/device by driving the real UI with adb, then composite them into the final…
Android
yang1ming/android-harness
Direct Android device control through ADB. An agent skill from yang1ming/android-harness.
Dongle Crash Analysis
haumacher/phoneblock
Decode and analyze an ESP32 dongle crash report (uploaded .coredump).
More from ReinaMacCredy/maestro
All 11 skills in this repoMaestro Improve
ReinaMacCredy/maestro
Turn filed lessons into the smallest doctrine edit. An agent skill from ReinaMacCredy/maestro.
Maestro Council
ReinaMacCredy/maestro
Lead-only council for a hard-to-reverse fork - a neutral brief, sealed independent seats, one premise verifier on unanimity, bounded verifiers, one cross-examination round, a draft-verdict audit…
Maestro Design
ReinaMacCredy/maestro
Resolve material unknowns blocking the next authorized slice, using research, grilling, prototypes, models, or wayfinding.
Maestro Graph
ReinaMacCredy/maestro
Drive a pre-known multi-agent path as a maestro graph - run it by name or from a file you just wrote, pull each agent node with graph next, spawn it as a sub-agent under its maestro-<profile…
Maestro Verify
ReinaMacCredy/maestro
Verify and close - cross-check coverage, run the VERIFY table, deliver the verdict, harvest durable lessons into decisions, close the bundle, and never claim remote state from local evidence.
Maestro Work
ReinaMacCredy/maestro
Implement or fix one authorized unit with minimal edits and sufficient evidence.
Related
Categories
Questions about Maestro Questionnaire
What does Maestro Questionnaire do?
Turn a decision the user cannot fully answer into a Markdown questionnaire for the one person who can - filled in async, or together over a meeting. Maestro Questionnaire is an agent skill from ReinaMacCredy/maestro. Turn a decision the user cannot fully answer into a Markdown questionnaire for the one person who can - filled in async, or together over a meeting.
When should I use Maestro Questionnaire?
Maestro Questionnaire fits situations like: vietnamese phrasings such as phỏng vấn đi; tasks that involve Mobile testing and debugging.
How do I install Maestro Questionnaire in Claude Code?
Run `npx skills add ReinaMacCredy/maestro --skill maestro-questionnaire -a claude-code`. Or copy the skill folder (src/plugins/skills/maestro-questionnaire in ReinaMacCredy/maestro) into .claude/skills/maestro-questionnaire in your project. Claude Code loads it when a task matches its description.
How do I install Maestro Questionnaire in Codex?
Run `npx skills add ReinaMacCredy/maestro --skill maestro-questionnaire -a codex`. Or copy the skill folder (src/plugins/skills/maestro-questionnaire in ReinaMacCredy/maestro) into .agents/skills/maestro-questionnaire in your project. Codex loads it when a task matches its description.
Can I use Maestro Questionnaire in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ReinaMacCredy/maestro --skill maestro-questionnaire -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/maestro-questionnaire, .gemini/skills/maestro-questionnaire, .github/skills/maestro-questionnaire and .opencode/skills/maestro-questionnaire in your project.
What does Maestro Questionnaire need to run?
SKILL.md names no scripts, command-line tools or credentials: Maestro Questionnaire is instructions for the agent only.
Does Maestro Questionnaire access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Maestro Questionnaire safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Maestro Questionnaire use?
Maestro Questionnaire is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Maestro Questionnaire use?
About 946 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Maestro Questionnaire?
Skills that share tags, products or a category with Maestro Questionnaire: Phone Harness (ShawnPana/phone-harness, 3.2k stars), Maa Issue Log Analysis (MaaAssistantArknights/MaaAssistantArknights, 24k stars), Mobile QA (tloncorp/tlon-apps, 107 stars) and Store Listing Screenshots (therxmv/Telegram-Themer, 119 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Maestro Questionnaire?
ReinaMacCredy (a GitHub user) maintains it in ReinaMacCredy/maestro, which has 233 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on September 28, 2026.
Source: ReinaMacCredy/maestro on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.