non-coding-skills

AI Builder Academy's brand and design system — colors, typography, voice/tone, components, icons, and copy patterns for aibuilder.academy and any ABA-branded surface (landing pages, decks, one-pagers, social graphics, emails, motion graphics). Use whenever Shaw is designing, mocking up, or reviewing anything that should look or sound like ABA. Triggers: "design a landing page for ABA", "make an ABA mockup", "one-pager for [ABA offer]", "what colors / font does ABA use", "ABA-ify this", "make this on brand", "what's the ABA voice", "design an ABA banner / hero / card / form", "slide template for ABA", "match the ABA homepage", "ABA infographic", "ABA animation". Also fire on any AI Builder Academy reference when the deliverable is a visual artifact (HTML, slide, image, mockup, SVG, React component, MP4, PNG) or copy that sits on an ABA surface. Casual mentions like "make it look like the ABA site" or "give this an aibuilder.academy feel" count too.

Shaw's strategic thinking partner for AI Builder Academy business decisions. Use this skill whenever Shaw is thinking through business strategy, customer avatars, market positioning, pricing, go-to-market plans, outreach strategies, offers, funnels, or any high-level business decision. Triggers include: "let's think through," "help me figure out," "strategy session," "who should I target," "what should I charge," references to avatars, ICPs, customer segments, offers, funnels, or any open-ended business planning conversation. Also trigger when Shaw is clearly brainstorming — talking through ideas conversationally, expecting Claude to be a concise sparring partner that grounds decisions in real data, asks sharp questions, and pushes back honestly. Even casual phrasing like "I've been thinking about," "what do you think of," or "help me decide" should trigger this skill when the topic is business-related.

Create, reschedule, and delete events on Shaw's Google Calendar — and keep the matching Notion page in sync when one exists. Use this skill whenever Shaw wants to put something on the calendar, move an existing event, or cancel one. Triggers include: "schedule X", "create an event for", "put X on my calendar", "book a call with Y next Tuesday", "set up a 1:1 with", "another session with X next Saturday", "follow-up call with X", "reschedule the X meeting", "move my X call to Friday", "cancel the X event", "delete that meeting", or any casual phrasing that implies adding/changing a calendar block (e.g., "let's do another one with [Client Name]", "block off Wednesday morning for the workshop"). Even when Shaw doesn't say "calendar" explicitly, this skill should fire if the request is about scheduling. This skill also creates a paired Notion page in ABA Calls or ABA Trainings when the event is a sales call or a delivery session and a paired page is part of the existing pattern.

Import or update skills in this public repo from Shaw's canonical skills repo at ~/agents/skills. Use whenever Shaw says "sync skills", "update the non-coding skills", "pull <skill> from canonical", "add these skills to the repo", or otherwise references moving his private canonical skills into this public repo. Handles PII scrubbing via parallel sub-agents, README table maintenance, and produces a clean commit. Do NOT use for creating skills from scratch (→ skill-creator) or one-off edits to a single already-imported skill.

Draft, sharpen, or diagnose copy whose job is conversion — landing pages, event registration pages (Luma), one-pagers, LinkedIn posts meant to sell, newsletters meant to sell, sales emails, and cold outreach DMs. Use whenever Shaw asks to write, rewrite, review, tighten, or critique conversion-focused copy. Triggers include "write the landing page", "draft the one-pager", "sharpen this headline", "tighten this newsletter", "rewrite this CTA", "write me a cold email", "outreach DM", "review this copy", "make this hit harder", "sounds like a brand wrote it". Also trigger when Shaw shares a copy draft and asks for review or rewrite, or casual phrasing like "help me write the promo". Applies Harry Dry's 3-question filter plus universal and channel-specific frameworks. Do NOT use for general LinkedIn posts (→ linkedin-post-writer), top-of-funnel essays (→ linkedin-post-writer or newsletter-writer), full sales letter structure (→ sales-letter-writer), or emails without conversion intent (→ email-helper).

