(and a small change to how we run these) Hello everyone!! 👋 First, the honest bit. This one is landing later than Monday, and on purpose. Two things got us here. One, a lot more of you are submitting now. If I am going to really sit with every entry and give it a proper look, a weekend is not enough. This round I went through all of them, watched the videos, opened the repos, the full pass. That takes time and I would rather do it right than rush it. Two, I could feel a few of you running hot. Weekly is a sprint, and burnout was starting to creep in for some. So we are moving to bi-weekly. More room to build, more room to breathe, and the time for me to actually review the work the way it deserves. 🎥 Quick word on the videos. They were a step up this round. Some of the animated walkthroughs and live demos were a genuine pleasure to watch, and yes, I weigh them. A clean demo that shows the thing actually working makes a real difference. However I don't want that to ALWAYS be a requirement. Also you will notice the Heavy hitters that you usually see up here are not currently, some posted late and I decided to let the new entries and first timers also have a chance as well! But certainly, check the original post as every submission has something for you to learn from : 💰 Competition 7 ➖➖➖ 🛠️ A FEW THAT STOOD OUT (in no order, and if you didn't make it, it doesn't mean yours wasn't great) The Pipeline Operator — @Jayden Forshee Runs a whole sales pipeline. Paste a lead and it grades it, writes the outreach, and moves the card itself. The live board where you watch cards move on their own, sat right next to a normal chatbot, was one of the clearest ways anyone has shown what an operator actually is. https://github.com/griffainai/studio-pipeline-operator Board: https://pipeline-operator.vercel.app/board

🎟️ PRIZE: FREE SEAT IN THE LYCEUM 🎟️ Pick your cohort. Technical, Business, or Creator. Your call. ---- 🇬🇧 We're back. Good morning from London. 👋 Thanks for the patience last week. Jake and I needed a few days to breathe before London Tech Week kicked off, and you all responded with nothing but support. We don't take that for granted. Now let's get back to building. ---- 📋 THE CHALLENGE Build a folder-based AI operator that handles ONE operational workflow end-to-end. You pick the workflow. This week's deliverable is one operator folder that someone could drop into a Claude project and use to handle a real business workflow without babysitting. ---- 🎯 PICK YOUR WORKFLOW The workflow is yours. Pick something specific. Pick something you'd actually use. A few sparks to get you thinking: - 🎫 Customer support triage (which tier handles this ticket?) - ✅ Content review and approval - 📨 Lead intake and qualification - 💸 Refund request handler - 🤝 Partnership pitch evaluator - 🎙️ Podcast guest pitch sorter - 💼 Freelance project intake - 📄 Resume screen for one specific role - 📅 Meeting request triage (book, decline, delegate) The more specific, the better. "Customer support" is too broad. "Refund request triage for an ecommerce store doing under 200 orders per month" is right. 📎 If you want a fully written client brief as a reference, the attached PDF walks through one example. Don't build the example. Use it as a template for how to think about scoping your own operator. ---- 🗂️ THE METHODOLOGY If this is your first comp, welcome. Here's what you need to know: This week (and every week) you're learning interpretable context methodology. Folders as architecture. Each file does one job well. Your operator is a folder with five things: - 📄 identity.md (who the operator is and what workflow they own) - 📐 rules.md (the decision logic: criteria, edge cases, escalation rules) - 💬 examples.md (decisions in action, including at least one edge case) - 📚 reference/ (checklists, templates, rubrics) - 📖 README.md (how to use it)

