Use this skill when the user requests invoking Droid, viewing Droid sessions, or handling its CLI issues. For ordinary inquiries, only verify and answer the question; send messages to a session only when the user asks to hand a task to Droid.
Before starting
- Determine whether the user wants to create a new session, resume a specified session, view records, or merely learn about the commands. Do not guess the target session based on similar titles or paths.
- For new sessions, use the project directory specified by the user; if unspecified, use the current working directory. Confirm the directory exists first. Existing sessions keep their original directory; handle the model according to the convention below.
- Run as needed
command -v droid、droid --versionanddroid exec --help. Installation, updates, login, or changes to global configuration should match the user's actual request and must not be performed automatically. - Select the model according to the convention below; other settings follow the existing configuration. Available models are subject to the current environment and the Factory model documentation.
Models and quotas
- Use Claude Sonnet 5.5 by default: model ID is
claude-sonnet-5-5, reasoning level isxhigh. New sessions and new tasks without a separately specified model use this selection; other models explicitly specified by the user for the current task or an existing session take precedence. - After confirming Standard Usage standard quota is exhausted, automatically fall back to Droid Core's Kimi K3.1 Pro: model ID is
kimi-k3.1-pro. Use that model's default reasoning level; the local CLI 1.8.0 returnsmax. When the standard quota is known to be still unrecovered, continue using Kimi for subsequent tasks; after recovery, use the preferred model again. Do not switch due to ordinary network errors, authentication failures, or rate limiting where the quota type cannot be determined. - Before switching, confirm the current turn has stopped and check the original session and completed work. If the original task has already entered the session, continue the unfinished part in the same session and do not blindly resend the original task; if the state is unclear, verify first. When the CLI has already automatically switched to the target model, do not switch again. When reporting results, state the model actually used and the reason for the fallback.
- These selections apply only to the current run or session and do not modify global default settings. For ordinary
droid execuse--modeland--reasoning-effort; for long-running mode, use the session request fields, see interaction protocol。
Choosing the execution method
- One-off task or the next turn of a finished session: use
droid exec; applicable when no human Q&A is needed. Normal mode is read-only by default; when modifications are needed, choose the--autoto bypass restrictions.--skip-permissions-unsafe。 - Need to receive AskUser or permission requests during execution: use a long-running JSON-RPC process that keeps stdin and stdout open, operating according to the interaction protocol. Call the Droid CLI directly; do not require installing an SDK or starting an additional service.
- Operated by the user in the terminal: use
droidto start the interactive interface; to resume, usedroid --resume <session-id>。 - Query history only: use
droid search <关键词> --jsonSearch local records, or read the target session file read-only at a confirmed location. When viewing a specific session, first confirm the ID and project directory; do not read history by sending a new message.
One-off execution and continuation
The following examples use the skill's default model; when the user explicitly selects another model for the current task or an existing session, use the corresponding setting.
droid exec --cwd /path/to/project --model claude-sonnet-5-5 --reasoning-effort xhigh --output-format json "任务内容"
droid exec --session-id SESSION_ID --model claude-sonnet-5-5 --reasoning-effort xhigh --output-format json "下一轮任务"
The first execution obtains from the JSON result session_id; continuation uses the same ID. Check the process exit status,is_error, result and error information; do not treat the command having started as task completion.-s is a continuation parameter, not a command to query run status or obtain AskUser; one-off droid exec does not provide AskUser.
When it is confirmed that the standard quota is exhausted and continuation is appropriate, you may specify in the original session --model kimi-k3.1-pro, without passing Sonnet's xhigh. To verify the actual session configuration, you may use --output-format stream-json to view the initialization event's model and reasoning_effort; the configuration value does not equal actual inference token consumption.
Follow-up and interaction
- When the user asks to wait for task completion or the task itself requires results, keep reading that process's events until the current round completes, fails, is interrupted, or requires user handling. No new output does not mean completion, nor does it mean it is waiting for an answer.
- When the user asks to see AskUser, accurately present the question, options, and single-choice/multiple-choice information. When the answer has been explicitly given by the user or can be determined from the authorized task scope, you may answer accordingly; for unknown preferences or decisions not yet authorized, ask the user and wait for a reply. Permission requests are likewise handled according to the user's existing authorization and host restrictions.
- The session ID, host command process ID and JSON-RPC request ID each serve different purposes. Use the session ID to continue a task, the process handle provided by the host to read/write a long-running process, and the original request ID to answer a question.
- When the send result is unclear, the process disconnects, or the request times out, first verify the session record and current state; do not automatically resend the task, repeat the answer, or create a replacement session.
- Session records, events and tool output may contain code or sensitive information. Only read and relay what the task requires; do not output credentials, and do not put credentials into prompts or command parameters.
Installation methods, parameters and protocols may change with versions; rely on the local --help and Droid CLI documentation.
When the user explicitly requests installation, on macOS you may use brew install --cask droid, or use npm install -g droid. The npm version does not auto-update by default; after installation check droid --version, and have the user log in as needed.