Claw Me for Kimi Claw

Prompts for Kimi Claw

I use Kimi Claw. Follow https://claw.me/plugins/kimi-claw and the verified shared claw-me skill. Check this environment’s supported tools before installing anything. Reuse an existing authorized connection if available. Request only the permissions needed for my task and complete Claw Me owner authorization. Never ask for secrets in chat. Verify an available read-only operation and explain any unsupported connection instead of claiming success.

Turn this conversation into a project handoff with decisions, open questions, and next steps. Save privately to Claw Me if authorized tools are available; otherwise prepare the files and explain the missing connection. Follow the verified claw-me skill, request only necessary access, and never put credentials in chat.

Let the owner approve the connection

Claw Me uses its own review screen. The client can ask for access, but it cannot approve itself or quietly add permissions.

1. 01

   Check that this environment supports secure HTTPS or remote MCP access before requesting account access.

2. 02

   Reuse a suitable existing connection or follow the shared skill’s device authorization. Review the Agent identity and permissions in Claw Me.

3. 03

   Store the issued credential in supported secret storage, outside chat and project files.

Prove the boundary before real work

A clean connection is not enough. Verify discovery, read-only access, and an approval-required action before relying on the setup.

1. 01

   Confirm the client can reach Claw Me through its approved transport.

2. 02

   Inspect the granted permissions and perform an available read-only operation. Read the Agent Guide only when access is granted.

3. 03

   Prepare a private test output and verify the intended visibility before relying on the connection.

Common connection issues