Independent creative technology studio
AI SKILL.md you don’t know about
Ten episodes. Eight repos. All real — these are the actual files my studio runs on today, complete, with only my private values swapped for named placeholders. Clone one, install it in your harness, then change every line to be about you.
“A prompt is a request. A file is a standard. The request is gone next session. The file gets read every time.”
My AI wrote “I’m excited to announce” and three rocket emojis. I never told it who it worked for.
Write down who you are, how you sound, what you always do, and what you never do — then make the model check its own work against it.
It nearly tagged a bar in Covington, Louisiana in a post about a cafe in Milwaukee. Same name, wrong business, 1,000 miles away.
Keep a registry of verified handles. If an account isn't in it, name the business in plain text instead.
It invented “over 10,000 creatives in Milwaukee.” There was no source. It made the number up.
Write down who you are, how you sound, what you always do, and what you never do — then make the model check its own work against it.
Every reel moved slightly differently. Nothing was wrong in any one of them, and the set still looked amateur.
Write your timings down once as a table, then render from the table — not from memory.
An AI host on my radio station started inventing station history live on air.
Put the canon in one file and make the rule explicit: if it isn't in this file, it didn't happen.
I kept catching the same four mistakes by hand, one post at a time, forever.
Write down who you are, how you sound, what you always do, and what you never do — then make the model check its own work against it.
Publishing one event meant filling the same form by hand every time. An hour per event.
If you do it the same way twice, write the file that does it. The API was always there.
Someone bought a ticket at 2am. I found out the next morning, by exporting a spreadsheet.
Let the other service tell you. A webhook is a file that listens while you sleep.
My content calendar was a subscription I paid for and still filled in by hand.
Make the calendar an API your AI can call. Then the month fills itself.
I recorded narration by hand, and the takes never matched from one reel to the next.
Put the gotchas in the file's own header. A comment you wrote once is cheaper than learning it twice.
A hand-written list of the app’s own building blocks went stale and was missing four real ones — so the model refused to build rooms the app could already draw.
Do not put facts in a skill file. Put the address of the facts, and the address of the checker. This one teaches a model to write for GM Spaces without listing a single word of the language.
Entries die on the settings, not the build — a submission with the count switched off cannot be voted for, and nobody finds out until the counting starts.
A skill can carry the checklist a person has to tap by hand. It asks the eight questions, writes the four beats, and hands back the settings it cannot set for you.
Steps from the show
Every episode of AI SKILL.md you don’t know about, as it aired: the command typed and the file printed on screen, ready to paste. Newest first. This is the link in the bio.
Loading the episodes…
Install
For Claude Code (or any harness with a skills folder), clone straight in — the description line in the frontmatter tells the model when to fire it:
git clone https://github.com/crafty-arl/skillmd-voice-file.git \ ~/.claude/skills/gm-linkedin-post
Other tools: paste the body into AGENTS.md, CLAUDE.md, or your custom-instructions box. Then make it yours — keeping my lines gets you my voice, which is not the point. MIT licensed, all of it.