Usage tips
Kimi Claw isn't just a Q&A tool — it's a moldable assistant. Set the rules and it adopts a new personality. Teach it a method and it forms a habit. Give it a schedule and it keeps you on track.
Customize the persona
You can reshape how Kimi Claw communicates with a single instruction. Think along three dimensions:
Example prompts:
- "From now on, your name is Claw. You're my research assistant. Start every reply with a one-sentence summary."
- "Reply in three parts: conclusion first, then reasoning, then actionable next steps. Be concise."
- "You are a rigorous investment analyst. Flag uncertainty in every conclusion and include one risk note."
Learn skills from ClawHub
Kimi Claw has a built-in ClawHub skill library. Before building a workflow from scratch, have it search for a ready-made Skill — think of it as installing a purpose-built module.
Send /skills in a conversation to browse and manage installed skills.
Good use cases for Skills:
Example prompts:
- "Find a competitive analysis Skill, install it, then walk me through the required inputs."
- "Search for a Skill that pulls stock market data, then run an analysis for me."
- "When you compile market updates, follow this structure: Opportunities / Risks / Data, then one action item."
Set scheduled tasks
Kimi Claw can run tasks on a schedule — turning it into a daily reminder engine and information radar.
For best results, include three things in every scheduled task:
- When — A specific time (daily at 9:17 AM, every Monday, etc.)
- Output format — Bullet points, table, template, word count, language
- Constraints — Max length, required sections, language, risk disclaimers
Template:
At [time], do [task], output as [format], following [constraints]. Examples:
- "Every day at 9:17 AM, summarize the latest market news: 3 key points + 1 risk note, under 200 words."
- "In 1 hour, remind me to finish my daily report and attach a four-section template."
- "Tonight at 10:32 PM, remind me to shut down, wind down, and get ready for bed. Keep it friendly."
Tip: Schedule tasks at non-round times (e.g., 9:17 instead of 9:00) to avoid peak-hour congestion and reduce execution delays.