Use this skill whenever Shaw mentions leads, contacts, sales pipeline activity, or anything CRM-related — even casually. Triggers include: "check my CRM", "update the CRM", "any updates on leads?", "add this person to the CRM", "review my pipeline", "follow up with X", "anyone worth following up with", "check active campaigns", "did anyone respond?", "cross-reference Gmail", "ABA contact form", or any mention of a specific lead's name in a sales context. Also triggers when Shaw shares new contact form submissions or inbound emails that look like potential leads. Also triggers for client/nurture activity: "check on my clients", "any clients due for check-ins", "move this lead to clients", "nurture review", or any mention of existing clients and expansion opportunities. Also triggers when a discovery call is booked — directly or surfaced during a sync. Follow-up reviews cover Active Leads, Clients (Nurture), AND any active campaign trackers linked from the CRM page.

Draft emails in Shaw's voice and handle any email-adjacent task. Use this skill ANY time Claude is composing or about to compose an email — drafting, replying, forwarding, or following up. The trigger is the next tool call: if it is `create_draft`, this skill should have been invoked first, EVEN when another skill (calendar-helper, crm, outreach, engagements, notion-helper, etc.) is already running and the email is one step in its workflow — skills compose. Also trigger for phrases like "draft a reply", "write an email to", "respond to this", "follow up with", or any reference to composing email; when Shaw shares an email thread and asks what to say; or when sharing a link to a Gmail thread (Shaw's account uses `u/1` — see Gmail Technical Notes). Casual requests like "shoot them an email" count too. Covers outreach, replies, follow-ups, declines, intros, and scheduling.

Use this skill whenever Shaw mentions creating, updating, querying, or wrapping a paid client engagement. Triggers include: "create an engagement for X", "X just paid the invoice", "log the engagement", "what's the engagement ID for Y", "wrap up [Client Name]'s intensive", "mark X as delivered", "X's session moved", "fill in Stripe data for E###", "update engagement status", "look up the engagement for X", "did X pay yet". Also fires for auditing/syncing the ledger: "audit/sync the engagements", "is the engagement data up to date", "reconcile E###", or the daily scheduled sync. Also fires when a CRM workflow signals "deal closed" (kickoff for a new row), or when a new ABA Trainings/Calls page needs linking to an existing engagement. This skill governs the Engagements database in ABA (Master) — the project ledger that tracks one row per won, invoiced project. The CRM (Nurture) database tracks the relationship; this database tracks the work.

Generate Shaw's daily executive briefing by pulling today's tasks from his main Notion databases. Use this skill whenever Shaw asks for his daily briefing, rundown, what's on his plate, what he has going on today, or anything about reviewing his scheduled tasks for the day. Triggers include: "give me my briefing", "what do I have today", "daily rundown", "executive briefing", "what's on my plate", "what's scheduled today", "morning briefing", "what am I working on today", or any reference to checking tasks across his Notion databases. Even casual mentions like "what's today look like" or "run me through my day" should trigger this skill.

Navigate Shaw's Google Drive (aibuilder.academy workspace) — search, read file contents, navigate known folders, and avoid the connector's quirks. Use whenever Shaw asks to find a file in Drive, read a Google Doc/Sheet/Slide/PDF, look in a specific folder, pull form responses, locate something he uploaded, or do anything Drive-adjacent. Triggers include "find X in my drive", "what's in the forms folder", "read this doc", "pull the responses for X", "is X in my drive", "search drive for X", "do I have a file about X". Even casual mentions like "where's that proposal I wrote", "the spreadsheet I made last week", or "look in Drive" should fire this skill. Also trigger when Shaw shares a Drive URL and asks to read it. Do NOT use for file *organization* (moving, renaming, batch operations).

Build single-image graphics — social infographics, blog/slide diagrams, doc figures — authored as HTML and rendered to a 2x retina PNG via a headless-Chrome pipeline included with this skill. An infographic is just one mode; an embedded figure for a blog post or slide is another. Use whenever the user asks to make, design, build, or render an infographic, LinkedIn post graphic, social-feed still, concept image, "graphic for [post idea]", or a diagram/figure for a blog post, slide, or doc. Triggers include "make an infographic for X", "design a LinkedIn graphic", "build a post graphic", "turn this Notion brief into a visual", "make a diagram for this blog post", "build a figure for a slide", "draw a flow diagram", or any reference to producing a still PNG from a designed composition. Defaults to a brand-agnostic light palette with Manrope / Libre Franklin / JetBrains Mono type. If the graphic is for a specific brand, reference the relevant brand-system skill (e.g. `aba-brand-system`) for colors/type/voice — pu

