Three ready-made skills. Copy one, adapt the bracketed parts to your business, and run it with your foundation file. They are starting points: the more you edit them toward how you actually work, the better they get.
Turns one real observation from your week into a post in your voice. No engagement-bait formats.
# SKILL: LinkedIn post from a real moment *Instruction file for AI. Use together with FOUNDATION.md.* ## How to use this file Give your AI the FOUNDATION.md first, then this file, then your input for the day. ## The job Write one LinkedIn post from a real moment in my work week: a client question, a mistake, a decision, something I noticed in the market. ## When to use [e.g. Twice a week, Monday and Thursday] ## Inputs required One real moment, described in 2-5 rough sentences. What happened, what I thought, what I would tell someone in the same spot. ## Steps 1. Find the one insight in my notes worth a reader's time. If there are two, pick one and say the other is for another post. 2. Open with the concrete moment, not the lesson. No "I've been thinking a lot about..." openers. 3. Keep my telling of it honest: what I got wrong stays in. 4. Close with the practical takeaway in one or two sentences. A question to readers only if it is genuine, never as an engagement tactic. ## Output format Under 200 words. Short paragraphs, one idea each. No hashtags unless I add them. No emojis. Line breaks for rhythm, not decoration. ## Quality rules - Sounds like me talking to one smart peer, not broadcasting to a feed. - Specific beats general: names of situations, not categories. - Never: hooks that overpromise, "unpopular opinion:", numbered listicles of obvious advice, fake vulnerability. - Follow the voice and hard rules in FOUNDATION.md. - Never invent facts, clients, or numbers. If information is missing, ask. --- *From the NYCScale client portal.*
Forces the thinking before the writing: who it is for, why now, what it must say. Ten minutes that saves an hour.
# SKILL: Content brief before you write *Instruction file for AI. Use together with FOUNDATION.md.* ## How to use this file Give your AI the FOUNDATION.md first, then this file, then your topic idea. ## The job Turn a rough content idea into a one-page brief that makes the piece easy to write and worth writing, or tells me honestly that it is not. ## When to use Before writing anything longer than a social post: newsletter, article, talk, lead magnet. ## Inputs required The rough idea in a sentence or two, plus where it will be published. ## Steps 1. State who exactly this is for, in one sentence, drawn from the customer section of FOUNDATION.md. 2. State why they would care this month, not in general. If there is no honest answer, say so and suggest a sharper angle or recommend dropping it. 3. Write the one-sentence takeaway a reader should leave with. 4. List 3-5 points the piece must cover, in order, with the strongest first. 5. List what to deliberately leave out (the tangents that would bloat it). 6. Suggest a working title that is plain and specific, plus one alternative. 7. Note how the piece connects to the current focus in FOUNDATION.md, and what the reader should be invited to do next (one step, low pressure). ## Output format One page maximum. Headed sections matching the steps. Written as instructions to the writer, not as the article itself. ## Quality rules - Honest: if the idea is weak, the brief says so before I spend an hour writing. - The takeaway must be something the reader can use without hiring anyone. - Follow the voice and hard rules in FOUNDATION.md. - Never invent facts, statistics, or examples. If information is missing, ask. --- *From the NYCScale client portal.*
Runs any draft (page, post, pitch, email) against your positioning and flags where it drifts generic.
# SKILL: Positioning check on anything *Instruction file for AI. Use together with FOUNDATION.md.* ## How to use this file Give your AI the FOUNDATION.md first, then this file, then the draft to check. ## The job Check a piece of writing against who we are, who we serve, and how we sound, then report what drifts and how to fix it. Review only: do not rewrite the whole piece unless asked. ## When to use Before anything customer-facing ships: website copy, a proposal, a post, an important email. ## Inputs required The draft, pasted in full. Optionally: where it will appear and who will read it. ## Steps 1. Swap test: could a competitor put their name on this and have it still be true? Quote the sentences where the answer is yes. 2. Customer test: does it speak to the customer described in FOUNDATION.md, or to a vague "everyone"? Point to the evidence. 3. Voice test: flag every phrase that breaks the voice or hard rules in FOUNDATION.md, including buzzwords and claims we cannot back. 4. Focus test: does this piece serve the current 90-day focus? If it serves nothing, say so plainly. 5. For each flag, give a rewrite of that line only, in our voice. 6. End with a verdict: ship it, fix the flags first, or rethink the piece. ## Output format Short report: the four tests as headings, quoted lines with fixes underneath, verdict at the end. No praise padding. ## Quality rules - Quote the actual text; never flag in the abstract. - One honest verdict, not a hedge. - Follow the voice and hard rules in FOUNDATION.md. - Never invent facts or claims in suggested rewrites. If information is missing, ask. --- *From the NYCScale client portal.*
Adapted to your business and run consistently, they change your output within a month. Built around your actual strategy, they change the business. That second part is what we do.
Let's talk