💰 $325 CASH PRIZE 💰 That's a full year of Premium. Win this and your membership pays for itself. 📋 THE CHALLENGE You just got hired again. Different client this time. Meet Sarah, a freelance copywriter who's drowning in context-switching. 📎 Download the full client brief attached to this post. Short version: She works with three types of clients (SaaS founders, ecommerce brands, local service businesses) and starts from scratch every project. She doesn't need another tool. She needs a system. Your job is to build her a folder-based AI specialist she can drop into any Claude project. The folder IS the deliverable. 🗂️ THIS WEEK YOU LEARN ICM Up until now, comps have been "build a thing." This week you utilize the methodology taught throughout the community. 🧠 Folders as architecture. That's it. That's the whole concept this week. Your specialist is a folder with five things: - 📄 identity.md (who they are) - 📐 rules.md (how they respond) - 💬 examples.md (what good looks like) - 📚 reference/ (source material) - 📖 README.md (how to use it) Drop the folder into a Claude project. Claude becomes the specialist. Reusable. Shareable. Portable. 🎯 PICK YOUR SPECIALIST Don't pick copywriting. That's Sarah's example. Pick something YOU would actually use. A few sparks to get you thinking: - A salary negotiation coach - A meal planner that knows your dietary restrictions - A code reviewer for your stack - A real estate market analyst for your city - A technical recruiter screener - A grant writer for nonprofits in your space The more specific, the better. "Marketing expert" is not a specialist. "B2B email expert for enterprise SaaS targeting CFOs" is. 💼 WHY THIS ONE LANDS ON YOUR RESUME Real talk. Winning a comp in a Skool community doesn't get you a job by itself. But shipping a working folder-based AI specialist with a clean README and a public repo? That's a portfolio piece.

14 likes. Most in the comments. Community voted, and @Ian Barriopedro took it. $200 cash. Yours. Check out his entry here: https://iatoba72.github.io/ruffcuts/ He didn't just write a brand voice doc. He built a site for it. Structured the whole thing so anyone Dana hands it to can actually use it. That's the bar. For everyone who entered, real talk: the quality across the board was strong. This was a tight vote. If you didn't win this round, you've got another shot coming. What's next: Comp #2 drops soon. Heads up though, we said it in the rules and we meant it. The challenges get harder from here. More creative. More technical. This first one was the warmup. If you're a free member watching from the sidelines, this is your sign. Premium and VIP only for comps. $200 cash up for grabs every week or a free lyceum entry!! @Ian Barriopedro , congrats. Dm me so I know where to send the cash. Everyone else, get ready. Next one's coming!!

This week @James Mackellar took the whole thing! Mayston is a research partner for UK neurophysios prepping stroke-rehab CPD. That's the kind of work where you walk in ready for the pushback or you don't walk in at all. So Mayston holds the debate for you. It won't open the discussion until it knows your current teaching position, it keeps the rival treatment schools apart so they don't blur into mush, and it hedges every claim on the GRADE evidence scale. Deepest folder in the comp. But here's why it won. This is productionize your opinion all over again. Mayston is built on a working UK physio's decades on the frontline. His dad. The follow-up calls are logged right there in the repo. James didn't research a persona, he built his father's life work into a tool, then shipped it like a launch. Landing page, a 60 second overview, a full walkthrough, annotated diagrams. Same lesson as last week, said a little different. YOUR expertise is the value. And when it's close to home, a son building his dad's craft into something other clinicians can actually use, you feel it. People trust that. You stay passionate because you care whether it's right. That's the whole game. - 📺 60-second overview: https://youtube.com/shorts/uDZyiZ-aD8w - 📺 Full walkthrough: https://youtu.be/gzHoSpZPWS0 - 💬 https://mayston.pages.dev - 🔗 https://github.com/JamesMack05/mayston 🎯 Honorable Mentions Six builds, no particular order, that made this so hard to call. 🇳🇱 @Arjen Stet , Lex Dutch worker-classification law, built for the exact enforcement wave the Belastingdienst just restarted. What got me, it refuses to cite a court ruling it hasn't verified, so no made up ECLI numbers, and it splits the sources that lead (statute, the High Council) from the ones that only signal (blogs, tax-authority posture). Every conclusion gets labeled settled, in motion, or not-yet-law. Bilingual EN/NL readme so the rest of us can follow it, plus a short intro video. This was my runner-up, and it was close.