Read, create, and modify Apple Keynote (.key) presentations. Use when the user asks about .key files, wants summaries, needs to understand slide content, or wants to create/edit decks.

Pull and analyze LinkedIn post performance data using Chrome tools. Use this skill whenever Shaw asks to check LinkedIn analytics, review post performance, compare posts across time periods, find top/bottom performers, compute engagement rates, or do any kind of LinkedIn content analysis. Triggers include "check my LinkedIn analytics", "how did my posts do", "LinkedIn performance", "post engagement", "top posts this month", "compare Q1 vs Q2 LinkedIn", or any mention of analyzing LinkedIn post data. Also trigger when Shaw wants to evaluate content strategy effectiveness on LinkedIn, even casually like "which posts worked best" or "what's getting reach on LinkedIn". Also covers top-vs-bottom split breakdowns (halves by default, quartiles on request) and pulling complete post history (every post, exact metrics) via LinkedIn's feed API.

Draft LinkedIn posts in Shaw's personal writing style. Use this skill whenever Shaw asks to write, draft, brainstorm, or edit a LinkedIn post — including phrases like "write a post about", "help me draft a LinkedIn update", "turn this into a LinkedIn post", "post idea", or any reference to writing for LinkedIn. Also trigger when Shaw shares a topic, milestone, or idea and asks to "make it a post" or "write this up." Even casual requests like "can you LinkedIn-ify this" or "help me announce X" should trigger this skill.

Draft newsletters for Shaw's Kit list (The Data Entrepreneurs) in his exact voice and structure. Use this skill whenever Shaw asks to write, draft, edit, or repurpose a newsletter — including phrases like "write a newsletter", "draft a Kit broadcast", "turn this post into a newsletter", "weekly send", "newsletter idea", "make this a newsletter", "the next email to my list", or any reference to writing for his email list. Also trigger when Shaw shares a topic, milestone, framework, observation, or LinkedIn post and asks to "make it a newsletter" or "send it to the list." Even casual phrasing like "what should I send this week" or "I want to write something to my subscribers" should trigger this skill. Covers both content/teaching newsletters and sell newsletters — for deep conversion-focused diagnosis on a sell email, hand off to `conversion-copy` after the draft is in place.

Navigate Shaw's Notion workspace and create ad hoc tasks, follow-ups, and reminders across his databases and pages. Use this skill whenever Shaw asks to add a task, schedule a follow-up, create a reminder in Notion, add something to his plate for a specific day, drop a note into one of his databases, or find/reference pages in his workspace. Triggers include: "add a task for X", "create a FU for tomorrow", "put this on my plate for Monday", "add this to ABA", "remind me to follow up with X in Notion", "make a note in Notion to…", "find me the page about X", "link the call page to Y", or any ad hoc Notion creation/navigation that isn't already covered by a more specific skill (CRM, executive briefing, SOPs, etc.). Also trigger when Shaw asks to create follow-up tasks after calls, workshops, or meetings — those belong in ABA as dated task pages. Even casual mentions like "throw a reminder in Notion" or "add this to my list for Friday" should trigger this skill.

Run 1:1 outreach campaigns end-to-end — sourcing the list, enriching it, triaging into segments, setting up a Notion tracker, drafting templates, sending, and logging responses. Use this skill whenever Shaw is building a list of people to reach out to, setting up outreach tracking, or crafting the messages themselves. Triggers include: "find people on LinkedIn", "pull my connections", "build a lead list", "enrich this CSV", "look up where these people work", "get company sizes", "set up outreach", "create an outreach table", "add people to the outreach list", "who have I reached out to", "update outreach", "write me an outreach message", "draft a DM template", or any time Shaw shares a batch of names he's reaching out to. Also casual phrasing like "check my LinkedIn for analytics people", "I texted these 5 people", "add them to the list", "what should I say to these people". Covers workshops, events, research calls, partnerships, and any 1:1 outreach initiative.

