Schedule a Bot that turns today's chats into skills

How this helps you

Wins from messy days become reusable skills instead of lost chat lore.

You are my skill distill Bot. Each night: (1) review today's chats and files in [projects], (2) propose at most three skill creates or updates, (3) sync approved skills to [repo], (4) reply with a short changelog. Never export secrets, cards, or Vault items. Ask before overwriting a skill that changed substantially.

What they did

In the follow-up advanced Chinese tutorial, after claiming a bot email and an 8pm news send, the creator runs a skill sedimentation assistant that inspects conversations and work experience, shows generated skills and file delivery rules, then configures sync to GitHub. Pages hold weekly reports and boards; a finder Bot retrieves them. No English captions, so details follow the published description and timestamps. Commenters discuss treating Grok Bot as a second self and ask about email approval taps. Keep the distill Bot off your heaviest daytime schedule so the retrospective does not compete with production routines for the same weekly pool.

Who it's for: Advanced builders who already use skills and feel knowledge dying in long threads.

Before you start

• A private GitHub repo for skills
• Permission for a Bot to read recent chats and write skills
• A quiet nightly window that will not collide with heavy jobs

How to try it

1. Create a specialist Bot whose only job is nightly retrospective and skill writing.
2. Give it read access to the day's project notes and a private skills repo URL.
3. Routine: every night at a fixed time, summarise what worked, draft or update skills, and open a short change list for you.
4. Require approval before overwriting a skill that differs a lot from the repo version.
5. Once a week, ask a finder Bot to confirm Pages and skills still match the live workflow.
6. After merge, smoke-test one updated skill on a throwaway chat before you rely on it in production Bots.

What to expect

After a messy outreach day, the nightly Bot proposes a "reply tone" skill and waits for your OK before pushing to GitHub.

Common mistakes

• Auto-pushing every chat quirk into skills without review.
• Storing secrets inside distilled skills.
• Running distill during peak work hours and doubling usage.
• Letting the distill Bot rewrite prompts for Bots it does not own without a human merge step.

Related tips

• Keep skills in a GitHub repo and sync them to your Bots nightly: One-line routines call skills; the skills live in a repo you edit elsewhere, and a nightly routine pulls them onto the Bots' computer.
• A 9-point upgrade audit for the skills you already saved: Your chief of staff checks every private skill for nine missing pieces, from when to use it to what happens if it runs twice, then drafts fixes for your approval.
• Do it by hand, save a skill, then schedule: Most automations break because they're scheduled before they've worked once.

Worth knowingWins from messy days become reusable skills instead of lost chat lore.

Learn more: How to Use Grok Bot: A Beginner's Guide (2026) · All Grok Bot skills tips