Keep the method in a skill, and put run data in a git repo

If a skill keeps absorbing last week's calendar and results, it gets hard to reuse. On Oct 13 at 6:04 AM ET, sughanthans1 wrote that a tweet Bot on Grok Bot "keeps only the method in its skills," while "calendar, hook bank and post results go in a git repo it commits after every run," so "the skill stays reusable."

How to use it#

1. Leave the skill as the method only.
2. Point the Bot at a repo for living data.
3. End each run with a commit of new results.
4. Copy the skill to another Bot without copying the data tree.

Split my posting workflow: keep only the writing and review method in a skill named post-method. Put the calendar, hook bank, and post results in a git repo at ~/bots/post-ops. After each run, commit the new results with a dated message. Do not put run data inside the skill folder.

Good to know#

• This is one power user's pattern, not a staff recipe. We did not reproduce it on this desk.
• It pairs with earlier tips about saving a process as a skill, without stuffing every run into that skill.