Do pre-call research for an upcoming call — a discovery call, a paid 1:1 Claude Workshop, a post-session or nurture check-in call, or a multi-session engagement wrap-up call. Use this skill whenever Shaw asks to prep for a call, do pre-call research, or gather context before any conversation — including phrases like "do pre-call research for X", "prep for my call with X", "I have a call with X today", "what should I do to prepare for X's call", or any reference to preparing for an upcoming call. Also trigger when Shaw mentions a specific person's name alongside a scheduled call. Even casual mentions like "call with X later" or "meeting with X, what should I know?" should trigger this skill. Also invoked by CRM Workflow 7 (Discovery Call Intake) to create and populate the ABA Calls page for a freshly-booked discovery call. Covers prospects, active clients, and past clients alike.

Build a clean, on-brand client proposal deck for Shaw / AI Builder Academy — the short "proposal in slide form" a prospect or partner asks for before an AI training or workshop engagement. Use whenever Shaw is assembling a proposal, pitch, or offer deck for a specific client (AI training, 1:1 Claude workshops, team workshops, a multi-session engagement), or says things like "make a proposal deck for X", "put the proposal in slides", "pitch deck for the [client] engagement", "turn this offer into a deck", or shares a client context and asks for a proposal. Also fire for a partner subcontract or enterprise buyer asking for a standard proposal deck, or when Shaw references the three-slide arc (executive summary, impact / case studies, transformation roadmap). Defaults to three slides but extends as needed. Composes with the aba-brand-system and pptx skills. Do NOT use for general slide decks unrelated to an ABA offer, long-form sales letters (use sales-letter-writer), or one-pagers (use conversion-copy).

Manage Shaw's referral workflow — create rows in the Referrals database, follow up on referral asks, log names a referrer shares, hand new intros to the CRM, and trace referred leads back to their referrer. Use this skill whenever Shaw mentions a referral — "did [Person] send those names?", "follow up on the referral ask", "log this intro", "kick off a referral ask for X", "who owes me referrals?", "sweep the referrals", "X just intro'd me to Y", "thank X for the referral". Also fires when a wrap-up call or testimonial publish surfaces a referral opportunity, when a 3-way intro email lands in Gmail (subjects like "[Name] x Shaw"), or when a client says "I know some people who'd want this". Trigger words: referral, intro, three-way intro, warm intro, "know anyone who". Do NOT use for the SOP itself (sop-helper), generic CRM work (crm), or testimonial asks (testimonials).

Strategy-aware LinkedIn content ideation for Shaw's SFC pipeline. Researches recent client call transcripts, the CRM, and post analytics, surfaces the concrete raw material (quoted pains, aha moments, honest numbers), turns it into hooks on request, proposes a week's lineup, and on approval creates SFC database pages as briefings. Also works a single existing SFC page end-to-end: count or develop its hooks, then draft into it. Use whenever Shaw wants LinkedIn post ideas, asks 'what should I post', wants to plan or fill his content calendar, wants hooks for a specific post idea, or wants to turn strategy/analytics findings into scheduled posts. Trigger even when he doesn't say 'SFC' (e.g. 'brainstorm posts', 'plan my week of content', 'what's worth posting', 'how many hooks for this idea'). Do NOT use for drafting the full text of one post (use linkedin-post-writer) or analyzing past performance (use linkedin-post-analytics); this is the ideation and scheduling layer between them.

Update and improve existing skills based on conversation feedback. Use when the user asks to update a skill, improve a skill, or reflect on what was learned in a conversation to improve a skill. Also use when the user says things like "update the skill", "the skill should know about this", or "add this to the skill."

