User
Write something
Pinned
Welcome to Clief Notes. Here's where to start.
1. Watch the intro video and introduce yourself in the intro post here 2. Start with The Foundation (free course). Concepts, folder architecture, prompting framework. Everything else builds on this. 3. Check in at the bottom of each lesson. Polls, discussion posts, other members working through the same stuff. Use them. 4. When you're ready to build real things, move to Implementation Playbooks (Level 2). When you're ready to build your own tools, Building Your Stack (Level 3). 5. Post your work. Ask questions. Help others when you can. What are you here to build?
Poll
4147 members have voted
Pinned
Two Big Drops: 20% Affiliate Program 🚀 & Lifetime VIP
Y'all have been flooding our DMs, so we're doing something we honestly weren't planning on doing. And while we're at it, we're dropping something else that's going to let you make money with us. Let's get into it. 👇 ---- 1. Lifetime VIP — $5,000 💎 We were not planning on ever introducing this. Truly. It wasn't even on the roadmap. But the amount of messages we've gotten asking "what would lifetime cost?" made us actually sit down and think about it. Here's where we landed: $5,000 for lifetime VIP access. A few things we want to be upfront about: VIP started at $47/mo. It's $97/mo now. We're not raising prices anytime soon. As the community keeps growing though, VIP will have to go up. We can only scale Jake's time so much. The $5K number factors in where VIP is heading down the road, not just where it sits today. And honestly? We don't expect anyone to actually pay this. 😅 That's the truth. We're posting this because you asked, and we'd rather give you a straight answer than dodge the question. ⚠️ Before you pull the trigger ⚠️ read this: If you're even thinking about lifetime access to us, you should probably wait. The Lyceum is coming, and Lifetime VIP is included. 🎁 The Lyceum is going to be the single biggest value drop we will ever do. By a mile. If lifetime access is what you want, it's inside the Lyceum at a better deal. Hang tight. 🔥 ---- 2. The Affiliate Program is LIVE 💰 This is the one we're most fired up about. You can now get paid for bringing people into the community. We're starting affiliates at 20% commission. 🎯 That's $5.40/mo on every Premium member you refer. $19.40/mo on every VIP member you refer. For as long as they stay a member. Recurring. Every month. Forever (or until they cancel). Here's how to grab your affiliate link: 🔗 1. Open our Skool community 2. Click the Invite button (top of the page) 3. You'll see your personal affiliate link right there 4. Copy it. Share it. Watch it work. Anyone who joins through your link gets attributed to you, and you start earning the second they pay.
Pinned
🏆 Weekly Comp #2: The Artifact Sprint 🏆
💰 Week 1 winner @Ian Barriopedro took home $200 cash. 🎟️ This week the prize gets bigger. ✨ Winner gets a FREE seat in The Lyceum. ✨ https://www.skool.com/quantum-quill-lyceum-1116/12-weeks-real-projects-250k-in-prizes-lets-talk?p=e850567b 🎯 Pick your cohort: Technical, Business, or Creator. Your call. 📋 THE CHALLENGE: "The Returning Client" You just got hired again. Different client this time. Meet Marcus. 👋 📎 Download the full client brief attached to this post. 🛠️ YOUR DELIVERABLE An interactive artifact built in Claude that does what Marcus asked for. ✍️ Plus a 100 word writeup covering: - 👤 Who it's for - ⚙️ What it does - 🎨 One design choice you made and why 📐 THE RULES ✅ It has to work ✅ It has to sound like Marcus, not a bank ✅ The writeup matters ⚖️ Judging: Myself, Jake, and the mods. 🎟️ Who can enter: Premium and VIP members only. Free members, this is your sign. Upgrade and you're in the running for a Lyceum seat. 🚀 📨 How to submit: Drop a screen recording or screenshot of your artifact, the link if you've got one, and your writeup in the comments below. 📅 Deadline: Saturday, May 2nd at 12:00 PM EST 🎉 Winner announced: Monday, May 4th at 12:00 PM EST 💡 A note before you start. This isn't a finance challenge. It's a design and voice challenge. You don't need to be a CFP to win this. Read the brief. Marcus tells you exactly what he wants and how he thinks. Your job is to build something that solves his problem and sounds like him. 🆕 If you've never built an artifact in Claude before, this is a great first one. The brief is clear, the scope is reasonable, and the bar is "would Marcus actually send this to a prospect?" 🔥 @Ian Barriopedro set the standard last week. Your turn. LFG 🚀
Council of 5
I am known to take Claude outputs and put them into ChatGPT for blind-spot checks. Today I decided to create a "council of 5" skill that runs any question, problem, solution, document, etc., through 5 distinct personalities, with 3 rounds of discussion, then a consensus. 1. The professor: peer-reviewed/cited sources only 2. The teacher: logical, wonders, "is this the right question to be asking" 3. The founder: can this be done, and what is the fastest way 4. The outside: zero context, thinks outside of the box 5. The contrarian: hunts for the fatal flaw in everything. Sharing the skill here if it could help anyone.
Four hours of documentation a week I'm no longer doing
Six weeks ago I built a KB article pipeline. My team closes 15-20 tickets a week where someone fixed a real problem, documented it in the ticket, and we have no article for it. That adds up. A year of good fixes trapped in closed tickets nobody can find. A Python script hits the ServiceNow API, pulls 30 days of closed tickets, strips PII, normalizes each one into structured JSON; symptom, environment, resolution, notes. Claude drafted the first version. I've been maintaining it since. The LLM stage reads that batch alongside the current article list. For each cluster: does coverage exist, rate it 1-5, draft a new article if the gap score clears a threshold. The threshold is a number I set in a reference file and can change without touching the code. Six weeks in: 23 new articles published, 8 existing ones flagged for revision. About 4 hours of documentation avoided per week. The 60-30-10 here is about as clean as I've gotten it. Normalization, dedup, and article-list comparison are all deterministic, so those live in the script. Rubric and threshold logic live in the reference file. LLM rates coverage quality and writes articles. First version had the LLM doing normalization too. Structure drifted week to week. Moving it into the script fixed that. One thing to flag: it doesn't know when the technician notes are thin. The output quality follows the input quality. I've also re-calibrated the coverage rubric twice. "Quality" is harder to operationalize than I expected. Anyone here run gap detection against a knowledge base outside IT? Sales playbook, legal, anything with a lot of tribal knowledge. The structure should transfer but I haven't tested it.
0
0
1-30 of 880
Clief Notes
skool.com/quantum-quill-lyceum-1116
Jake Van Clief, giving you the Cliff notes on the new AI age.
Leaderboard (30-day)
Powered by