Use OpenClaw with a company receiving number
Make Phonekit available in the OpenClaw workspace that performs your account task. Keep the number assignment stable across sessions and bound each receive attempt.
Install in the active agent workspace
From the workspace used by the intended OpenClaw agent:
npx skills add https://www.phonekit.io --skill phonekit --agent openclaw --copyOpenClaw loads workspace skills from <workspace>/skills. Follow its official skills guide for workspace precedence and host configuration. A skill placed in another checkout does not configure this agent's workspace.
Connect the worker, then name its assignment
Supply the scoped credential in the worker's configured environment, or perform the local CLI approval on that runtime. Confirm that it can read its selected number before scheduling account work. Keep the number's label and account owner in the workspace context.
The skill uses an authenticated Phonekit MCP connection when available and the CLI otherwise. OpenClaw's own runtime and tool policy determine whether the agent can run that command and operate the target application.
Make a recurring check actionable
Use the Phonekit skill to check the staging account assigned to this worker. Use the existing account and its named number. Capture the position before requesting a new sign-in code, wait within 120 seconds, and confirm the authenticated page. Report a changed outcome or a failure stage. If the service requests another approval or the code never arrives, stop this attempt and ask for a decision instead of repeatedly resending.
Completion record for the scheduled task
The account, check time, final application state and any next decision. Phonekit supplies the receipt; the host supplies the schedule and persistent task record.
Keep independent workers isolated
Give independently running workers their own receiving numbers, or serialize tasks using one number. A new session does not create a new inbox identity. Use the reliability guide to plan the receiving and account-state ownership together.
The skill installer above does not depend on a published ClawHub listing. A listing is a separate distribution step.
Questions you may have
Which workspace should contain the skill?
Use the active workspace for the agent that will perform the task. OpenClaw’s workspace configuration determines that directory. Put skills/phonekit/SKILL.md there and verify discovery in that agent’s session.
Does installing the skill grant inbox access?
No. Configure the worker’s Phonekit connection and explicitly select its readable numbers. The instructions and the credential are separate parts of setup.
Can one number support multiple scheduled workers?
Only with deliberate coordination when the same inbox receives indistinguishable requests. Give workers independent numbers or serialize the affected verification steps.
Why is there no ClawHub install command here?
This guide uses the skill installer in the active OpenClaw workspace. It does not assume a Phonekit listing has passed review or been published in ClawHub.