Read requests the owner placed in HTML共有くん from a phone and start them on this computer. Use when the user says /inbox, $inbox, or asks to pick up phone requests.
Scanned 9/4/2026
Install to Claude Code
npx -y skills add minorun365/html-share --skill inbox --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Inbox?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/minorun365-inbox)More formats (shields.io, HTML) on the badges page.
---
name: inbox
description: Read requests the owner placed in HTML共有くん from a phone and start them on this computer. Use when the user says /inbox, $inbox, or asks to pick up phone requests.
---
# Inbox
Use the `html-share` CLI. Do not call the review API directly and do not print device tokens.
## 1. Read waiting requests
```bash
html-share review inbox
```
- `requests` are unfinished owner requests, oldest first
- `target` is a project nickname the owner typed on the phone. It may be `null`. Treat it as a hint, not a filesystem path
- If the array is empty, say there are no inbox requests and stop
- If the CLI says this computer is not paired, ask the owner to tap "Macを登録" in the inbox and run `/mobile pair <code>`
## 2. Close every request you picked up, before starting
```bash
html-share review complete <id...>
```
- Close them all now. Do not wait until the work is done
- The inbox is a handover box, not a progress tracker. A request has no "in progress" state,
so anything left open looks identical to a request no computer has picked up yet
- Closing is not abandoning. Report progress and results in chat as usual
- Finish what you picked up in this session. If something has to wait,
say so in chat — it is no longer in the inbox to remind anyone
- Requests expire after 90 days, so do not leave them unread either
## 3. Identify the starting folder
Requests from a phone often belong to different projects. Do not start everything in the current working directory.
- Pull 1–3 distinctive words from the request text. If `target` is present, search for that nickname first
- Look in nearby README / AGENTS.md files. Do not keep a hardcoded map of nicknames to folders
- If the folder is the current working directory, start here
- If it is a different folder, start a new session there and tell the owner you did so
- If one request spans two places, start from the folder you will write to
- If you cannot tell, ask with 2–3 candidates. Do not guess from recency or a similar name
## 4. Start the work
Treat each request as a normal user instruction.
- If there is one request, start it without asking which to do first
- If there are several, list them in one line each with the folder you chose, then start from the oldest
- Still confirm before sending, publishing, deleting, or spending money
## Related
- `/mobile` is the opposite direction: send a PC task to the phone and wait for a reply
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!