Before we start

A skill is a file of instructions.

Before you build

Two questions pick the way.

Question one

Does the work, or checks the work?

Finished work · reverse engineer it

Show it the work. It finds the pattern.

Finished work · the look

Pixel for pixel.

Your best deck

Methodically reverse engineer the design of this deck, pixel for pixel: fonts, colors, spacing, and the layout of each type of slide.

Then build a skill that makes every new deck look exactly like this one.

Finished work · longer writing

The doing skill. Then the checking skill.

The doing skill

Here are my last four board updates, and the notes and numbers each one came from.

Reverse engineer how I do this: my style and tone, how I structure it, and how I decide what to keep, what to cut, and what goes first.

Work out as much as you can on your own. Ask me only what you can't tell, one question at a time, five questions at most.

Then build a skill that works for any future update, not just these four.

The checking skill

Using what you learned from my board updates, build a separate checking skill.

It should review a draft update, written by me or anyone on my team, and list every place it doesn't match how I'd do it, with a suggested fix.

The steps you take

Do it once with the AI. Then save it.

The steps · once it's right

At the end of the chat.

Say this

Turn what we just did into a skill. Include the steps, the fixes I made along the way, and what the finished result should look like.

Keep it general so it works on next month's file, not just this one.

Every line should earn its place.

Your head

It knows your industry. It doesn't know you.

Your head · the interview

Let it interview you.

Say this

I want to build a skill for how I [review a proposal from a vendor]. Interview me to learn how I think about it.

Ask one question at a time, and let each answer shape your next question.

Focus on my judgment: what I look at first, what good looks like to me, and what a smart new hire would most likely get wrong.

Stop at 15 questions, or sooner if you have what you need. Then build the skill from what you learned.

Steps and judgment

Most real work is a mix. Get both.

A custom GPT · a project · a Gem · a process doc

Already built one? Convert it.

Already built · clean house

Convert it. Clean it up.

Say this

Here are the instructions and files from my [proposal GPT]. Turn them into a skill that does the same job.

Cut every line that doesn't change the result. Remove anything that only made sense for one client or one file, so the skill works for any future job.

When you're done, show me what you removed.

Whichever way you build it

Rules for every skill.

Where does the know-how live?

Recap

Finished workreverse engineer it
The steps you takedo it once, then save it
Your headlet it interview you
Something you builtconvert it, clean it up