The finished document
A real deliverable — the status update, the synthesis, the report — with every claim marked against the material it came from, so you know what is safe to send before you send it.
Free while in early access
Everyone has AI. Almost nobody has a system for it.
Skillcraft AI is where professionals turn the work they redo every week into a written procedure that runs — and get properly good at AI while doing it.
Pick one thing you produce. Do it cold, see where it broke, fix it, keep the procedure.
About 30 minutes to your first document · No credit card · No certificates, real documents
If you use AI at work
Sound familiar?
You retype the same instructions into ChatGPT every Monday, slightly differently each time.
One written instruction you reuse, with the sources and the quality bar attached to it.
You skim the output, it reads well, and you send it. You are not really sure what it got wrong.
A check you wrote runs against every draft, and flags the claims nothing in your material supports.
Somebody asks how you made it and the honest answer is: I fiddled with it until it looked right.
A procedure on a page. You can hand it over, improve it, or run it in ten minutes.
After about half an hour
You walk away with two things
The procedure that produced it
Five lines you keep: what to attach, what to ask, what done means, what to check, and what never goes in. Set a cadence and it is waiting for you next week, on next week’s material.
Start with whichever costs you the most time
- A status update
- A research synthesis
- A report for executives
- A spec or a brief
- A digest someone else reads
- An analysis of numbers
How it works
You’ll do it badly first. That’s the method.
Nothing to work through before you start. You attempt real work, and whatever goes wrong picks the lesson you get.
- 01
Cold run
about 5 minutesDo the job with no help at all.
It finds your real edges in five minutes. Guessing at them takes weeks — and the gap it finds is what picks the one lesson you get next.
- 02
Repair
Your own sentences, marked where nothing supports them.
A number tells you how you did. A mark under your own words tells you what to change — and each one links to the single lesson that closes it.
- 03
Warm run
The same job again, with hints and a worked answer.
This is where the document actually gets made, and where you find out whether the fix took. Revise and resubmit as often as you like.
- 04
Keep it
10 secondsSave the procedure and say when it comes round.
This is the part you still have next Monday. Everything above it is proof the procedure works; this is what makes it come back.
What “see where it broke” means
Marked, not scored
A number tells you how you did. A rule under your own sentence tells you what to change — and which claim you should not have sent.
The team resolved most blockers this week1 and the migration is nearly done2.
Checkout latency is down to 310ms at p95, from 890ms3.
- 1. Nothing in your material says how many. Two of seven is “most” to nobody.
- 2. No date. “Nearly done” is what it said last week too.
- 3. Both figures trace to the latency dashboard. Send this one.
What a procedure is made of
Five parts. Only one of them is a prompt.
Prompt craft is the part that depreciates — every model generation absorbs more of it. The other four don’t get easier, and they’re where the work actually goes wrong.
- Sources
What gets attached every time — and what deliberately doesn't?
Without this you paste whatever is nearest and the model answers from nothing.
- Instruction
The prompt you send, every time.
A vague ask gets a fluent answer in the wrong shape, and you redo it by hand.
- Done
What must be true of the output before you'd accept it?
Written after you look, this is just a description of what you got.
- Check
What do you verify before any of this leaves the building?
Skip it and the invented number goes out with your name on it.
- Owner
Who is accountable, and what never goes in?
Nobody owns it, so nobody catches it — and confidential text leaks by habit.
01
02
03
04
05
And the learning half
7 paths and 36 lessons, handed out one at a time
You never work through a path first. Whichever part of a run goes wrong, the one lesson that fixes that part is what you get — about eight minutes, then straight back to the work.
- AI Foundations for Professionals
- Prompt Craft: From Vague to Precise
- Verify & Trust AI Output
- Automate Your Week
- Directing AI Work
- AI-Powered Product Thinking
- AI for Marketers
Plus guided walkthroughs, on real material
8 screens · 14 min
Raw notes to product bets
Three contradictory user interviews and forty minutes before a roadmap review. Produce a memo where every claim traces back to a quote.
6 screens · 12 min
Audit a shaky report
An AI-drafted investor update with invented numbers in it. Find them, prove they are wrong, and rewrite it before it reaches the board.
5 screens · 10 min
Weekly status in ten minutes
Scattered team updates into a status email your VP will actually read, ending with the prompt you reuse every Monday after.
Looking at this for a team? There’s no team plan yet — each person builds their own procedures, and you compare how you each do the same job.
Questions, answered
Your first working procedure is half an hour away
One job you already do — done cold, repaired, and turned into five lines you keep.
Build your first one