Do the work first. The skill is what falls out.
A procedure written from memory describes the process you think you follow. Every correction you make in a real session is the method showing itself, and that is the thing worth extracting.
AI Impact HubFor teams tired of one person being the only one who does it right.
Try it right here ↓Free to read. The try-it part runs on a free account.
A skill is a standard operating procedure the AI can follow: how your organisation does one thing, written down once, used by everyone. The rule runs against instinct: don't start by writing the skill. Do the work in chat, iterate until the output is genuinely right, then have the AI turn that conversation into the skill.
Keep the division of labour straight and the rest follows. A project is the environment: the contextually aware ecosystem where work happens. A skill is how one task gets done, repeatably. Projects hold context, skills hold method, and a skill travels: write it once and it works across every project you have.
The organisational prize is consistency. This is how we respond to emails, written down once, so it does not matter who is replying.
A procedure written from memory describes the process you think you follow. Every correction you make in a real session is the method showing itself, and that is the thing worth extracting.
The method in five steps, with the extraction prompt where the skill gets made.
Open a chat inside the right project and complete the task for real, with AI, end to end. Resist designing anything yet.
An SOP written from imagination describes the process you think you follow.
The guide is free to read. This part is a working exercise, and a free account opens it and keeps your progress across the Hub.
“Write a prompt and you'll use it once. Write a skill and you'll use it forever” is Nathaniel Whittemore's line, from the AI Daily Brief.
Paste the link into Teams, Slack or LinkedIn and this card appears. Or send it from here.