Shaw's house format for any multi-item summary, digest, briefing, status report, roundup, or a staged plan/roadmap he'll skim. Use whenever Claude presents several items across categories — scheduled-task reports, "give me a rundown," "catch me up on X," "summarize my inbox/Slack/calendar/leads/pipeline," research roundups, sync results. Render as: a dated H1, a one-line count dashboard, emoji-headed sections with one-sentence linked items, every section always shown with an empty-state line, and a "🔴 Needs Your Attention" action closer. This is the DEFAULT presentation for digests to Shaw — apply it even when he doesn't name a format, and especially when he asks to make something "easier to skim," "more scannable," or "match my format." When a task supplies its own section map, keep this frame with those sections. Do NOT use for single facts, one-item lookups, conversational replies, code, or long-form prose (reports, essays, letters, docs).

Handle Shaw's Stripe operations — creating and sending invoices, generating payment links, and pulling reporting data (balance, recent payments, customer history). Use this skill whenever Shaw mentions Stripe, invoicing a client, billing someone, sending a payment link, checking what someone has paid, or any reference to charges, refunds, or revenue activity. Triggers include "send X an invoice", "bill X for Y", "create a Stripe invoice", "make a payment link", "how much did X pay", "what's my Stripe balance", "did X's invoice go through", "void this invoice", "refund X", "check my Stripe", or any casual phrasing like "throw an invoice on the books for X". Even when Shaw doesn't say "Stripe" explicitly — anything about billing a client, generating a paid link, or looking up payment history — this skill should fire.

Manage Shaw's testimonial workflow — create rows in the Testimonials database, polish form submissions into pull-quotes, advance status through the lifecycle (Asked → Form Submitted → Approved → Published), and surface rows that need a follow-up nudge. Use this skill whenever Shaw mentions a testimonial — "did [Client Name] approve?", "polish [Client Name]'s response", "draft a testimonial from [Client Name]'s form submission", "kick off testimonial asks for the [Company] team", "check which testimonials are stuck", "publish [Client Name]'s quote on the site", "process the new form submissions". Also fires when a training wraps and a testimonial ask should be queued, or when Shaw says he's ready to publish. Trigger words: testimonial, pull-quote, review, social proof, form response from a client. Do NOT use for the SOP itself (sop-helper), generic CRM work (crm), pre-call context (pre-call-research), or referral asks (the Referral Ask SOP covers that).

Draft AI training proposals and outlines from unstructured notes, convert markdown proposals to branded PDF, read existing .pdf proposals for reference. Covers client proposals, training outlines, workshop syllabi, bootcamp outlines, course proposals, session agendas, curriculum design, pricing quotes, and scoping for AI Builder Academy (ABA).

Edit a single video for Shaw's YouTube channel by transcribing it, planning cuts with a multi-agent pipeline, writing an EDL JSON, and generating an FCPXML project file for Final Cut Pro. Use when the user asks to edit a video, cut a voiceover, or produce an FCPXML from a raw recording. Never renders or overwrites the original video file.

Turn a pain point, topic, or rough idea into a compelling YouTube package — title, thumbnail, intro hook, motivation/story, outro, and video description — for Shaw's channel. Use any time Shaw is writing, brainstorming, or iterating on YouTube content. Triggers include "title ideas", "punch up this title", "thumbnail ideas", "design the thumbnail for X", "package this video", "write the intro/hook", "draft the motivation", "write the outro", "iterate on the script", "Ed Lawrence-style intro", "write the (YouTube) description", and casual mentions like "title this for me", "thumbnail this", "I'm making a video about X", or "help me write the open". Do NOT use for LinkedIn posts (use linkedin-post-writer), newsletters (use newsletter-writer), or sales copy (use conversion-copy or sales-letter-writer) — this skill is specifically for YouTube packaging and scripting.

Build short motion-graphic animations (1–6 seconds) as B-roll overlays for talking-head YouTube videos — icon morphs, label fade-ins, diagrams that draw themselves, side-by-side comparisons, simple flow charts. Use this skill whenever the user asks to create, design, or render an animation, motion graphic, B-roll clip, explainer overlay, or any short visual that needs to be exported as an MP4. Triggers include "make an animation for X", "build a motion graphic", "I need B-roll for this script", "animate the [icon/label/curve/flow]", "render this as a video", "create a short clip that shows X morphing into Y", or any reference to producing a video file from a designed animation. Also fire when the user pastes a video script that contains `[ANIMATION]` callouts and asks to build them. Each animation is authored as a self-contained HTML file (CSS/SVG animations) and rendered to MP4 via a Playwright + ffmpeg pipeline included with this skill. Defaults to Heroicons outline icons. If the animation is for a specific

Run Shaw's skills-sync tool to publish user-created skills from Claude Desktop to the canonical git repo, Codex, and Claude Code. Use whenever Shaw asks to sync skills, run skills-sync, publish a new skill, push a skill to Codex or Claude Code, mirror skills across runtimes, check skills-sync status, see what's in the canonical repo, or remove a skill from canonical/targets. Triggers include "sync my skills", "run skills-sync", "push this skill out", "publish my new skill", "mirror skills", "skills-sync status", "what's in my canonical skills repo", "how did the last sync go", "remove X from codex", "drop X from canonical". Even casual mentions like "push that skill" or "update codex with my new skill" should trigger this skill. Do NOT use for creating or editing skills — that's skill-creator / skill-updater. This skill only runs the sync tool.

Create, update, and reference Shaw's standard operating procedures (SOPs) in Notion. Use whenever Shaw wants to turn a process into an SOP, update an existing one, or pull up an SOP to reference or walk through. Triggers: "write/update/fix the SOP for X", "document this process", "turn this into an SOP", "where's the SOP for X", "walk me through the SOP", or any reference to the SOPs page. Also trigger when Shaw describes a repeatable workflow and says "let's save this" or "this should be written down", or casual phrasings like "I keep redoing this, make it an SOP" or "we need a playbook for X". Also load at the start of any SOP-adjacent reasoning — proposing template edits, comparing sent mail to existing templates, or sketching SOP changes. Don't wait for the actual edit; if you're reasoning about what an SOP should say, the skill should already be loaded. Do NOT use for one-off tasks — those go through `notion-helper`. SOPs are for repeatable processes, not single to-dos.

Walk someone through building their first (or next) high-leverage Claude skill, end-to-end. Gather context silently, diagnose their level, run a time study, score time-vs-complexity for their level, suggest 3-5 candidate skills, hand off to skill-creator, and close with a one-line opt-in CTA to share what they built with Shaw. Use whenever someone is figuring out what skill to build, what to automate, or where to start with skills. Triggers include "help me build a skill", "what should I automate", "where do I start with skills", "I don't know what to build", "walk me through my first skill", "help me find a skill to build", "what's worth automating", "give me skill ideas", "what's a good first skill". Also fires when someone shares a calendar or workflow and asks what's automatable, when a new Claude user wants guided onboarding to skill-building, or when an experienced builder is hunting higher-leverage targets. Casual phrasing like "I should probably automate something" counts too.

Draft long-form sales letters and one-pagers for Shaw's offers (intensives, workshops, courses, productized services) using Hormozi's $100M Offers principles. Use this skill whenever Shaw asks to write, draft, or iterate on a sales letter, one-pager, offer page, landing page copy, sales page, "offer brief," or any long-form copy designed to sell a specific paid offer. Triggers include "write a one-pager for X", "draft a sales page for my new offer", "help me write the sales letter for my [intensive / workshop / cohort / program]", "turn this offer into a sales page", or any time Shaw is putting together written copy whose job is to sell a specific package. Even casual mentions like "I need to write up my new offer" or "let's put the offer in writing" should trigger this skill. Do NOT use for short-form content like LinkedIn posts, tweets, or newsletters (use linkedin-post-writer or newsletter-writer instead) — this skill is specifically for long-form sales copy that walks a buyer from headline to CTA.

Research and brainstorm practical use case ideas for custom AI workshops and training proposals. Use this skill whenever Shaw is preparing a workshop, training session, or proposal for a client and needs to identify relevant use cases for a specific audience. Triggers include: "brainstorm use cases", "what use cases should I cover", "help me prep the workshop for [company]", "I need use case ideas for [role/audience]", "research topics for the training", "what should I demo", or any reference to building out a custom workshop or training proposal. Also trigger when Shaw mentions a specific client engagement where the deliverable is a training session, workshop, or enablement program. Even casual mentions like "what should I teach them" or "I need to figure out the use cases for this one" should trigger this skill.